This page provides an overview of the various user roles within the Kinship platform, detailing their permissions and responsibilities to help you effectively manage your team. 

There are five user roles available:

• Owner
• Security Administrator
• Administrator
• Content Manager
• Team Member
  

Owner

The Owner role within the Kinship platform is designed for individuals who are responsible for overall account management. This role is not intended for everyday users but for those who oversee the account's administrative aspects. 

Owners have complete control over the account, which includes managing all content, projects, team settings, and sensitive operations like changing subscription details or shutting down the site. 

Note: To ensure continuity and avoid potential management issues, it is possible to nominate up to five owners. It s recommended to have more than one owner, as this can prevent situations where a sole owner leaves the company, leaving the site without a manager. Having multiple owners ensures that there is always someone who can manage the site.

Security Administrator

The Security Administrator is an optional role that can be enabled for enhanced security and privacy. This role is intended for specific users to handle sensitive data and manage restricted projects and collections as well as team settings.

When Security Administrators are enabled, regular Administrators can no longer change certain team settings, and they lose their access to all restricted projects and collections which are now visible only to Security Administrators. 
 

In this state, Administrators retain the rights to manage users and non-restricted projects and collection, but no longer have access to restricted items by default.  

Administrator 

An Administrator has full access to the system and can perform all operations, excluding those reserved for the Owner. This includes managing and organizing content and projects, as well as managing team settings. They also have the authority to add, remove, or change the roles of team members other than Owners.

Administrators can view, edit and manage all Projects and Team Collections. This role is ideal for individuals who need to oversee and manage most aspects of the platform, excluding sensitive operations like changing subscription details or shutting down the site.

Note: If the Security Administrator role is enabled, the Administrator's permissions will be limited. They will no longer be able to change certain team settings, or see and manage all restricted projects and collections.  

Content Manager 

A Content Manager is a user role intended for those responsible for managing and organizing content. They have control over the Library, Lists and Team Collections. They can share Collections internally and externally. 

While they have extensive permissions related to content, Content Managers do not have the authority to manage Projects, users or Team settings. This role is ideal for individuals who need to oversee and curate content without needing access to administrative or project management functions.

Team Member 

The Team Member role is intended for users who will participate in projects and use the team library or collections in their work. While these users can search, view and load content, they do not have permissions to manage or modify it.

Permissions Tables 

Note: The Administrator permissions shown in the tables below apply when Security Administrators are enabled. If Security Administrators are not enabled for your team, then Administrators will have the same permissions as the Security Administrator shown here. 

Projects 

All users have permission to view projects and can view and open models within these projects. However, restricted projects are only visible to Administrators and team members working on that project. A user becomes part of a project team when they perform a Sync with Central (SwC) with one of the project models. 
 

Note: When Security Administrators are enabled, Administrators cannot see restricted projects (unless they are part of that project team).

Content

All users can search, view and load content from the Library and non-restricted Team Collections. Content Managers have the ability to manage the Library and Team Collections, making the role ideal for users responsible for curating and managing content for the team. 

Library 

• All members have the ability to view and load content from the Library and Team Collections.

• Team Members can suggest content for the library by adding their own content. However, to maintain quality and relevance, any content added by Team Members goes into a "Pending Approval" section. This content must be reviewed and approved by a user with the appropriate permissions (such as an Administrator or Content Manager) before it becomes accessible to the rest of the team. 

Team Collections

All members have the ability to view and load content from Team Collections. However, restricted Team Collections are only visible to Administrators and users who have been given access either by sharing the collection with them or by assigning the collection to a project they are part of. (A user becomes part of a project team when they perform a Sync with Central (SwC) with a project model.) Content Managers can view and edit non-restricted Team Collections.  

Regular Team Members can create and manage Personal Collections, but cannot convert those to Team Collections.

 

Note: When Security Administrators are enabled, Administrators can no longer access restricted collections (unless it is shared with them or they are part of a project to which that restricted collection is assigned.)

 

Tips:
 

• Viewing and editing access can be granted to specific users by sharing the collection with them. 
• In the settings of a specific collection, you can enable a feature that allows all team members to add and modify its content. This will allow all user roles (including regular members) to contribute without the need to share the collection with all team members individually. This setting will only affect that specific collection. 

Personal Collections 

Personal Collections are individual to each user and, as such, each member can manage and share their own Personal Collections. 



Note: A Personal Collection (unless shared) is only accessible to the team member that created it. 

Team

Team and team member management is the domain of Administrators. They are able to invite new members, change team member roles, reset passwords, and manage team settings. 

Members

While all members can see other members in the team, only Administrators (and Security Administrators if enabled) can manage other team members' accounts.

Team Settings

Only Administrators can view and manage team settings.  

Note: When Security Administrators are enabled, regular Administrators can no longer edit team settings (except for the Thumbnail extraction setting).