Your team members need to be added to Acoustic Content so you all can start working together. As an administrator, you can add users from Settings > User management. You can add users with their IBM ID or with their IBM email address.

As team members are added you need to assign a role to each of them. You can assign users to the following roles: Administrator, Manager, Editor, Viewer and Authenticated Visitor. You can always change the role of a user or remove them anytime after they are added to your hub.

Roles help you in managing the hub, as permissions and responsibilities are based on roles. You can save time from having to manage permissions individually. It is important for you to understand what the various responsibilities and permissions are for each role before you assign them to users.

Permissions for each role

Administrator

Administrators have a superuser access level to the hub and therefore the most responsibilities. Only the administrators have permission to set up the org and its privileges, manage hub usage, and manage user privileges in addition to working with content types, content items, and assets.

Note
There always needs to be at least one user in the administrator role. If you are added as the first user to Acoustic Content, you’re automatically assigned the role of an administrator. You can also be to the administrator role by another administrator.

Managers

Managers have permission to work with content types in addition to working with content items and assets.

Editors

Editor role permissions allow them to work only with content items and assets.

Viewers

The user with the viewer role typically works in other products that integrate with your org. The viewer role permissions allow them to select content and assets from the content selector and use them in their products. Viewers can’t access the hub directly or edit content.

Authenticated visitor

Authenticated visitors can access secured content and assets from the org through the APIs to deliver content. They cannot access the hub directly or edit content.

User responsibilities per role