Last Updated: 8/19/2026

Managing a Space

Overview

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. It opens with its own left-hand menu, with a link at the top to return to the Space.

Prerequisites

• The Admin or Owner role in the Space to change most of these settings. Contributors and Viewers can open the pages but can’t modify them. Deleting a Space is Owner-only.
• The tabs you see depend on the type of Space and your role in it. Workflows appears only when Workflows is enabled for your organization, and Storage only when git-backed Spaces are enabled for your deployment.

The tabs

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, covered below.

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.

An organization Admin or Owner does not automatically get access to every Space. Their organization role lets them see Spaces set to Public, and nothing more - a Private Space they haven’t been added to doesn’t appear for them at all. Add them on this tab like anyone else if they need access.

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.

• Space 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 change sets - 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. A new shared Space starts with it on, because Jolli creates it backed by a repository Jolli manages and those publish automatically. A Space you bind to your own repository starts with it off. The toggle is hidden on Spaces whose repository Jolli manages, where merging is already automatic and the choice would have no effect; it is also hidden while Jolli cannot read how the Space is backed, rather than showing a control that might not apply.
• 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 Git backing on a first bind and Update Git backing afterward.

Binding a Space that already has content erases that content. The repository becomes the source of truth, so Jolli clears what the Space held before pulling the repo in. That covers every document and folder, and also their edit history, their comments, and the Space’s sync cursor. It cannot be undone. Jolli stops and asks first, naming how many documents and folders will go, and the confirm button spells out what it does - read that dialog rather than clicking through it. A Space you intend to keep is best migrated elsewhere first, or bound while it is still empty.

Switching repositories

Choosing a different repository re-binds the Space and re-clones from scratch. The clone runs in the background; while it’s in progress the Space’s content is temporarily unavailable.

A switch is not confirmed the way a first bind is. The emptiness check that produces the wipe dialog applies only to a Space that isn’t git-backed yet, so switching an already-git-backed Space goes ahead as soon as you save, with no dialog. The effect is still a replacement: the Space’s documents are cleared and rebuilt from the new repository’s files. Be sure of the repository before you save.

What a switch does not do is throw away work in flight. Changes not yet pushed to the old repository keep syncing to that repository’s pull request in the background, and Jolli says so when the switch completes.

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.

Repos in this space

Jolli Memory Spaces show a Repos in this space panel where Storage would otherwise be. It lists the repositories registered to route their commit-summary pushes into this Space, and you add one here to register it.

By default any repository may push into the Space, registering itself on its first push. To close that off, turn on Restrict pushes to listed repos:

• Off (the default) - any repo can push, and a repo that pushes for the first time is added to the list automatically.
• On - only the repos already listed may push. Anything else is refused, and a repo can no longer add itself. Registering a repo from this panel is the one path that still works, because this panel is the list.

Turning it on never removes an entry, and the repos already listed keep pushing exactly as before. Changing the setting needs the Admin or Owner role for the Space.

When a push is refused, the message asks you to have a space manager or owner add the repo. That is the Space Admin role in the table above. Someone with it can register the repo from this panel, after which pushes resume.

One case to watch: a repository with no git remote cannot be identified, so it cannot be on the list. If you turn this on for the Space that Jolli Memory pushes to by default, pushes from a repo with no remote are refused too. Registering that repo is not possible while it has no remote.

Deleting a Space

Deleting a Space lives in the Danger zone at the bottom of the General tab. It’s available only to the Space Owner - the Danger zone doesn’t render for anyone else, including a Space Admin and including an organization Admin or Owner who doesn’t own this Space. If you need a Space deleted and don’t own it, ask its Owner or have ownership transferred to you first. 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.

Related

• Jolli Spaces - what a Space is and what lives in it.
• Editing & Organizing - the article editor and organizing a Space.
• Jolli Sites - publish a Space at a URL.
• Settings - organization-level users and roles.