Share your account with a team

Team members work in your account with their own Coritan account and password, so nobody has to share yours. You invite each one on the Team tab of Settings, with a role that sets what they can do. You stay the owner of the account.

• Sign in to the dashboard.
• Have the email address of each person you want to invite. They accept with the Coritan account that signs in with that address, or create one with it.
• While account plans apply to your account, check how many seats your plan includes. See Seats.

A role covers the account's own resources. Each member keeps their own sign-in, sessions, password, API keys and email choices, and nobody can change those for them.

1. In the sidebar, select Settings, then the Team tab.
2. On the Team members card, select Invite member….
3. Enter their Email and choose a Role.
4. Select Send invitation.

A message confirms it, such as Invitation sent to sam@example.com. The invitation appears in the table as Pending, with the date its link expires. We email the link to that address, and it works for 7 days.

If someone invited you:

1. Open the email and select its link. It opens the Team tab of Settings, with an Invitation card.
2. If the dashboard asks you to sign in, sign in with the address the invitation went to. If you do not have an account yet, create one with that address, then open the link again.
3. Select Accept invitation.

A message confirms it, such as You joined the team of Example Ltd. The account appears under Teams you are on and in the account menu.

1. Select your initials at the top right. Under Work in another account, select the account. On the Team tab, Work in this account in the account's row under Teams you are on does the same.
2. The dashboard opens the account's home page. A banner at the top of every page names the account and your role there, such as You are working in Example Ltd and Your role here is Technical.

What you do then happens in that account, within your role. When your role does not allow something, the dashboard tells you, such as Your role on this account (Technical) does not allow this. The account menu lists five accounts at most, and All teams you are on opens the Team tab with the rest.

To go back, select Switch back in the banner, or Switch back to your account in the account menu.

The choice belongs to the tab you made it in, and lasts until you close that tab or sign out. Organizations open only in your own account, because each brand has its own team. If you leave the team, or the account stops letting you in, the dashboard goes back to your own account and says why.

To work in an account from a script, use the API, as Act for an account shows. Teams you are on lists each account with the Account ID the API needs.

1. In the table, open the actions menu at the end of the member's row, and select Change role….
2. Choose the new Role, then select Save role.

A member's new role applies from their next request. For an invitation that is still waiting, the new role is the one it offers.

1. Open the actions menu at the end of the row.
2. Select Remove from team… for a member, or Withdraw invitation… for an invitation that is waiting.
3. Confirm with Remove member or Withdraw invitation.

Within 10 seconds, a removed member can no longer work in your account, and the link in a withdrawn invitation stops working. You can invite them again later. For an invitation that expired, select Remove invitation to clear it from the table.

1. On the Team tab, find the account under Teams you are on.
2. Select Leave…, then Leave team.

You can no longer work in that account. If you were working in it, the dashboard goes back to your own account. Its owner can invite you again.

While account plans apply to your account, your plan sets how many people can share it, as What each plan includes lists: 1 on Free, 3 on Pro, and no limit on Business and Enterprise. You count as the first seat, and so does every member and every invitation that is still waiting. An expired invitation frees its seat.

The caption under the table shows how many seats you use, such as 2 of 3 seats used, counting you. When every seat is taken, Invite member… is greyed out until you remove a member or withdraw an invitation, and a card above the table offers the plan with room for one more person, with its price. Until account plans apply to your account, there is no limit and no caption.

The people you invite can work in your account within their role, each with their own sign-in. Coritan records every change a member makes in your account, and who made it.

That person is already on the team.

The address belongs to a member already. To change what they can do, change their role.

An invitation to that address is waiting. Remove it first to send a new one.

Withdraw the waiting invitation, then invite the address again.

That is the account owner's own address.

You entered your own address. You are the owner already.

Every seat is taken

Every seat your plan includes is taken. Remove a member or withdraw an invitation, or select the upgrade the card offers (Change your account plan).

Your role on this account (Technical) does not allow this.

You are working in another account, and your role there does not cover that change. Ask the account's owner for another role, or switch back to your own account.

You are back in your own account

You left the team of the account you were working in, its owner removed you, or the account is closed or suspended. Ask its owner to invite you again if you still need it.

Organizations opens only in your own account

Each brand has its own team, so the Organizations area cannot work in another account. Select Switch back to your account, or ask the brand's owner to add you to the brand's team. With account plans, the area is called Reseller program.

You sent a lot of invitations in the last hour. Wait a while and try again.

You can send 20 invitations an hour. Wait an hour, then try again.

Sent to another address

You are signed in with an address the invitation was not sent to. Select Sign out and switch account, then sign in with the address the invitation went to.

This invitation has expired

The link is more than 7 days old. Ask the person who invited you to send a new one.

This invitation no longer works

The invitation was accepted or withdrawn. Ask the person who invited you for a new one if you still need access.

This invitation is for your own account

You opened a link you sent. The person you invited accepts it from their own account.

That account is closed or suspended, so it cannot be joined.

The account that invited you cannot be used right now. Ask its owner.

• Review your account's activity
• How account plans work
• Sign out and end sessions
• Authentication

Routes about you always answer for you and ignore the X-Coritan-Account header: your sign-in routes (/auth/...), the routes under /account/memberships and /account/invitations, and webmail (/client/webmail/... and /webmail/...). The billing address at /auth/me/billing-profile belongs to the account, so it follows the header. Only the Admin and Billing roles can read or change it.

GET /account/members answers the owner, the members and the invitations that are waiting or expired:

curl https://api.coritan.com/api/v1/account/members \
  -H "Authorization: Bearer $CORITAN_TOKEN"

{
  "owner": {"user_id": 4821, "email": "alex@example.com", "name": "Alex Morgan"},
  "members": [
    {
      "id": 57,
      "email": "sam@example.com",
      "name": "Sam Taylor",
      "user_id": 5310,
      "role": "technical",
      "role_label": "Technical",
      "status": "active",
      "invited_at": "2026-09-20T10:02:11",
      "invite_expires_at": null,
      "accepted_at": "2026-09-20T12:40:05",
      "invited_by": 4821
    }
  ],
  "seats_used": 2,
  "seats_limit": 3
}

status

active for a member, pending for an invitation that is waiting, and expired for one that was not accepted in time.

name and user_id

The member's name and account number, or null until they accept.

invite_expires_at

When a waiting invitation expires, or null once it is accepted.

seats_used

You, every member and every waiting invitation.

seats_limit

Your plan's limit, or -1 for no limit. It is null until account plans apply to your account.

POST /account/members takes the address and one of the roles admin, technical, billing or readonly:

curl -X POST https://api.coritan.com/api/v1/account/members \
  -H "Authorization: Bearer $CORITAN_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"email": "sam@example.com", "role": "technical"}'

It answers 201 with the invitation, in the shape of a member above. When every seat is taken, it answers 402 with "code": "entitlement_exceeded" and "entitlement": "team_members", as When you reach a limit describes. The other refusals are in Troubleshooting: 422 for your own address, 409 for a member or a waiting invitation, and 429 after 20 invitations in an hour.

PATCH /account/members/{member_id} with {"role": "billing"} changes the role of a member or a waiting invitation, and answers the row.

DELETE /account/members/{member_id} removes a member or withdraws an invitation, and answers {"removed": true, "id": 57}.

Both answer 404 with Team member not found for a row that is not on your team or was already removed. Only you and your Admin members can change the team.

The link in the email is https://www.coritan.com/dashboard/settings/team?invite=.... Read what its invite value offers with GET /account/invitations/{token}. The answer holds status, account_name, inviter_name, role, role_label, expires_at, email_matches (whether you can accept it) and own_account.

Accept it with POST /account/invitations/{token}/accept, signed in with the address it was sent to:

curl -X POST https://api.coritan.com/api/v1/account/invitations/TOKEN/accept \
  -H "Authorization: Bearer $CORITAN_TOKEN"

{"membership_id": 57, "owner_user_id": 4821, "account_name": "Example Ltd", "role": "technical", "role_label": "Technical"}

GET /account/memberships lists the accounts you can work in:

{
  "memberships": [
    {
      "id": 57,
      "owner_user_id": 4821,
      "account_name": "Example Ltd",
      "owner_email": "alex@example.com",
      "role": "technical",
      "role_label": "Technical",
      "accepted_at": "2026-09-20T12:40:05"
    }
  ]
}

DELETE /account/memberships/{membership_id} leaves a team, and answers {"left": true, "id": 57}, or 404 with Membership not found.

The dashboard names the account for you while you work in it. To work in an account you joined from a script, send its owner_user_id in the X-Coritan-Account header with your own access token:

curl https://api.coritan.com/api/v1/client/servers \
  -H "Authorization: Bearer $CORITAN_TOKEN" \
  -H "X-Coritan-Account: 4821"

The request then answers for that account, within your role. Coritan records each change you make there, and who made it, before the change runs. Pricing an order with POST /checkout/quote changes nothing, so every role can do it.