Groups

Groups model the units people belong to: teams, departments, offices, leadership groups, communities of practice, and structures from operating models such as Product Operating Model, SAFe, and LeSS.

You can use groups to share pages, select a session audience, and route participants through different session questions.

Every workspace also has an organization-wide group whose membership includes everyone automatically.

Create a group

Any workspace member can create a group.

Open Settings → Groups.
Select New group.
Choose a group type and name.
Optionally add a description, icon, color, access level, and parent group.
Add members now, or let people join later if the group is open.

The creator becomes the first owner. Group owners and workspace admins can update the group and manage its membership.

Choose an access level

Access controls who can see a group and how membership works:

Default — everyone in the workspace belongs automatically.
Open — everyone can see the group and choose to join or leave.
Closed — everyone can see the group; an owner or admin manages membership.
Private — only members and workspace admins can see the group.

Use Open for voluntary communities. Use Closed for visible teams with managed rosters. Use Private when the existence or membership of the group should not be visible across the workspace.

Manage owners and members

Owners can edit group settings, invite or remove members, change member roles, and archive the group. Workspace admins can manage groups across the organization.

A group must keep at least one owner. The last owner needs to transfer ownership before leaving.

Members can join an open group and leave an explicit membership themselves. Membership inherited from an organization-wide group or a parent structure is not removed with a Leave action.

Build a hierarchy

Assign a parent group to represent relationships such as:

squad under tribe
department under division
office under region

Members of a child group are included in the parent group’s combined roster and marked as joining through that child. This avoids maintaining the same membership in several places.

Do not use hierarchy only for visual organization. A parent represents a larger unit whose membership includes its descendants.

A page can belong to a group, making it available to members according to the group’s permissions.

In the session designer, groups can be used in two ways:

choose a group as the audience for a run
add a Group route to send members down different conversation paths

If someone belongs to several groups used by a route, the first matching route wins.

Archive a group

Open the group’s menu and select Archive. Archived groups become read-only and leave the active list. Owners or admins can filter for archived groups and restore them.

Archiving preserves references and history. It does not behave like permanent deletion.

Pages explains private and group-owned documents.
Sessions uses groups as audiences.
Session designer uses Group routes inside a conversation flow.
Attributes describes member properties used for segmentation rather than roster-based units.
Workspace settings covers organization membership and admin roles.