Dave, When implementing dynamic permission groups, you need to ensure that the field you are using not only needs to be in that field, but also in request id....did you miss that by chance?
On Mon, Jul 22, 2019 at 2:59 AM Dave Barber <[email protected]> wrote: > All, > > This is on ARS 9.1.02. > > We have a range of users making use of both Atrium and Change Management. > We have a range of CIs uploaded against a large number of compaies, and > users have always been given unrestricted access. > > A recent requirement has involved us wanting to restrict visibility of > some CIs to specific users. Multi tenancy would not be viable (as there > are hundreds of companies within our system), so I had thought that > replacing the value for "Unrestricted Access" in field 112 in Base Element > for the relevant CIs with another permissions group, and adding that > permissions group to the required users would have the desired effect. It > does not work - profiles without the new permissions group can still see > the "locked down" CIs. > > Has anyone else implemented anything along these lines? > > Regards > > Dave Barber > -- > ARSList mailing list > [email protected] > https://mailman.rrr.se/cgi/listinfo/arslist >
-- ARSList mailing list [email protected] https://mailman.rrr.se/cgi/listinfo/arslist
