> 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/integrations/mcp/permissions-and-safety.md).
# Permissions and safety
You stay in control of what an assistant can see and change. Permissions are chosen when you connect, and every change goes through a preview you confirm.
## The Four Permissions
When you approve a connection, four permissions are offered. Untick the ones you do not need, you can add them later by [connecting again](/docs/integrations/mcp/connect-an-ai-assistant.md#connecting-again-or-connecting-another-project).
| Permission | What it allows |
| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Read project data and analytics** | Read experiences, survey responses, user segments, end-user adoption data, and the AI agent's setup and conversations. Ask the agent test questions. |
| **Manage Experiences** | Draft and edit every experience kind (posts, banners, modals, tours, surveys, hints, checklists, resource centers), set display rules, themes, tags, audiences and A/B tests, translate, publish, pause, and delete. Changes end users would see ask for confirmation. |
| **Teach my Jimo Agent** | Save custom answers, import documents and websites, and refresh or remove the knowledge the in-app agent answers from. |
| **Build and run my Jimo Agent** | Create and edit the agent's pages, skills, suggestions, and settings, and switch it live. Changes end users would see are previewed first. |
Display rules, themes, tags and A/B tests have no permission of their own: they come with **Manage Experiences**. For an API key, see which Custom Access box each one needs in [API Keys for Automations](/docs/integrations/mcp/api-keys-for-automations.md).
{% hint style="info" %}
**Connected before October 7, 2026?** Your assistant does not have **Build and run my Jimo Agent** yet. [Connect again](/docs/integrations/mcp/connect-an-ai-assistant.md) and approve it: it is added on top of what you already granted. **Teach my Jimo Agent** alone does not cover pages, skills, settings, or going live.
{% endhint %}
## Every Change Is Previewed First
**Reading never changes anything.** Analytics, feedback, agent test questions, and "show me the draft" are read-only and do not count against any allowance.
When you ask for a change, the assistant first receives a preview, shows it to you, and only confirms once you agree. That covers publishing, pausing, deleting, editing a live experience, changing an audience or display rules, renaming or deleting a tag, running an A/B test, saving an agent answer, editing the agent's settings or pages, activating skills, and putting the launcher live. Drafting a new experience needs no confirmation: a draft is invisible to end users until it is published.
The confirmation expires after **10 minutes** and is tied to exactly what was previewed. A retry with different values is refused, so what you approve is what happens.
If the same setting was changed in the dashboard between the preview and your confirmation, the confirmation is refused and the assistant previews again with the current values.
## Safety Rules
### Published Content
* **Live edits are previewed and versioned.** The assistant can edit a published experience step by step: copy, buttons, steps, survey logic, checklist tasks, and tour triggers. The preview shows what changes, end users see it within minutes, and the edit is refused if someone changed the experience since the assistant read it. An edit of several steps is applied whole or not at all, and removing a step from a live survey hides it.
* **Drafts are checked before they are saved.** The assistant reports warnings, such as a button that launches an experience end users cannot see yet. For tours, it turns a tooltip on a button or a link into a cursor: the element, the text and any step name you set stay, the tooltip title and Next button go, since a cursor has neither. It may also tighten the wording of a step. It always says what it changed, and can switch a step back to a tooltip if you ask.
* **Steps are pinned without selectors.** A tooltip, hotspot, cursor, or hint is pinned to an element you capture in your app with `anchor:capture`. When the assistant cannot use a browser, it can use an element from a screen the Jimo Agent has scanned instead. When a capture matches more than one element, capture something more specific or add a `data-jimo-id` to the element.
* **Themes replace builder styling.** Applying a theme writes its colors, fonts, and spacing onto every step, the way the dashboard does. On a published experience, you confirm it first.
* **Publishing is scoped to environments.** You can publish to a pre-production environment first and promote to production later. Widening the scope shows a warning in the preview.
* **Your plan applies.** Publishing and pausing follow the same plan rules as the dashboard. A publish your plan does not allow is refused at once, before any confirmation.
* **Audience changes show the real number.** The preview counts the people who would be targeted before you confirm, and warns when the audience gets wider.
{% hint style="danger" %}
**Deleting cannot be undone.** The assistant can delete a published experience or post after a preview, when your account or API key has the delete permission. Deleting also removes what it collected: survey responses, comments, and reactions. The preview offers pausing instead when that is enough, and lists anything else that pointed at the deleted item.
{% endhint %}
### The Jimo Agent
* **Skills start inactive.** Skills the assistant writes are created switched off. It tests them with real questions and activates them only once you agree.
* **Going live is its own step.** Putting the launcher live is a separate confirmation, and it is refused when your plan does not include the agent.
* **URL rules are tested before they are saved.** Every rule is checked against example URLs with the same matcher the widget uses. A rule that does not behave as stated is refused.
* **Deleting cleans up after itself.** Deleting an agent page also deletes its skills, and deleting a skill turns off the suggestions that started it, so the launcher never offers something that is gone.
### Your Data and Your Dashboard
* **Your role still applies.** An assistant signed in through the browser works with your own Jimo role on every call. Without permission to view end users, identities come back hidden.
* **Dashboard work is protected.** Editing a draft that someone also worked on in the dashboard asks for an extra confirmation, and copy with formatting the assistant cannot reproduce is refused rather than flattened. When the experience was saved in the dashboard in the last 30 minutes, the preview warns you before you confirm.
* **A/B tests need a signed-in user.** Creating and ending a test works from an assistant connected with your Jimo account, not from an API key.
* **Names, not identifiers.** Tools work with the titles you see in Jimo. If a name matches several items or is misspelled, the assistant asks rather than guessing. Audience names are matched exactly.
* **Missing analytics are never shown as zero.** If the analytics backend is unreachable, counts come back as "not measured" with a note, never as 0.
## What Stays Outside the Assistant
| Area | What the assistant cannot do | Do it here instead |
| ----------- | -------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
| Experiences | Pin a step with a CSS selector | Capture the element in your app with `anchor:capture`. Jimo writes the selector. |
| Experiences | Apply a different theme to a single step | The builder. The assistant applies a theme to the whole experience, and sets the position step by step. |
| Experiences | Style freely: colors, fonts, radius, custom CSS | The builder. The assistant applies a project theme. |
| Experiences | Run an A/B test on a changelog post | Not available for posts |
| Experiences | Upload an image | Host the image at a public URL first, then give the assistant the link |
| Experiences | Write custom JavaScript conditions or actions | The builder. The assistant keeps the ones that exist as they are. |
| Experiences | Assign an experience to a Space | The dashboard. The assistant can tag experiences. |
| Experiences | Trigger an experience for one specific user | The Jimo snippet on your site, or audience targeting with a segment |
| Jimo Agent | Write selectors or click in your product | It describes screens and writes URL rules instead |
| Jimo Agent | Build a skill out of steps that point at elements | The skill builder in the dashboard |
| Jimo Agent | Connect Intercom, Crisp, or Zendesk | The dashboard. A revoked Zendesk sign-in counts as not connected. |
| Jimo Agent | Change the agent's name, avatar, or greeting | [Chat](/docs/experiences/agent/chat.md) in the dashboard |
| Jimo Agent | Add buttons on a custom answer | [Custom Answers](/docs/experiences/agent/knowledge/custom-answers.md) in the dashboard |
| Jimo Agent | Target the launcher with an on-the-fly segment | A saved segment |
| Access | Work across projects | One connection per project: connect again for another one |
| Access | Read other systems | Your assistant reads Drive or Notion with its own tools and passes the text. Jimo never holds those credentials. |
| Access | Show who asked a question without permission to view end users | The message text is returned either way |
## Next Steps
* [Tools Reference](/docs/integrations/mcp/tools-reference.md): every tool, and which ones ask for confirmation.
* [Managing Access, Usage & Limits](/docs/integrations/mcp/managing-access-usage-and-limits.md): revoke a client or change its permissions at any time.
