Advanced user/organization collaboration allows you to delegate and control access to repositories.
Cloudsmith supports organizational support out-of-box. As soon as you sign up as a user - or click the link in the invitation email - you have access to create or join an organization.
This allows you to share repositories and packages with colleges, but most importantly allows you to implement security and privileges across all repositories. Once a user has joined an organization - you can specify them with one of four roles:
- Owner - User can manage organization administration and settings, and have all permissions implicity
- Admin - User can manage organization settings, non-admin user roles and teams, and inherit privileges from the organization and team membership
- Member - User can see other members and visible teams, and inherit privileges from the organization and team membership
- Collaborator - User can only see other team members and only inherit privileges from the teams they belong to
Note: A user can also be made public or private. A public member is one that has visibility displayed outside their organization. Private membership is not displayed outside organization.
All users can be assigned to one or more teams.
A Team exists with one or more managers and zero or more members. Each team can be assigned privileges - for example - access to a package repository. They can be give one of three rights:
- Admin - Team members can manage privileges and API keys. Includes Read & Write privileges.
- Write - Team members can upload packages and edit existing packages. Includes Read privileges.
- Read - Team members can view and download packages.