This is particularly helpful if you are overseeing a team that should have varied permissions with respect to your team chatbots.

Role-based access control (RBAC) in TARS Teams helps you manage user access to the chatbots of your organization. By assigning roles, you can limit what they can see and change. Each role has a set of permissions that determine what users with that role can access and change within your organization.

To create, edit, or assign roles, you must begin with creating a team first. This guide breaks down into two parts:

  1. What is a role?

  2. Assigning Roles

What is a role?

A role defines the set of permissions granted to users assigned to that role and their access would be dependent on the role assigned. For now, TARS Teams has three built-in roles: Manager, Maker, and Viewer.

Assigning roles

Manager Role- Since you are the admin of your account, by default you will be assigned the Manager role. A Manager has the highest level of access and control. This includes administrative access, team management, and irreversible actions.

With the Manager role, you or your team member can create chatbots, edit, analyze and delete data. Make sure you're very careful while assigning this role to a team member.

Maker- A Maker has similar access to the Manager but cannot add team members to a team already created. Makers can create, edit and analyze chatbot data just like Managers.

Viewer- This is a read-only access to all the information in your account. Viewers can only view the chatbot conversation flow, configuration setup, and analyze data. They will not be able to take any actions and is perfect for team members you'd like to only show the backend of the chatbot to and not make any updates.

When Team Access is enabled, the chatbots become searchable and discoverable by the team, and team members have access permissions according to their role.

Did this answer your question?