Give every team member the right amount of authority
Each organization is its own tenant. Roles decide who can create tasks, configure policy, decide approvals and manage keys, and a per-member spend cap bounds what any one person can commit.
Updated · by the ThreadPool team
The problem
An AI workforce that anyone can point at a budget is a liability. A workforce nobody can use is useless. Teams need graded authority that is enforced by the backend, not by the interface.
How it works
- Roles: Owner, Admin, Finance, Manager, Member and Viewer. The role-to-permission map is a pure function covered by unit tests.
- No privilege escalation: nobody can grant a role above their own, and no change can leave an organization without an active Owner.
- Per-member spend cap: the Circuit Breaker also checks the creating member's per-task limit.
- Invites: members join through invitations with the same escalation rules.
- Tenant isolation: tasks, events and live streams are filtered by organization. A non-member and a nonexistent organization get the same 404, and a suspended member is treated as a non-member.
- Everything is server-side: the frontend never decides authority or money.
Limitations and trade-offs
- Roles govern access and spend authority. They do not review the quality of output; independent QA does.
Related
Try it: give a task a budget and watch the workforce form.
Get started