Export (0) Print
Expand All

Scope of permission for the Modeler role

Scope of permissions for Modeler role

A user in a Modeler role can read rules that are associated with a model, and can create, edit, delete, and execute rules. (A user in the User Administrator role can only read rules associated with a model.)

A Modeler role can be scoped at the application level or the model site level. At the application level, a user in the Modeler role has full rule permissions across all model sites in the application. At the model site level, a user in the Modeler role has full rule permissions only for the model site for which the Modeler role is defined. In role-based security, there is no inheritance relationship between model sites and model subsites.

NoteNote:

To create rules that reference multiple models across model sites, you must be a member of the Modeler role in both the source and target model sites.

For example, suppose you have created an application called MyPerformancePointApplication. Then suppose that application contains a model site called Corporate, and that Corporate has a subsite called Corporate_subsidiary_1. Then the following diagram depicts the relationships between these elements.

MyPerformancePointApplication

|--------------Corporate

|-----------Corporate_subsidiary_1

The following table provides descriptions of a possible permission structure for different modelers who use these models.

Scope level Permissions

MyPerformancePointApplication

Create, edit, delete, and execute rules in all models and model subsites of MyPerformancePointApplication. This includes Corporate and Corporate_subsidiary_1, but also includes any other models in the application

Corporate

Create, edit, delete, and execute rules for Corporate, but not for Corporate_subsidiary_1.

Corporate_subsidiary_1

Create, edit, delete, and execute rules for Corporate_subsidiary_1, but not for Corporate.

Corporate and

Corporate_subsidiary_1

Create, edit, delete, and execute rules for Corporate and for Corporate_subsidiary_1, but not for other models in the application.

See Also

Other Resources

Security for business rules

Show:
© 2014 Microsoft