Skip to content
Delay Docs

Teams and roles

A team holds your crons, queues, jobs, alerts and usage. It also has its own notification channel, signing secret and plan. When you sign up, Delay creates a personal team for you (named after you, for example “Ada’s Team”) and selects it.

Roles

A team has two roles, admin and member. The owner is the person who created the team. Owner isn’t a separate role: the owner is an admin who also has a few extra rights.

What you can doMemberAdminOwner
Create, edit, run and delete crons, queues and jobs; replay dead letters; manage alerts and maintenance windowsYesYesYes
Use the API with your own tokenYesYesYes
Rename the team, invite and remove people, change rolesNoYesYes
Set the notification channel; view or regenerate the signing secretNoYesYes
Manage billing, delete the teamNoNoYes

There is no read-only role.

Create a team

  1. Click the team name in the header and choose Create team. You can also go to the account menu > Teams > Create team.
  2. Enter a Team name and click Create Team.
  3. Delay opens the new team’s page but keeps your current team selected. Switch to the new team to start working in it.

Switch teams

Click the team name in the header and pick a team under Switch team. The dashboard reloads with that team’s crons, queues and jobs. The selected team is also the one your API calls go to (see below).

Invite people

  1. Click the team name in the header and choose Team settings.
  2. Under Invite member, enter the person’s email address and click Send invite.
  3. They get an email with a link. The invitation expires after 7 days.
  • Everyone joins as a member. Make them an admin afterwards if they need it.
  • Someone new to Delay registers with the invited email address and joins the team automatically. Someone who already has an account signs in with that address, then opens the link again.
  • After joining, they still have their own team selected. They switch to yours with the team switcher.
  • There’s no resend. If an invitation got lost or expired, delete it under Pending invitations (trash icon) and invite the person again.

Change roles and remove people

On the team page, under Members, admins see icon buttons next to each person:

  • shield: make admin
  • person with a minus sign: make member
  • trash: remove from the team, immediately and without a confirmation

The owner can’t be demoted or removed. Ownership can’t be transferred, and there’s no “leave team” button, so ask an admin to remove you. Someone who is removed while working in the team gets switched to another of their teams.

Rename or delete a team

  • Rename: admins edit Team name in the Team settings card and click Save.
  • Delete: the owner clicks Delete team under Danger zone and confirms.

Teams and the API token

Your API token belongs to you, not to a team. Each API call creates its job or cron in the team you have selected in the dashboard at the moment of the call. If you switch teams in the browser, your scripts’ next calls go to the new team.

Every member has their own token, and roles don’t limit it: a member’s token can create crons and jobs too. Details on the token itself: API overview and authentication.

Use teams for environments

Separate teams for production and staging keep them apart. Each team has its own:

  • crons, queues, jobs and run history;
  • notification channel, so staging failures don’t page the production channel;
  • signing secret;
  • monthly request quota and plan. A new team starts on the free plan (1,000 requests a month), and each team is billed on its own, so staging doesn’t use up production’s quota.

Name them so they’re easy to tell apart in the switcher, for example shop-production and shop-staging.

Because a token follows your selected team, one person can’t hold a “staging token” and a “production token”. Pick one of these:

  • One account per environment (recommended for CI and servers). Create a Delay account for each environment, for example with [email protected], invite it to that team, sign in as it once and switch to the team. Its token then always goes to that team, as long as nobody switches it.
  • Your own token, switched by hand. Fine for trying things out. Check the team in the header before you run a script.

Next steps