Skip to end of metadata
Go to start of metadata

Model-level access control can be set for model packages and projects in Enterprise Studio. Users can share model packages and projects with other users and user groups by inviting them, and assign them edit permissions to determine which parts of the model package or project they can edit for contributing.

Sharing content

When a model package or project is shared with other users, edit permissions can be assigned to allow these users editing content of the model package or project and creating new content. If no edit permissions are assigned, the shared model package or project will be read-only.

Edit permissions can be given for models and folders on model-level in the model package or project, including the cross-model relations folder (if available). This folder allows one to explicitly include or exclude the collection of cross-model relations so that invited users can be selectively given permissions to edit cross-model relations or not. The levels in a model package or project you can give edit permissions for are illustrated in the following figure:



Which items of a model package or project a user can give edit permissions for, depends on which content this user can edit in the model package or project.

Model packages and projects can be shared in Enterprise Studio, but users can also be invited to model packages and projects via the Team Server. The user's role in the Team Server determines the possibilities in sharing model packages and projects and assigning edit permissions.

In Enterprise Studio, a user with the Designer or Lead designer role can share model packages and projects the user is contributing to. Also, this user can only change edit permissions for folders and models in the model package or project that he or she can edit. These limitations also apply when inviting users via the Team Server. An Administrator or System administrator user in the Team Server can change access permissions to any model package and project in the Team Server and for any selection of folders and models in it.

Managing access

Once a model package or project has been shared with other users and/or user groups, their access to it can be managed in the Team Server. There a user's or user group's edit permissions for a model package or project can be changed.

The user's role in the Team Server determines the possibilities of managing access. Designers and Lead designers can manage access to model packages and projects they are contributing to. They can only change edit permissions for folders and models in them that they can edit. Administrators can change access permissions to any model package and project in the Team Server, and for any selection of folders and models in it.