DocsAccess and roles

Access and roles

Each person gets only their access, tool by tool. An access level and a role decide it.

Two settings per person#

Access level
Member or Admin. Admins manage the workspace. See Member or admin.
Role
Which tools and actions their AI can use, whether they can use or manage agents, and which accounts they can connect.

You set both when you invite someone, and change them in People.

Roles#

Open Roles in the sidebar. Every workspace has two built-in roles. They cannot be edited or deleted.

Full access
Every connector and every action. Admins always hold it.
Read-only
Only actions that look things up. Nothing is ever changed.

Create a role#

  1. Create roleIn Roles, press Create role and give it a name and a description.
  2. ToolsFor each connector, pick No access, Read only, All tools, or Custom to tick single actions.
  3. AgentsPick None, Use or Manage. See who can use agents.
  4. AccountsChoose which tools people in this role may connect their own accounts for, and which shared accounts they get.

Only admins can create or change roles. Members can read them.

Shared accounts#

An account belongs to the person who connected it. They can share it with a role or the whole company, read only by default. People then use it without seeing its password or key. See sharing accounts.

Changes ask first#

Every action that changes something is a dry run first. Your AI shows what it would do, and only does it when confirmed. For agents, admins choose per action: ask a person first, or run on its own. See Approvals.

What admins can see#

Activity (admins only) lists every tool call: when, which action, who or which agent, and whether it worked. Filter by tool, person or connector, and Export CSV. Homla records that a call happened, not what was in it.

Remove someone#

Remove the person in People. Their access ends, and a personal API key they made stops working. Accounts they connected belong to them, so reconnect any account the team relies on under another owner first.