Enhance the security of your Oomnitza instance and the experience of your users by creating roles that restrict user access to the information that your users need to complete their tasks.
You can create two types of roles:
- An independent role, which is the default role. Own role is selected in the Primary UI role field.
- A dependent role. A source role is selected in the Primary UI role field. In this case, the role that you create inherits the tabbed page views of the source role.
Let's say you want to create multiple IT roles. All of the IT roles will have access to assets, desktop software, accessories, and kits. As all of the IT roles will need access to the same type of information, you want to remove sensitive information and reduce the clutter so that the IT users can complete their tasks. And, instead of configuring the tabbed page views for assets, desktop software, and so on, for each role, you decide to create a source role that acts as a template for the tabbed view pages of the target roles. Then, when you create the IT roles, you reference the source role as the primary UI role so that target roles inherit the tabbed page view of the source role.
To do this, you create the source role and you use the screen builder to configure the tabbed page views for each object such as assets, desktop software, and so on.
Figure: Mockup of screen builder for tabbed pages
For example, in the mockup, the Information page for asset records, has been reconfigured for IT roles.
Target roles inherit only the tabbed page views that were configured for the source role. This allows you to enhance security and refine access by granting read or write permissions depending on the IT role. You must grant permissions and configure the navigation for each target role.
To prevent target roles from changing the source role settings for tabbed view pages, either grant no access (screen builder is disabled) or read-only Customization permissions to the objects.
Comments
0 comments
Please sign in to leave a comment.