Org Settings
Organization settings are accessible for organization owners from the Dashboard, by clicking on the gear icon of the organization icon. The settings are broken out into four areas.
Webhooks (for Organizations) are covered in the Additional Features section of the documentation.
Labels are explained under the Issues section of the documentation.
External Identity Management is covered in a separate section
Multi-Site Agents are covered in a separate section.
The rest of the organization-level options are described as follows:
You can add or modify the organization name, full name and description.
If there is a related website or location, you can add this, as well.
The Permissions setting, if checked, allows admins of a repository to give team access to their repository only.
Your organization's avatar can be customized, if desired.
Single-Role Teams
By default, this setting is disabled, allowing team administrators to set different permission levels for individual members within the team.
If enabled, within a given team, every member of the team has the same permission level for that team (Read, Write, or Admin). The single-role requirement applies to all teams in your organization.
Single-role teams do not require all teams to have the same permission level. For example, it would be reasonable to have one Technicians team with all of your organization's Read users, and another Controls team with all of your organization's Write users.
Single-role teams apply the same permission level to all users in a team. However, users can have different permissions on other teams. For example, a user can be a Writer on the NewYorkWriters team, and a Reader on the DetroitReaders team.
The team's role is set during team creation and applies to all members. Organization owners can modify the role for a team in the team settings panel:
When using Single-Role teams, you can also set up Team Mapping with SAML Assertions or Directory Sync to maximize access control of Copia resources from your external Identity Provider. With both of these features enabled, you can control a user's access level in Copia simply by assigning them to a group in your Identity Provider.
Single-Role Teams FAQs
What happens to permissions when single-role teams are first enabled?
When single-role teams are first enabled, all teams besides the Owners team will be set to Read access. Owners can then go through each of the teams and set the appropriate access level for each team.
What happens if I start using single-role teams, and disable it later?
In this case, users will revert to whatever more-granular permissions they had before you enabled single role teams. An illustrative example follows:
Owner creates Team A, with User 1 set to Write, and User 2 set to Read
Owner enables single-role teams:
Team A is set to Admin access.
User 1 and User 2 have admin access to all of Team A's resources.
Owner disables single-role teams
User 1 reverts to Write access for Team A, and User 2 reverts to Read access for Team A
Last updated
Was this helpful?