Skip to content
Merulan

Workspaces and membership

Workspaces and membership set the scope for people, Groups, and access requests within an organization.

Workspaces and membership set where people can act. Governance & Administration owns this scope. Access also needs the right grants.

Ownership

A Workspace belongs to one organization. A Member belongs to that organization. A Workspace membership links that Member to one Workspace. Check both links when someone cannot reach their work. Groups collect Members in a shared roster. A grant to a Group follows that roster, so adding a Member can change their access.

Lifecycle

A Workspace is created from a selected plan and reads as active. A Join Request starts pending. Approval attaches the person to the target organization. The decision, membership change, and audit intent are kept together. Denial closes the request without admitting the person. Group membership changes who receives access through that Group.

Boundaries

A Workspace membership requires the Workspace and Member to share an organization. Join Request approval admits a Member to the organization. It does not grant every Workspace permission. A Group roster needs an access policy to grant actions. The Roles and capability bundles model explains those grants and their scope.

Failures

A Workspace access problem can start with a pending Join Request. A missing membership or refused grant can also block access. A decided request cannot be approved again. An approver from another organization is refused. Read the current request and the Member's organization before changing a Role to solve an entry problem.

Recovery

For Workspace membership checks, open Members at /governance/members in the Console. Groups at /governance/groups shows each shared roster. Confirm the request's current state and the resulting Member. Match that person to the intended work before granting actions. The Join Request approval contract owns the programmatic call. Console approval uses its own team action.

For controlled Records, /governance/cui-access shows field grants and Purpose bindings. For retained Records, /governance/records-lifecycle shows retention schedules, legal holds, and progress for a selected disposal operation. These are readback tools for the Workspace. Inspect the named evidence before changing membership to resolve a refusal for one Record.

  • The access workflow takes Workspace membership through grant checks and observed access.
  • The Console guide explains how to select the Workspace before opening its administration pages.