Skip to main content
Access in BluBash combines two things: the workspace role (Administrator, Manager, or Member) defines what a person can do, and the teams they belong to define which conversations, contacts, channels, and Pipelines they work on.
Every member must belong to at least one team. Without a team, the person cannot access conversations, contacts, Pipelines, or tasks.

​
Roles at a glance

​
What each role can do

Only Administrators create, train, and configure AI agents. Managers and Members work on the conversations the AI agent transfers to their teams and can hand a conversation back to the AI when it makes sense.
A tag restricted to several teams can only be edited or deleted by someone who belongs to all of those teams. Global tags are managed by Administrators and Managers. See Create tags →.

​
Team role: Manager or Agent

Besides the workspace role, each person has a role inside every team they belong to: Manager or Agent. You set it in the team’s Members tab. Here, “Agent” is the person who handles conversations, not the AI agent. The team role identifies who coordinates that team and appears, for example, in the list of people when you transfer a conversation. It does not replace the workspace role: what the person can do in the platform is still defined by the Administrator, Manager, or Member role.

​
Where the AI agent fits in

Before transferring a conversation, leave an internal note with a summary of the case. Whoever receives it starts with the full context.

​
How to choose each person’s role

​
Common issues

Review roles regularly and keep the number of Administrators low.

​
Next steps

Add a member

Invite people with the right role and teams.

Edit a member's role

Promote someone or restrict their access.

Create and configure teams

Set up each team’s channels, Pipelines, and rules.

Tasks

See how task scopes change by role.