Team and roles
Invite members and grant OWNER, ADMIN, OPERATOR or VIEWER; each role sees only its authorized surfaces.
Before you start
- An OWNER or ADMIN role to manage the team.
Steps
Invite a member
Invitation and password reset emails are actually delivered.
Assign a role
OWNER/ADMIN configure; OPERATOR handles conversations; VIEWER reads.
Check isolation
A member only ever sees their own workspace data.
Expected result
A mutation or provider test is controlled by role at the API level, with no internal stack exposed.
Errors and solutions
Mutation refused
A standardised field/code/message/action error is returned; the role does not allow this action.
Screens
/team — Team: members, roles, invitations, isolation.Reference of the console screen to capture (redacted) during the browser recipe (XP14). No fabricated image is shown.
Limits and dependencies
VIEWER is read-only by design; there is no silent privilege escalation.
Provider documentation
—