Cloud/Settings/Members
Members
The people in your organization: who they are, what role they hold, how roles change, and how new people are invited in.
Members is the roster of the active organization. Its description promises the whole picture in one line: "People in your organization, their roles and invitations." Seeing it requires org:members:read; changing it requires more.
Members
People in your organization, their roles and invitations.
Renato Marinho
renato@acme.com
Ana Souza
ana@acme.com
Bruno Lima
bruno@acme.com
Carla Dias
carla@acme.com
Invite member
Send an email invitation to join this organization.
The mockup is the real roster. Cycle a member's role badge and remove a member to watch the list react.
One row per person
Each member shows an initials avatar, their name, their email and their role. Roles are the organization's access model in miniature: Owner holds org:manage and cannot be removed from this list, Admin and Member hold narrower sets, and members whose role grants nothing show as No role. Changing a role and removing a member are org:members:manage actions: the role changes in place, and removal takes the person's access away immediately.
Inviting
The invite form sends an email: one address plus a role chosen from the organization's roles. "Send an email invitation to join this organization." The invited person appears in the organization only when they accept, and until then their invitation is managed on the next page, Invitations.
Why this page exists
Roles decide what a person's agents can touch inside the organization, and membership decides who is in the room at all. This page is where both are adjusted as the team changes: someone joins, someone grows into a bigger role, someone leaves. Everything here is permission-checked twice over, once to see the list and once to change it.
What comes next
Invitations manages the pending side of this page: the emails not yet accepted and the shareable join link.