drift Docs
Pages
drift Docs
Start
What is Drift?
The tour, if you are new here.
Use cases
Whether Drift does your thing.
Getting started
Nothing to deployed, in one command.
Architecture
How a slice is put together.
What it costs
The free grant, four unit prices, two rules.
Moving off Azure
Estimate, snapshot and transform a resource group.
Build
Canvas
Static sites, same origin as your API.
Tools
Operate
Auth
Route gates, API keys and your account.
Teams
More than one person on one account.
Security
Boundaries, sandboxing and hardening.
Troubleshooting
Error codes
What went wrong, and what to do about it.
Legal
Acceptable use
What a slice may not be used for.
Data processing
The DPA, and every sub-processor.

Teams

More than one person can work on one Drift account. The account has one owner, and the owner invites members. A member logs in as themselves and works on the owner's slices, so a team shares an account without sharing a password.

What a member is

A member has their own username, password and second factor, and their own identity in the account's audit trail. Nothing the owner does can set or read any of those: the owner names an email address, and the person proves it is theirs by signing up against the invite. Their account is attached to the owner's, and their commands act on the owner's slices.

A member can create, resize, restart and delete slices, deploy and roll back Functions and Workers, and read and write Backbone. A member cannot read or change the account's secrets, read its audit trail, change how the account is protected, mint an access token, invite anyone, or delete the account. The CLI reference lists the commands.

A member or a token

Use a member for a person, and an access token for a pipeline or a script. Either would work for the other's job, and that is the trap: a pipeline that deploys as a shared member login leaves an audit trail that names a person who did nothing, and a colleague who deploys with a token leaves a trail that names nobody.

Inviting someone

Shell
drift account member invite alice@example.com
drift account member list

The invite goes to one email address and is emailed as a code. The code is also printed to you, so if the email does not arrive you can pass it on yourself. The invitee creates their own account with it, and the account lands attached to yours.

An unspent invite expires after 14 days. drift account member remove --email alice@example.com withdraws one before then.

The limit

One account carries at most 25 people, counting members and unspent invites together. Past that, an invite is refused until you remove a member or withdraw an invite.

Taking someone off

drift account member remove alice

Removing a member does not delete their account: their login, password and second factor stay theirs, and they keep nothing of yours. Their access ends within about fifteen minutes, the lifetime of the session token they already hold.

Who owns the account

Exactly one person, the one who signed up. Only the owner can invite members. There is no way to hand the account itself to someone else.

If the owner needs to hand work over, hand the slices: drift slice transfer offers a running slice to another account by name, and nothing changes until that account accepts. The slice keeps running, with its data, and its bill moves with it; its address moves too, taking the new account's name, and the old address redirects for 30 days before it stops answering. Do this from the owner's account, to an account the other person owns, before the owner's account is deleted. Deleting an account deletes every slice still on it.