Members and roles

Pulse separates workspace membership (who belongs to the organization) from team membership (who delivers on a team) and roles (what they may change).

Workspace members

Workspace admins manage people at:

Settings → Administration → Members (`/settings/users`)

From here admins:

• Invite users by email
• Deactivate or remove members
• Assign workspace-level roles when custom roles are enabled

Workspace roles

When role management is on, open:

Settings → Administration → Roles (`/settings/roles`)

Roles bundle permissions such as initiative edit, user administration, or read-only portfolio access. Assign roles to members from the Members page.

Requires roles:read to view the roles list.

Team members

Each team maintains its own roster:

Settings → Your teams → <team> → Members

Team managers can:

• Add existing workspace members to the team
• Remove members from the team (without deleting their workspace account)
• Set team-level manager flags where supported

Team membership controls which Your teams links appear and which team-scoped issues a person may edit.

Team managers vs members

Team managers accept requests, edit team settings, and configure workflow. Regular members create and edit work they have permission for but cannot change team policy.

Workspace admins override most team restrictions for administration tasks.

Application identities

Pulse may provision application principals (for example the Pulse Agent service account) with workspace membership for automation. Seat counts for humans exclude these identities — see workspace billing guidance from your admin.

Next

• Create a team
• Teams overview
• Administration
• Requests triage — managers accept intake