Feature · Platform

Members

People in this organization and their roles.

Last changed

Generated from commit be57775 ·

How it works

The roles

  • Owner: everything, including other owners, billing and the organization itself.
  • Admin: integrations, models, policies, budgets, members, tokens and settings.
  • Approver: approve risky actions, resolve escalations, and confirm facts and lessons.
  • Member: assign work, message workers, tell them things and add documents.
  • Viewer: read everything, change nothing.

Each role can also do everything the roles below it can do. The server checks every call.

Invite people

  1. On Members, select Invite people.
  2. Enter the email addresses, choose a role and add an optional note.
  3. Select Create invitations. Agent emails them when available. Otherwise, copy and share the invite links.

An invite expires after 72 hours. A new invite to the same address replaces the old one. When Agent shows an invite link, it shows it only one time; send it privately. Pending invites can be revoked.

Change a role

Admins change roles in the list, but not their own. An admin can give roles up to admin. Only an owner can make someone an owner or change an owner's role. The organization always keeps at least one owner.

From the help article Members and roles, checked against the product on .

What you can do

The operations this feature's screens call. Each one is POST /api/<name>, and the badge says who may call it.

  • listMembers

    Viewer

    Lists members.

    Types: EmptyRequest returns ListMembersResponse

  • updateMemberRole

    AdminNo API tokens

    Updates the member role.

    Types: UpdateMemberRoleRequest returns MemberSummary

  • revokeInvite

    AdminNo API tokens

    Revokes the invite.

    Types: RevokeInviteRequest returns OkResponse

  • sendInvite

    AdminNo API tokens

    Makes an invitation as createInvite does and emails it; url is the fallback when nothing was emailed.

    Types: SendInviteRequest returns SendInviteResponse

  • listWorkers

    Viewer

    Lists workers.

    Types: ListWorkersRequest returns ListResponse<WorkerSummary>

Screens

What it records

The feature writes these events to the audit log, the permanent record of what happened.

  • Address proven
  • API token created
  • API token revoked
  • Integration changed
  • Member added
  • Member role changed
  • Onboarding changed
  • Org created
  • Signup completed
  • User signed in
  • Vendor trigger removed

Generated from code at commit be57775 ·

Turn the numbers into shipped work.

Agent runs these choices for you: a persistent AI worker with memory and rules, on your Claude and Codex subscriptions.