To expand on that a bit, which fields are editable for each permission level is
defined in the code of a superclass for each area, so not quite that flexible,
but good enough for what we are doing.
> On Aug 13, 2017, at 6:11 PM, Morris, Mark wrote:
>
> No, it’s really just something bolted on
No, it’s really just something bolted on top of a permission system on a suite
of applications that have been in continuous development for almost 20 years.
In other words, not an ideal architecture at this point, but I think impressive
that it’s holding its own!
> On Aug 13, 2017, at 6:02 PM,
Is this an ABAC implementation?
Paul
Sent from my iPhone
Please excuse iOS autocomplete
> On Aug 13, 2017, at 5:08 PM, Morris, Mark wrote:
>
> This is a topic that was discussed back in 2011, but my searches haven’t
> turned up a satisfactory solution.
>
> Some quick background info, we hav
This is a topic that was discussed back in 2011, but my searches haven’t turned
up a satisfactory solution.
Some quick background info, we have information-dense, complex pages, and there
are a variety of permission levels for internal and external users that needed
to be implemented at field-l
