It makes a difference where a Role has been defined.
If a Role is defined at the Portfolio level, it is restricted to that portfolio so it can't later be applied to the Data Source context. During the assignment of Role Memberships, if the Portfolio Context is specified as All, then only the Roles defined at the Data Source level will be available in the pick list.
If a Role is defined at the Portfolio level, it can be applied only within that Portfolio. During the assignment of a Role Membership to a User, if the Portfolio Context is specified as Acme Fine Dining for example, then the Roles defined within the Acme Fine Dining portfolio will be available in the pick list, as well as the roles defined at the Data Source level.
Roles Task Button
The logic is similar when accessing the Roles Library using the Roles task button. If the Data Source is selected in the Portfolio Tree, you will see only those roles applicable at the Data Source level. Any Role you define at that point will be a Data Source Role and will therefore be applicable to all Portfolios within the Data Source.
If the Acme Fine Dining portfolio is selected in the Portfolio Tree, you will see the roles applicable to Acme as well as those applicable at the Data Source level. Any new Role you define at that point will be applicable only to the Acme Fine Dining portfolio.
|