Sharing and access

A new agent is private, only you see it. You can share it with the whole workspace or with selected members. You can also provide it in Microsoft Teams or to a client, or pass it on as a copy.

Share an agent with the workspace

You change the visibility with a chip. It is in the header of the editor and in the column Visibility of the list. The visibility is not in the row menu.

Set the chip from Private to Workspace. Everyone in the workspace then sees the agent and can chat with it. Anyone who may build (the role admin, or the former role developer) can edit it. No copy is made, there remains one agent.

You can set it back to Private only when no workflow that is visible to the team uses it any more.

Restrict access to selected users

If an agent is set to Workspace, an admin can decide who uses it.

1. Click the chip Workspace.
2. Click the entry Access. The dialog Access opens.
3. Choose Selected users.
4. Tick the people who should use the agent.
5. Click Save.

After that, only the author, the selected people and everyone who may build see the agent. Admins always have access. Only members with the role member can be selected, because everyone who may build sees the agent anyway.

If you later switch back to All users, the list of selected people stays saved. Access to the base chat cannot be restricted.

Workflows have the same chip and the same dialog, with the same rules. If someone loses access to a workflow this way, their setup is paused.

Provide an agent in Microsoft Teams

You can link an agent that is set to Workspace and has no restricted access to a Teams bot. Colleagues then write to it in a 1:1 chat in Microsoft Teams. How to set up the bot is described under Microsoft Teams.

Provide an agent to a client

You provide an agent to a client in the client's client workspace. This works only as a partner. A partner is an organisation with one client workspace per client.

1. Build the agent in the client workspace, or bring it there with Share as link.
2. Set it to Workspace.

The client's people use the agent but see no build functions. An admin of the client can still set the access.

Pass an agent on as a copy

Share as link and Export are in the row menu of the list. Both pass on a copy. Your agent stays unchanged.

For an agent with a price, both entries are missing. An agent with a custom integration can be neither shared as a link nor exported.

Share as a link

1. In the row menu, click Share as link.
2. Copy the address from the dialog.

The link always delivers the state shared last. If you share again, the address stays the same. Revoke link in the same dialog withdraws the link.

Install from a link

Whoever opens the link lands on the page Install agent.

1. Fill in the variable fields.
2. Click Install.

The page of the new agent then opens. An imported agent arrives restricted:

• Use knowledge is off.
• It uses only the skills attached to it.
• Skills that came along are switched off and private.

Export and import

Export downloads the agent as a file with the extension .agent.json. To take the file in again:

1. Open an empty chat.
2. In the tile row, click +.
3. Choose Import agent.

The import works like installing from a link. What the export contains of the knowledge is described under Knowledge.

Permissions

For people with the role member, the chip only shows the state. Share as link and Export are missing from their row menu.