Members & sharing
Invite people, assign roles, bring in guests, and manage who belongs to a space.
A space is a shared workspace built around one memory. Two things decide who can reach it and what they can do:
- Membership - who belongs to the space, and at what role.
- Topics - how each piece of content is filed, which is also what decides who can see it.
This article covers membership: inviting people, roles, guests, and member management. How content is shared - the topic model that replaced per-item visibility settings - lives in Topics.
Sharing content
Threads, notes, canvases, and views no longer carry a visibility level of their own, and there is no space-wide "make public" switch. Where a thread, note, canvas, or view is homed - private, shared with the whole space, or filed into one or more topics - is what decides who can see it. A space becomes reachable on the public web only when at least one of its topics has public web access turned on.
All of that is covered in Topics, including the Home picker, guest invites, and public web access.
Invite members by email
Open the Members section of the space settings. If you have permission to manage members, an invite field lets you add people by email: type the person's email address, pick the role they should start with, and send the invite. You can also get there without leaving a conversation: the @ mention picker in the composer ends with an Add members row that opens the same invite flow in place.
The person then receives a pending invitation. Until they accept, they appear in a separate Pending invites section marked "Invite sent" and don't yet count as a member. While they're pending, you can still change their role or revoke the invite.
On the free plan a space has a limited number of seats. If you have reached the seat cap, the invite field is disabled and you will see a prompt to upgrade.
Roles
Every member has a role that determines what they can do across the whole space. Roles are ordered from most to least privileged:
| Role | What it can do |
|---|---|
| Owner | Full control: settings, deletion, members, topics, and all content. Exactly one per space. |
| Admin | Everything an owner can do except final ownership transfer - manages settings, members, topics, and content. |
| Editor | Creates and edits nodes, edges, threads, notes, and views. The default role for new members. |
| Viewer | Read-only - can view content they have access to, add reactions, and comment on notes, but not edit. |
| Guest | The most limited role, used for outside collaborators brought into a single topic. |
A member's role sets what they can do; the topics they've joined set what they can see. The two are independent - a viewer who belongs to more topics sees more content than an editor who belongs to fewer.
Viewer access is enforced by the server, not just hidden in the interface: a viewer genuinely cannot edit, and their allowed writes are limited to reactions and comments on notes.
To change someone's role, open the Members section of the space settings, find their row, and pick a new role from the dropdown next to their name. The owner's role can't be changed in place - to move ownership, use the transfer flow below.
Remove a member
In the members list, open a member's actions (the ellipsis menu or right-click) and choose Remove member. They immediately lose access to the space and its content. You can't remove the owner - transfer ownership first. Removing yourself is the same as leaving the space.
Transfer ownership
Ownership can be handed to another member from Space Settings → Danger Zone → Transfer ownership. Pick the new owner from the list of existing members. They become the owner with full rights, and you step down to admin - you stay in the space rather than losing access.
On a paid space, transferring ownership does not move billing. The subscription stays on your card. To hand off billing as well, cancel the subscription and let the new owner resubscribe on their own. You also can't leave a paid space directly while you own it - transfer ownership first.
Guests
A guest is an outside collaborator invited into a single topic rather than the whole space. Only owners and admins can invite guests, and each invite is scoped to a topic: from that topic's sharing surface, invite someone by email and choose their access level. A guest invite carries one of two levels - View (read and react) or Contribute (also post messages and comment). A guest can later be granted additional topics without becoming a full member.
Guests see only the topics they have been granted, plus any topics shared to the web - nothing else in the space, not even the space's unfiled misc lane.
Guests are managed from the Guests section of the Members directory in settings. From a guest's row you can review exactly what they can reach, promote them to a full member, or remove them. Promoting a guest turns them into a regular member with the role you choose; removing them ends their access.
A guest is a billable member: like anyone else on the space, a guest occupies a seat on the space's plan - a single seat, no matter how many topics they've been granted.
To learn how a topic controls its own access - including public web access for signed-out visitors - see Topics.
Mentioning someone who isn't in a conversation
When you mention a member (or an agent) who isn't already a participant in a thread, Naumu doesn't add them silently. Instead it posts a small card asking Add [name] to this conversation? with Add and Dismiss buttons. Choosing Add brings them into the thread; Dismiss leaves the conversation as it is. This keeps people from being pulled into threads by an offhand mention.
Related
- Topics - how content is filed, shared, and opened to the public.
- Spaces - creating, describing, and managing a space.
- Nodes & edges - the content your topics organize.