Teams
A team is the top-level organizational unit in Recuro. All crons, queues, jobs, alerts, and billing are scoped to a team.
How teams work
When you sign up, a default team is created for you. You can create additional teams to separate environments (staging vs. production) or organizational units.
Every resource you create belongs to your currently active team. Switch teams from the team switcher in the dashboard to view and manage resources for that team.
Roles
Each team member has one of two roles:
| Role | Permissions |
|---|---|
admin | Full access: create, edit, and delete crons, queues, jobs, and team settings. Manage members and invitations. Manage billing. |
member | Read and write access to crons, queues, and jobs. Cannot manage team settings, members, or billing. |
The team owner (the user who created the team) has admin privileges and cannot be removed from the team.
Inviting members
Admins can invite new members from Teams > [team] > Invite Member:
- Enter the email address of the person to invite
- Recuro sends an invitation email with a unique link
- The invitee clicks the link to accept — if they do not have an account, they are prompted to sign up first
- The new member joins with the
memberrole by default
Invitations expire after a set period. Admins can cancel pending invitations from the team page.
Switching teams
If you belong to multiple teams, switch between them from the team switcher in the sidebar. Your current team determines which crons, queues, jobs, and alerts you see.
Switching teams updates your current_team_id and redirects you to the dashboard.
Team settings
From the team page, admins can:
- Rename the team
- Remove members (except the owner)
- Change member roles between admin and member
- Delete the team (only the owner can do this)
API and team scope
Your API token is tied to your user account and operates in the context of your current team. All API calls create resources in your current team. Switch teams in the dashboard before generating a token if you need to target a different team.
The same applies to the MCP server — all tool calls are scoped to the team associated with the API token.
Billing
Each team has its own subscription and usage limits. Manage billing from Teams > [team] > Billing:
- View your current plan and usage
- Subscribe to a paid plan
- Cancel your subscription
Usage limits (monthly request count) are enforced per team.
Next steps
- Managing Teams — Step-by-step guide for invitations and roles
- Team Organization Best Practices — Structuring teams for staging and production