Team members
Let colleagues sign in to the same account with their own email and password, work in several accounts from one address, and see what each of them can do.
An account has one owner — whoever signed up — and any number of members. A member signs in with their own email and password and works inside the same account: the same agents, knowledge bases, records and console. What stays with the owner is money and membership: the plan, payment details, invoices, and who is on the team.
Inviting someone
Dashboard → Team → enter their email → Send invitation. They get a link, choose a password, and land in your account. Nothing else needs setting up: their access to the console follows automatically, under their own address, so actions there are attributed to the person rather than to the account.
The list shows three states, which is usually what you actually want to know:
| What you see | What it means |
|---|---|
| Member | They have signed in and are working in the account. |
| Email not verified | They can sign in and work normally. Verification is a nudge, not a gate — the badge stays until they click the link in their confirmation email. |
| Pending invitation | Nobody has accepted it yet. Resend it (once a minute) or revoke it. |
An invitation is good for 14 days. Resending pushes that out again, so an invitation someone finds late still works.
One address, several accounts
An address can work in more than one account. Someone who already has their own agent4.io account can be invited into yours, and a consultant can be in five customers' accounts at once. They sign in once; if they can open more than one account, they pick which to work in and can switch at any time. Whoever has only one account never sees any of this.
Two limits are worth knowing:
- One account at a time, per browser. Switching changes what the whole dashboard shows. Two browser tabs cannot sit in two different accounts.
- An address still owns at most one account — its own. Being invited into others does not change that, and you cannot create a second account of your own under the same address.
Naming your account
An account needs a name before it can invite anyone. Someone who works in several accounts chooses between them by name, and a list where every row says the same thing is not a choice. Set it under Settings → Organisation; the invite screen links straight there if it is still empty.
Removing access, and leaving
Removing a member ends their access to your account immediately. Their sign-in still exists — they simply stop being in your account, and can be invited again later.
A member can also leave on their own, from the account list. An owner cannot leave their own account: there would be nothing left to own it. If someone leaves the last account they were in, they end up with no account and can start their own.
Cancelling an invitation before it is accepted is Revoke in the pending list.
What a member cannot do
- See or change the plan, payment method or invoices
- Buy top-ups or cancel the subscription
- Invite or remove other members
Everything else — creating agents, uploading knowledge, editing storylines, reading the inbox, connecting channels — a member can do exactly as the owner can. If you need finer-grained permissions than that, tell us what the split should be; we would rather build the distinction you actually need than guess at a role matrix.