Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Specifying privileges for an Access of Role to Object rule

Updated on July 1, 2021

To more precisely define access to instances of a class, you update the Access of Role to Object rule to grant or revoke privileges for a role and access class. Specifying privileges is optional.

You can make these updates by using Access Manager or the Access of Role to Object rule form. The production level values that you can specify are different on these two forms. For more information on Access Manager, see Access Manager landing page.

A privilege associated with an Access of Role to Object rule is granted to users who have the access role, when they work with instances of the rule's access class (or child class), on a system that has a specific production level (or lower).

  1. In the navigation panel, click RecordsSecurityAccess of Role to Object, open the rule you want to change, and click the Privileges tab.
  2. In the Privilege field, enter the name of the privilege to grant to this role. The privilege must already be defined for this access class.
    You can add more privileges by clicking the Add a row icon.
    You can remove privileges by clicking the Delete row icon, or updating the Level to 0 or blank.
  3. In the Level field, enter a When rule name or a production level. At run time, the system evaluates this value in the following ways:
    • If you enter a When rule name, the system uses the access class and class inheritance to find the Access When rule, and then evaluates the When rule to see if access is granted.
    • If you enter a production level, the system compares this level with the production level of the current system. The privilege is granted only if the privilege's production level is greater than or equal to the system's production level. Enter 0 or leave blank to provide no access. A value of 5 allows access to all systems.
  4. Click Save.
    Result: Active requestor sessions on the current node are immediately updated. Requestors on other nodes in a cluster are updated when the next system pulse occurs on their nodes.
    • Previous topic Defining permissions by using Access of Role to Object rules
    • Next topic Defining access settings for an Access of Role to Object rule

    Have a question? Get answers now.

    Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

    Did you find this content helpful?

    Want to help us improve this content?

    We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

    Close Deprecation Notice
    Contact us