Redirects used to belong to a single login. They now belong to an account -- a workspace with its own business details, its own domains and redirects, and its own list of linked people. This piece is the reference for how the pieces fit: ownership, the four roles, the invite lifecycle, and plan limits on a shared account.
Ownership moved from people to accounts
Every domain in the registry and every redirect carries an account where it used to carry only a person. A person's access comes from their membership in that account, at one of four levels. Practically:
- A new signup gets a personal account automatically -- owner, sole member. Solo users notice nothing except a slightly richer profile page.
- Inviting a colleague links them to your account at the role you choose. They immediately see the account's domains and redirects alongside their own personal ones.
- Transferring a domain to another user now moves it into their personal account -- recipient-side limits and ownership follow, same as the old handover but account-aware.
The old sharing layers still work exactly as before: Projects and per-domain access remain the way to share part of a portfolio with outsiders. Accounts are for the people who belong to the business.
The four roles, precisely
| owner | admin | member | viewer | |
|---|---|---|---|---|
| See the account's domains & redirects | ✓ | ✓ | ✓ | ✓ |
| Add/remove domains, edit redirects, DNS manager & forwards | ✓ | ✓ | ✓ | — |
| Invite people, change roles, remove members | ✓ | ✓ | — | — |
| Edit account details (business name, contact, address) | ✓ | — | — | — |
Two structural rules back these up: an account always keeps at least one owner (the last one can't be demoted out), and a viewer's restrictions are enforced server-side, not just hidden in the interface -- the write endpoints reject them too.
The invite lifecycle
- An owner or admin enters an email address and a role. The address receives a one-time token link.
- The link only works for an account registered to that email address -- forwarding the token to a colleague can't attach someone else's login to your business.
- Existing users accept instantly while signed in. New users register with the invited address and accept once their account is approved (invitations don't bypass the signup review).
- Pending invitations can be revoked by any admin, and a removed member can always be re-invited later -- nothing they built is lost, it stays in the account.
Plan limits on a shared account
Domain and redirect caps are counted per account and drawn from the account owner's plan, regardless of which member does the work. Two consequences worth knowing:
- A member without their own subscription can still work in your account -- your plan covers it.
- Personal projects stay on the member's own plan. Work in one account never consumes another account's quota, and nothing is double-counted.
Ownership transfer, two ways
Invite keeps the account in place and adds a person -- use this for teams. Transfer (on the Domains page) hands a single domain -- and the redirects you personally own on it -- out of your account entirely, into the recipient's own. Transfers are limited to the domain's creator and the account's owners/admins, so a plain member can't give away the whole portfolio.
Records and exports
The account's business details (name, contact email, phone, mailing address) live on the account, are visible to its members, and are editable only by the owner. Everything the platform holds about you -- memberships included -- is downloadable as JSON from My Profile → "Download my data" at any time, and an owner leaving a team is a membership removal, not a data loss: the domains and redirects remain with the account.