Last Updated: 9/2/2026

Settings

Overview

Workspace and account settings live under the Settings menu. This page covers the areas that matter day-to-day: your profile and preferences, the people in the organization, the roles that govern what they can do, the apps you have connected to your account, and - for developers - API keys and the MCP surface.

Prerequisites

Profile, Preferences, Connected apps and personal API keys need no special role.
Workspace and Users need Owner or Admin. Changing someone’s role is Owner-only, as is resetting the Getting Started guide.
Custom roles need a paid organization.

Profile

Personal account settings at Settings → Profile.

Name - edit freely. Shown in the Users list.
Email - read-only. Contact support to change it; the change affects sign-in and outstanding invites.
Password - set or change it (if you sign in with a password rather than OAuth).
Timezone - used where the app schedules things for you, such as auto-publish times.

Sessions

A list of browsers and devices currently signed into your account. Each row shows device, approximate location, and last-active time.

Logout this device - ends a specific session.
Logout other devices - ends every session except the one you’re using.
Logout from all devices - ends every session, including the one you’re using. A confirmation dialog appears first.

Sessions also expire when your Remember Me token does (30 days), or when you reset your password - the reset ends your other sessions as a security precaution.

Getting Started guide

Owners can Reset Getting Started Guide here. It brings back the Getting Started conversation so you can walk through setup again; open the Jolli Agent afterward to see it.

Preferences

App preferences at Settings → Preferences, grouped into four sections.

Appearance

Theme - Light or Dark for the whole web app. Sites you publish have their own theme controls, independent of this.
Language - your preferred language for the interface.

Interface

Sidebar default state - whether the sidebar starts Expanded or Collapsed.
Chat panel width - the default width of the chat panel, from 300 to 800 pixels.

Articles

Default draft filter - which drafts show by default: All, My New Drafts, or Shared With Me.
Show AI tool details - show detailed information about AI tool usage in article drafts.

Agent

How the Jolli Agent starts a conversation, each overridable per-conversation:

Default conversation mode - Plan, Exec, or Auto. See The Jolli Agent.
Allow auto mode - makes Auto selectable in the Jolli Agent; Auto auto-approves non-destructive agent actions.
Show extended thinking - show the AI’s thinking blocks in Agent conversations.

Connected apps

Settings → Connected apps lists the agents and applications you have authorized to reach a workspace on your behalf - the ones that connected by signing in through the browser rather than with an API key. Everyone sees this page; these are your own credentials, not the organization’s, so there is no role requirement and no admin equivalent.

Each row shows the Application, the Workspace it was granted, its Access, when it was Connected, and when it was Last used. Access is spelled out in plain terms. Read it carefully, because it covers more than reading:

“Read content in this workspace, and start or cancel Workflow runs that can add or change content in it.”
“Save new memories into this workspace”, where that was granted.

An agent listed here can therefore change what is in the workspace, not just look at it: starting a Workflow run is how content gets added or rewritten. Browser approval can grant both lines at once, so treat this page as the record of what each application is actually able to do.

The consent screen you saw when you first authorized the application words the same permission slightly differently, because it is describing a workspace you are about to pick rather than one already chosen: “Read content in the workspace you choose below, and start or cancel Workflow runs that can add or change content there.”

Disconnect on the row is how you cut an agent off. Jolli confirms first, then the application loses access on its very next request; reconnecting means authorizing it again from the application itself. This is the place to come when an agent is retired, a laptop is lost, or a tool has more access than you meant to give it. Grants and API keys are two separate ways in: deleting one does not touch the other.

Workspace (Owner, Admin roles)

Settings → Workspace is where you rename your workspace - the name shown to everyone in the organization. Only Owners and Admins see this page.

Workspace name - edit it and click Save (the button reads Rename until you change the value). Up to 255 characters.

This sets the organization’s display name; the unique slug it was created with doesn’t change.

Users (Owner, Admin roles)

The Users page is at Settings → Users.

Inviting your team

The Users page leads with an Invite your team card offering two paths - Invite a colleague (a single person) and Import a CSV (bulk). Both open the same Invite your team dialog, which has an Invite someone tab and an Import CSV tab. (For the organization Owner, a dismissible Invite your team banner also appears atop the default shared space.)

The first-run Set up Jolli for your team page carries its own Invite your team card, which opens the same dialog. The cards on that page are shown only to someone who can invite people - see the permission matrix below. Anyone else lands straight on the install commands, with no cards above them and nothing to collapse.

On the Invite someone tab, enter an email, pick a role (default Member), and send. The invitee gets an email from Jolli; if they already have a Jolli account the link adds them to this organization, otherwise it takes them through signup first. Invites are per-email - if someone changes their address, they need a fresh invite.

An invitation link is good for 7 days. After that it stops working and the row shows as expired on the Pending tab; use Resend to send a fresh one. To withdraw an invitation instead, use Cancel Invitation on the row - Jolli asks you to confirm the address, then the invite stops working and the row leaves the list. Cancel and re-invite is the way to correct a mistyped address or change someone’s role before they accept.

The Import CSV tab onboards a whole team at once. Each valid row becomes a standard invitation, identical to inviting one person at a time.

The file needs an email column, plus optional name and role columns:


email,name,role
jane@acme.com,Jane Doe,admin
sam@acme.com,Sam Lee,

Up to 100 rows per file. Larger files are rejected - split them or send more than one.
Rows with a blank role use the default role you pick in the dialog (Member unless you change it).
A preview flags each row before you send: Ready, invalid email, unknown role, or duplicate. Only Ready rows are invited.
After sending, each row reports its outcome - invited, already a member, rate-limited, or failed.

The three tabs

The Users list is split into Active, Pending and Archived.

Active - everyone currently in the organization.
Pending - invitations sent and not yet accepted, with when they were invited, by whom, and when they expire.
Archived - people who have been removed, showing Removed At, Removed By and Reason. This is where to look when someone’s account has stopped working and you need to know who removed them and when.

Managing

Each row in the Users list has a three-dot menu:

Edit - opens a dialog where you can rename the user, and where an Owner can also change their role to any built-in or custom role. Changing a role needs role-management permission, which Admins do not have by default, so an Admin sees the dialog but can only rename.
Deactivate / Activate - Deactivate revokes their tokens immediately; their data and assignments stay intact. Activate restores access.
Delete - permanent. Non-personal Spaces owned by the user transfer to you (the admin performing the deletion); personal Spaces are soft-deleted. Articles and Changesets keep their original author reference (which now points to an archived user); they are not reassigned.

Roles

Every user has a role. Roles determine what they can see and do - which Articles they can edit, whether they can manage Sources, whether they can invite teammates, and so on.

Jolli ships with three built-in roles. Paid organizations can also create custom roles.

Built-in roles

Owner - full access. Exactly one per organization. Can promote, demote, transfer ownership, or delete the organization.
Admin - broad day-to-day management. Can manage users, Sources, Sites, and content. Can’t transfer ownership or delete the organization. Roles are Owner-only by default, so an Admin does not see the Roles page at all and can’t change anyone’s role.
Member - the everyday contributor. Can view and edit Articles in the Spaces they have access to. They cannot manage users, roles, integrations, or sites by default. Use a custom role if you need a more restricted contributor.

The permission matrix

Permissions break into categories, each with a View and an Edit level.

Category	View	Edit
Articles	Read Articles	Create, edit, delete; comment moderation
Spaces	See Spaces and structure	Create, rename, delete Spaces
Integrations	See connected Sources	Connect, configure, disconnect
Sites	See published Sites	Create, customize, publish
Users	See organization users	Invite, deactivate, delete
Roles	See roles	Create, edit, delete custom roles
Jolli Memory	See API keys and Jolli Memory configuration	Create / disable / delete API keys, configure push targets

The Jolli Memory category carries a third permission that is neither View nor Edit: View Team Memory Activity, which governs the Team Dashboard group in The Web Dashboard - other members’ sessions, spend and commits. It is separate from View because seeing the organization’s API keys and seeing colleagues’ work are different questions. Owner and Admin have it. Member does not. Since built-in roles cannot be edited, the way to give it to someone is a custom role that includes it.

An additional Workflows category appears if Workflows is enabled for your organization. It governs the organization-wide workflow run defaults at Settings → Workflow Defaults: View sees them, Edit changes them and any per-workflow override. Running, pausing, and cancelling a Workflow is controlled separately, by your role in the Space the Workflow targets - see Workflows.

Some permissions have cross-category dependencies - for example, Roles (Edit) requires Users (Edit) - and enabling any Edit level automatically includes its View.

Custom roles

To create one:

Settings → Roles → Clone next to whichever built-in role is closest.
Rename, toggle permissions, save.
Assign from the Users page or the invite dialog.

Editing a custom role takes effect immediately for assigned users (they may need to sign out and back in to pick up new permissions).

Built-in roles can’t be edited or deleted.

Ownership transfer

Always exactly one Owner on an account. To change an owner on an account, contact support@jolli.ai.

Developer

API keys

API keys let the Jolli CLI and external tools act on your behalf. Keys are scoped to what their creator can access.

There are two places to manage them, and which one you want depends on whose keys they are:

Settings → Jolli Memory, under Personal, holds your own keys. Anyone can use this page; no special permission is needed. You can hold up to 10 keys at a time, and creating an eleventh is refused until you delete one.
Settings → Jolli Memory Manager, under Account, lists the keys across the organization. This one needs Jolli Memory permission, and it is where an admin revokes a key belonging to someone else.

On either page you can create a key, disable it, or delete it. Disabling is reversible; deleting is not. A key stops working immediately if the person who created it is deactivated, and starts working again if they are reactivated.

What a key is allowed to do is set organization-wide, not per key. There is no per-key scope list yet, so when a capability is enabled for the organization, every key already in existence gains it, with nothing reissued and no restart needed. That is how the session-statistics upload behaves: it is enabled by default, so any key your organization holds can upload session statistics, including keys minted for CI a long time ago. If you would rather it could not, an admin can turn the session sync off for the organization, and individual machines can turn it off for themselves. See Troubleshooting and FAQ.

Connect an external AI client (MCP)

Jolli exposes an MCP (Model Context Protocol) surface so an external AI client can read your documentation using one of your organization’s API keys. Most of it reads; a few tools write or act, and those are called out where they appear. It’s on by default; an organization admin can turn it off, which makes the whole surface unavailable.

The tools an authorized client can call:

Tool	What it does
`list_remote_spaces`	List the Spaces the key’s owner can access.
`search_remote_articles`	Search Article titles and body content across accessible Spaces. Each result carries a link you can open, a plain-text snippet of the match, and a relevance score.
`get_remote_article_content`	Fetch one published Article’s content by its JRN.

Access is scoped to what the key’s creator can view. Personal Spaces and deleted Articles are never returned; only published content is served. These three documentation tools also leave Jolli Memory Spaces out.
Create an API key under Settings → Jolli Memory. While MCP is enabled, every API key can reach this surface automatically - there’s no separate scope to toggle.
Point your client at your organization’s Jolli API base (the /api/mcp endpoints) and authenticate with the API key.

Let a hosted agent read your memory

Alongside the documentation tools above, an authorized client can read your organization’s Jolli Memory:

Tool	What it does
`search_remote_memory`	Search your organization’s memory across every memory Space the key’s creator can access.
`get_remote_memory_content`	Fetch one memory document’s content by its JRN.
`create_remote_memory`	Create a new memory - a decision, a summary, or a note - in a memory Space.

These are the mirror image of the documentation tools: they reach memory Spaces and nothing else, while the documentation tools continue to exclude memory.

create_remote_memory is the only one that writes. It targets your organization’s default memory Space unless the caller names another, and it fails rather than creating a Space if there is no default and none was named. Documentation and personal Spaces are refused. What decides whether a write is allowed is the per-space contribution permission of whoever created the key, so an agent can never write somewhere its key’s creator could not.

An agent that cannot run a local process connects over the web, at https://jolli.ai/mcp, as a Streamable HTTP MCP server. Turning MCP off for the organization turns this off with it.

Hosted assistant endpoint on this page shows that address with a button to copy it, so you do not have to transcribe it. It is the only address the endpoint accepts: a connection arriving on a workspace subdomain or a custom domain is turned away, with a message naming this one instead.

Agents connect either by signing in through the browser, where the person approving picks which organization the agent reaches, or with an API key using Authorization: Bearer sk-jol-..., where the key itself determines the workspace. Either way there is no workspace name in the URL.

The six tools above are the documentation and memory ones. The hosted endpoint carries more: reads over a connected repository, and discovery, status and run control for Workflows. Use Your Memory from Any AI Agent (MCP) lists all twenty-three and covers setup end to end. If you are deciding what an agent will be able to do once you authorize it, read that list rather than this one.

This is all distinct from the Jolli Memory MCP server your local coding agent runs - that one is a process on your own machine reading the memories stored with your repo, while this surface is hosted by Jolli.

Managing a Space - per-Space members and roles, distinct from the organization roles above.
The Jolli Agent - what the AI mode defaults control.
Jolli Memory - the API keys and MCP settings above power Jolli Memory.