Lesson 7 of 11 · 10 min
Creating and sharing the assistant
Bring instructions, sources and tools together in a project’s assistant or a console assistant, test it, then open it to the team.
Instructions, sources, tools and guardrails are ready. What remains is to bring them together in an assistant the team can open by itself. Learnya offers two paths. A project’s assistant serves the members of that project. A console assistant serves several teams, or the whole organisation.
- Open “Projects” and create the team’s project with “New project”. For an existing project, choose “Edit” in its menu.
- Paste the tested instructions into the “Project knowledge” field. The agent keeps them in mind in every conversation of the project.
- Place the reference documents in the project’s Drive.
- Invite the future users to the project. They find the same documents and the same framework, without sharing file by file.
- Click “Start a conversation” and run the test set again before announcing the assistant.
The administration console brings together the workspace’s assistants. Access to it depends on your role, and it is often the administrator who runs it. If that is not you, prepare the assistant’s profile and set it up with the administrator, screen by screen.
- In the console, open “Assistants”, then click “Create an assistant”.
- Fill in “Name”, “Instructions” and “Model”. Leave the “Visibility” on “Private” until testing is finished.
- In the “Knowledge” tab, link the base that holds the reference documents.
- In the “Tools” tab, keep only the tools you selected.
- In the “Test” tab, run the test set again. Each try opens a “Studio test” conversation that also shows the “Tools called”.
- When the threshold you set is reached, open the “Settings” tab and switch the “Visibility” to “Organization” or “Workspace”, depending on the intended audience.
Sharing an assistant is more than making it visible. Open it first to two or three colleagues and gather their feedback. Then announce it to the whole team with three examples of questions it handles well and one it does not handle. Say who keeps it up to date and where to report an error.