Teams
Teams group organization Members and grant them access to specific AI Workspaces. They are the practical mechanism behind Employee AI least privilege.
Short definition (citation-ready)
A Team is an organization-scoped group of Members with attached workspaces. Members only see Internal Portal assistants for workspaces their Teams grant.
How Teams relate to RBAC
| Concept | Role |
|---|---|
| Owner / Admin / Member | Who can configure vs who only chats |
| Team | Which workspaces a Member may use |
| Workspace | Isolated knowledge + tools |
See RBAC and Configure RBAC.
API surfaces (org)
Typical REST routes (Owner/Admin JWT):
| Method | Path | Purpose |
|---|---|---|
| GET/POST | /api/v1/org/teams | List / create teams |
| PUT | /api/v1/org/teams/:id/members | Set membership |
| PUT | /api/v1/org/teams/:id/workspaces | Grant workspaces |
Exact payloads: Admin Console + REST APIs.
Architecture
Workflow
Grant Employee AI access
- Create Team — Name by function, not by person.
- Add Members — Contractors get temporary membership.
- Attach workspaces — Only what that function needs.
- Verify as Member — Confirm portal list is minimal.
- Review leavers — Remove Team membership promptly.
FAQ
Do Teams affect the website widget?
No. The widget uses a workspace id + widget token. Teams gate Employee AI portal access.
Can a Member belong to multiple Teams?
Yes. They see the union of granted workspaces.