Sharing with Teams: what changes
With Teams, the way agents and knowledge are shared in your organisation changes. This page describes what changes for whom, what happens to your existing links, copies and embeds, and what can be undone.
As long as Teams is not enabled for your environment, nothing changes: ChatBot links, view links and embeds work exactly as before. Everything on this page applies from the day your environment moves to Teams. We agree the date with you beforehand.
The features described here are being introduced step by step. Before the move we go through with you which of them are already available for your environment.
Why sharing changes
Until now, a project reached people outside it in three ways:
- ChatBot link (
/s/…): everyone who opened it got their own copy of the project. - View link (a ChatBot link with the option “Share this agent itself”): whoever opened it was added to the project as a viewer.
More on both variants: Sharing agents.
- Embed: visitors to a website chatted anonymously, each in their own copy.
With Teams this no longer fits. A copy belongs to the person who opened it, not to the team. It therefore has none of the team's knowledge, tools or logins, and a ChatBot answered worse than the same agent inside the team. There were also two models side by side: teams decided who reaches what, and links went around that.
With Teams there is therefore one model:
- Sharing goes through teams. Whoever should use an agent is a member of a team the agent is granted to.
- An administrator approves whatever reaches everyone or the public. For the whole organisation there is the built-in “Everyone” team, for websites the ChatBot.
- Chats stay private. Members of a team, “Everyone” included, can't see each other's chats, memories or logins.
What changes for users
ChatBots become agents in “Everyone”
An agent that a ChatBot link used to hand out is found in the “Everyone” team from now on. Everyone who can sign in to your environment belongs to “Everyone” automatically, with the Viewer role. So nobody needs to send you a link any more: as soon as an administrator releases an agent to “Everyone”, “Everyone” appears in your team switcher and you can chat with the agent.
Unlike in the copy, you use the real agent there, with the knowledge “Everyone” and its project provide. Your chats in it are private.
Join links instead of view links
With Teams there are no new view links, not even for personal projects. To share a project with others, put it into a team. To bring people into a team, team admins can send a join link. Whoever opens a new join link while signed in asks to join, and a team admin approves the request; then they are a member of the team with the Viewer role. A link set to Open, and every join link that existed before this change, lets people in at once.
Existing chats and copies stay
- Chats you had through a ChatBot link in your own copy are kept and can still be opened. As a rule you can also keep writing in them. In environments whose ChatBot chats are carried over, your copy becomes a chat in a project in “Everyone” (see Per environment). No new copies are created.
- Projects you were added to through a view link stay accessible. Your Viewer role there does not change.
What an old link does now
| You open … | With Teams |
|---|---|
an old ChatBot link (/s/…) | You land on the agent in the “Everyone” team if it has been released there. Otherwise a page says the ChatBot has moved and whom to ask. |
| an old view link to a team project | You are not added any more. The page names the project's team and offers a join link if the team has published one; otherwise ask a team admin to add you. |
| an old view link to a personal project | You are not added. The page names the owner; ask them to share the project through a team. |
| a join link that has expired, been switched off or used up | The page names the team and asks you to contact a team admin. |
For other links there is no request to send; ask the person named directly.
| You open a join link that is … | With Teams |
|---|---|
| set to Ask first (the default for new links) | Your request is sent to the team admins. You become a member once one of them approves it. If it is declined, the page says so and asks you to contact a team admin. |
| set to Open (including every link from before this change) | You join at once. |
If a team admin removed you from a team, no join link of that team adds you again, open links included: you can only send a request, and a team admin decides. An invitation made before you were removed no longer works either; a new one does.
What changes for team admins
Join links
Team admins create join links on the Members tab of the team settings. Each link has a joining mode:
- Ask first (the default for new links): whoever opens the link asks to join. The requests are listed above the members, with a note when someone's sign-in does not confirm their e-mail address; a badge on the team switcher and on the Members tab shows how many are waiting. Approve adds the person as a viewer and tells them in the app; Decline keeps the request, and no link of the team admits that person unless an admin approves the request after all or adds them.
- Open: whoever opens the link and signs in joins at once. Join links that existed before this change keep working this way.
You can switch a link between the two at any time. A join link
- always grants the Viewer role. Editor and Admin are still given through the member list;
- if it is open, can be restricted to e-mail domains, such as
city.example. Then only people whose sign-in confirms an e-mail address in that domain can join. Someone whose sign-in does not confirm their address is turned away with a page that says so. The option is only offered when your environment has a sign-in that confirms e-mail addresses: the sign-in BasePeak runs for your environment, Google, GitHub or an e-mail login link. A separately added sign-in of your own (such as OIDC, Nextcloud or Entra) does not count. Without one, the option does not appear; - can have an expiry date, and if it is open, a maximum number of uses;
- never lowers anyone: a member who already has a higher role keeps it;
- requires signing in. Someone who isn't signed in signs in first and then joins. A join link never grants anonymous access.
When you switch a link off or delete it, nobody can join through it any more. People who already joined stay members; remove them in the member list if needed. Someone you remove from the team cannot come back through any join link of the team, not even an open one: they can only send a request, which is marked “Removed from the team by … on …”. An invitation made before the removal no longer admits them. Approving the request, adding them by hand or a new invitation lets them back in.
Personal teams and “Everyone” have no join links: a personal team is yours alone, and everyone already belongs to “Everyone”.
Join links come in addition to the existing invitation links, which can be redeemed once, within 7 days, with a chosen role; those stay as they are.
Overlays: tuning an agent for your team
Agents are built by the instance's administrators and granted to teams. A team admin can add to a granted agent for their own team without changing the agent itself (an overlay). An overlay may
- append instructions to the prompt (the original prompt stays);
- add knowledge;
- switch on tools the agent already offers.
An overlay can't change the model, replace the original prompt or add new tools. Projects still carry project context, not per-agent settings.
You open an overlay under Team settings → Agents with the sliders icon next to the agent (“Customise … for this team”). Optional tools are switched on there, per agent, and no longer for the whole team.
Team tools from before: tools you switched on for the whole team under Tools & credentials keep working in every chat of the team until an administrator completes the switch. Each one then moves once into the overlay of every agent of the team that offers it as an optional tool. An agent that always has the tool needs nothing. An agent that does not offer the tool no longer gets it in your team; if you still need it there, ask the agent's owner to offer it before the switch.
Team-level logins
Tool logins meant for the whole team are set up by team admins in the team settings, not in a chat. A login you enter in a chat is always personal; there is no “save for the whole team” option in the chat.
A chat looks for a login in this order: your own, then the project's, then the team's, then the agent's.
Team logins you saved so far under Team settings → Tools & credentials keep working unchanged. Until an administrator completes the switch, they are listed under Tools & credentials as “Sign-ins from before team logins”; there you can remove them, but not change them. The switch then moves each one once into the team login of the tool that needs it. If a team admin has signed in to that team login in the meantime, their login wins. A login that no agent of the team uses any more is not moved and keeps working.
Publishing a ChatBot for your website
With Teams, projects can no longer be embedded. Their place is taken by the ChatBot: a chat window for your website, bound to an agent of your team, that uses a fixed, read-only version of that agent. Visitors only reach what the approved version exposes. They never reach into your team directly: no team chats, files, memories or logins.
- Under Apps → New → ChatBot, pick an agent your team can use. New ChatBot on the agent's page leads to the same place.
- In the ChatBot editor, set the greeting, colour, allowed websites, budgets and limits, which knowledge sets are searched, and whether sources may be opened as links. The ChatBot can have additional instructions of its own.
- Publish creates a numbered, immutable version. The screen shows the changes since the live version and exactly what visitors can reach: knowledge sets, tools, accounts, budgets and websites.
Approval: an instance administrator always approves the first version before it goes live; a version an instance administrator publishes counts as approved. A later version needs approval only when visitors can reach more than before, such as a new knowledge set, a new tool or account, another website or a higher budget. Changes to instructions, model, colour or greeting go live without approval, as does going back to a version approved earlier. Until a version is approved, the previous one stays live.
Further rules:
- The embed code stays the same across all versions.
- A ChatBot never uses a personal login. Tools that need a login only work with an account an administrator has set up explicitly for that ChatBot. Tools an administrator configured for the whole instance keep working.
- A ChatBot has no memory.
- New documents in an approved knowledge set are available at once, without a new version.
- Your team sees the usage (questions per day, tokens, budget left). It sees the full visitor chats only if an administrator allowed that when approving.
What changes for administrators
The “Everyone” team
“Everyone” is a built-in team that exists once in every Teams environment. It can't be deleted, renamed or left.
- Members: everyone who can sign in, as Viewer, without you adding anyone. The member list shows them all as a single row All users (N). Internal and technical accounts (ChatBot visitors, API keys, support logins) are not included.
- Curators: people who should maintain the knowledge in “Everyone” are added with the Editor or Admin role, as in any team.
- Release: only instance administrators can release an agent to “Everyone”. That release is the step where you decide what the whole organisation can reach.
- Visible in the team switcher only once something has been released to it. Until then nobody sees an empty team.
- Knowledge goes into the team itself or into projects inside “Everyone”.
A former ChatBot link therefore becomes: the agent, released to “Everyone”; optionally a project in “Everyone” with the former project's instructions, knowledge and files; optionally an overlay for ChatBot-specific tuning.
Releasing existing ChatBot links in one step
When Teams is switched on for your environment, BasePeak.AI offers you a list
of all existing ChatBot links with one action, Release to “Everyone”. It
releases the agent of each selected link to “Everyone”, so old /s/… links
have a target from the start. Untick whatever you don't want to release.
Approving ChatBots
Approval requests for ChatBots appear in the Inbox. The card shows what visitors can reach and highlights what is new compared with the live version. You choose Approve & go live or Reject with note. A rejected version stays in the version list with your note.
Under Admin you see every ChatBot of every team, with its live version and status, and can take any of them offline at any time. A ChatBot taken offline no longer answers on the website. A ChatBot stays live when its team or its agent is deleted; the list then marks it “source deleted”.
Moving team logins and team tools
Team logins and team-wide tools from before Teams (see the team admin section above) move once. We agree the time with you and then start the switch; until then, nothing stops working. Beforehand, a trial run lists for each team which login moves to which team login and which tool goes to which agent, and what stays or is dropped. It changes nothing. We go through it with you, so that a tool an agent does not offer can be added to that agent first.
Logins in “Everyone”
A team-level login in “Everyone” is in effect a shared account for the whole organisation. That is why only instance administrators can set one up, not the admins of “Everyone”.
A ChatBot's visitor chats
Whether the publishing team may read a ChatBot's full visitor chats is decided when you approve it; you can change it later on the ChatBot's page. Without that permission the team sees usage only. Instance administrators can always read visitor chats. Visitor chats follow your environment's retention period.
Per environment
Environments without Teams
Nothing changes.
Environments with Teams
- Embeds become ChatBots automatically, with the same ID. The code on your website stays the same and does not have to be replaced. The ChatBot is already approved and takes over the project's instructions, tools, model choice, knowledge sets, budgets and allowed websites. Files in the project's workspace are not carried over. Ongoing visitor conversations start afresh.
- Stored logins of an embed are copied into accounts of the ChatBot, but stay switched off until an instance administrator confirms each one. In the past a personal login entered in a chat could also end up among the project's logins, and the two can't be told apart afterwards. Until it is confirmed, the tool that needs it is unavailable to visitors; the ChatBot itself is live at once. Pending confirmations show in the Inbox.
- Copies from ChatBot links are kept as legacy. They can be opened and written in; no new ones are created.
- Team logins from Tools & credentials are carried over once to the team level, and team-wide tools into the agents' overlays, when an instance administrator completes the switch. Until then both keep working.
- Join links that already exist stay open. New ones ask first by default.
Until the ChatBot widget is available for your environment, existing embeds keep running unchanged. New embeds can't be created in that time.
Environments whose ChatBot chats are carried over
For environments where we have agreed it, we carry the chats from ChatBot links over into the “Everyone” team, once:
- The agent of each ChatBot link is released to “Everyone”.
- A project is created in “Everyone” with the former project's instructions, knowledge and files.
- Each copy becomes a chat of its owner in that project, with all its messages and files.
Before that we run a trial run that changes nothing and lists what would be carried over and what stays. We go through it with you before the real run.
- What is carried over is what still exists at that time. Copies your environment's retention period has already removed can't be brought back.
- Anonymous visitor copies from embeds belong to no signed-in person. They stay as read-only legacy and are removed after the normal retention period. The carry-over deletes nothing.
What becomes what?
| Before | With Teams |
|---|---|
ChatBot link (/s/…) | Agent released to “Everyone”, optionally with a project in “Everyone” as context. The old link leads to the agent in “Everyone”. |
| Copy from a ChatBot link | Stays as writable legacy. In environments with a carry-over: a chat in a project in “Everyone”. |
| View link | Retired. The old link adds nobody any more and points to the team. Instead: a join link to the team. |
| Access gained through a view link | Stays unchanged as the Viewer role in the project. |
| Embed | ChatBot with the same ID, already approved; the website code stays the same. |
| Visitor copy of an embed | Stays as read-only legacy until the retention period; not carried into the ChatBot. |
| Team login from “Tools & credentials” | Carried over once as a team-level login, managed by team admins. |
| Team-wide tool from “Tools & credentials” | Carried over once as an optional tool, switched on in the overlay of each agent of the team that offers it. |
| Join link from before this change | Stays open: people join at once. New links ask first by default. |
| Memories from before Teams | Carried into your private memories, as a memory for the project or team they came from. Nothing is lost. |
Timeline and the way back
- Date: we agree with you beforehand when your environment moves to Teams. The changes on this page apply from that day.
- Embeds keep running until the ChatBot widget is available for your environment, and are then converted automatically.
- The move to Teams is final. It is not reversed. ChatBot links and view links don't come back.
- What can be undone:
- A release to “Everyone” is withdrawn by removing the agent from “Everyone”.
- A join link can be switched off or set to Ask first; members are removed in the member list.
- A tool carried into an overlay can be switched off there.
- A ChatBot can be set back to an earlier approved version or taken offline.
- A carried-over ChatBot account can be deleted instead of confirmed.
- Contact: your contact at BasePeak answers questions about the move.
More on teams, roles and team settings: Teams.