Namespace membership

A person works in a namespace only while they are a namespace member. Membership is what makes someone eligible for the namespace’s base permission and for grants inside it. Organization membership alone gives no repository access.

Why someone is a member

A member can belong to a namespace for several reasons at once. The namespace Members list shows every one of them:

Membership source	How it happens
Added directly	An administrator added them with Add members, or they accepted an invitation into this namespace
Auto-join	The namespace adds new organization members automatically, and they joined the organization while that was on
Namespace admin	They administer this namespace
Attached Team	An organization Team attached to this namespace includes them

Someone stays a member while at least one source remains. For example, if Kai was added directly and also belongs to the attached Release Engineering Team, removing Kai’s direct membership keeps Kai in the namespace through the Team.

Organization administrators have full access to every namespace whether or not they are members. The namespace directory lists them separately with Full access so it always shows everyone who can reach the namespace.

Add members

Organization administrators and the namespace’s administrators can add existing organization members:

1. Open the namespace workspace and select Members.
2. Select Add members.
3. Search for people, select them, and confirm.

You can also start from the member page: open Namespaces and use Add to a namespace. To bring in someone who is not yet in the organization, invite them.

When granting access to someone who is not yet a namespace member, the Grant access dialog offers Add to namespace and grant, which does both in one step.

Remove a member

Open the member’s actions in the namespace Members list and choose Remove from namespace. This removes the direct and auto-join sources. If the person still belongs through an attached Team or as a namespace administrator, Ravenstash tells you which sources keep them in; remove them from the Team or remove their namespace administration to end the membership.

When someone leaves a namespace, they lose its base permission and every grant they had inside it, and they are removed from its namespace Teams.

Auto-join

Auto-join adds people who join the organization later to a namespace automatically.

• Organization policy. In Access → Policies → Membership, Auto-join new namespaces is on by default. A namespace created while it is on includes every current organization member and keeps adding people who join later.
• Namespace switch. Each namespace has its own Auto-join switch in its Members section. Changing it affects only people who join the organization afterwards; it never adds or removes existing members.

Turn auto-join off for namespaces that should stay limited to selected people, and add those people directly, through an attached Team, or by invitation.

Suspended members

A suspended member keeps their namespace memberships, but they are inactive until the member is reactivated.