Member access and roles
Invite human teammates to a Yodu workspace, choose owner, admin, or member access, and restrict who can configure tools or approve work.
Human member roles control who can administer the workspace. They are separate from AI employee roles and per-employee tool access.
Current human roles
| Role | Intended use |
|---|---|
| Owner | Accountable company owner with full organization control |
| Admin | Trusted operator who manages members, settings, AI employees, and workspace operations |
| Member | Teammate who participates in the workspace without full administrative authority |
Workspace owner and admin checks protect employee-management operations. Only trusted people should receive either role.
Invite a member
- Open Organization settings → Members.
- Enter the teammate's email address.
- Choose the role.
- Send the invitation.
- Confirm the member appears after accepting.
Use a company-controlled email address when the workspace contains customer data or production connections.
Change a role
Owners and admins can use the role selector in the member list. Review the person's responsibilities before promoting them.
The owner role is protected in the member list. Plan ownership changes carefully rather than treating the owner as a routine admin role.
Remove or leave
Use the member menu to remove another user or leave the workspace yourself. Before removing an admin:
- transfer any human review responsibility
- review provider and connected-account ownership
- reassign important tasks
- confirm another trusted admin remains
What human roles do not replace
Human roles do not grant an AI employee access to a tool. Manage AI employee capabilities under Tool access → Employee access.
Likewise, changing an AI employee's tool access does not change what a human member can administer.
Sensitive workspace boundaries
During the beta, treat owner, admin, and member roles as workspace-level access. When a person must be isolated from a client, employee, or connected account, use a separate workspace instead of relying on naming conventions.
Approval responsibility
Use a trusted owner or admin as the human reviewer for sensitive work. The task and approval request should make the expected reviewer clear.
Avoid shared reviewer accounts. A named member gives the team a clearer decision trail.
Access review checklist
Review members monthly and after every team change.
- Every member still needs workspace access
- Only trusted operators are owners or admins
- Company emails are used where possible
- Review responsibility has a named human
- Removed teammates no longer own connected accounts used by the workspace
- Client or company boundaries use separate workspaces
The simplest safe rule is: give administrative access to as few people as the operating model allows.