Who: Admins and Members · Where: Workforce › Catalogue, open a use case, then Activate · Works on: Enterprise and SaaS (on SaaS, the plan must have room for the agents and workflows it creates)
Activate a use case
Four steps follow Activate: Connect, Documents, How it runs and Build. Move between them with Back and Continue.1
Connect
Connect what it reaches for lists only what this use case touches. Each toolkit shows one of these:
- Ready: it is connected.
- Connect: opens the connection form in a new tab. An administrator connects a toolkit once, and every use case that needs it can then use it.
- Ask an administrator: you cannot connect it yourself. See the list after these steps.
- We arrange it: your installation cannot connect this toolkit yet; we set it up with you.
2
Documents
Point it at your documents. For every document set the use case reads, choose one of your knowledge bases, or Create “…” to create one named after the document set. A knowledge base with the same title is preselected.New knowledge bases are created empty. Add the documents after activation; indexing takes minutes. They get the same audience you choose under Who can use it in the next step. A use case that works on the files handed to it at run time needs no knowledge base, and the step says so.
3
How it runs
How it starts, and who signs off. The use case proposes both, and you can change them now or later.
- How it starts: the options the use case allows, from When someone starts it, from the workspace or through the API, On a schedule and In a conversation.
- Who approves as a role: for every approval in the use case, an admin picks the groups whose members decide.
- Who can use it: Only me, for now, Everyone at your organization, or Specific groups (admins only).

4
Build
This step runs by itself. It creates the knowledge bases you asked for, then the draft (Create the draft). You land on Your draft is ready, with a summary, the list Before you publish, and Open the draft.
- Enterprise: admins. Members see Ask an administrator.
- SaaS: admins and members.
Before you publish
The list on the last step names what is left to do. It can include:- a toolkit that is not connected yet, so steps that use it fail until it is
- a toolkit your organization has no connection of that kind for, which was left off the agent: connect it, then add it to the agent
- an approval with nobody set to approve it
- a schedule that is switched off: switch it on once the workflow is published
- one of your own systems that is not connected yet
- a knowledge base that has no documents yet
Try it, then publish
The draft is a normal item in Agents or Workflows. Nothing can run it until you publish it: a schedule on it starts no run, an agent cannot run it as a workflow, and nobody can start a task with it. Run it on two or three real cases with the people who own the process. Then publish it from the workflow designer or the agent studio, the same way you publish anything else. Once a use case is activated, its page offers Open in Agents or Open in Workflows instead of Activate.Details
Schedules
Schedules
For On a schedule, enter a Schedule (cron) expression of five fields and a Time zone. Next runs shows the next three times. A schedule can fire at most every 15 minutes (the default limit), and it is created switched off. See Schedules.
Approvals
Approvals
Approvals land in the Inbox, and nobody approves their own run. If you choose nobody (Decide later), only admins, or members of a group with that role’s name, can decide that step.
Who can use it on a SaaS personal account
Who can use it on a SaaS personal account
Only Only me, for now is offered, because a personal account has nobody to share with.
When the build fails
When the build fails
The step shows why and offers Try again, which repeats only what failed. A knowledge base created by an earlier attempt is found by its title and reused.
The model of an activated agent
The model of an activated agent
An activated agent runs on your installation’s default model. You can change it in the agent’s AI model section.
Plan limits (SaaS)
Plan limits (SaaS)
Activation creates agents and workflows, which count toward your plan’s workers. When the plan has no room for them, Activate is disabled and its tooltip says how many are needed.