Configuring the User Interface › Tab and Menu Configuration

Tab and Menu Configuration

You can configure tab and menu access to help protect the integrity of the data for your objects, prevent users from performing unauthorized tasks such as adding or deleting object information, and to support separation of duties so users only see the information appropriate for their particular job function.

Note: For assets, models, and legal documents, you provide a specific configuration by specifying the asset family (assets and models) and legal template (legal documents).

You can configure tab and menu access in the following ways:

• Hide a tab. You do not want a user to be able to see any information for legal documents. Therefore, you hide the Legal Document tab.
• Make a tab appear. You want a user to be able to see all information for legal documents. Therefore, you make the Legal Document tab appear.
• Make a tab read-only. You want a user to be able to see, but not change, the information for a model. Therefore, you make the Model tab read-only.
• Make a tab accessible. You want a user to be able to see, and edit, all information for a model. Therefore, you make the Model tab accessible.
• Hide a menu option. You do not want a user to be able to view model dependencies. Therefore, you hide the Dependencies menu option.
• Make a menu option appear. You want a user to be able to view model dependencies. Therefore, you make the Dependencies menu option appear.
• Make a menu option read-only. You do not want a user to change any notes for a model. Therefore, you make the Notes menu option read-only.
• Make a menu option accessible. You want a user to be able to change the generic configuration for a model. Therefore, you make the Model Configuration menu option accessible.

Combine tab and menu configuration and field configuration to enforce more granular levels of access.