For a summary of access permissions required to perform primary tasks, see Access permissions required for performing tasks.

After installing Modeler, decide on the security needs of your Models and then set up Modeler accordingly. You can control security at the database, Model and Model item level.

At the database level you can set database options in SQL Server Management Studio and database access permissions through Model Explorer.

Through the database options you can grant global read access permissions to all Models in the database. You can grant global write access permissions to all Models in the database by disabling the use of access permissions within Models. Global read and write permissions granted at the database level cannot be revoked at the Model or Model item level. Alternatively, you can grant no permissions at the database level, so that the access permissions of each Model are determined within the Model itself.

Through the database access permissions you can allow users to create (and import) Models.

At the Model level you can specify which users can open the Model (assuming that global access permissions have not been granted at the database level).

At the Model item level, write access is controlled through the Packages (assuming that global write permissions have not been granted at the database level). The owner of a Package can specify which users have write access permissions to the items scoped by the Package. Note that if a user can open a Model, that user has read access to all items in that Model.