A teammate cannot see the chatbots

What it is

A teammate accepted your invitation, signed in, and sees nothing. This is the most common team support question in the product, and it is almost never a fault.

Six causes, ordered by how often each turns out to be the real one:

1. They are in their own workspace. Accepting an invitation grants access; it does not move them into your workspace. This is the answer roughly nine times out of ten.
2. Their chatbot access is set to Selected chatbots and the list is short, empty, or missing the chatbot they are asking about.
3. A chatbot you created after inviting them was never added to their selected list. New chatbots are not added automatically.
4. A custom role without the view-chatbots permission. Only possible on a Custom role; every preset includes it.
5. They never actually accepted, or their membership was removed.
6. The workspace itself is unavailable because its owner's account is suspended or scheduled for deletion.

Where to find it

Dashboard → Settings → Members on your side, to check their role, status, and chatbot access.

Dashboard → Accounts on their side, to switch workspaces.

Steps

Do these in order. Stop when one of them explains it.

1. Ask them to switch. Have them open Dashboard → Accounts — or the account switcher in the user menu — and choose your workspace under Accounts I joined. The dashboard reloads and your chatbots appear. See Switch accounts.
2. Ask what the switcher says. When they are in someone else's workspace it reads Acting in {your workspace name}. If it shows nothing of the sort, they are in their own.
3. Check they accepted. Open Settings → Members. If their row is under Pending invitations rather than Members, the invitation is still outstanding. Re-send it if needed — and note that re-sending invalidates the previous link, so they must use the newest email.
4. Check their chatbot access. Their row shows either All chatbots or {count} selected chatbots. If it is selected, open Edit access and confirm the chatbots they need are actually ticked.
5. Check their role. Admin, Editor, and Viewer all include viewing chatbots. A Custom role might not — open Edit access and confirm the Chatbots group has at least the view permission ticked. See Roles and permissions.
6. Ask them to reload. Access changes apply on their next action, but a page they already had open may still show the old navigation.

The switching problem, explained

It is worth understanding why this happens so often, because the explanation is what stops it recurring.

Everyone who signs up gets their own workspace. When you invite someone, they still have that workspace, and it is where they land by default. Your invitation gives them the right to enter yours; it does not put them there.

So a new member's first experience is signing in and seeing an empty dashboard that looks exactly like a broken invitation. Nothing is wrong. They are standing in the wrong room.

The cure is a sentence in your welcome message: "After you accept, open Dashboard → Accounts and switch into our workspace." Send them Switch accounts with the invitation and you will never have this conversation.

Selected chatbot access, and its gotcha

If you limited someone to specific chatbots, they see only those. That is the setting working.

The part that catches people: chatbots you create later are not added to their list. A member scoped to two chatbots stays scoped to those two forever, even after you build a third and expect them to work on it.

If a member says "I can see the old chatbots but not the new one", this is it. Open Edit access, tick the new chatbot, and save — or switch them to All chatbots if the restriction has stopped being useful.

What they will still not see

Even with everything correct, some things are invisible to a member and this is not a bug:

• Settings → Billing and Settings → Developer are owner-only, always. See Why Billing is missing.
• Settings → Members appears only for the owner and members whose role includes managing members.
• Delete on a chatbot is not available to an Editor.

If their complaint is "I can see the chatbots but I cannot do X", that is a role question rather than a visibility one.

Limits and plan notes

Paused chatbots still appear in the list for anyone who can see them. If a member says a chatbot "is not working" rather than "is not there", they may mean it is paused.

A pending invitation grants nothing but still consumes a seat. See Seats and billing for teams.

Removal takes effect immediately. If access disappeared mid-session, check whether they were removed — the dashboard drops a removed member back into their own workspace, which looks a lot like everything vanishing.

Their own workspace is unaffected the whole time. Anything they build there is separate from yours and does not transfer.

If nothing here works

Write to support with:

• the account owner's email address and the member's email address,
• the role and chatbot access shown on their row in Settings → Members,
• whether their row is under Members or Pending invitations,
• what their account switcher shows,
• the time they last tried, with their timezone.

See Contact Support.

Common problems

They switched and still see nothing.

Their chatbot access is Selected chatbots with an empty or wrong list, or they have a custom role missing the view permission. Both are on their row under Edit access.

They see two chatbots and I have ten.

Selected chatbot access. Tick the rest or move them to All chatbots.

They built a chatbot and now nobody can find it.

They built it in their own workspace. There is no way to move it — it has to be rebuilt in yours, which is exactly why the switching step matters on day one.

They keep getting an access error and land back in their own account.

Their membership ended, or your workspace is unavailable. Check whether their row is still on the Members table; if it is not, invite them again.

Can I give them Billing so their screen matches mine?

No. Billing and Developer are owner-only and cannot be granted to any role.