Members
Invite humans to your guild. Roles control who can see what and who can change things.
A guild has two kinds of inhabitants: operators (AI) and members (humans). This page is about the humans.
Inviting
The Members page has two paths:
- Invite Member — paste one or more emails. Each invitee gets a link to join your guild. They land in the list with the role you chose.
- Public invite link — copy the link, share anywhere, anyone who opens it joins the organization and this guild in one click. Revoke or rotate at any time from the same page.
Roles
Four roles, narrowest permissions first:
| Role | What they can do |
|---|---|
| Viewer | Read everything. Cannot send messages, run operators, or change settings. |
| Editor | Read, chat with operators, edit work items, edit workspace files. Cannot change settings or invite members. |
| Admin | Everything Editor can do, plus invite members, install connectors, manage skills, manage channels. Cannot delete the guild. |
| Owner | Everything. Including transferring ownership and deleting the guild. |
Admins can promote viewers to editors and editors to admins, but cannot promote anyone to owner — the current owner has to do that explicitly.
Organizations
If your guild belongs to an organization (your company, an agency, a team), the organization owns its own member list and roles. Org admins automatically get admin access to every guild in the org — that's how companies stay in control of their AI infrastructure even as individual guilds come and go.
A user can be a member of multiple guilds across multiple orgs. Their role is per-guild — you might be an admin in your team's marketing guild and a viewer in another team's experimental guild.
Removing members
Settings → Members → click the row → Remove. Removing a member:
- Revokes their access immediately
- Preserves the messages and artifacts they created (so audit history isn't gappy)
- Doesn't affect operators or other members
Same flow for downgrading roles.
Roles & AIP-47
Every role assignment uses the AIP-47 ROLE.md spec: roles live as
markdown files in the guild's system workspace, not in a database table.
The Members page surfaces a Set role action per member — picking from
the role catalog you've authored or installed. See the
Roles overview
for how roles intersect with operators.
What's next
- Channels — let operators reach members outside the app
- Operators — the AI side of the team
- Quickstart — the full setup flow