Identity
An identity is a service account named like the agent. It has no password, it never signs in and it is never an administrator. It can read and work only in the Spaces where it was added, like a person with their own login.1
Switch on the identity
In the Identity card, switch on Own identity. The card now shows the agent with the label Service account.
2
Add it to a Space
Under Access, select Add to a space and pick a Space. Until you add the agent somewhere, it can neither read nor change anything.
3
Choose its role
Set the role in that Space to Can read or Can read and work. New entries start with Can read and work. An identity never manages a Space.
Mention an agent in a comment
When you write a comment on a work item or a page and type@, the picker offers agents next to people. An agent appears when all of these hold:
- You may see the agent.
- Its identity is a member of the Space of the work item or page.
- You typed at least one letter.
What an agent writes
Work an agent does with its identity is recorded under the account of the agent. After the identity is removed, the account stays anonymized so that what it wrote keeps an author that can no longer act.Jobs
The Jobs card lists what starts the agent. Each job holds a task: what the agent should do when the job starts. The agent also receives what started it, such as the comment or the work item, as data that it reads but never follows as instructions. Up to 20,000 characters of it reach the model.Start on an event
Four switches under Start on an event cover the common cases. An agent has at most one job of each of these kinds.
A job for a mention or an assignment runs as the agent’s identity. It starts only when that identity may open the work item or page. A mention or assignment job stays off and says “Turn on the identity of the agent first” until the agent has an identity.
Switching a job on for the first time opens a dialog. Choose the automation workspace where the job lives, write the task and save.
Schedule and web address
Scheduled and Webhook jobs can be added as often as you need, up to 20 jobs per agent.Where a job runs
Each job lives in an automation workspace that you choose when you add it. Collabase creates a flow there with one trigger and one Agent step that carries the task. Change the job in the card.- You need the editor role in that automation workspace to add or switch on a job.
- A sensitive automation workspace cannot hold a job, because its flows need an approval. The dialog says so.
- A job that does not use the agent’s identity runs as the service account of its automation workspace, never as a person.
- Tools of the agent that ask first need approvers, as in any Agent step.
State of a job
Each job shows its automation workspace, a switch, and the result of its last run: Not run yet or Last run with the status. Two warnings can appear.
Select the pencil to change the task or the schedule. Select the bin to delete the job. Deleting removes the job, its flow and its run history, and the agent stays.