Members and roles
Who can see and change what in a Runbear organization.
Everyone who uses the Runbear dashboard belongs to an organization. Membership determines which agents a person can open in the dashboard, and their role determines what they can change.
Roles#
| Role | Can do |
|---|---|
| Owner | Everything, including billing and transferring ownership |
| Admin | Manage agents, integrations, and organization settings |
| Member | Work with the agents they have access to in the dashboard |
Owners and Admins hold the organization-wide permissions to read and configure agents. Members work with the agents they are given access to.
Agent access applies to the dashboard only. It doesn't decide who can talk to an agent in Slack, Microsoft Teams or another channel: anyone who can reach the agent where it is deployed can use it there.
Inviting and removing people#
Member management runs through the hosted account pages. Open Settings and select Members; the link opens the organization page where you invite people, change roles, and remove access.
Removing someone from the organization revokes their access to every agent at once, including the personal Inbox Agent tied to their account.
Restricting a single agent#
Roles govern the organization. To limit who can view and edit one agent in the dashboard, open its Settings tab and, under access control, choose Only invited users can view and edit, then add the members who should have access. This doesn't change who can use the agent in its channels.
An agent's Settings tab needs edit permission on that agent. Owners and Admins have it on every agent; a member has it on the agents they were invited to this way. Anyone else sees an access-denied page on that tab.
Related#
- Organization settings — which Settings items each role sees
- Tool approvals — review which tools agents may use
- Single sign-on — authenticate through your identity provider
- Audit log — record of who changed what