Magic Collaboration Studio 2022x Refresh2 Documentation

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

As explained in the section User roles and permissions, the scopes of pre-existing (i.e., pre-defined) roles in the Magic Collaboration Studio system fall under two categories: Global and Resource-specific.

A role with a global scope allows a user to work on any protected objects in Magic Collaboration Studio; the permissions coverage is comprehensive and not limited to a specific resource. Users whose role scope is global are authorized to carry out their tasks (aligned with the permissions) anywhere within Magic Collaboration Studio. For example, a User Manager maintains and manages all user accounts on the Magic Collaboration Studio system. There is no need to assign resources for this role. 

A role with a resource-specific scope allows a user to work on a local project. The permissions of this role are graded on a resource basis. A user who reviews a project or document has a resource-specific role. A user can have more than one resource-specific role (for example, user A can be both the Resource Contributor of Project A and the Resource Manager of Project B). This supports the working concept of different roles in each project of an organization. 

Error rendering macro 'children'

Cannot invoke "com.atlassian.confluence.spaces.Space.getId()" because "space" is null

  • No labels