Members

The Members page is where org admins and super admins manage who belongs to the organization, which role they hold, and whether outstanding invitations should be revoked. Member state feeds every other surface — projects, teams, CLI keys, and audit attribution all resolve to org membership.

Inviting members

1. Send an invitation

   Click Invite member, enter the person's work email, and choose a role:

   Role	When to assign
   Member	Default for engineers and ICs who work in projects
   Admin	Delegated operators who manage members, models, budgets, integrations
   Super admin	Org owner and backup owners — smallest possible group

   The invitee receives an email with a join link bound to your organization slug.

2. Track pending invites

   Pending invitations appear in the members list with Pending status until accepted or expired. Resend from the row menu if someone missed the email.

3. Assign teams and projects

   After acceptance, add the member to teams and projects as needed. If Require project assignment is enabled in Settings, members cannot use agents until they belong to at least one project.

4. Revoke if needed

   Revoke an outstanding invitation at any time from the invitation row. The action is recorded in the audit log with actor and invitee email.

Roles and capabilities

Organization roles map to dashboard capabilities. Exact grants may be narrowed by your contract or delegated admin policy.

Role comparison matrix

*Unless granted team.usage.view or similar.

†When Admins can invite is enabled in Settings.

‡When org.audit.view is delegated.

Managing active members

1. Change role

   Open a member row → Change role. Promotions to admin should follow your internal access review policy; demotions take effect immediately for dashboard modules.

2. Suspend or remove

   Remove member revokes org access immediately — all project and team memberships for that user are cleared. Reassign open tasks and rotate CI keys tied to their User API keys first.

3. Review last active

   Sort or filter by Last active during access reviews to find stale accounts with admin privileges.

Transferring ownership

Only a super admin can transfer organization ownership.

1. Choose successor

   The new owner must already be an org member. Many orgs promote them to admin first, verify they can operate the dashboard, then transfer.

2. Transfer

   From Settings → Organization (or the Members ownership action), select Transfer ownership, confirm the target member, and acknowledge the prompt. The previous super admin typically remains admin unless you demote them separately.

3. Verify audit entry

   Ownership transfer is always audited with previous owner, new owner, and actor (if different).

Groups and service accounts

Enterprise orgs may also use:

Groups inherit team and project access according to admin configuration — prefer groups over one-off project adds for large orgs.

Provisioning API for operators

Org member changes initiated from the dashboard ultimately persist through the platform API at api.4rged.ai. Operator tooling exposes routes such as /api/provisioning/organizations/{organizationId}/people for listing, inviting, and removing members, and /api/provisioning/organizations/{organizationId}/sessions/{sessionId} for revoking active desktop sessions. These routes require an authenticated platform or org-admin session — they are not public REST endpoints. Audit entries record the actor for each membership change.