Skip to Content
Jolli SpacesManaging a Space

Last Updated: 7/24/2026


Managing a Space

Every Space has its own settings, separate from your organization’s Settings. Space Settings is where you control who can work in a single Space, how automation behaves for it, where its content is stored, and whether the Space exists at all.

Space Settings opens with its own left-hand menu, with a link at the top to return to the Space. The tabs you see depend on the type of Space and your role in it.

You need the Admin or Owner role in a Space to change most of these settings. Contributors and Viewers can open the pages but can’t modify them.

The tabs

TabWhat it covers
GeneralName, description, visibility, and the danger zone (delete).
MembersWho belongs to the Space and at what role, plus ownership transfer.
AutomationConnected Sources and the auto-apply / auto-update toggles.
StorageBinds the Space to a git repository for git-backed publishing.

A Workflows tab also appears if Workflows is enabled for your organization.

Not every Space exposes every tab:

  • Personal Spaces are private to you. They have no Members tab and no Storage tab, and their name, description, and visibility are read-only.
  • Jolli Memory Spaces (see Jolli Memory) have no Storage tab and no Automation tab (their content arrives through repository pushes rather than Source polling). In place of Storage they show a Repos in this space panel.

Members

The Members tab lists everyone who belongs to the Space, each with a role badge and the date they were added. Adding, removing, and role changes require the Owner or Admin role.

Space roles

Space roles are separate from the organization-level roles (Owner / Admin / Member) described in Settings. They apply only within a single Space. The two share the name Admin, but a Space Admin governs just that one Space, while an organization Admin manages the whole organization.

RoleWhat it can do
OwnerFull access within the Space. Exactly one per Space. Manages members and can transfer ownership.
AdminManage content and members. Can assign the Contributor and Viewer roles.
ContributorCreate and edit content.
ViewerRead-only access.

Organization Admins and Owners already have full access to every Space, so they can’t be added as explicit Space members.

Adding members

Click Add member. What you see depends on your permissions:

  • If you can view the organization’s user directory, you get a searchable list and can select several people at once.
  • Otherwise, you look people up one at a time by their exact email address.

Pick a role for the people you’re adding. An Admin can grant Contributor or Viewer; an Owner can also grant Admin. The Owner role is never assigned this way - it changes hands only through ownership transfer.

Changing a member’s role

Each row has an inline role dropdown. You can change any member whose current role is one you’re allowed to assign. You can’t change your own role, and you can’t change the Owner’s role from here.

Removing a member

Use the Remove button on the member’s row. The Owner can’t be removed, and you can’t remove yourself.

Transfer ownership

Only the current Space Owner can transfer ownership, and only when the Space has at least one other member. This is an invitation-based flow - ownership doesn’t change until the other person accepts.

  1. Click Transfer ownership at the bottom of the Members tab.
  2. Pick an existing member to receive the invitation and confirm. They become the new Owner and you’re demoted once they accept.
  3. Jolli emails the invitee an acceptance link.

A Space can have only one pending ownership invitation at a time; the button is disabled (with an explanation) while one is outstanding. The pending invitation shows who it was sent to and when it expires, with Resend and Cancel actions. Removing the invited member cancels the invitation automatically.

General

The General tab holds the Space’s basic identity and access settings.

  • Name and Description - edit each inline with the pencil icon.
  • Visibility - Private or Public.
  • Default Member Role - shown only when visibility is Public.

Private vs. Public

  • Private - only the people you’ve added on the Members tab can access the Space.
  • Public - every member of your organization gets access automatically, at the Default Member Role you choose.

For a Public Space, the Default Member Role can be Contributor or Viewer (Contributor by default). It applies to organization members who reach the Space through its public visibility; anyone you’ve added explicitly keeps the role you assigned them.

Click Save access settings after changing visibility or the default role.

Automation

The Automation tab has two parts: the Sources connected to the Space (add or remove them here - see Jolli Spaces), and the automation toggles that govern how proposed changes and Source updates are handled.

  • Auto-apply changesets - when on, routine AI-suggested Changesets apply without manual review. On a git-backed Space this becomes auto-merge pull requests (which requires the GitHub App to have merge access), since git-backed Spaces publish through pull requests rather than Changesets. Off by default for most Spaces.
  • Auto-update from sources - when on, connected Sources are watched for changes. On a git-backed Space this reads as creating pull requests when Sources update.

When Auto-update from sources is on, choose how updates arrive:

  • Listen for GitHub events - near-real-time, driven by webhooks.
  • Check on a schedule - polls on an interval you set (in days), at a time of day, using the timezone from your profile.

See The Jolli Agent for how these toggles fit into drift detection, Changesets, and review.

Storage

The Storage tab binds a Space to a GitHub repository so its content lives in git. This is what enables git-backed publishing - the repository becomes the source of truth, and content changes flow through it. Storage appears only on shared (non-Personal, non-Jolli Memory) Spaces, and only when git-backed Spaces are enabled for your deployment.

To bind a repository:

  1. Click Connect GitHub repo and complete the GitHub App install/authorization if you haven’t already.
  2. Pick a Source - the repositories you can use are grouped by GitHub account. A repository already bound to another Space is shown as in use and can’t be selected.
  3. Set the Root path (the folder within the repo that holds your docs) and the Include / Exclude file globs. Include defaults to Markdown and JSON files (**/*.md, **/*.mdx, **/*.json). Jolli tracks the repository’s default branch.
  4. Save. The button reads Enable on a first bind and Update afterward.

Switching repositories

Choosing a different repository re-binds the Space and re-clones from scratch. If the Space already contains content, Jolli asks you to confirm before wiping it, showing exactly how many documents and folders will be removed. The clone runs in the background; while it’s in progress the Space’s content is temporarily unavailable.

Storage also surfaces health banners when something needs your attention - for example, if the bound repository’s access was revoked, if the local mirror needs to be reconnected, or if GitHub blocked the last publish because a file contained a secret.

Deleting a Space

Deleting a Space lives in the Danger zone at the bottom of the General tab. It’s available only to Space Owners (and organization Admins/Owners). Deletion is permanent and can’t be undone.

You can’t delete:

  • Your last remaining Space.
  • A Personal Space.
  • Your organization’s default Jolli Memory Space.

Deletion is a two-step, guarded flow:

  1. Choose what happens to the content.
    • Move to another space - migrate this Space’s Articles into a compatible Space you pick, then remove this one. (A git-backed Space can only move into another git-backed Space, and a regular Space into another regular Space.) If there’s no compatible target, this option is unavailable.
    • Delete all content - remove the Space and everything in it.
  2. Confirm by typing the Space’s name. The confirm button stays disabled until the name matches exactly.

Deleting a git-backed Space carries an extra warning, since its content is tied to a repository.

Next steps