Is anyone restricting access to specific Recipe Management (RM) objects (specifications and recipes) by a project designation and/or team composition?
We are using role-based security along with authorization object and sub-object settings within RM. Up until this point, a given role would be authorized to display and edit substance specifications for example. Now, we have a limited sub-group of people working on a super secret project and only want these people to be able to display and edit the specific substance specs created for the project.
Any ideas or tips and tricks would be welcome. Thank you for your help.
Beth
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.