Spaces and repos

Scope your workspace with spaces, and switch between documentation repos.

LivingContext has two levels of scoping: spaces, which group repositories and Salesforce connections, and the active repo, which selects a single repository for repo-bound surfaces.

What a space is

A space is a named scope that groups:

• One or more documentation repositories
• One or more Salesforce connections

Workspace-wide surfaces operate on your active space:

Surface	What the space scopes
Home	The workspace agent’s view of activity and org intelligence
Inbox	Which agent proposals and generation events you triage
Coverage	Which repos and Salesforce metadata count toward documentation coverage

Use spaces to keep unrelated work separate — for example, a Sales Cloud space and a Service Cloud space, each with its own repo and Salesforce connection, so each team’s Home, Inbox, and Coverage only show what’s theirs.

An organization with no spaces yet gets one created automatically per configured docs repository — named after the repo and carrying every connected Salesforce org — so nothing needs setting up until you decide to reorganize.

The space switcher

The switcher sits at the top of the left rail. It’s a two-lane popover: highlight a space on the left to preview its repositories on the right, then pick either — choosing a space switches your scope, choosing a repository also sets the active repo. A Manage spaces entry at the bottom jumps to Settings → Spaces. Your choices persist across visits.

If nothing is set up yet, the switcher shows a single Connect a repository button instead.

Managing spaces

Manage spaces in Settings → Spaces:

1. Create or edit a space

   Each space is a card with a name, a Repositories checklist, and a Salesforce connections checklist. A space needs at least one repository — the repo list comes from Settings → Docs repositories, so configure repos there first.

2. Save

   Changes apply immediately. The active space is marked with an active pill.

3. Switch your active space

   Use the space switcher in the rail. Home, Inbox, and Coverage update to match.

Deleting a space also deletes what’s scoped to it — saved ERD views, agent secrets, and agent memories — and any agent triggers scoped to it widen to the whole organization. If you’re just removing a repository, remove it from the space instead of deleting the space.

See the settings reference for everything else in Settings.

The active repo

Some surfaces are bound to a single repository rather than a space. The repo switcher in the workspace sets your active repo, which scopes:

Surface	What you see
Docs	The rendered documentation in that repo
Changelog	The repo’s changelog page
Edits	Change requests for that repo
Commits	The tracked commit timeline for that repo
API Reference	API reference pages generated for that repo

Switching repos in the switcher changes all of these at once, so the surfaces always agree on which repo you’re looking at.

Space and active repo are independent choices: the space decides what Home, Inbox, and Coverage aggregate; the active repo decides which single repo the docs surfaces display. Most teams set both once and rarely think about them again.

Adding repositories

Repositories come from your connected git provider:

1. Connect GitHub or GitLab on the Connections page if you haven’t already (one provider is required during onboarding, unless you’re on a starter workspace).
2. In Settings, open Docs repositories and choose which repositories hold documentation.
3. Assign the repo to a space in the Spaces section.

Docs are stored as Markdown files in the repo itself, so anything you merge in LivingContext appears as commits in your git history — and anything committed directly to the repo appears in Docs.

Related pages

Settings reference

Every Settings section, including Spaces, Repos, and Commits.

Core concepts

How spaces, docs, and change requests fit together.