Usage Limits & RBAC
How plan-based usage limits are enforced, and what each of the 5 team roles can do.
Every chat request is checked against your plan's limits before it reaches any AI provider. If you're over, Tarqa answers 429 (code: rate_limit_exceeded) and never forwards the request, so you're never charged for it. The exact numbers per plan are on Plan Limits.
429 means quota. 403 is used only for roles and plan-gated features, never for quota.
Which limits apply to you
Your personal workspace and each team workspace have completely separate limits.
| Where you are | Whose plan applies |
|---|---|
| Personal workspace | Your own plan (Free / Starter / Pro) for chat, knowledge bases, webhooks and API keys. A Free user stays on Free limits here, even if they belong to a paid team. |
| Team workspace | The team's plan (Team / Enterprise), as one shared monthly pool for all active members, whatever their personal plan is. |
| Per-member caps (optional) | Team admins can cap how many requests or tokens one member uses per month. A member who hits their cap gets a 429 asking them to contact their admin; the rest of the team is unaffected. |
The 5 team roles
| Role | Call the API | Manage keys | Manage team | Billing |
|---|---|---|---|---|
| Owner | ✓ | ✓ | ✓ | ✓ |
| Admin | ✓ | ✓ | ✓ | — |
| Developer | ✓ | ✓ | — | — |
| Member | ✓ | — | — | — |
| Viewer | — | — | — | — |
Single sign-on (SAML 2.0)
Connect Okta, Azure AD, Google Workspace or any SAML 2.0 identity provider. People sign in with their company account, with no separate password. Available on the Team and Enterprise plans.
FAQ
I'm on a paid team but my personal chats are limited. Why?
Personal and team workspaces are separate. In your personal workspace your own plan applies; switch to the team workspace to use the team's plan.
One member is blocked but others aren't.
That member probably hit a per-member cap set by a team admin. An admin can raise it in the team's settings.
Who can create API keys in a team?
Owners, Admins and Developers.