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
Projects are the workspaces where your people and AI agents collaborate. Each project lives inside an organization and brings together a team, a budget, and an overview of how everyone connects. Open the Projects plane from the plane switcher in the top header.

The Projects plane pairs a searchable project list with a per-project workspace — here the Onboarding Automation project, scoped to the active Acme Automation Org organization.
How projects fit in
A project always belongs to one organization, and the active organization scopes which projects you see. Switching organizations in the header switcher reloads the Projects plane for the newly selected organization.
- Organization → projects — you need at least one organization before you can create a project. If your tenant has no organizations yet, the Projects plane prompts you to Create an organization in Admin first. If none is shared with you, it reads Nothing is shared with you yet and names your tenant's Platform Admins, who can share one with you.
- One workspace per project — selecting a project opens its workspace, where the Overview, Team, Workspace, Interactions, Activity, Budget, Dashboard and Events tabs live.
- Team and budget — every project tracks the people and agents working on it (the Team tab) and an optional spending budget.
- A live team — the Interactions tab runs the project's agents and people as an autonomous workspace, with messages, a task board, and Start/Stop controls.
- Access levels — a project's Admins share it at Read, Write or Admin, which decides who sees it, who works in it, and who makes its weightiest decisions: raising an agent's autonomy, editing, resetting and deleting it.
Projects are scoped to the active organization, and you see only the ones shared with you. If the project list looks wrong, confirm which organization is active in the header org switcher — see Organizations for how the active organization works — and ask one of a missing project's Admins to share it with you.
Browsing projects
The Projects sidebar lists every project in the active organization that you can read. Use it to search, switch between projects, and start a new one.
- Search — type in the Search projects box to filter the list by name or description. Press Alt+/ (Option+/ on a Mac) anywhere on the Projects plane, outside a text field, to jump to it. While you search, the list shows every match under a count of how many there are, and a search nothing matches says so, quoting it. The × in the box clears the search; Escape clears it and leaves the box.
- Two groups — the six most recently updated projects appear under Recent; the rest are grouped under All projects.
- Status at a glance — an entry shows On hold or Archived beside the project's name, and one showing neither is Active. Those under Recent also show how long ago each was updated: Today, Yesterday, or a number of days such as 3d.
- Run state at a glance — the dot before each project's name says whether its team is running: a breathing green dot while it is Running, an amber one while it is Paused, and a hollow ring while it is Stopped. Hover the dot to read the state, and a screen reader hears it after the project's name. It follows a start, pause or stop of the project you have open at once, and of any other project within about 15 seconds, without a reload. While any team you can see in the organization is running, the logo at the top left gently drifts; it holds still if your system asks for reduced motion.
- Archived projects — left out of the list. When the organization has any, switch on Show archived under the search box to list them too.
- Select a project — click any project to open its workspace on the right.
- Return to it — the browser's address bar names the project and tab you have open, so reloading the page, or opening a copied link to it, brings back the same project on the same tab.
When the active organization has no projects you can read yet, the workspace shows an empty state with a New project button to create your first one.
Creating a project
Creating a project needs Write access to the active organization. For anyone else, the + button, New project and the header's Create → Project stay in place, disabled, with a reason saying creating a project needs Write access to this organization.
Click the + button at the top of the project list in the sidebar (or the New project button in the empty state) to open the create dialog. You can also choose Create → Project at the right of the top header, from any tab.

On the Projects plane, Create starts a project or adds an agent or an assistant to the project you have open.

New projects are created in the current organization; you set the status and budget afterward by editing the project.
Open the create dialog. Click + in the Projects sidebar. The dialog notes that the project is created in the current organization.
Name the project. Enter a Name — this is required and identifies the project throughout the workspace. It must differ from the name of every other project in the organization by more than case, symbols or extra spaces, so launch plan! is refused where Launch Plan exists. The same name in another organization is fine.
Add a description (optional). Use the Description field for a short summary of what the project is for.
Create. Click Create. The new project is added, selected automatically, and opens to its Overview tab.
Whoever creates a project is its Admin, and joins its team unless they are a Platform Admin. New projects start as Active, with no budget and an Idle check-in of 60 minutes. To set a status, allocate a budget or change the idle check-in, edit the project after creating it.
Project fields
| Field | Description | Required |
|---|---|---|
| Name | The project's display name, shown in the sidebar and workspace header. Unique within the organization, whatever its case, symbols or extra spaces | Yes |
| Description | A short summary of the project's purpose | No |
| Status | Active, On hold, or Archived — set when editing (new projects default to Active). Only an Active project's team can run, and an Archived project is read-only; see Project status | Set on edit |
| Budget total (USD) | An optional ceiling on what the project may spend in total — set when editing | Set on edit |
| Idle check-in (minutes) | The longest an agent with nothing to do waits between beats — set when editing. Defaults to 60 | Set on edit |
| Assistant suggestions | Whether the project's assistants offer help unasked when a run hits something they can help with — set when editing. On by default | Set on edit |
The project workspace
Selecting a project opens its workspace. The header shows the project name and status, its description, Share, a More menu holding Edit and Delete, the Reset icon button and the run controls — Share opens who the project is shared with. Four tiles sit under them: Team counts its people and agents, shows the first eight as avatars, says how many agents are active, and reads how many are working, or Idle; Interactions counts its open tasks, how many of all its tasks are done, on a bar showing how many are done, in progress, blocked and to do, and beside them its messages, how many came from AI agents and a dot for each of the newest 18, an agent's in purple and a person's in grey, and says how many proposals wait for your approval, or failing that how many tasks are blocked; Budget gives what has been spent of the budget total and the share used, on a bar that turns amber at 75% and red at 90%, or with no budget total what has been spent, under No cap; and Activity shows how busy the team is: its events per minute over the last minute, a line of that pace across the last ten minutes, and the run peak, its busiest minute since the project was last reset. Below, eight tabs organize the work. The Team tab counts the project's people and agents, and the Interactions tab its messages and tasks, until approvals wait on it: it then counts those instead, in purple. A screen reader announces each count in words, such as Interactions, 3 waiting for approval.
The workspace stays live on every tab, whatever the team's run state: the header's run state, its badges and its Budget figure follow the team — a budget stop included — and so do the messages, tasks, activity and agent run state the tabs show, with no reload.
The project itself does too. When another admin edits its name, description, status, budget or idle check-in, the header, the run controls and the Budget tab show the change within a few seconds. If they set it to On hold or Archived, Start team or Resume is disabled here and says why.
So does its team. An agent another admin adds appears on the Team tab, the relationship graph and the header's counts within a few seconds, and what it writes on Interactions carries its name. One they delete leaves them, and the Team tile's working count with it. Another admin's edit of an agent — its name, model or heartbeat — is not brought to your page: reload it to see the change on the roster.
Overview tab
The Overview tab summarizes how the project is staffed and connected.
- Pinned dashboards — the dashboards someone pinned to the Overview from the Dashboard Assistant, each a card showing its current figures, which follow the work with no reload. Click one to open the whole dashboard. The row appears only once a dashboard is pinned.
- Project relationships — a live interaction graph of how people, agents, and models connect.
- Recent activity — a feed of what the team's agents and people are doing, drawn from the Interactions workspace, and what the project's assistants did, as on the Activity tab.

Pinned dashboards, each showing its first figure and trend as the project stands now.
The interaction graph
The Project relationships card on the Overview tab draws the project as a graph: who is on the team, who reports to whom, which model each agent runs on, which of the project's workspace folders each agent may read and write, which knowledge packs each agent searches, and the project's assistants beside the team. While the team is running, it also animates the work as it happens.

The graph places the team on the left, and on the right their models with the workspace beneath them, so each line runs straight from an agent to what it uses or reaches. Beacon reports to Atlas, and both run on the same model — so it collapses into a single shared node. Atlas reads the whole workspace and writes only to screens; Beacon reads and writes all of it.
What the graph shows
| Element | Meaning |
|---|---|
| Person node | Someone on the project team, labelled with their name and job title |
| Agent node | An AI agent, labelled with its name and the model that powers it |
| Model node | A model an agent runs on. Agents sharing a model share one node, so you can see at a glance which model the project leans on |
| Reports to edge | The reporting line between two members, mirroring the org chart. Each manager sits below the people who report to them, so these lines nest, and each arcs out to the left of the team |
| Uses edge | Connects an agent to its model. These edges animate while the team is running |
| Workspace node | The project's whole workspace, for an agent that may read or write all of it. Click it to open the Workspace tab |
| Folder node | A folder an agent was granted on its Access & Data tab, with its path when it is nested. Click it to open the Workspace tab at that folder |
| Knowledge pack node | A knowledge pack an agent searches, drawn while the project's organization is still granted it. Agents holding the same pack share its node. Click it to open the pack on the Knowledge Packs page |
| Accesses edge | Connects an agent to the workspace, a folder or a knowledge pack, labelled write where it may write and read where it may only read. An agent only ever reads a knowledge pack |
| Assistant node | One of the project's assistants, labelled with its name and kind. Assistants stand in a column of their own, outside the team, so their card is dashed, and the legend's Assistant reads key appears with them. Click one to open its chat on the Team tab |
Watching the team work
Start the team and the graph goes live — the status line reads Live — pulses show real agent heartbeats, messages, and task handoffs. Three kinds of pulse then light up the graph as the events actually happen:
| Pulse | What just happened |
|---|---|
| Agent heartbeat | The agent glows green — it is taking a beat right now. With reduced motion on, it stays still and shows the word Working instead |
| Message (live) | A line flashes from the sender to the recipient. A broadcast to everyone glows the sender instead |
| Task handoff (live) | A line flashes from the task's creator to its new assignee, labelled with the task's title. It is drawn from the creator even when someone else did the reassigning |
Each pulse is an event the team produced. Each agent beats on its own configured cadence — five minutes by default, and as often as every 30 seconds — so a healthy graph is calm rather than busy. If you see nothing at all, check that the team is Running and that your agents have Automatic heartbeat enabled.
Reading the graph
- Focus a member. Click a person or agent to focus it, or Tab to it and press Enter or Space. Everything it connects to stays sharp, everything else dims, and a hint reads Showing relationships for …. Click the canvas, or press the member again, to clear it.
- Filter. Turn People, Agents, Models, Workspace, Knowledge or Assistants off to hide that kind of node, or use All to turn everything on or off at once. Models, Knowledge and Assistants show once the graph has a node of their kind: Knowledge appears with the first knowledge pack an agent holds, and Assistants with the project's first assistant. With every filter off, the card reads Nothing matches your filters. Your filters stay as you left them when you open another tab.
- Pan and zoom. Drag to pan, scroll or pinch to zoom. Nodes cannot be dragged. The graph frames itself again when the window changes size.
If the project has no people, agents or assistants yet, the card reads No team yet — add people and agents on the Team tab to populate it. A project with assistants but no team draws its assistants alone.
Workspace tab
The Workspace tab holds the project's files: the ones its people upload and the ones its agents produce, organized into folders by the people with Write access to it. An agent writes Markdown, CSV, JSON and plain-text files itself, into the folders it may write, and an agent at Manual approval proposes each one for approval first. When an agent calls a hosted tool that writes a file — a chart, a spreadsheet export, a Markdown summary — or saves an email's attachment, the file lands here: in the agent's default folder when it has one, and otherwise in a tool-outputs folder with one subfolder per tool server. An agent whose workspace access lets it write nowhere saves no file. Anyone who can open the project can open its files.
- Browse — the tab shows one folder at a time, its folders first and then its files, each in name order. Click a folder to open it, and use the path above the list to go back up. Each file shows its name, size and when its current version was made, and its preview adds its version once it has more than one, the tool that wrote it, written by an agent for a file an agent wrote itself or uploaded for a file a person uploaded. A folder holding more than 200 items lists the first 200, and Load More at the end of the list adds the next 200.
- Live — the tab follows the project as it changes: a folder someone else creates, a file they upload, move or delete, or a file a tool or an agent writes appears in the folder you have open without a reload. If someone deletes the folder you are in, the tab goes back to the top of the workspace and says so.
- Preview — click a file to open it beside the list. PNG, JPEG and WebP images show inline, Markdown files render as formatted text, plain-text, CSV and JSON files show as text, laid out as they are stored, and Word documents (
.docx, and macro-enabled.docm) of up to 25 MB are laid out as pages. Links in a Word document show as text and do not open. Excel workbooks (.xlsx, macro-enabled.xlsmand Excel 97-2003.xls) of up to 10 MB show each visible sheet in a tab of its own, as a grid of what each cell displays in Excel, number, date and percentage formats applied: the first 1,000 rows and 100 columns of a sheet and the first 1,000 characters of a cell, a formula's last calculated value, and links as text. A formula the file holds no calculated value for, or only a placeholder, as in a workbook a script or library wrote, shows as written (=SUM(B2:B3)) in italics, with a line under the sheet saying Excel calculates it when it opens the file. Charts, images, colours, borders, column widths and merged cells are left out. PDFs of up to 50 MB show their pages, whose text you can select and copy; a PDF's links, form fields and scripts do nothing there. PowerPoint decks (.pptx, and macro-enabled.pptm) of up to 50 MB show as slides you scroll through, with their text, pictures, shapes, tables and charts; charts and effects are approximate, animations, speaker notes, video and sound are left out, and links show as text and do not open. A macro in a Word, Excel or PowerPoint file never runs in a preview. Every other kind of file, Word 97-2003.doc, PowerPoint 97-2003.ppt, binary.xlsband SVG images included, is offered as a download rather than displayed. The Versions tab beside the preview lists the file's versions. - Download — every file can be downloaded, from its row's menu or from its preview. Links are made when you ask for one and expire shortly after, so ask again for a fresh one.
- Files an agent cites — a file an agent names in a message, a task's result or an activity entry shows there as a link, usually reading as the file's path, that opens the same preview and Versions tab. A file deleted since reads deleted file.
Organizing files
The people with Write access to the project or above organize its workspace:
- New folder — creates a folder in the folder you have open.
- Rename — from a file's or folder's menu. A name must be unique in its folder, and cannot be
.or..or hold a slash. - Move… — from a file's or folder's menu, opens the workspace's folder tree to pick where it goes, the top of the workspace included. A folder cannot be moved into itself or into a folder inside it.
- Delete — from a file's or folder's menu. Deleting a folder deletes everything inside it. A delete is final: there is no trash to restore from.
A folder that is, or holds, an agent's default folder cannot be deleted, or moved where that agent may not write: the refusal names the agents, and you change their default folder on their Access & Data tab first.
Folders nest at most 16 deep, and a project holds at most 5,000 folders. Each change is recorded on the project's Activity tab with who made it.
Anyone with Read access can browse, preview and download the project's files, but sees these controls disabled, with a reason naming the Write access they need.
Uploading files
The same people upload files from their computer:
- Upload — picks one or more files, which go into the folder you have open. You can also drag files from your computer onto the list, into the folder you have open, or onto a folder's row, into that folder.
- Upload new version — from a file's menu, uploads a file from your computer as that file's next version. It keeps its name and place.
- A name already taken — when the folder already holds a file of the same name, AskRAI asks what to do with each such file: Replace uploads it as that file's next version, Keep both uploads it beside it with a number added, as
report (2).md, and Skip leaves it out.
A file can be up to 100 MB. Each one shows its progress as it goes up, then Uploaded, or why it could not be. A file that is uploaded appears for everyone who has the folder open, and each upload is recorded on the project's Activity tab.
An Outlook mailbox archive, a .pst or .ost file, can be up to 20 GB. One larger than 100 MB goes up in parts:
- Progress — the row shows how much of the archive has gone up.
- A part that fails is sent again on its own, a few times. If it still fails, the row says so and offers Retry, which carries on from the parts not yet sent rather than starting over.
- Cancel — stops the upload. Nothing of it is kept, and the room it set aside is freed at once.
- Time — an archive must finish uploading within 23 hours of starting, about 2 Mbit/s for 20 GB. Past that, it is refused and has to be uploaded again.
A 20 GB archive is larger than the 10 GB file storage allowance your tenant starts with, so it needs AskRAI to raise the allowance first: the upload says so when there is not room for it.
Once uploaded, an archive is indexed, its folders and messages read one part at a time, and its row shows how far that has got:
- Waiting to be indexed, then Indexing, with the messages indexed so far: Indexing: 4,210 messages so far. A 20 GB archive takes an hour or two.
- Indexed — how many messages it holds: 19,038 messages indexed. A damaged archive can hold folders or messages that cannot be read. They are skipped and counted, never left out silently: 19,038 messages indexed; 2 folders and 193 messages could not be read.
- Not indexed — why, in words: the archive is encrypted, its format cannot be read, it is too large, or indexing kept failing.
The index counts against your tenant's file storage allowance beside the archive itself.
Once an archive is indexed, the agents granted a mailbox connection can search its messages and read them.
A file's type comes from the extension in its name, and AskRAI keeps that type only when the file's contents bear it out: PNG, JPEG and WebP images, PDFs, Word, Excel and PowerPoint files (macro-enabled and Excel 97-2003 ones included), Outlook mailbox archives, Markdown, CSV, JSON and plain text. A file of any other type, or whose contents do not match its extension, is kept as a plain download, but for a mailbox archive larger than 100 MB, which is refused.
File versions
Every file keeps its versions. A file's Versions tab lists them newest first, each with its number, who made it — the tool and the agent that called it, the agent that wrote it, or the person who uploaded or restored it — what made it, when, and its size, with the current version marked Current. A version an agent proposed at Manual approval also names who approved it: Written by Atlas · approved by Nadia Rahman. A file keeps its last 50 versions; an older one leaves the list.
- Open — shows that version in the Preview tab, where you can download it too. Anyone who can open the project can open any version.
- Restore — the people with Write access to the project or above can restore an earlier version. AskRAI copies it and makes the copy the file's new current version, numbered after the newest, so the versions before it stay in the list, the one restored included, until the file passes the 50 it keeps. Each restore is recorded on the project's Activity tab.
Anyone with Read access can open every version, but sees Restore disabled, with a reason naming the Write access it needs. A restored copy takes up storage as any file does, so a restore is refused while your tenant's file storage allowance is full.
The agent that called the tool is told each file's name, type, size and link, so it can cite the file in its messages, where it shows as a link to the file. The tool's result never carries the file's contents.
AskRAI checks every file before it appears here. A file's type comes from the extension in its name, not from what the tool claimed, and is kept only when its contents bear it out, so a file named as an image whose contents are not shows as a plain download. A tool can only write files into the project whose agent called it.
All of your tenant's projects share one file storage allowance, 10 GB unless AskRAI has raised it. The bottom of the Workspace tab shows how much of it your tenant's files use. Once it is used up, uploads and restores are refused, an agent's own file is not saved and the agent is told why, and hosted tools still run but can no longer save new files: the agent is told, and the call's row in the tool's Calls tab reads Not saved: workspace storage is full or unavailable; overwritten and removed copies count until they expire.
- An upload sets aside room for its file as it starts. A file you upload counts at once; one abandoned before it finishes uploading keeps its room for about two hours, and a mailbox archive going up in parts for up to 23 hours unless you cancel it.
- A file an agent writes counts as it is written, a proposal waiting for approval included. Rejecting a proposal frees its room only once AskRAI removes what the agent wrote and its kept copy expires, up to about 39 days later.
- Every hosted call sets aside room for its files. For about 17 minutes after it starts, a call holds room for the most it could save, 5 files of 25 MB, until AskRAI has counted what it actually saved. So an empty 10 GB allowance has room for about 80 calls in any 17 minutes, and fewer as it fills; a call past that runs without saving files.
- Overwritten and removed copies count until they expire. AskRAI keeps each copy of a file that is overwritten or removed for 30 days. A tool that saves to the same file again and again uses room for every copy, and once that fills the allowance, hosted calls save no files until enough copies expire.
- Deleting a project frees its share only once its files are removed and their kept copies expire, up to about 39 days later.
Activity tab
The Activity log lists what happened on the project, newest first: what its agents and people did, and what its assistants did. An assistant is not on the team, so each of its entries is marked Assistant: when it joined the project and when it left. Show assistants, beside the title once the project has had an assistant, takes their entries out of the list and puts them back. Load more reads older entries.
Each call an agent makes to one of its tools is an entry too, such as called crm_createCase on tool server 'CRM', with the tool's name at its right; one the platform refused before it ran reads could not call. Click it to see the tool and its server, the input the agent sent and the start of what came back, with the server's credentials removed. A call whose input a guardrail refused shows none. A call made to a server while it is marked as a simulated system is marked Simulated, and keeps the server's name and mark as they were then. Agents do not read these entries in their own activity, so a busy team's lookups never crowd out its tasks and messages.
A reset clears the team's entries and leaves the assistants'.
Budget tab
The Budget tab tracks spending against the project's budget total.

The Budget tab follows spend as the team's agents beat and its assistants reply, so the latest figure appears without a reload.
When a budget is allocated, the Budget overview shows the amount used against the total (for example $62.43 of $100 allocated), the percentage utilized over a bar, and rows for Allocated, Spent by the team, Spent by assistants while the project has assistants or a removed one has spent or replied, and Remaining, the last of which reads an amount, At budget limit, or Over budget by $20.00. The two spent rows add up to the amount used. If no budget is set, the tab reports that spend is uncapped, tells you how much has accrued so far, and prompts you to edit the project to allocate one.
Under Spent by the team, each agent on the team has a row with its spend and its share of what the team has spent, largest first; an agent that has not spent anything reads no spend yet. Deleting an agent removes its row but not its spend, so a last row, Deleted agents and earlier spend, holds whatever the agents listed do not account for, so the rows cover all of the team's spend. A project with no budget lists the same rows, since a share is of what was spent rather than of a budget.
Under Spent by assistants, each of the project's assistants has a row with its spend and how many replies it has given, counting everyone's chats with it, in the order they were added. Removing an assistant keeps its spend, so its row stays while it has spent anything or given a reply.
The Budget tab reads amounts of $100 or more in whole dollars. Below that, they read in dollars and cents, and small amounts are never rounded away: a project that has spent a fraction of its budget total reads <1% utilized rather than 0%, one that is nearly exhausted reads >99% utilized rather than 100%, and an amount under a cent keeps two significant digits, such as $0.0041, rather than reading $0.00. The project header's Budget tile carries the same percentage, as <1% used, beside what has been spent of the budget total.
The budget total is the only budget value you set directly. Usage accrues automatically as the project's agents beat and its assistants answer — each beat and each answer is priced from its model's token rates, which you can set per model on Model Providers. The cap is measured against the project's lifetime spend; it does not reset at the start of a month.
When a project exhausts its budget, AskRAI hard-stops the whole team: every agent stops, the run state becomes Stopped, and the project's status is set to On hold. The header's Budget tile reads Budget exhausted and Start team is disabled. Recovery therefore takes two steps — raise the Budget total (USD) and set the status back to Active — because raising the budget alone leaves the project on hold, and Start team stays disabled until its status is Active. Neither edit restarts the team: once both are saved, press Start team. Lowering the budget total below what the project has spent changes no status: on a project still Active, raising the budget is the only step before Start team.
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 of the stop, which opens this tab. So does an agent stopped by its own spend cap.
Idle check-in
Beneath the budget, the Budget tab reports the project's Idle check-in — the longest an agent with nothing to do waits between beats.

The readout states the ceiling in plain units, and says outright that a wake overrides it.
This is the other half of what a team costs. The budget total bounds the total a project may spend; Idle check-in bounds the rate a team that has finished its work keeps spending, because a beat is a model call whether or not there is anything to do. An agent whose beats change nothing doubles its own interval toward this ceiling; anything sent to it — a message, a task, a person acting — wakes it immediately regardless. See Agent Heartbeat for the full rule.
Change it by editing the project.
Dashboard tab
The Dashboard tab is one grid of cards and charts that the people on the project arrange for everyone who reads it: dashboards pinned from the Dashboard Assistant, charts of the project's events, and figures your own systems write through the API. See Dashboard.
Events tab
The Events tab declares the event types the project records, such as a case closed and whether the customer stayed, and lists the events its agents and people have recorded. See Project Events.
Editing a project
Open More in the project header and choose Edit to open the edit dialog. Editing is where you set the project's status, budget and brief. Edit opens with Write access to the project, which writes the brief; every other field needs Admin, and with Write alone they are disabled, under a reason naming the Admin access they need. With Read, Edit is disabled, with a reason naming the Write access it needs.

The edit dialog adds Status, Budget total (USD), Idle check-in (minutes), Assistant suggestions and the brief on top of the name and description.
The edit dialog exposes these fields:
| Field | Description |
|---|---|
| Name | The project's display name (required), unique within the organization as on create. The project's own name always saves, in another case too, as does a name two projects already shared |
| Description | A short summary of the project's purpose |
| Status | Active, On hold, or Archived. Saving On hold or Archived stands a running team down as soon as you save — see Project status |
| Budget total (USD) | The ceiling on total project spend, in US dollars. Must be greater than zero; cents are accepted. Leave it blank for no budget |
| Idle check-in (minutes) | The ceiling an idle agent's interval backs off to. A whole number of minutes from 1 to 525,600 (one year) |
| Assistant suggestions | Whether the project's assistants speak up unasked when a run hits something they can help with. On for a new project. Each suggestion is charged to the project's budget |
| Brief | The team's first message, up to 400 characters, which waits in the message composer while the project has no messages. Nothing is sent until someone sends it. Clear it to remove the brief |
| Brief goes to | Whom the brief starts addressed to: Everyone on project, or one person or agent on its team |
Click Save changes to apply. A value a field cannot take is named under that field as you type, and Save changes stays disabled until you correct it. Zero, a negative number, or text the field cannot read as a number in Budget total reads Enter an amount above $0, or leave it blank for no cap. To remove a cap entirely, clear the field rather than setting it to zero.
The dialog keeps the values it opened with, even if another admin changes the project while it is open. If they change a field the dialog shows, it says so above the fields. Saving writes only the fields you changed, so their change to any other field stands. To see their change, close the dialog and open it again. If you both changed the same field, the later save wins. Saving without changing anything closes the dialog and writes nothing.
Idle check-in is checked the same way: a value outside 1 to 525,600, or one that is not a whole number, reads Enter a whole number from 1 to 525600. under the field.
Project status
A project's status decides whether its team may run at all; the run controls in the header decide whether it runs now. Only an Active project's team can run.
| Status | Meaning |
|---|---|
| Active | The project is in normal use, and its team can be started |
| On hold | Work is on hold. Saving On hold while the team runs pauses it as soon as you save: the run state becomes Paused, and every running agent stops beating and spending. A beat already under way finishes |
| Archived | The project is retired but retained for reference, and is read-only. Saving Archived while the team runs stands it down the same way, except that the run state becomes Stopped |
While the status is not Active, Start team — or Resume, on a paused team — is disabled, and the reason is shown under the run controls: Project is on hold — set its status to Active to run the team, or Project is archived — set its status to Active to run the team. An agent's Run heartbeat on its Heartbeat tab and the Resume on its Budget tab are disabled too, with the same reason. Pause and Stop stay available whatever the status, so you can always wind a team down.
The save only moves what is still running. A team you had already paused or stopped keeps its run state, and so does an agent stopped on its own — from its own run control, or by its own spend cap.
Setting the status back to Active restarts nothing. Once it is saved, press Resume in the header for a paused team, or Start team for a stopped one — the same last step as recovering from a budget stop.
An archived project is read-only
While a project is Archived, nothing on it can change: no message can be sent, no task created, edited or deleted, no proposal approved or rejected, nobody added to or removed from its team, no agent created or edited, no workspace file or folder uploaded, renamed, moved, deleted or restored, no event type declared or event recorded, and no Dashboard arranged. A reset is refused too. Everything stays readable: its messages, tasks, team, agents' settings, workspace, activity and budget.
The header says Read-only: Project is archived — set its status to Active to change it. The message and task composers are not shown, and every other control that would change something is disabled with that reason. AskRAI refuses these changes however they are made, not only in the console. To work on it again, edit the project and set its status to Active — Edit and Delete stay available on an archived project.
Deleting a project
Open More in the project header and choose Delete to open a confirmation dialog. Deleting a project is permanent, so AskRAI asks you to confirm.
Deleting a project needs Admin access to it, which every Platform Admin holds. Anyone else sees Delete disabled, with a reason naming the Admin access it needs.
Deleting a project permanently removes it and cannot be undone. The confirmation dialog names the project and warns that it will be permanently deleted with its agents, its team and its workspace files, and every task, message and activity entry on it — make sure you have selected the right project before confirming.
The project's team and its work go with it:
- Its agents are deleted, together with their skill pins, tool grants and governance attachments. The skills, tool servers, guardrails, policies and egress allowlists themselves stay, and stop counting those agents as users, so an agent of a deleted project never holds up deleting one.
- Its people come off the team. They stay in your directory.
- Its workspace files are deleted.
- Its tasks, messages and activity are deleted.
- Its notifications and run state are removed.
Its proposals and beat transcripts are kept as the record of what its agents did, but no screen can reach them once the project is gone. To remove them too, Reset the project before you delete it.
Anyone else with the project open learns of the delete within a few seconds. Their workspace is replaced by a page saying This project was deleted, which offers no control but Back to projects, and the project leaves their project list. Someone whose connection had dropped meanwhile, or who stops being able to read a project while it is open because it is no longer shared with them, sees This project is no longer available to you instead, within about 30 seconds.
Troubleshooting
| Symptom | Likely cause | Resolution |
|---|---|---|
| You see no organizations or projects, and Projects reads Nothing is shared with you yet | No organization or project is shared with you | Ask one of the Platform Admins the message names to share an organization or a project with you, then reload the page |
| No organizations yet appears instead of projects | The tenant has no organizations, which projects require | Create an organization under Admin → Organizations, then return to Projects |
| The project list is empty or unexpected | A different organization is active, or the project is not shared with you | Confirm the active organization in the header org switcher — the list is scoped to it — and ask one of the project's Admins to share it with you |
| The + button, New project or Create → Project is disabled, with a reason naming Write access to this organization | You hold less than Write on the active organization | Ask one of its Admins, or a Platform Admin, to share it with you at Write, then reload the page |
| Edit in the project header's More menu 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 make the change |
| Name reads This organization already has a project named '…', and Create or Save changes is disabled | Another project in the organization goes by that name, differing at most in case, symbols or extra spaces | Choose a name that differs by more than that. The project the message names may not be shared with you |
| Save changes is disabled and Budget total reads Enter an amount above $0, or leave it blank for no cap. | Zero, a negative value, or text that is not a number was entered in the edit dialog | Enter a number greater than zero, or clear the field for no budget |
| The Budget tile reads Budget exhausted and Start team is disabled | The project spent its budget total and hard-stopped, which also set its status to On hold, or its budget total was lowered below what it has spent, which leaves it Active | Raise the Budget total (USD), set the status back to Active if it is On hold, then press Start team |
| Start team or Resume is disabled and reads Project is on hold — set its status to Active to run the team (or Project is archived — …) | Only an Active project's team can run | Set the status back to Active when editing the project, then press Start team or Resume |
| The team stopped beating right after you saved the project | You saved its status as On hold or Archived, which stands a running team down at once | If that was not intended, set the status back to Active and press Resume (On hold) or Start team (Archived) |
| A project is missing from the sidebar | It is Archived, which the list leaves out | Switch on Show archived under the search box |
| Nothing on a project can be changed, and the header reads Read-only | The project is Archived | Set its status to Active when editing the project |
| You set the project back to Active but the team is not running | Saving Active restarts nothing | Press Resume or Start team in the project header |
| Start team is disabled and says no chat model is enabled | No chat model is enabled for the tenant, or the model list is still loading | Enable one under Model Providers — a project with budget to spare still cannot start without a model |
| The Budget tab says spend is uncapped | No budget total has been allocated | Edit the project and set a Budget total (USD) |
| The graph reads No team yet | The project has no people, agents or assistants | Add members on the Team tab |
| An agent says it wrote a file, but the Workspace tab does not show it | The tab lists what was there when you opened it, or the tool linked a file it never finished uploading | Open the tab again; a file the tool never finished uploading is not added |
| An agent says it saved a file itself, but the Workspace tab does not show it | The agent is at Manual approval, so the file waits in Pending approvals, or the folder left the agent's write access before the file was saved, which the Activity tab names | Approve the proposal on the Interactions tab, or see what an agent writes |
| A file shows No preview for this type of file | Only PNG, JPEG and WebP images, Markdown, plain-text, CSV and JSON files, Word documents, Excel workbooks, PDFs and PowerPoint decks are shown in the console | Use Download to open it on your computer |
| A PDF says The file is protected by a password | The PDF needs a password to open, which the preview never asks for | Use Download and open it on your computer with its password |
| A link in a message or a task's result reads deleted file | The file the agent cited has been deleted since, or was never one of this project's files | A delete is final; ask the agent to write the file again if it is still needed |
| An upload is refused with This organization's workspace storage is full | Your tenant's files use its whole file storage allowance, which the bottom of the Workspace tab shows | Delete files you no longer need, whose room frees once AskRAI removes them and their kept copies expire, or ask AskRAI to raise the allowance |
| A file you chose to upload is refused as larger than 100 MB | A workspace file can be at most 100 MB, but for an Outlook mailbox archive (.pst, .ost), which can be 20 GB | Split it, or share it from where it already lives |
| A mailbox archive is refused with This organization's workspace storage cannot hold this archive | The archive is larger than the room left in your tenant's file storage allowance | Ask AskRAI to raise the allowance, then upload it again |
| A mailbox archive's upload ran out of time | It did not finish within 23 hours of starting | Upload it again from a faster connection |
A .pst or .ost larger than 100 MB is refused as no Outlook mailbox archive | Its first bytes are not an Outlook data file's, though its name says so; nothing of it is uploaded | Export the mailbox from Outlook again, and upload that file |
| A mailbox archive reads Not indexed: it is encrypted and cannot be read | An .ost that Windows encrypted for its own computer, which only that Outlook can open | In Outlook, export the mailbox as a .pst file, and upload that |
| A mailbox archive reads Not indexed: its format cannot be read | The file is damaged, or is not an Outlook data file at all | Repair it with Outlook's Inbox Repair Tool, or export the mailbox again, and upload that file |
| A mailbox archive reads Not indexed: indexing kept failing | Indexing failed five times in a row on AskRAI's side | Upload it again as a new version; if that fails too, contact AskRAI |
| A mailbox archive reads Not indexed: no message in it could be read | The archive opened, but every folder holding mail is damaged | Repair it with Outlook's Inbox Repair Tool, or export the mailbox again, and upload that file |
| An indexed archive says some folders or messages could not be read | Those parts of the archive are damaged | Repair it with Outlook's Inbox Repair Tool and upload it again as a new version |
| A Word, Excel or PowerPoint file shows as a plain download of no particular type | Its contents are not the file its extension names, such as a renamed ZIP | Open it in its application, save it again under its proper type, and upload that |
A macro-enabled (.docm, .xlsm, .pptm) or Excel 97-2003 (.xls) file shows as a plain download of no particular type, though its contents are right | It was uploaded before AskRAI previewed these files | Upload it again as a new version |
An .xls file's preview says the file could not be read | It is another Office 97-2003 file under an .xls name, such as a Word .doc, or a workbook locked by a password | Use Download to open it on your computer |
| An agent beats far less often than its interval says | The project's team has been idle, so the agent has backed off toward Idle check-in | Send the agent something, or lower Idle check-in when editing the project |
| Save changes is disabled and Idle check-in reads Enter a whole number from 1 to 525600. | A fractional or out-of-range value in the edit dialog | Enter a whole number of minutes within the range |
| Delete in the project header's More menu 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 — or to share it with you at Admin, then reload the page |
| A workspace control, such as Upload, New folder or Restore, is disabled, with a reason naming Write access | You hold less than Write on the project | Ask one of its Admins, or a Platform Admin, to share it with you at Write, then reload the page |
Related pages
- Team — add people and AI agents to a project and map how they report to one another
- Interactions — run the project's team as a live, autonomous workspace with messages, tasks, and run controls
- Dashboard — arrange the project's cards and charts, and pin an assistant's dashboards to it
- Project Events — declare what the project records, and chart it on the Dashboard
- Sharing & Access — share a project at Read, Write or Admin, and the decisions each level holds
- Organizations — the organizations that contain your projects and scope the Projects plane
- Users, Roles & Groups — manage the directory of people you can assign to projects
Notifications
The bell in the console header and its toasts — what its count means, how the list behaves, which events notify whom, where each notification opens, and how long notifications last
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