Interface Core C · Industry convention Platform: Web

Member Management

Member management is the place where allowed admins invite people, see their status, change roles, or remove access.

See how it works
You might call it team directoryworkspace membersteam management

See how it works

Original worked exampleMember Management

Another example

A workspace owner resends one pending invite and changes an active member from Editor to Viewer.

Main parts

  1. 01Member identity
  2. 02Invite status
  3. 03Role
  4. 04Seat use
  5. 05Allowed actions
  6. 06Change history

Use it when

Use it when a shared workspace needs invitations, roles, member status, or paid-seat tracking.

Do not use it when

Do not let every member change roles. Protect the last owner and record sensitive changes.

Name used in code

identity + membership + invite state + role + seat + audit event

Before you ship

Before release, check the page structure, keyboard access, visible focus, contrast, and zoom. Also check loading, empty, error, success, cancel, and reduced-motion states.

Request you can copy

Outcome: Use Member Management to solve this user need without losing the current context. User context: A workspace owner resends one pending invite and changes an active member from Editor to Viewer. Recommended pattern: Member Management. Why it fits: Use it when a shared workspace needs invitations, roles, member status, or paid-seat tracking. Do not use it when: Do not let every member change roles. Protect the last owner and record sensitive changes. Product requirements: Define the default, loading, empty, error, success, and recovery states. Keep user input. Give clear feedback after every action. Accessibility and resilience: Use semantic HTML, full keyboard access, and visible focus. Make the layout work when zoomed and support reduced motion. Follow the project’s current rules. Do not add a new UI library unless the project already uses it. Acceptance criteria: The main task works with keyboard only and at 320px width. Focus and status changes are announced. Check loading, failure, retry, cancel, and reduced-motion paths. Evidence and limits (evidence boundary): No single official standard controls the whole term. Its meaning may change across teams, platforms, or frameworks. Unknowns to confirm: Product wording, data source, analytics events, supported devices and languages, and platform limits.

Check this request

Review the current use of Member Management. Definition: Member management is the place where allowed admins invite people, see their status, change roles, or remove access. Release checks: Before release, check the page structure, keyboard access, visible focus, contrast, and zoom. Also check loading, empty, error, success, cancel, and reduced-motion states. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.

C
How official is this term?

Industry convention

People often use this term at work. The listed sources may support practice or limitations. They do not define every part of the term.

No single official standard controls the whole term. Its meaning may change across teams, platforms, or frameworks.

Scope
Cross-platform workspace-member convention; GitHub documents one organization-membership model
Document status
stable
Checked on
2026-07-30

Evidence sources & scope

Authority source + Term reference · GitHub Docs · stable Managing membership in your organization Scope: GitHub organization invitations, membership states, roles, removal, and reinstatement Role here: Direct term reference Source covers: definition, semantics, interaction, implementation, usage guidance

Copy it yourself

The browser could not copy this. Select the request below and copy it yourself.