Spaces

Create and manage spaces, control who can see them, and import or export your data.

Updated August 4, 20267 min read

Everything you do in Naumu happens inside a space. A space is a self-contained workspace built around one memory (a network of connected information), and it holds its own members, threads, notes, canvases, and settings.

This article walks through the full life of a space: creating one, describing it, controlling who can see it, backing it up, handing it off, and deleting it.

Create a space

From your home hub, type a name into the Create new space field and submit, or use the Create new space dialog. A name is the only thing required up front - you can fill in everything else later.

Once the space exists, you become its owner, with full control over its settings, members, and lifecycle.

You can also create a space by importing a backup (see Backups) - useful when you want to start from an existing copy rather than an empty memory.

Name and description

You can rename a space at any time, as long as you have at least admin rights: open Space Settings, edit the Name field, and click Save.

The description is a short, 2-3 sentence summary. It does double duty - it appears on the card shown on the public landing page, and it gives context to every AI agent working inside the space. Keeping it accurate matters: if the description is wrong, the agents work from the wrong picture.

You can manage the description in two ways:

  • Auto-refresh on - Naumu rewrites the description for you as the space evolves, after a short pause in your edits.
  • Auto-refresh off - the description stays exactly as you wrote it.

You can also click Generate (or Regenerate) to have Naumu draft a description on demand, or write your own and click Save.

Icon, color, and the rail

Give a space a recognizable identity from Space Settings, where an Icon & color control sits next to the space name. The icon and color you pick show up in the rail (the strip of space squares) and in the sidebar header.

On desktop you can drag the space squares in the rail to reorder them. The order is saved to your account, so it stays the same on every device, and the mobile space switcher follows it too.

Right-click a rail square for quick actions on that space:

  • Space settings - jump straight into its settings.
  • Leave space - remove yourself as a member.
  • Delete space - owners only.

Switch spaces from the keyboard

Press Cmd+1 through Cmd+9 (Ctrl on Windows and Linux) to jump straight to one of the first nine spaces in the rail. Hold the modifier on its own and each square shows its number, so you can see where a digit will take you before you press it.

The number belongs to the position in the rail, not to the space itself - reorder the rail and the digits follow the new order. Spaces past the ninth have no digit; click their rail square instead.

These shortcuts are rebindable like any other. If one clashes with something else you use, change it under Settings → Shortcuts - see Account settings.

Home: who can see an item

Each item you create - a thread, note, view, or canvas - has a Home that decides who can see it: kept private to you, shared with everyone in the space, or filed into one or more topics whose members can then reach it. Filing an item is both how you organize it and how you share it, so there is no separate visibility switch. For the full model of how topics gate access, see Topics.

Nodes work differently. A node carries its own visibility level: Open (visible to everyone who can reach the space, including guests), Internal (visible to members, hidden from guests), or Invite only (only owners, admins, and individually granted people). Each space sets a default node visibility for new nodes under Space Settings → Visibility, and a schema type can override it for nodes of that type.

Public web access

There is no single switch that makes a whole space public. A space becomes reachable by signed-out visitors only when at least one of its topics has Public web access turned on.

When it does, a visitor who isn't a member sees a minimal Public topics index - just the space's public topics and their contents. They never see your memory, the member list, or the schema, and they can't edit anything. If the space has no active public topic, there is no public front door at all.

Public pages are not indexed by search engines.

Public spaces can also appear in the Explore public spaces browser on your home hub, where you can search them by name.

Backups

Naumu protects a space's data two ways - automatic nightly snapshots you can roll back to, and a manual JSON export you can download and re-import. Both live under Space Settings → Backups.

Daily backups and restore checkpoints

On paid plans, turn on Daily backups to have Naumu take a full snapshot of the space every night and keep your most recent ones. Each snapshot becomes a restore checkpoint.

To roll back, open the Restore checkpoints list, pick a checkpoint, and confirm. Naumu restores the space to that moment - anything added since is removed. Before it rolls back, it saves the current state as its own checkpoint first, so a rollback is itself undoable.

Daily backups keep your recent snapshots; each is a checkpoint you can roll back to, and the state saved just before a rollback is tagged Pre-rollback.

Rolling back removes everything added after the chosen checkpoint. Your pre-rollback state is saved as a checkpoint, so you can return to it if needed.

Export and import a JSON backup

You can also take a full backup of a space as a single JSON file, then restore it later into a brand-new space.

  • Export (admins and above) - click Export Space to backup. Naumu downloads a .json file containing your space's data.
  • Import - click Import Space from backup in settings, or Import from backup on your home hub, then choose a .json backup. Naumu checks the file, then creates a new space from it. (It never overwrites an existing space.)

During import, Naumu may show warnings - for example, a property that needs converting, or an attachment that can't be copied. Review them and continue; the import still completes. Once it finishes, you can jump straight into the new space.

Import always produces a new space. Use it to clone, migrate, or recover - not to merge data into a space that already exists.

Transfer ownership

An owner can hand a space to another member under Space Settings → Danger Zone → Transfer ownership. Pick a member - you can only transfer to someone already in the space - and they become the new owner with full admin rights. You stay on as an admin.

On paid spaces, billing stays with you after a transfer. To hand off billing too, cancel the subscription and let the new owner resubscribe on their own card.

If you try to leave a space you own, ownership transfers to another member first; if there are no other members, the space is deleted. Owners of paid spaces must transfer ownership before leaving.

Usage metrics

The Usage settings tab shows how much the space is consuming for the current billing period:

  • Nodes - the entities stored in the space's memory (capped, or unlimited on higher tiers).
  • Shared interactions - AI interactions pooled across everyone in the space, with optional extra capacity on top.
  • Per-member usage - those interactions broken down by member for the period.

Owners can also top up shared capacity from here.

Delete a space

Deleting is permanent. Under Space Settings → Danger Zone, an owner or admin can choose Delete space and confirm. This removes the space and all of its content - nodes, threads, notes, canvases, and members - with no undo. On a paid space, deleting also cancels the active subscription right away, with no refund for the current period.

There is no recovery after deletion. If you might want the data later, export a backup first.

  • Topics - the channel-like groups that gate who sees what in a space.
  • Sidebar - navigating a space's pinned items, topics, and private chats.
  • Claude - connect AI clients like Claude and ChatGPT to your spaces over MCP.
Anything missing?
Tell us what would make these docs better.