Who's in a Work account is managed from the Team tab (adding and removing people) and the Settings tab (claiming domains). Both are admin-only.
Inviting members
On the Team tab, invite a teammate by email. Someone who already has an account is added straight away; someone who doesn't gets a sign-up invite and joins the account once their account exists. New members start as plain members.
Roles
Every member is an owner, admin, or member (see How Work accounts work for what each can do). Owners set roles. A few guard rails keep an account safe:
- An account always keeps at least one owner; the last one can't be demoted or removed.
- Admins can remove plain members. Removing another admin, or an owner, is an owner-only action.
Removing someone takes away their access and their budget but never rewrites the books: their past expenses and trips keep their work attribution, and anything the company still owes them stays owed.
Verifying a domain
Instead of inviting people one by one, a company's email domain can be claimed so anyone who signs in with a matching email joins the account automatically.
Add the domain on the Settings tab. A TXT record is shown to add
to that domain's DNS: a host, the type TXT, and a
constellations-verify=… value. Add it with the DNS provider, then
come back and verify. DNS changes can take up to an hour to show up,
so a first check that doesn't find the record is worth retrying
after a while.
Company sign-in
Once a domain is verified, a Work account admin can connect the company's own sign-in to it: Okta, Microsoft Entra ID, Google Workspace, or any provider that supports OpenID Connect. People with an address at that domain then choose Sign in with your company and sign in on the company's own page.
The provider only signs in addresses at its own domain (and that domain's subdomains); it can't be used to sign in as anyone else. The client secret is stored encrypted.
Require company sign-in then makes it the only way in for that domain's addresses: passwords, Google sign-in and passkeys stop working for them, and the email-and-password form sends them to the company's sign-in. It can only be switched on once company sign-in is connected, and has to be switched off again before company sign-in is disconnected or the domain removed, so nobody is locked out. Removing a domain also removes its company sign-in.
Groups
Everyone in a Work account shares one group, named after the company — it appears in each member's own constellation list as Acme · Everyone, and its membership follows the account. Nobody joins or leaves it by hand; people arrive when they join the company and go when they leave.
Admins can create further groups on the Team tab — a region, a department, a project — and pick who is in each. Only people already in the Work account can be added, so a group can never outlive somebody's employment.
Groups do two things. Members can share a trip into one, the same way they would with any other constellation. And admins can narrow the whole dashboard to a single group: the map, the spend rollup, the trips list, the approvals queue and both exports all follow the selection, so "what did the Berlin team spend in March" is two controls rather than a spreadsheet.
Managing trips
The Team tab also lists the trips attributed to the account, with their traveller and approval state. It's the admin's view of the travel the account is carrying, the companion to the personal trip attribution each traveller sets from their own trip.
Closing a Work account
An owner can delete the account from Settings — not an admin, since this one can't be undone. Confirming sends an email, and the link in it does the deleting, so a misclick costs nothing.
What survives is everything people made. Trips go back to being ordinary personal trips, expenses keep their amounts, receipts and categories, and company cards become ordinary payment methods. What goes is the company: its groups, whatever was shared into them, its claimed domains, and everyone's membership.