Team
Your dashboard can be shared: everyone you invite works with the same assistants. What each person can do depends on their role.
Invite someone
There are two ways, and they are equivalent. One phrase in the conversation:
Invite mariia@smak.example.com as an admin
The builder asks for your consent: the invited person will get access to the dashboard's data. After your "yes", it gives you a link.
Or use the form in the Team section: email, permissions, Create invite — and the same link appears in the window.
The link is shown once, and you pass it on yourself
The platform doesn't send any emails. Copy the link from the conversation and send it to the person however suits you. Lost it? Create the invite again.
What the person sees when they open the link
An invite page — and right there, before they even sign in, it shows who is inviting them, with which permissions, and until what date the invite is valid. The address it was issued to is shown shortened (i•••@gmail.com): enough for the recipient to recognise their own.
What happens next depends on who opened the link:
- hasn't signed in yet — sign in or sign up, and afterwards they are brought straight back here: the link doesn't expire along the way;
- signed in with the right account — a single Accept invite button;
- signed in with a different account — the page says so and offers Sign in with another account, rather than a button that would refuse;
- the invite is no longer valid (expired, revoked, already used) — this is said straight away, before signing in or signing up.
An invite is valid for 7 days and only for the address it was issued to — that's what protects a link that accidentally ended up in the wrong hands. Upper and lower case in the address don't matter; an address with a "plus" (ivan+shop@…) is a different address.
Already has their own dashboard? No problem
Someone who already uses YouSelfBot accepts the invite with the same account. Their own agents stay where they are: they now have two spaces — their own and your team — and they switch between them in the Team section.
Roles
| Role | What they can do |
|---|---|
| Member | reads conversations and replies to customers |
| Admin | the same, plus setting up agents |
| Owner | everything, including money and the team |
The role really does limit things: if someone is a member, the builder won't create an agent on their behalf — and it says so plainly instead of silently doing nothing.
You change a colleague's permissions right there in the list — the change takes effect immediately, with no separate confirmation.
The dashboard looks the same for everyone
The top bar is the same for every role. The difference isn't which screens exist, but what they say: a member who opens Plan sees the current plan and the remaining balance, but instead of buttons there's a line saying that the owner makes purchases. Anyone who opens Team sees an explanation, not a refusal.
The same goes for the conversation: a member who asks to create an agent gets the reason, not an agent.
Who already has access — and how to take it away
The Team section is at the top of the dashboard. It shows everyone who works in your space and every invite that's still pending.
What you can do there:
- change a colleague's permissions — member or admin (a space has only one owner);
- remove someone from the space: their access to conversations, customer contacts and settings disappears immediately;
- revoke an invite sent to the wrong address — the link stops working.
This is access to your conversations with customers
That's exactly why the owner manages the team. A colleague who opens the section sees an explanation, not a refusal.
The same, in words
The owner can tell the builder all of this — it does the same as the buttons, and first asks "Yes" / "No" wherever access is being removed or changed:
| Say | And it |
|---|---|
| "who's on my team?" | lists the people, their roles and the invites still pending |
| "make Olena an admin" / "take admin rights away from Petro" | changes the role after your "yes" |
| "remove Petro from the team" | removes the person after your "yes" |
| "revoke the invite for …" | the link stops working |
To a colleague, or to someone else's program using a key, the builder shows nothing about the team and changes nothing in it.
You can't remove or demote yourself — a space without an owner would be left with nobody who pays and hands out access.
Several spaces for one person
A space is one business: its own agents, its own conversations, its own plan. A person can belong to several: their own, plus the teams they've been invited to.
When you have more than one space, a Where you work list appears in the Team section: next to each one is your role there and a Switch button. Under your email at the bottom of the navigation, it says which space you're in right now — the agents in the list on the left belong to it.
The space is chosen for the whole browser, not per tab. If the dashboard is open in two tabs and you switch spaces in one, the other refreshes itself on its very next action and shows the space you're now working in — the action you clicked there a moment earlier is not carried out, so it doesn't land in the wrong place.
- Each space has its own conversation with the builder. In a team you don't see the conversation about your own agents, and vice versa: the builder doesn't mix up agents from different spaces and doesn't continue in one space what was started in another. Come back to a space — and the conversation is right where you left it.
- You can leave a team yourself: there's a button in the row of the space you're currently in. You can only come back with a new invite. An owner can't leave their own space.
- Someone who only works in another person's team can create their own space: the button is in the same place. It comes with a first agent straight away, and the plan is Free until you choose another one.
- An invite is waiting, but the link is lost? The dashboard says so and offers Start in your own space — the invite stays valid.
You can also switch in words: "switch to my space", "switch to Ivan's team" — the builder switches the dashboard, and a line appears above the conversation field saying where you are now. "I want my own dashboard too" creates your own space; "leave this team" takes you out of the team (it asks for consent first). The conversation with the builder stays in the space where it was started.
Hand an agent over to another person
Inviting someone to your team gives them your whole space: they see all your agents and remain with you. Handing over is different: you give away one agent for good, without giving away the rest and without letting anyone in. This is how you hand a finished agent to a client, a partner or a new owner of the business.
There are two ways, and they are equivalent. One phrase in the conversation:
Hand this agent over to Olena, olena@smak.example.com
The builder asks for your consent and tells you what moves over and what gets erased. Or use the Hand over button in the header of the agent panel: the recipient's email — and Send request.
Only the owner of the space can hand over an agent.
The person must already have an account
The request is tied to the account with that email, not to the address itself. If the person hasn't signed up yet, ask them to create an account (it's free) and try again.
What happens next
- The recipient sees the request in their dashboard: a number appears next to the Team section, and inside the section there's An agent is being handed to you with Accept and Decline buttons. The same in words: "is anyone handing me an agent", "accept the agent from Ivan".
- While the request is pending, the agent keeps working for you as usual. Its panel says who it's being handed to and until when; Cancel handover is right there.
- The request is valid for 7 days. If it isn't accepted, it expires on its own and the agent stays with you.
- As soon as the recipient accepts, the agent moves to them. There's no way back: neither you nor they can undo an accepted handover.
The move is a single action and takes seconds: either the agent is fully with the recipient, or nothing has changed. There's no such thing as half a move. If something got in the way (the agent was in the middle of answering someone and didn't finish, or the recipient has no room for another agent), the recipient sees a refusal with the reason, and the agent stays with you exactly as it was. They can accept again.
For those few seconds the agent freezes: it doesn't answer and doesn't accept changes. A visitor in the chat window or in a messenger reads "the assistant is moving to a new owner right now — please try again shortly", schedules and webhooks wait and fire after the move, and the buttons and the builder say the same and change nothing. This is so that a conversation or a record that started on your side during those seconds doesn't travel to the new owner along with the agent.
You'll be told about an accepted handover through your other agents (an owner notification), and in the Team section it stays in the list of handovers.
What moves over and what doesn't
| Moves with the agent | Doesn't move and is erased |
|---|---|
| character, flow and skills | your keys and connections: action keys, email, calendar, payments, other people's accounts, MCP servers |
| the knowledge base and files the agent sends to customers | the agent's notes about you |
| actions (without your keys) | your personal conversations with the agent |
| schedules | files in the agent's persistent folder |
| the product catalog | channels (Telegram, Viber, WhatsApp, email and others), together with the people linked in them |
| customer conversations and contacts, records collected by the agent, the stop list | access keys of other programs and the agent's secret key |
| the chat window on your site — the same code | postponed work and long tasks |
Credits don't move over: the agent runs on the new owner's plan and uses their credits.
You don't need to change the chat window code on your site — the public key stays the same. During the seconds of the move, the window tells the visitor that the assistant is moving, and after that it answers on behalf of the new owner.
For the new owner: what to do first
Connect your own keys and channels — again, with your own tokens. If an action is missing a key, the agent will tell you which one, rather than answering a customer with someone else's service error. Reissue the agent's secret key (for your own code) in the dashboard. What exactly was disconnected is written in the agent's change log — the first entries after the handover.
Channels get disconnected — and here's why
A bot token is issued by the messenger (in Telegram — @BotFather), and a mailbox password by the email provider; the platform can't reissue them. The previous owner knows them, so with the same token they could keep reading customers' messages and writing to them as the bot. That's why channels are disconnected on handover, and the messenger is unsubscribed from the platform: the new owner connects them with their own tokens (their own bot, their own mailbox).
Trigger webhooks move over, but get a new signing secret — the previous owner knew the old one too. The secret is shown only when it's created, so the webhook has to be created again. Customer conversations from disconnected channels stay in the agent's history.
When there's no room to accept
How many agents you can have is decided by the plan. If the recipient has no room left, this is said right away, in the request itself — together with a way out: delete an existing agent or switch to a plan with more agents. Until then the Accept button is disabled, and the request stays valid.
The agent always lands in the recipient's own space — even if they're currently working in someone else's team. If they don't have their own space yet, it appears empty, together with the agent.
How many agents are allowed
This is decided by the plan, not the team: Free — one agent, Starter — one, Pro — three, Business — unlimited. See How much it costs.
If you ask to create one more agent beyond the limit, the builder passes on the refusal word for word — with the reason, not as "something went wrong".
Next
- How much it costs — plans and limits.