> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chargerdojo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Work with a colleague

> Invite someone into your organisation, what each role can do, what a colleague shares with you, and what happens to their work when they leave.

Everything you create in ChargerDojo belongs to an **organisation**, not to you personally: the
partner endpoints, the runs, the reports and the schedules. Inviting a colleague into yours gives
them the same work to look at, on the plan you already pay for. Connectors are the exception, and
there is a section on them below.

Seats are free. We do not charge per person, and no plan sells a number of people. There is a
ceiling of 200 in one organisation, which is a limit on abuse rather than a rung you can buy past;
if you need more, write to us.

## Invite someone

1. Sign in and open **Settings**, then **Members**.
2. Check the organisation named at the top of the page is the one you want them in. If you belong
   to more than one, the switcher is in the account menu, under your initial in the top right, and
   it shows which organisation holds your plan.
3. Choose **Invite**, enter their work email, and pick a role.
4. Send them the link the invitation gives you. It is shown once and it expires.

The link is bound to the address you invited. Opening it signed in as anybody else is refused, and
so is opening it before that address has been verified, so a forwarded link joins nobody. They do
not need an account first: the link takes them through signing in with that address and drops them
straight into your organisation.

If they tell you the link says the invitation was sent to a different address, they are signed in
as someone else. Sign out, then open it again as the invited address.

<Note>
  Invite them into the organisation that holds your subscription, rather than creating a new one
  for the team. A new organisation starts on the free plan and your subscription stays where it
  is. We cannot move a subscription between organisations for you yet.
</Note>

## What each role can do

|                                              | Member | Admin | Owner |
| -------------------------------------------- | ------ | ----- | ----- |
| See every endpoint, run, report and schedule | Yes    | Yes   | Yes   |
| Add endpoints, run suites, run journeys      | Yes    | Yes   | Yes   |
| Delete or re-point what **they** created     | Yes    | Yes   | Yes   |
| Delete or re-point what **anyone** created   | No     | Yes   | Yes   |
| Invite people, change roles, remove people   | No     | Yes   | Yes   |
| Pair and revoke connectors, create API keys  | No     | Yes   | Yes   |
| Set up scheduled runs                        | No     | Yes   | Yes   |
| Rename the organisation                      | No     | Yes   | Yes   |
| Buy, change or cancel the plan               | No     | Yes   | Yes   |
| Read the audit log                           | No     | Yes   | Yes   |
| Hand the organisation to somebody else       | No     | No    | Yes   |

Invite an engineer as a **Member** unless they need to manage the team or the plan. A member adds
endpoints, runs suites and journeys, reads every report and shares any of them. What they cannot do
is undo somebody else's work, pair a connector, or set up a scheduled run.

Two things the table cannot say in a column. An admin cannot remove, suspend or re-role an **owner**,
and nobody can invite somebody straight in as one: ownership moves only by handing it over. And
"what they created" means a row that records who made it. A handful of older endpoints, made before
we started recording that, belong to nobody and need an admin to remove.

Owner is one step above admin and holds one thing: handing the organisation over. Everything else an
owner can do, an admin can do too.

## What a colleague shares with you, and what they do not

**Partner endpoints are shared, and they are the meter.** Your plan's endpoint allowance belongs to
the organisation, so two people on Integrate hold three partner endpoints between them, not three
each. A colleague brings no extra capacity with them. See [Plans and pricing](/guide/plans).

**Runs are counted per person.** Your colleague's suites do not eat into your rate limit.

**Reports are shared.** Anybody in the organisation can open, read and share any report the
organisation produced, whoever started the run.

**Connectors are personal.** A connector runs on one person's machine and is paired to them, and
pairing one needs **admin**, so a member asks an admin to pair theirs. Nobody shares a connector:
each of you gets your own. See [Use the connector](/guide/use-the-connector).

**The simulator is per browser.** The chargers and sessions on the simulator screens belong to the
browser session you are in, so you and your colleague will not see each other's. That surface is
for learning and demos; the paid testing surfaces are all organisation-wide.

## When somebody leaves

Remove them in **Settings**, then **Members**. Removing someone:

* takes away their access at once, on every device;
* revokes the API keys they created, so anything running with one stops;
* revokes the connectors they paired, and closes the sockets those connectors were holding;
* pauses any scheduled run they set up, because the run acted for them. Re-save the schedule to
  take it over.

Everything else they made stays: the endpoints, the reports, the journey presets and the runs all
belong to the organisation and are still there.

You cannot remove whoever is paying for the organisation, because their card is what the plan runs
on. Move the subscription to somebody else first, in **Settings**, then **Billing**.

<Warning>
  If any of your partner endpoints ran over a connector **they** paired, those endpoints stop
  working until you point them at a connector that is still live. Pair one of your own in
  **Settings**, then **Credentials**, then open **Testing**, then **Endpoints**: the affected
  endpoint offers **Move to connector**. You do not need to register with the partner again.
</Warning>

## Leaving an organisation yourself

Open **Settings**, then **Members**, and choose **Leave**. You lose access to that organisation's
endpoints, runs and reports. Anything in your own organisation is untouched.

Two things stop you leaving. If your card is paying for the organisation, move the subscription
first, in **Settings**, then **Billing**. And an owner cannot leave while they are the only owner:
open **Settings**, then **Members**, and choose **Make owner** on the person taking it over. You
stay an admin afterwards, so you keep everything except the ability to hand it on again.