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.

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	Create, play or pause, publish, delete, or change changelog posts, banners, and modals. Publishing and deleting 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.

Connected before October 7, 2026? Your assistant does not have Build and run my Jimo Agent yet. Connect again 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.

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, saving an agent answer, changing an audience, editing the agent's settings or pages, activating skills, and putting the launcher live.

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

• Copy is edited in the dashboard. The assistant rewrites the copy of drafts only. Once something is published, it can pause and resume it, change its audience and schedule, re-scope its environments, or translate it.

• 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.

• 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.

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.

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. The permissions of your Jimo account apply to 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.

• 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	Draft tours, hints, surveys, checklists, or resource centers	The dashboard builders. The assistant can still read, pause, resume, translate, and re-target them once published.
Experiences	Edit the copy of a published experience	The dashboard
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 in the dashboard
Jimo Agent	Add buttons on a custom answer	Custom Answers 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: every tool, and which ones ask for confirmation.

• Managing Access, Usage & Limits: revoke a client or change its permissions at any time.