Overview of database access permissions
At the database level you can set:
• Database access permissions through Model Explorer
• Database access permissions through Stored Procedures in SQL Server Management Studio
 | Database Administrators and users that have Owner access permissions to a database have owner access rights to all Models and Packages in that repository. These access permissions cannot be revoked at the Model or Model item level. |
Database access permissions set through Model Explorer
Only Repository Administrators can set Database access permissions in Model Explorer. You can set up the read, write and owner access permissions for a database:
• Read Access Permissions
This access permission does not allow a user to do anything; however, if you grant a user Read access to a Database and then create, clone (using default access permissions) or import a Model in that Repository, the new Model will inherit the Read access permissions that are set for the Repository.
• Write Access Permissions
Allows a user to:
◦ Create Models in the database.
◦ Import Models to the database.
◦ Add profiles to models in the database.
| | • Having Write access permissions to a database does not grant any Write access permissions to the Models and Model items in that repository. • The first person that uses a Reverser to reverse engineer code to a Model must have Write access permissions to the database, because the Reverser adds its associated profile to the Model. |
• Public Read
All users of the database have read access permissions to each Model in the database. This read access cannot be revoked at the Model or Model item level.
• Owner Access Permissions
In addition to the access granted through Write access permissions, Owner access permissions gives a user Owner access permissions to all Models and Packages in the database.