Access Control
You can set up permissions to control access to items stored in a server database accessed via a Model Manager server. You can define these at various levels in The Databases Tree — from coarse-grained permissions set on Repositories to fine-grained permissions set on individual Models and Files.
When you authenticate with a Model Manager server, the server matches the provided username with a user stored in the database. Your user, as well as any groups that you are a member of, are checked whenever you perform a database action that requires authorization. The one exception is if you authenticate using an administrator account, in which case authorization checks automatically pass.
In this section, you will find answers to:
•
Who can set permissions? See Owners.
•
How are permissions set? See Granting Permissions
•
What permissions can be set for database objects? See Permission Catalog.
•
How do permissions combine to control access to models and files? See Permission Levels.
•
How can the same permission assignments be reused between different database objects? See Reusing Permission Assignments Using Permission Templates.
All access control functionality is either hidden or disabled for a local database in the Model Manager workspace.