Overview of model access permissions
At the Model level you can prevent users from opening a Model (assuming access permissions have not been granted at the database level). A user requires read access permissions to a Model to see and open the model:
• See the Model in Model Explorer.
• Open the Model.
If a user can open a Model, that user has read access permissions to all items in that Model.
 | Database Administrators and users that have Owner Access Permissions to a database have owner access rights to all Models and Packages in that database. These access permissions cannot be revoked at the Model or Model item level. |
The Model access permissions, Public Read and Public Write properties affect read access as follows:
• Read Access Permission—When granted to a user, that user can open the Model.
• Write Access Permission—When granted to a user, that user can open the Model.
• Owner Access Permission—When granted to a user, that user can open the Model.
• Public Read—When selected, all users of the database can open the Model.
• Public Write—When selected, all users of the database can open the Model.
The Model is a special Package. When you set Model access permissions and options to control read access to a Model, you are also setting options that determine which users can change items scoped by the Model. For more information about what the preceding access permissions mean within the Model, click here to open the Overview of Model Item Access Permissions topic.
| | • When you create, clone (using default access permissions) or import a Model, it inherits Read, Write and Owner access permissions from the Read, Write and Owner access permissions set for its Database, assuming some have been set. • You cannot change the access permissions of a Model that is checked in to a CM tool. |