> For the complete documentation index, see [llms.txt](https://help.usejimo.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.usejimo.com/docs/getting-started/your-workspace/roles-and-permissions.md).

# Roles and permissions

Three questions decide who you invite and with which role: who builds, who publishes, who installs. Settle them at Step 1, because the symptom of a wrong role shows up at Step 5, when you cannot publish.

***

## Who does what

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2F2RXMTeRFF5jOnqO3xX6c%2Fn09-who-does-what.png?alt=media&#x26;token=c6af49d9-b94a-4d9c-bef8-6e7d8d0f43d8" alt="Permissions and the tasks they unlock"><figcaption></figcaption></figure>

#### Build and preview experiences

Needs a role with edit rights on experiences. Typical person: product, CS, marketing.

#### Publish and unpublish

Needs a role with the publish permission. Not every editing role has it. Typical person: the owner of the trial, a product lead.

#### Install the snippet, set up identify

Needs access to your application's code or tag manager. In Jimo, a role that can open Settings > Installation to read the snippet and the CSP allow-list. Typical person: a developer.

#### Connect an AI assistant

Needs the Integrations access, the same permission as the Integrations settings page. Without it, the connection is refused at the approval step. Once connected, the assistant works with that person's own role: it cannot publish if they cannot. Typical person: whoever builds from Claude or Cursor. See [Set up with an AI assistant](/docs/getting-started/set-up-with-an-ai-assistant.md).

#### Invite members, change roles, see billing

Needs Admin. Typical person: the workspace owner.

Roles and their permissions live in [Settings > Team](/docs/settings/team-management.md) (`/settings/team`), **Roles** tab. Predefined roles are Admin, Editor and Viewer, and you can create custom ones with the exact permissions you need.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FRso5zjGSCrK4nSDNiOnH%2Fsettings-team-roles.png?alt=media&#x26;token=d436f822-da30-4ca5-982c-d90e11e046d5" alt="Role settings with the permissions of one role"><figcaption></figcaption></figure>

## Invite your developer

{% tabs %}
{% tab title="Invite with an account" %}
In Settings > Team, **Members** tab, enter their email and pick a role that can open Settings > Installation.
{% endtab %}

{% tab title="Share instructions without an account" %}
Skip the invitation: on the Get Started page, step 4, **Share Instructions to Engineer** sends them everything they need without an account.
{% endtab %}
{% endtabs %}

An account is better: they can use the [Troubleshoot](/docs/settings/troubleshooting.md) tool on your app at Step 5.

## Auto-join

Anyone with an email on your company domain can join the workspace as a Viewer when Auto-Join is on. Convenient for visibility, and the reason a colleague may "already have an account" with no rights: ask an Admin to change their role.

## Team members

There is no limit on the number of team members: invite as many people as you need, on every plan. The list of members is in [Settings > Team](/docs/settings/team-management.md), **Members** tab.

## Related

* [Team Management](/docs/settings/team-management.md)
* [Publish your first experience](/docs/getting-started/publish-your-first-experience.md)
* [Permissions and safety](/docs/integrations/mcp/permissions-and-safety.md), for what an assistant can change