Team
Build a project team of people and AI agents, organize them into a reporting hierarchy, and configure each agent's model and behavior from the project's Team tab
The Team tab is where you staff a project with the people and AI agents that do its work, and arrange them into a reporting hierarchy. People come from your directory; agents are configured here with a model and behavior. Open it from the Team tab inside any project workspace.

The org chart shows the whole team at a glance — people and AI agents (tagged AI, labeled with their model) connected by reporting lines.
People and agents
A project team mixes two kinds of members:
- People — members drawn from your organization's directory. Each carries their directory identity (name, email, job title, department). The project's agents know each person by their directory name, too. Someone your directory has deprovisioned or suspended stays on the team, and agents are told so: an agent that messages them or gives them work is refused, and has to address a current teammate instead. Nobody else can message them or give them work either, since they cannot sign in to see it. The tasks they already hold stay theirs until someone reassigns them, because a suspension can be lifted.
- Agents — AI agents you create on the project, each backed by a model and an optional behavior prompt.
Both kinds share one reporting hierarchy: any member can report to any other member, whether person or agent. The Team header shows the total member count for the project.
Who can change the team's people
A place on the team grants nothing by itself: what someone may decide on a project comes from their access level on it. Adding a person, changing a person's reporting line and removing one need Write access to the project, and the person you add must already hold Write or above on it, so Add person offers only those people. To add someone who does not, share the project with them at Write first.
Anyone with Read access still sees the whole team, but Add person, a person's Reports to (org chart) and Remove from project are disabled for them, with a reason naming the Write access they need. A project starts with whoever created it on its team, unless a Platform Admin created it.
Agents follow the same levels. Adding an agent and changing its settings need Write. Changing an agent's autonomy, deleting an agent and deleting the project with its whole team need Admin. Levels are given per project, from its Share dialog. Admin on the project's organization, or a role on Access holding Administer every organization or Administer every project, also gives Admin on it.
Org chart and list views
Switch between two views of the team using the toggle in the Team header:
- Org chart — a visual hierarchy. People appear as cards with their initials; agents appear as cards tagged AI and labeled with their model. The chart fills what the tab has left of the window and refits when the window changes. Paused agents are dimmed, and a dimmed agent is genuinely idle: it is not beating and not spending. While the team runs, a running agent's card is ringed in green with a dot before its name, and while its latest beat has recorded an action, the line under its name shows that action in place of its model: in green, or in red when the beat failed. Hover the dot to read Running, or the line to read the whole action. Every member with no manager sits at the top of the chart, with no line to anyone: a line is drawn only where a member reports to another. Click any card to open that member's details. When viewing the chart, use Fit to screen, Expand all, and Collapse all to navigate large teams.
- List — a sortable table of every member. A running agent carries a Running badge in its Status column.
A person who has left your organization — your directory has deprovisioned them — stays on the team until you remove them, but reads Name (former user) and is dimmed, here, in their detail panel and on the project's Overview graph. A person your directory holds no record of is named the way the Interactions tab names them, and reads Former user when the directory cannot name them.

List view shows people and agents together. The Title / Model column holds a person's job title or an agent's model, which is why one column carries both.
In the list view you can:
- Search members by name, title, email, or model.
- Filter by type — All types, People, or Agents.
- Filter by status — All statuses, Active, Paused, or Archived (agents only; people have no status).
- Sort by Name, Type, or Title / Model.
Assistants
Beside the org chart, a narrow strip holds the project's assistants: the Dashboard Assistant, Team Builder and the Integrations Assistant. They aren't on the team, take no tasks and message no agents. Click one to open its chat, or + to add one.
Adding a person
Click Add person to assign someone from your directory to the project. It needs Write access to the project, and offers only the people who hold Write or above on it — see Who can change the team's people.

Search your directory, select a person, and choose who they report to before adding them to the project.
Open the panel. Click Add person in the Team header. The panel explains that you are adding someone from your directory.
Search the directory. Type a name, email, or department in Search directory. People already on the project are excluded from the results, and so are people who hold less than Write on it.
Select a person. Click a candidate in the Select person list to choose them.
Choose a manager. Reports to starts at a person at the top of the org chart who has not left, or at No manager (top level) when there is none. Pick another team member to place the person under, or No manager (top level) to add them at the top.
Add to project. Click Add to project. The person joins the team and appears in both views.
You choose a person's manager when you add them, and you can change it later: open the person from the org chart or list, pick a new manager under Reports to (org chart) in their Project assignment card, and click Save and close at the foot of the panel. Agents' reporting lines are editable the same way (see Configuring an agent).
Adding an agent
Click Add agent to create an AI agent on the project, or choose Create → AI Agent at the right of the top header, which opens the Team tab and the same panel from any tab of the project you have open. It needs Write access to the project: anyone else sees it disabled, with a reason naming the Write access it needs. On an Archived project it is disabled for everyone, and Create → AI Agent is also disabled while no project is open.

Give the agent a name and the model that powers it. Its heartbeat and governance start from safe defaults, which you can change before you add it.
Open the panel. Click Add agent. The From scratch tab is selected by default. To start from a configuration your organization already has, use From template instead.
Choose an avatar. Pick Initials (auto-derived from the name) or an Icon.
Name the agent. Enter a Name of up to 120 characters — this is required. It must differ from the name of every other agent, and every person, on the project's team by more than case, symbols or extra spaces.
Describe it (optional). Use Description to note what the agent does on the project.
Pick a model. Select the Model that powers the agent. The list comes from the chat models available to your tenant, each named with the provider it runs on, so two providers' models of one name read apart — see Model Providers. A decision model writes no text, so it cannot run an agent and is not listed. The optional Decision model offers decision models only: see Decision model.
Set behavior (optional). Use Behavior (system prompt) to describe how the agent should act and what it is responsible for.
Choose a manager (optional). Reports to starts at a person at the top of the org chart who has not left, or at No manager (top level) when there is none. It never starts at an agent, because an agent manages its reports' tasks. Pick another member, agent or person, to place the agent under, or No manager (top level) to add it at the top.
Set its heartbeat (optional). Under Heartbeat, switch on Automatic heartbeat to let the agent beat by itself while the project is running, and set its Interval (seconds), Autonomy, Max actions per beat, Max tool calls per beat and Events per beat. They start from the defaults of its Heartbeat settings: off, 300 seconds, Manual approval, 3 actions, 5 tool calls and 10 events, and take the same ranges. Only someone with Admin access to the project can choose an autonomy above Manual approval: for anyone else Autonomy is disabled, with the reason.
Choose its governance (optional). Under Governance, choose the policies, guardrails and egress allowlist the agent starts under. Baseline safety is ticked for you. This section needs the governance permission: without it the panel says the agent starts with nothing attached, and someone who manages governance attaches it on the agent's Guardrails tab.
Add the agent. Click Add agent. While it is disabled, the line under it names what it still needs, such as a name. The agent joins the team with Active status. If you switched on Automatic heartbeat and the team is running, it starts at once, with its first beat due straight away.
Adding an agent from a template
An agent template is a complete agent configuration your template admins, the holders of Manage agent templates, keep once and grant to organizations. The From template tab lists the published templates granted to this project's organization, and the platform's own, with a badge on each: Ready when everything it names applies here, or how many items are not available.

What the template applies here, and what it does not and why, is shown before anything is created.
Pick a template. Search the gallery or narrow it by category, and select a card. The panel shows what the template will be applied as here: each skill, tool, policy, guardrail, egress allowlist, workspace folder and knowledge pack it names, under Applied or Not applied, and why each one is not applied — not granted to this organization, not adopted, a draft, unpublished, and so on. An item matched by an equivalent, such as a skill or knowledge pack of the same name, says so. Folders the template names that this project does not have yet are listed as folders it will create, for people with Write access to the project or above, who may create folders; for anyone else they are not applied.
Fix what you can (optional). Someone who manages the item sees how to fix it beside it: Grant to this organization for a tool server or a knowledge pack, Adopt for a platform skill, Activate for a draft guardrail, policy or allowlist. The panel then reads the template again.
Name the agent. Enter its Name, and change its description, avatar and manager if you like. When the template's model is not one of your tenant's, pick a Model: the template's is shown as a hint.
Check its heartbeat. The Heartbeat section starts from the template's. The autonomy line says what the agent will start at.
Acknowledge what will not be applied. When anything is not applied, tick I understand N items will not be applied, and the button reads Add agent (partial).
Add the agent. While the button is disabled, the line under it names what it still needs (a name, a model, heartbeat settings in range or your acknowledgement), and the panel says so when no agent can be made from this template here: among other reasons, when it gives the agent a knowledge pack the organization holds that no group of yours grants, since an agent gets only the packs the person making it can read. The agent is a copy of the template's published version, with the template's prompt, goals, model settings, skills, tools, governance, workspace access and knowledge packs, with their notes, as the panel showed them. If any of that changed since you opened the template — a tool granted, a guardrail activated, a new version published — the panel says so and shows the template again, so you never add an agent you have not reviewed.
Two things keep an agent made from a template safe:
- A missing control starts it at Manual approval. When a guardrail, policy or egress allowlist the template names is not applied, the agent starts at Manual approval whatever the template's autonomy, so every action it takes is a proposal until the control is attached, or a project Admin decides to do without it, and an Admin raises its autonomy. A knowledge pack not applied does not: it only takes away what the agent could look up.
- Only someone with Admin access to the project starts it above Manual approval, as with any new agent. For anyone else the agent starts at Manual approval, and the panel says why.
The template's guardrails, policies and allowlist are attached even when you do not have the governance permission: a template admin chose them when they published the template, and a control only ever narrows what an agent may do.
An agent made from a template
The agent's Overview tab shows which template and version it was made from — From Corporate Writer · v3. The agent is a copy: a later version of the template, or a change to it, never changes the agent. The same line tells you what has happened since:
- A newer version. When the template has published a later version, the line reads v5 available. What changed opens what that version changed against the one the agent was made from, by the template editor's tabs: Overview, Behavior, Skills & Tools, Guardrails, Heartbeat & Budget and Workspace. It is read-only, and nothing in it changes the agent.
- A deleted template. The agent keeps the template's name, and the line says template deleted. When the template is no longer granted to this project's organization, it says so, and shows no newer version.
- Items not applied. 3 not applied lists what the agent was made without, each one looked up again as you open the pane: Available now, or why it still is not. Someone who manages the item sees its fix beside it — Grant to this organization, Adopt or Activate — as when the agent was added.

The tool server granted to this organization since the agent was made is available now; the guardrail is still a draft.

What a newer version changed, shown beside what the agent was made from. Nothing here changes the agent.
When something has become available, the line reads 1 now available, and Apply adds it to the agent as it applies here now: a skill at its published version, a tool server's tools that are approved, a guardrail, policy or allowlist, a workspace folder where the template gave it access, a knowledge pack with the template's note. Applying an item takes it off the list. Applying never raises the agent's autonomy: an agent held at Manual approval for a missing control stays there until someone with Admin access to the project raises it.
- Applying needs Write access to the project, as any edit to the agent does. A guardrail, policy or allowlist applies without the governance permission: a control only ever narrows what an agent may do.
- A tool never widens a grant. When you have narrowed the agent's access to a tool server by hand, applying the template's tool adds it beside your choice, and applying the whole server leaves your narrowing as it is.
- An item you added by hand stays listed until you next choose Apply, which finds it already on the agent and takes it off the list.
Agent fields
| Field | Description | Required |
|---|---|---|
| Avatar | An Initials or Icon avatar | No (defaults to initials) |
| Name | The agent's display name, up to 120 characters. Agents are told their own and each other's names on every run, in a plain form: on one line, without punctuation such as :, / or quotes. An agent named Sales: EMEA reads to them as Sales EMEA, and that is the name they use when they write about it. Because agents address each other and the project's people by name, an agent may not share one with another agent or a person on the team: names that differ only in case, symbols or extra spaces, such as Sales: EMEA and sales emea, count as the same. A person goes by their name in your directory | Yes |
| Description | A short summary of what the agent does, up to 1,000 characters | No |
| Model | The model that powers the agent, chosen from the tenant's available models | Yes |
| Decision model | A decision model that checks whether a scheduled beat has anything to act on, and whether a task the agent creates is one it already has. See Decision model | No |
| Behavior (system prompt) | Instructions describing how the agent should behave, up to 40,000 characters | No |
| Status | Active, Paused, or Archived (set when editing). A Paused agent stops beating and stops spending as soon as you save; a beat already under way finishes. Setting Status back to Active restarts it straight away, if the team is running, its automatic heartbeat is on and it is within its budget. Archived is the permanent form of the same thing | Defaults to Active |
| Reports to | The member this agent reports to, or top level | No |
| Heartbeat | Automatic heartbeat, Interval (seconds), Autonomy, Max actions per beat, Max tool calls per beat and Events per beat, as on the agent's Heartbeat tab | Defaults to off, 300, Manual approval, 3, 5 and 10 |
| Governance | The policies, guardrails and egress allowlist the agent starts under, as on its Guardrails tab. Shown to someone with the governance permission | Defaults to Baseline safety |
Configuring an agent
Click an agent — a card in the org chart or a row in the list — to open its detail panel.

The reporting line is what the org chart draws, and it is how a manager agent knows whose work to oversee: each of its beats includes what its direct reports have been doing.
The agent's avatar sits in the panel header — click it to open Edit avatar and choose an Initials or Icon avatar. Below the header, the settings are split across two tabs, each saved with Save and close:
- The Overview tab is the agent's identity: Name, Description, Model, Status (Active, Paused, or Archived — see Status), Reports to, and Decision model. An agent's reporting line is editable here at any time; AskRAI prevents a reporting loop by excluding the agent and everything beneath it from the options. This tab also holds Delete agent.
- The Behavior tab shapes how the agent works: Goals (one per line, at most 50, each up to 1,000 characters), the System prompt prepended to every run (up to 40,000 characters), and an Advanced section for model parameters (temperature, max tokens, top P) and response settings (format, language, citation style). On an Anthropic or Amazon Bedrock provider, or a Custom provider whose model name is a Claude model ID, alone or with a gateway's prefix or suffix (such as
anthropic/claude-opus-5-5), a Claude model is sent the temperature but never top P, which Claude 4 and later refuse beside a temperature, and Claude Opus 4.7 and every Claude model after it take neither, so they run on their own sampling settings. On Amazon Bedrock, an OpenAI GPT model that reasons, such as GPT-6, refuses both temperature and top P, so it is sent neither and runs on its own sampling settings; the open-weight gpt-oss is sent both. A GPT model's reasoning counts against max tokens, so where it offers a low reasoning effort, it reasons at that. An agent that already holds a longer prompt or more goals, from a template say, keeps them, and saves its other settings as before; only text you add past a limit is refused.
Changing either tab needs Write access to the project.
A holder of Manage agent templates, Platform Admins among them, also sees Save as template in the panel header. It copies the agent's saved configuration into a new, unpublished agent template, granted to this project's organization, and offers a link to open it in Admin. The agent itself is not changed.
Someone with Write access to the project who cannot manage agent templates sees Suggest as template there instead. It sends the agent's configuration as it stands, with an optional note, to your template admins, who may edit it before they publish it, or reject it with a reason — and the bell tells you which. The dialog says what publishing means: everyone in the organizations the template is granted to can create agents from it, its prompt included. For an agent made from a template, you can suggest it as a new version of that template instead. While a suggestion waits, the panel says so, and you can Withdraw suggestion, once you confirm: your template admins can no longer approve it, and suggesting the agent again sends it as it stands then, with its note written afresh. See Suggestions.
Save and close writes only the fields you changed on that tab, so another admin's change to any other field of the agent stands. Model parameters are written as a set when any one of them changed, and so are response settings. Saving without changing anything closes the panel and writes nothing. If you both changed the same field, the later save wins. When the panel learns that the agent was changed in another session after you opened it — as it does when you save the avatar — the tab says so; close the agent and open it again to see the current values.

Goals are what the agent is told to pursue on every beat, so editing them changes the agent's behaviour from its next beat onward — there is nothing to restart.
The Heartbeat tab is where you set how often the agent acts and how much it may do without you — see Agent Heartbeat & Autonomy.
Starting, pausing and stopping one agent
The panel header also holds the agent's own run controls. Start agent starts this agent; once it runs, the header shows Running with Pause agent and Stop agent beside it, and a paused agent shows Resume. Each acts on this agent alone and leaves its teammates where they are. While the agent runs, the line under its name shows what its latest beat did.
The team follows its agents. Starting or resuming an agent on a stopped or paused team runs the team with it, and the project header reads Running, while every other agent stays where it was. Pausing or stopping the last agent that runs pauses the team, or stops it once none of its agents is paused either. To start every agent that may run at once, use Start team in the project header.
Start agent and Resume are disabled, with the reason under them, when the agent may not run: its status is not Active, its automatic heartbeat is off, the project is not Active or has spent its budget, the agent has spent its own spend cap, or no chat model is connected. Pause agent and Stop agent stay available, so you can always wind an agent down. All of them need Write access to the project; anyone else sees them disabled, with that reason.
Agent tabs
On a wide screen the tabs stand in a rail beside the settings, grouped as Profile, Capabilities, Safety & cost and Monitor. On a narrower one they sit in a row above the settings, which scrolls sideways when they outrun it.
| Tab | What it does |
|---|---|
| Overview | Name, description, model, decision model, status, and reporting line — plus Delete agent |
| Behavior | Goals, the system prompt, and (under Advanced) model parameters and response settings |
| Heartbeat | Cadence, autonomy, per-beat limits, and the beats it has run |
| Activity | What this agent has done on the project |
| Logs | One entry per beat, with its transcript |
| Skills & Tools | Pin skills from the org library, and grant the tool servers this agent may call |
| Guardrails | Attach policies and guardrails, choose an egress allowlist, and read what the selection composes to. Platform Admins and holders of Manage policies, guardrails and egress only: a holder of View policies, guardrails and egress also sees what the selection composes to, and anyone else sees what is attached, read-only |
| Budget | The project budget pool, an optional per-agent spend cap, and this agent's cadence and token limits |
| Access & Data | Which of the project's workspace folders the agent may read and write, and where the files it and its tools save land, and the knowledge packs it searches |
| External access | Whether agents outside AskRAI may hand this agent work over the A2A protocol, the API keys they call with (Create key makes an A2A credential, which calls only the agents that list it), the skills and input it offers them, the limits their requests are held to, and a preview of the agent card they read. Changing it needs Admin access to the project; anyone else sees it read-only |
Who can change an agent's goals, prompt, skills and tools
Only people with Write access to the project or above, whatever the agent's autonomy: everything on its Overview tab but Delete agent, everything on its Behavior, Skills & Tools, Budget and Access & Data tabs, and everything on its Heartbeat tab but Autonomy. Anyone with Read access sees those controls disabled, with a reason naming the Write access they need.
Two things are held further:
- Autonomy and deleting need Admin. Raising autonomy lets the agent act without the proposals that Write decides, and deleting it rejects the ones it has waiting.
- Skills and governance need a permission. Pinning skills takes View skills or Manage skills, so anyone else sees a note on the Skills card instead of a picker — see Skills. The Guardrails tab is held as its row above says.
Whoever raises an agent's autonomy takes the agent as it then reads. Nothing asks you to re-read an agent before it starts acting on its own, and until that moment anyone with Write access to the project could have edited it. Review its name, goals, system prompt, model parameters, skills, tools, workspace access and knowledge packs each time before you raise its autonomy above Manual approval.
Response settings
The three response settings under Advanced on the Behavior tab say how the agent writes. They take effect on every heartbeat: each beat tells the agent's model all three.
| Setting | What the agent is told | Options | Default |
|---|---|---|---|
| Format | How to format what it writes for others: messages, task results and activity notes | Markdown, Plain text, JSON | Markdown |
| Language | Which language to write in | A BCP-47 language tag such as en or fr-CA, at most 35 characters | en |
| Citation style | How to cite a source it relies on | Inline, Footnotes, None | Inline |
They are instructions to the model, like the agent's system prompt — not a filter applied to its output afterwards.
Every agent has all three, whether or not anyone has set them. An agent left on the defaults is told to write in en, so if its instructions ask for another language, set Language to match.
Workspace access
The Workspace card on the Access & Data tab decides which of the project's workspace folders the agent may read and write, and where the files it writes itself and the files its hosted tools save land.
- Read and Write each take No access, Full project workspace or Specific folders. Specific folders shows the project's folder tree with a checkbox per folder. Ticking a folder grants it and everything inside it, folders created there later included, and a folder keeps its grant when it is moved, so the folders inside a ticked one show as covered rather than ticked.
- The agent writes only where it may also read. Write cannot reach further than Read: a full workspace to write needs a full workspace to read, and each folder it may write must be one it may read or inside one.
- Default folder is where the agent's tools' files land, and where a file the agent writes itself goes when it names no folder. It must be a folder the agent may write, and it is required while Write is Specific folders. With a full workspace to write and no default folder, its tools' files land in tool-outputs, in a subfolder per tool server, and a file it writes naming no folder lands at the top of the workspace.
- With no write access, the agent cannot save a file itself, and its hosted tools still run but save no file. The agent is told, and the call's row in the tool's Calls tab reads Not saved: the agent has no write access to the project’s workspace.

Atlas may read every file in the project but writes only to screens, where its tools' files land.
An agent nobody has restricted reads and writes the whole workspace, with no default folder. Save workspace access saves the whole card. If someone else changed the agent's workspace access after you opened it, the save is refused and nothing changes: Reload agent shows their change, and you make yours again.
A folder that is an agent's default folder cannot be deleted, or moved where that agent may not write: AskRAI names the agents, and you change their default folder first. A tool's file that arrives after its agent was deleted, or once its default folder can no longer take it, lands in tool-outputs instead, and the project's Activity tab says why.
What an agent reads of the workspace
Each heartbeat, an agent sees the files it may read:
- What it is shown. Its inbox lists the 20 files inside its Read access that changed most recently, each with its path, type, size, who wrote it and when. The inbox also says, in words, what the agent may read and write and where its tools' files land.
- What it can open. An agent with at least one file to read can list a folder and read a file by its path or its link.
- Which files it reads as text. It reads the text of a Markdown, CSV, JSON or plain-text file, a part at a time from where it left off. For any other file it learns only its type, and that a hosted tool can read it.
- PDF and Word documents. It reads a PDF's or a Word (
.docx) document's text, a part at a time, once AskRAI has extracted it, a few seconds after the document lands. Each new version's text is extracted again. Until then the agent is told the text is still being extracted, and it is told instead when a document has no text to read (a scanned page is a picture, and there is no OCR), is too large to extract, as any document over 25 MB is, or could not be read. The text kept is a document's first 2,000,000 characters. A document saved before AskRAI extracted document text has none until a new version of it is uploaded. - How much it reads. Reading costs none of the agent's actions, but each read uses one of the heartbeat's turns. One heartbeat makes at most 8 reads and reads at most 128 KiB between them, because each later turn of the heartbeat sends what was read to the model again. Past either limit the agent is told to work with what it has read.
- What it can never reach. A file outside its Read access, or in another project, does not exist for the agent: asked to read one, it is told there is no such file.
What an agent reads is treated as information, never as instructions it must follow, as a teammate's message or a tool's result is.
What an agent writes to the workspace
An agent saves files into the workspace itself, as well as through its hosted tools:
- What it writes. A Markdown, CSV, JSON or plain-text file, named with its extension (
.md,.csv,.jsonor.txt), of at most 1 MiB once any redaction is done. An agent never deletes, renames or moves a file. - Where it writes. Only inside its Write access. It names a folder by its path from the top of the workspace, and a folder on that path that does not exist yet is created there, inside its write access. Naming no folder, it writes to its Default folder, or to the top of the workspace when it may write all of it and has no default folder.
- A name already taken. Writing to the name of a file makes the write that file's next version, so the earlier ones stay in its version history. The name of a folder is refused.
- What governs it. The file's name, its folder and its content pass your Output guardrails as a message does: a guardrail that blocks stops the write, and one that redacts saves the redacted text.
- What it costs. Each write spends one of the agent's Max actions per beat, and the file counts against your tenant's file storage allowance. A write refused for its name, its size, its folder or a guardrail spends no action, and the agent is told why.
What happens to the file then depends on the agent's autonomy:
- At Manual approval, the write is a proposal. It waits in Pending approvals with a preview of the file, and nothing is saved until a person approves it. The agent proposes one write per file in a beat, and does not propose a file again while its earlier write to it is waiting.
- At Full autonomy, the file is saved when AskRAI applies the beat. The project's Activity tab reads saved file 'report/summary.md', or saved version 2 of file 'report/summary.md' for a file that was already there. A write whose folder or file is no longer inside the agent's Write access by then — its access narrowed, or the folder moved — is not saved, and the Activity tab says why: did not save file 'report/summary.md': it is outside the folders the agent may write.
The agent is told the file's path and its link, which it can cite in a message or a task's result, where the console shows it as a link that opens the file. The file's Versions tab shows each version the agent saved as Written by the agent, and approved by the person who approved it when it was a proposal.
Knowledge packs
The Knowledge card on the Access & Data tab attaches the knowledge packs the agent searches when its work needs a fact they hold: a policy, a procedure, a product detail, a figure.
- Which packs. The picker offers the packs granted to the project's organization, in each pack's Organizations section, that one of your groups also grants you. An agent gets only the packs the person giving them can read, so the card says how many of the organization's packs it leaves out for that reason: someone who manages users and access can grant one to a group of yours. With none granted to the organization, the card says so: someone who manages users and access grants a pack on the Knowledge Packs page. An agent holds at most 50 packs.
- When to search it. Each pack you attach takes an optional When to search it note, at most 300 characters, in your own words: Search it for anything a customer could quote back at us. The agent reads it beside the pack's name and description, and a note only ever tells it when to search.
- A pack with no approved items answers nothing. A QnA pack's generated pairs start as drafts, so the card flags a pack with none approved until its items are approved.
- A pack that is no longer available. Revoking the organization's grant, or deleting the pack, takes it off the agent. A pack the card still shows after that reads No longer available to this organization, with Remove. A pack the agent already holds stays whoever saves the agent next, whatever their groups grant.
- Who sees what it finds. Everyone on the project reads what the agent writes, and its tools receive what it sends them, so attaching a pack shares what the agent finds in it with them. The card says so above its packs. A heartbeat's transcript keeps what each search returned, and everyone with Read access to the project can open it.

Atlas searches Refund policy for anything a customer could quote back; Product manuals answers nothing until its items are approved.
Save knowledge packs saves the whole card. If someone else changed the agent's knowledge packs or their notes after you opened it, the save is refused and nothing changes: Reload agent shows their change, and you make yours again.
Each heartbeat, an agent holding packs is told what each one holds: its name, its kind, how many sources it has, when it was last updated, its description and your note. Nothing is searched until the agent asks:
- When it searches. When its work needs a fact one of its packs may hold, before it puts that fact in a task, a message, a proposal or a file, rather than stating it from memory. It does not search for what its inbox already says, or on a heartbeat with nothing to act on.
- What it gets back. The curated answers and document passages that clear your tenant's minimum relevance threshold, ranked together across the packs it chose, at most two passages from any one document, each labelled with its pack and source. The agent cites what it relies on by that label, in its citation style.
- Reading on. When a passage from a documents pack is the start of what the agent needs, a policy section say, it can read on through that document from the passage, in order, and is told where to continue. It reads only documents its searches found in this heartbeat; a curated answer is whole already.
- When nothing matches. The agent is told nothing cleared the bar, rephrases once at most, then carries on and says the packs did not cover it. If the search fails on AskRAI's side, it is told that nothing was searched, and never that the packs lack the answer.
- How much it searches. Searching and reading on cost none of the agent's actions, but each uses one of the heartbeat's turns. One heartbeat makes at most 4 searches and reads between them, returning at most 48 KiB, because each later turn of the heartbeat sends what was found to the model again. Asking for the same thing twice in a heartbeat costs nothing: the agent is pointed back to what it already has.
- Where you see it. Each search and each read is a line in the heartbeat's log: what it asked for or read on from, which packs or document, what came back and the labels it returned, the opening of what it found, and, unless its citation style is None, the line telling the agent which labels to cite.
What an agent finds in a pack is treated as information, never as instructions it must follow, as a teammate's message or a tool's result is.
Decision model
An agent's Decision model is a decision model your tenant connected under Model Providers, such as TypeSafe's Jev, which makes two checks for it: whether a scheduled beat has anything to act on, and whether a task it creates is one it already has. It is optional and offers decision models only. An agent without one makes neither check, and neither check ever lets an agent do more than it could without it.
- Templates do not carry it. An agent made from an agent template starts without one, and Save as template leaves it out.
- It is a model in use. It cannot be removed or disabled while the agent names it, and correcting its model ID moves the agent with it, as for the agent's Model.
- What it costs. Each check is charged at the decision model's Input $ / 1K tokens price, since TypeSafe charges for input tokens only. It counts in the beat's cost on the Logs tab, and so against the project's budget and the agent's spend cap.
- What it reads. The agent's name and role, its inbox and task titles, processed under your own agreement with TypeSafe. The agent's teammates write that text, and text written to steer a decision model can move its answers.
Wake check
Before a scheduled beat, the decision model reads the agent's inbox and answers how likely it is that something there asks or needs the agent to act.
- Scheduled beats only. A beat woken by something happening to the agent — a message to it, a task assigned to it, a proposal of its decided, the work one of its tasks waits on finished — always runs, though its Logs line reads scheduled too. So does a beat you start with Run heartbeat.
- After your Input guardrails. It reads the inbox once your Input guardrails have run on it, so it reads what they redacted, and never a message they blocked.
- Below 0.2, the beat is skipped. It ends without a turn, and counts as idle, so the idle backoff keeps doubling the agent's interval.
- Never more than three in a row. The fourth scheduled beat runs whatever the check answers, so a check that is wrong about an agent cannot silence it. A beat that runs, or anything that wakes the agent, starts the count again.
- A check that fails runs the beat.
- Where you see it. The beat's entry on the Logs tab says it was skipped, and its transcript gives the probability, the threshold and the versioned model that answered, such as
jev-1.14.0. The agent's Activity and its Last action read skipped a scheduled beat: its decision model found nothing in its inbox to act on.
Duplicate-task check
When the agent creates a task, or proposes one at Manual approval, AskRAI first refuses it if the agent already has one of the same title for the same owner. When nothing matches exactly, the decision model compares the new task's title with the agent's open tasks, its waiting tasks, its reports' tasks in flight and the tasks it created earlier in the beat, among those held by the new task's owner. A new task with no assignee matches any owner.
- At 0.85 or above against any of them, the create is refused as an exact match is, naming that task. The agent is told within its beat, which the beat's transcript shows.
- Below 0.85, or when the check fails, the task is created.
- Titles go as they are stored. An Input guardrail that redacts does not cover what this check reads.
Watching what an agent does
The Activity tab answers what has this agent been doing? It lists the actions the agent has taken on this project — beats, messages it sent, tasks it created, status changes it made, and files it saved — newest first, each marked agent.

The Activity tab is the agent's own slice of the project activity feed — the fastest way to see whether an agent is pulling its weight.
The feed is not streamed entry by entry: it reloads after each of the agent's beats, and Refresh pulls the latest actions at any time. It shows the 50 most recent.
When an agent closes a task, its entry here records what the work produced — for example status → done — Welcome pack published to the People Ops wiki; 14 checklist items, IT and Security sections signed off. Read those lines to judge the quality of an agent's output, not just its volume.
Reading an agent's logs
The Logs tab is the operational view: one entry per heartbeat, with the cost and outcome of each.

Each log entry is one beat — its outcome, what triggered it, how long it ran, how many actions it took, and what it cost. The failed beat records why.
Every entry carries a level badge, the time the beat started, and a one-line summary in the form succeeded — beat #42 · scheduled · took 38.2s · 3 actions · 4,830 tok · $0.02 · Claude Sonnet 4.5. The model goes by the name the agent's Model list gives it, or by its internal id (byom:…) once your tenant can no longer run it: its provider deleted or no longer active, or the model disabled. An entry recorded before beats reported their own start and end shows no duration. A beat that the wake check skipped says so. A beat that failed appends the reason, as in — model provider returned 429 (rate limited). A beat whose agent asked for more actions than its cap allows says so after its action count, as in 3 actions · action cap reached — 1 call not recorded: the extra actions were never recorded, and the beat's transcript names them. The cap is the agent's Max actions per beat, or a lower Actions per beat on a policy attached to it. If the agent keeps reaching it, raise whichever is lower. A beat that recorded events counts them next, apart from its actions, as in 2 events. Then come any refused as the beat's work was saved, such as an event whose type was retired meanwhile, as in 1 refused (or 1 event refused when none was recorded), and any past its Events per beat, as in event cap reached — 1 event not recorded. The beat's transcript gives each refused event's reason. For a moment after a beat ends, while what it did is still being saved, its entry and its transcript read applying in place of the outcome. The list checks again by itself and shows the outcome once the beat's proposals, tasks and messages are in place.
| Level | Meaning |
|---|---|
| INFO | The beat succeeded, is still running, or is queued |
| WARN | The beat timed out or was cancelled |
| ERROR | The beat failed — the summary line ends with the error |
A beat stopped by an Input guardrail that Blocks names the message that tripped it and the guardrail that stopped it: who wrote it, when, and its opening words, with anything a word, pattern or detector guardrail matched masked (an LLM judge points at nothing to mask), as in — No fruit: 1 match(es) — in Ada Lovelace's message of 2026-10-22 07:40 UTC: “I brought a [REDACTED] for everyone”, which this agent's later beats leave out. That beat fails, and from the next one on the agent reads the rest of its inbox without that message, so one message cannot stall an agent however long it stays among the newest. The message stays out for as long as that guardrail governs the agent: detach it, and the agent reads the message again from its next beat. The message stays in the project's thread, marked as set aside from the agent and naming the guardrail, and other agents still read it unless it blocks them too. An entry of the project's recent activity that trips the guardrail on its own, such as a task someone created under a name holding a denied word, stops no beat: each beat the entry would block runs without it while it stays among the newest, and its transcript names the entry, masked, as in No fruit: 1 match(es) — in the activity row “Ada Lovelace: created task 'Plan the [REDACTED] tasting'”, which this beat leaves out. When an LLM judge is what blocks the entry, each of those beats asks the judge about the inbox twice, and about the entry once more. A block that no single message or activity entry trips, such as a word in one of the agent's tasks, names no message: edit the task, or detach the guardrail. When only several messages or activity entries taken together trip an LLM judge, the line says so, as in — the messages and the activity rows together: none blocks on its own, so none is set aside. Until the inbox or the guardrails change, each later beat asks the judge about the inbox once, not about every part of it again.
Select any entry to open its transcript — the record of what the agent read, reasoned, and decided on that beat. The agent always reads a result whole, but the transcript keeps each entry short: a long one is cut and says so, as in … [cut: 3412 more characters], and a tool's or a knowledge pack's text may be kept shorter than the agent's own words. A transcript holds at most 8,000 characters, and one that runs longer ends by saying how many of its entries it leaves out. A beat that recorded events lists them under Events, each with its type and fields, and Not recorded with the reason for one that was refused. Some beats have no transcript captured, in which case the dialog says so.
The levels map onto the beat's outcome: see beat statuses for what each one means, and what triggers a beat for the trigger named in each line.
The Logs tab is where a misbehaving agent gives itself away. A run of WARN or ERROR beats usually points at the model provider rather than the agent's prompt; a long run of successful beats that took 0 actions usually means the agent has nothing in its inbox — give it a task or a message.
Logs is the only place an agent's beat history is listed — the Heartbeat tab sets the cadence and shows live state, and sends you here for the record of what those beats did and cost.
If an agent's model later becomes unavailable (for example, its provider is switched inactive), the agent's beats fail until the provider is active again or you pick a new model, and the form shows its selection as (unavailable). A model an agent runs on cannot be removed or disabled, and correcting its model ID moves the agent with it: see Model Providers.
Capping what one agent spends
The agent's Budget tab is where you bound what a single agent costs, inside the budget the whole project runs against.

A cap is a ceiling drawn against the project pool — not an allocation carved out of it.
Project budget pool. What the project has spent against its total, so you can see how much room the cap is being drawn from. If the project itself is out of budget, the card says so — no agent on the team runs until the project budget is raised, its status is set back to Active and the team is started again from the project header, whatever its own cap says.
Agent spend cap. Off by default: an agent with no cap draws on the project budget until the project's own limit is reached. Turn on Limit this agent's spend and enter an amount above $0 to bound it; turning the switch back off clears the limit. The card also shows what this agent has spent so far, and how much of its cap remains. An amount under a cent is shown to two significant figures, such as $0.004, so a cap smaller than a cent can still be compared with the spend.
Two properties are worth knowing before you rely on a cap:
- It is checked after each run completes, so a run already in flight can carry spend slightly past the cap.
- It bounds what this agent spends on its own runs. Work it hands to another agent is charged to that agent.
An agent that hits its cap stops on its own — the rest of the team keeps running. The Budget tab then shows Stopped — budget exhausted with a Resume button beside it. The people on the project's team who hold Write access or above — or, when none does, the next in line — also receive a notification naming the agent; it opens the project's Budget tab, not this one.
Raise or clear the cap first, then press Resume: until the cap is above what the agent has spent, Resume is disabled, and the banner beside it names the cap as the step still outstanding. Resume returns this agent to its schedule and leaves the rest of the team where it is — unlike Start team in the project header, which restarts every agent that may run within its budget. On a project whose status is not Active, Resume is disabled and the reason is shown beside it: set the project Active, then use Start team or Resume in the project header. Resume is disabled too, with its reason beside it, on a project whose own budget is exhausted, for an agent whose status is not Active, and for one whose automatic heartbeat is off.
Cadence & tokens. A read-only summary of the other things that decide what an agent costs: how often it beats and how many actions each beat may take (both set on Heartbeat), the hours it is active, and the token ceiling per model call (set under Advanced on the Behavior tab). An agent whose automatic heartbeat is off shows no cadence, because it does not beat at all.
Checking a person's workload
Click a person in the org chart or list to open their detail panel. Alongside their read-only Directory profile (display name, email, job title, department, and project role, all managed in your corporate directory) and their Project assignment, an Inbox on this project card shows what the team has sent their way:
- Assigned tasks — every task currently assigned to them, with its status and when it last changed.
- Direct messages — messages addressed to them specifically, with the sender and date.
This is the quickest way to see whether an agent has been handing work to a colleague who has not picked it up. Agents have no inbox card — use their Activity and Logs tabs instead.
The reporting hierarchy
The org chart is built from each member's reporting line, which can span both people and agents:
- People and agents alike get their manager, or the top level, when added, and you can change it later from the member's detail panel. A new member starts under an agent only when you pick one.
- No loops — a member can't be set to report to one of its own reports.
When you remove a person or delete an agent who has direct reports, those reports are not deleted — they move up to the top level so the rest of the hierarchy stays intact.
Removing people and agents
- Remove a person — open the person's detail panel and click Remove from project, then confirm. The person is removed from the team but remains in your directory. Their unfinished tasks become unassigned and keep their status, and adding them back does not restore them. From then on, neither an agent nor the task board can give them work, though you can still message them.
- Delete an agent — open the agent's detail panel, click Delete agent, and confirm. The agent is permanently removed from the project, and the proposals it still had waiting for approval are rejected, since none can be applied without it. Its unfinished tasks become unassigned and keep their status; no agent picks up an unassigned task on its own, so assign each one to whoever should do it. Its finished tasks still show who did the work. A teammate's proposal that messages the deleted agent or gives it work can no longer be approved — reject it, and address the work to a current member instead. Because deleting an agent disposes of its proposals, it needs Admin access to the project. Anyone else sees Delete agent disabled, with a reason naming the Admin access it needs.
In both cases, any direct reports move to the top level of the org chart.
Removing a person from a project does not delete them from your directory — it only takes them off this project's team. Deleting an agent is permanent and cannot be undone.
Troubleshooting
| Symptom | Likely cause | Resolution |
|---|---|---|
| A person isn't in the directory search | They are already on the project, they hold less than Write on it, or they aren't provisioned in your directory | Check the existing team; share the project with them at Write; provision the user via Users, Roles & Groups or Directory Sync |
| Adding a person is refused with Only a person with Write access or above to this project can join its team | Their level on the project fell below Write after the panel listed them | Share the project with them at Write, then add them again |
| Add person, a person's reporting line or Remove from project is disabled, with a reason naming Write access | You hold less than Write on the project | Ask someone with Write, or one of the project's Admins, to make the change — or an Admin to share it with you at Write, then reload the page |
| Delete agent is disabled, with a reason naming Admin access | You hold less than Admin on the project | Ask one of its Admins, or a Platform Admin, to delete it |
| Add agent, or an agent's settings, are disabled, with a reason naming Write access | You hold Read on the project | Ask someone with Write to make the change — see who can change them — or an Admin to share the project with you at Write, then reload the page |
| Saving an agent is refused, naming the Write access it needs, though the controls were not disabled | Your level on the project was lowered after you opened it. Nothing in that save was applied | Reload the page. The controls then show as disabled, and the change is one for someone with Write |
| Adding or renaming an agent is refused under Name with This project already has an agent named … or A person on this project's team is named … | Another agent or a person on the project's team holds that name, or one that differs from it only in case, symbols or extra spaces. Nothing was saved | Choose a name that differs in its letters or digits. An agent that shared a name before this rule, or whose name a person took later by joining the team or being renamed in your directory, keeps it until it is renamed |
| Adding an agent shows Configure a model provider instead of the form | The tenant has no enabled chat model | Connect one under Model Providers and enable at least one chat model |
| An agent's model shows (unavailable) | The selected model is no longer available to the tenant | Open the agent and pick an available model |
| Saving an agent's workspace access is refused | Write reaches further than Read, a folder you ticked was deleted meanwhile, or the default folder is missing or outside what the agent may write — the card says which | Correct the card and save again |
| Deleting or moving a folder is refused, naming agents | The folder is, or holds, those agents' default folder, which the change would remove or put where they may not write | Change their default folder on the Access & Data tab first |
| The project's Activity tab reads did not save file '…': it is outside the folders the agent may write | The agent's Write access was narrowed, or the folder or file was moved out of it, between the agent writing the file and AskRAI saving it | If the agent should write there, widen its Write access on the Access & Data tab, and ask it to write the file again |
| An agent never searches a pack it holds | The pack is not granted to the project's organization any more, it has no approved items, or the agent's work has not needed a fact it holds | Check the pack's Organizations and approved items, and say in the pack's When to search it note when the agent should search it |
| The org chart can't be drawn | The team's structure can't be laid out as a chart | Switch to the List view to see and manage all members |
Related pages
- Agent Heartbeat & Autonomy — set each agent's cadence, autonomy, and per-beat limits, and review the beats it has run
- External Access (A2A) — open an agent to agents outside AskRAI, which hand it work over the A2A protocol
- Projects — the project workspace that contains the Team tab
- Sharing & Access — the access levels that decide who may change the team and its agents
- Interactions — run the team as a live workspace with messages, tasks, and proposals
- Model Providers — manage the models that power your agents
- Users, Roles & Groups — the directory of people you can add to a team
- Organizations — the organizations that contain your projects
Projects
Organize work into projects within an organization — create, browse, edit, and delete projects, and track each project's team and budget from a single workspace
Agent Heartbeat & Autonomy
Set how often an AI agent acts and how much it can do without you — configure an agent's cadence, autonomy level, and per-beat limits, and review the beats it has run