Properly managing permissions is the first and most critical step to successfully implementing Components Center in your organization. This guide explains the high-level strategy for setting up permissions and directs you to detailed instructions for implementation.
Choosing Your Permission Strategy
Before you begin assigning permissions, it's important to decide on a management strategy. There are two primary approaches you can take:
- Add Permissions to Broad, Existing Roles (Recommended):
Your organization comes with default roles like "Project Administrator" and "Team Member." The recommended and most manageable approach is to add Components Center permissions directly to these wider, multi-purpose roles. For example, adding the "Read" permission to the "Team Member" role instantly grants all team members the ability to find and use components.- Benefit: This keeps your list of roles clean, simple, and much easier to manage long-term.
- Create New, Service-Specific Roles:
Alternatively, you can create new roles that are exclusively for Components Center, such as "Component Uploader" or "Component Approver."- Benefit: This offers very granular control over who can do what.
- Drawback: This can lead to "role bloat," where managing a long list of very specific roles becomes cumbersome for administrators.
For most organizations, the first approach provides the right balance of control and simplicity.
How-To Guides and References
Once you have decided on your strategy, you can use our detailed documentation to perform the setup and understand the specifics of each permission.
- Step-by-step instructions on how to create, configure, and assign roles: Permissions
- A detailed definition of what each specific permission allows a user to do: Configuring Organizational Roles and Permissions
What Happens if Permissions are Missing?
It is important to understand that if a user has not been assigned a role with at least "Read" permission for Components Center, the service will be visible to them but they will be unable to access your organization's component libraries.
If a user reports that they cannot access Components Center, the first step is always to check that they have been assigned a role with the necessary permissions (minimum: Read)