RelevanceAI · jordanc-relevanceai · Sep 7, 2026
diff --git a/build/agents/create-an-agent.mdx b/build/agents/create-an-agent.mdx
@@ -88,4 +88,4 @@ Once you've created an Agent, explore the rest of the build guides to refine it:
 - [Triggers](/build/agents/build-your-agent/triggers) — run your Agent automatically on a schedule, from a webhook, or from an integration
 - [Alerts](/build/agents/build-your-agent/alerts) — get notified when your Agent needs attention, and define when it should loop in a human
 - [Memory](/build/agents/build-your-agent/memory) — configure how your Agent retains context across conversations
-- [Version history](/build/agents/build-your-agent/version-history) — every save creates a snapshot you can restore, so you can experiment without losing working versions
+- [Version history](/build/platform/version-history) — every save creates a snapshot you can restore, so you can experiment without losing working versions
diff --git a/build/invent/invent.mdx b/build/invent/invent.mdx
@@ -27,7 +27,7 @@
    Invent defines the checks each Agent must pass before launch and samples live runs after deployment. When quality drops, it diagnoses the problem and proposes changes to prompts, Tools, examples, models, or orchestration. It can test those changes against the same requirements before you approve them.
  </Card>
  <Card title="Review performance and find opportunities" icon="chart-line">
    Invent reviews Agent activity, errors, Evals, and performance dashboards to diagnose problems and recommend improvements. Describe a recurring process, and it can help identify where Agents, Tools, or Workforces could automate it.
  </Card>
 </CardGroup>

@@ -89,7 +89,7 @@

 <AccordionGroup>
  <Accordion title="Project isolation">
    Invent's access to Relevance AI is scoped to the active project at the API-key and fine-grained authorization layers, not only in the interface. Each internal platform request uses the active project ID and the caller's API key, then passes through the standard authorization checks. Enabling Invent in a sandbox project does not grant it access to assets in a production project.
  </Accordion>

  <Accordion title="Integration reach">
@@ -220,7 +220,7 @@
   <Accordion title="Restore a version" icon="clock-rotate-left">
     Ask Invent to roll an asset back to an earlier version — for example, "Restore the previous version of this tool". Invent copies that version into the current draft, leaving the live published version unchanged until you publish. This restores an earlier version of an existing asset; it doesn't recover one that's been deleted.
 
-    Invent always asks you to confirm before restoring, and appends `(restored)` to the version name so the restored state is easy to identify later. For a full guide to version history — including how to restore and rename versions from the builder UI, and how retention works — see [Version history](/build/agents/build-your-agent/version-history).
+    Invent always asks you to confirm before restoring, and appends `(restored)` to the version name so the restored state is easy to identify later. For a full guide to version history — including how to restore and rename versions from the builder UI, and how retention works — see [Version history](/build/platform/version-history).
   </Accordion>
     </AccordionGroup>
   </Tab>
@@ -230,7 +230,7 @@
 
 Invent can build an initial Evals suite, review results, investigate failed Checks, and diagnose performance alarms for Agents and Workforces.
 
-<Card title="Learn more about Evals" icon="chart-line" href="/build/agents/evals/introduction">
+<Card title="Learn more about Evals" icon="chart-line" href="/build/platform/evals/introduction">
   Learn how to create scenarios and reusable Checks, run evaluations, and monitor live performance.
 </Card>
 

diff --git a/build/agents/evals/checks.mdx → build/platform/evals/checks.mdx b/build/agents/evals/checks.mdx → build/platform/evals/checks.mdx
@@ -10,7 +10,7 @@ A Check is one pass-or-fail criterion. Every Agent and Workforce has its own lib
 - **To a Monitor dashboard** — it runs on a sampled portion of live tasks.
 - **To a one-off evaluation** of already-completed tasks selected from the task list.
 
-This page is the reference for what each type scores. To attach one while building a Test, see [creating Tests](/build/agents/evals/test-sets).
+This page is the reference for what each type scores. To attach one while building a Test, see [creating Tests](/build/platform/evals/test-sets).
 
 ---
 
@@ -99,7 +99,7 @@ The Checks tab lists every Check on the Agent or Workforce, grouped by type. Fil
 
 ---
 
-Next: Learn how to [run Evals](/build/agents/evals/running-evaluations) against your Test sets.
+Next: Learn how to [run Evals](/build/platform/evals/running-evaluations) against your Test sets.
 
 ## Frequently asked questions (FAQs)
 

diff --git a/build/agents/evals/introduction.mdx → build/platform/evals/introduction.mdx b/build/agents/evals/introduction.mdx → build/platform/evals/introduction.mdx
@@ -1,10 +1,10 @@
 ---
 title: 'Introduction to Evals'
 sidebarTitle: 'Introduction to Evals'
 description: 'Test and evaluate Agents and Workforces with simulated conversations and reusable scoring criteria'
 ---

 Evals is where you test and measure performance. It works on both Agents and Workforces, and lives in the **Evaluate** tab of the Agent or Workforce builder, next to **Build** and **Run**. Use it to create Test sets, define reusable scoring criteria, run evaluations, and monitor quality on live conversations.

 <div
  className="video-embed"
@@ -30,11 +30,11 @@
  ></iframe>
 </div>

 ## Why use Evals?

 Any time you put an Agent to work, you want to be sure it's accomplishing your business outcomes. That might be increasing marketing qualified leads, or reducing the time it takes to respond to a lead. Evals gives you the confidence that your Agent is hitting the mark with its target audience — and that it still does after the next change.

 You write Tests that simulate the users and situations you care about, and Evals scores each one against success criteria you define. Agents and Workforces are non-deterministic — the same input can produce a different answer, and a change to a prompt, a Tool, or a model can shift behavior somewhere you weren't looking — so holding the Tests and the criteria steady is what makes one version's score comparable to the next.

 <CardGroup cols={3}>
  <Card title="Run Tests" icon="flask-vial">
@@ -50,11 +50,11 @@

 ---

 ## Overview of Evals

 Evals has five core features, each with its own section in the left sidebar of the Evaluate tab:

 - **Test** — Create and manage Test sets. Each Test set holds Tests that simulate users; running a Test produces a conversation with the Agent or Workforce that gets scored by the criteria you attach.
 - **Runs** — Past evaluation run results. Browse average scores, tasks evaluated, progress status, cost (Credits and Actions), and creation date for every run.
 - **Checks** — Your library of scoring criteria; each one is called a Check. Create a Check once, then attach it to Tests, to Monitor dashboards, or to one-off evaluations of completed tasks.
 - **Publish** — Choose which Test sets must pass before your Agent or Workforce can be published. Set a minimum pass rate and optionally block publishing on failure.
@@ -89,13 +89,13 @@
 
 ---
 
-Next: Learn how to [create Tests](/build/agents/evals/test-sets) — the simulated conversations your Agent gets evaluated against.
+Next: Learn how to [create Tests](/build/platform/evals/test-sets) — the simulated conversations your Agent gets evaluated against.
 
 ## Frequently asked questions (FAQs)
 
 <AccordionGroup>
  <Accordion title="I don't see the Evaluate tab. How do I get access?">
    Evals is available on every plan. The **Evaluate** tab sits next to **Build** and **Run** in the Agent or Workforce builder — if it isn't there, [contact support](/get-started/support).
  </Accordion>

  <Accordion title="How are evaluations billed?">

diff --git a/build/agents/evals/monitor.mdx → build/platform/evals/monitor.mdx b/build/agents/evals/monitor.mdx → build/platform/evals/monitor.mdx
@@ -1,10 +1,10 @@
 ---
 title: 'Monitoring Evals'
 sidebarTitle: 'Monitoring Evals'
 description: 'Score the real conversations your Agent or Workforce is having against Checks, on dashboards you configure per sample rate'
 ---
 
-The **Monitor** section continuously scores live tasks against [Checks](/build/agents/evals/checks). Unlike the **Test** section, which runs simulated conversations, Monitor evaluates the real conversations your Agent or Workforce is having.
+The **Monitor** section continuously scores live tasks against [Checks](/build/platform/evals/checks). Unlike the **Test** section, which runs simulated conversations, Monitor evaluates the real conversations your Agent or Workforce is having.
 
 Monitor is organized into **dashboards** — you can create more than one (for example, one focused on tone, another on tool-use accuracy) and configure each independently.
 
@@ -44,7 +44,7 @@

 You also get:

 - **Overall score timeseries** to spot regressions or improvements over time.
 - **Per-Check charts** so you can see which criteria are slipping.
 - **Version markers** that line up score changes with each publish.
 - **A list of evaluation runs** with score, name, and a drill-in to the full conversation.

diff --git a/build/agents/evals/running-evaluations.mdx → build/platform/evals/running-evaluations.mdx b/build/agents/evals/running-evaluations.mdx → build/platform/evals/running-evaluations.mdx
@@ -1,10 +1,10 @@
 ---
 title: 'Running Evals'
 sidebarTitle: 'Running Evals'
 description: 'Run Test sets and individual Tests, read the scores that come back, and require evals to pass before publishing'
 ---
 
-Once you've created [Tests](/build/agents/evals/test-sets) and defined [Checks](/build/agents/evals/checks), you're ready to run evaluations and see how your Agent or Workforce performs. You can run them by hand, or have a publish run them for you.
+Once you've created [Tests](/build/platform/evals/test-sets) and defined [Checks](/build/platform/evals/checks), you're ready to run evaluations and see how your Agent or Workforce performs. You can run them by hand, or have a publish run them for you.
 
 ---
 
@@ -94,7 +94,7 @@
 
 ---
 
-Next: Learn about [monitoring Evals](/build/agents/evals/monitor) — scoring the real conversations your Agent or Workforce is having.
+Next: Learn about [monitoring Evals](/build/platform/evals/monitor) — scoring the real conversations your Agent or Workforce is having.
 
 ## Frequently asked questions (FAQs)
 

diff --git a/build/agents/evals/test-sets.mdx → build/platform/evals/test-sets.mdx b/build/agents/evals/test-sets.mdx → build/platform/evals/test-sets.mdx
@@ -4,7 +4,7 @@ sidebarTitle: 'Creating Tests'
 description: 'Create Tests that simulate real user conversations with your Agent or Workforce, and group them into Test sets'
 ---
 
-A **Test** simulates one conversation with your Agent or Workforce. You describe a user in the **Scenario** field — *"You are a long-time customer who was charged twice for the same order"* — and Relevance plays that user, generates their messages, and hands back the transcript. The [Checks](/build/agents/evals/checks) you attach score it.
+A **Test** simulates one conversation with your Agent or Workforce. You describe a user in the **Scenario** field — *"You are a long-time customer who was charged twice for the same order"* — and Relevance plays that user, generates their messages, and hands back the transcript. The [Checks](/build/platform/evals/checks) you attach score it.
 
 Tests live in a **Test set**, which is what a run points at — run the whole set, or a single Test inside it.
 
@@ -47,7 +47,7 @@ Tests live in a **Test set**, which is what a run points at — run the whole se
      </Tab>
    </Tabs>
 
-   See [Check types](/build/agents/evals/checks) for what each type scores and the fields it takes.
+   See [Check types](/build/platform/evals/checks) for what each type scores and the fields it takes.
 
 8. Set **When the test hits an approval** to control how the Test resolves Tool approvals and escalations mid-conversation:
 
@@ -112,7 +112,7 @@ Tests can be reorganized across Test sets as your testing strategy evolves. Each
 
 ---
 
-Next: Read the [Check types](/build/agents/evals/checks) reference — what each type scores and how the Checks tab works.
+Next: Read the [Check types](/build/platform/evals/checks) reference — what each type scores and how the Checks tab works.
 
 ## Frequently asked questions (FAQs)
 

diff --git a/build/agents/share-your-agent.mdx → build/platform/sharing/share-your-agent.mdx b/build/agents/share-your-agent.mdx → build/platform/sharing/share-your-agent.mdx
@@ -1,7 +1,7 @@
 ---
-title: "Share Your Agent"
-sidebarTitle: "Share Your Agent"
-description: "Learn how to share your agent with others using different UI options"
+title: "Share your Agent"
+sidebarTitle: "Agents"
+description: "Learn how to share your Agent with others using different UI options"
 ---
 
 ## Overview
@@ -9,10 +9,10 @@
 Easily share your AI agent with others by choosing how they can interact with it. Whether you want to send a live chat link, embed a support widget, showcase tasks in an iframe, or allow full template cloning, you have flexible options to fit any use case.

 <Warning>
 Enabling any embed option (Chat UI, Chat Widget, or Task UI) or the Clonable Template option makes your Agent publicly accessible. The resulting link is a public URL that search engines can index and that anyone can share, so the Agent may be discovered without you sending the link yourself — anyone with it can run your Agent on your credits or clone it into their own project. Disable the option in the Agent's share settings to revoke access.
 </Warning>

 ## Clonable Template

 Let others clone your Agent - complete with its instructions and setup - into their own workspace. This makes it easy to share best practices, pre-built use cases, or workflows without needing to rebuild from scratch. Cloned agents use the recipient's credits, not yours, making this perfect for scalable distribution.


diff --git a/build/tools/share-your-tool.mdx → build/platform/sharing/share-your-tool.mdx b/build/tools/share-your-tool.mdx → build/platform/sharing/share-your-tool.mdx
@@ -1,5 +1,6 @@
 ---
 title: 'Share your Tool'
+sidebarTitle: 'Tools'
 description: 'Learn how to share your Tool with others using different UI options'
 ---
 
@@ -8,11 +9,11 @@
 By default, your tool is only accessible by you and your agents. Click on `Share` to: 

 1. Create a sharable link for your tool
 2. Get an embeddable iframe for your tool
 3. Allow others to clone a copy of your tool

 <Warning>
 Enabling a sharable link, embed, or cloneable template option makes your Tool publicly accessible. The resulting link is a public URL that search engines can index and that anyone can share, so the Tool may be discovered without you sending the link yourself — anyone with it can run your Tool on your credits or clone it into their own project. Disable the option in the Tool's share settings to revoke access.
 </Warning>

 <div

diff --git a/build/workforces/share-your-workforce.mdx → ...platform/sharing/share-your-workforce.mdx b/build/workforces/share-your-workforce.mdx → ...platform/sharing/share-your-workforce.mdx
@@ -1,24 +1,24 @@
 ---
 title: "Share your Workforce"
-sidebarTitle: "Share your Workforce"
+sidebarTitle: "Workforces"
 description: "Learn how to share your Workforce with others as a cloneable template"
 ---
 
 ## Overview

 You can easily share your Workforce with others by creating a cloneable template. Once you create and share your Workforce's cloneable template, this will allow others to clone your entire Workforce into their own projects. 

 <Info>
 **Enterprise customers:** When sharing workforces with team members using RBAC, you'll need to grant permissions to both the workforce and all agents within it. Learn more about [Workforce Permissions in RBAC](/enterprise/rbac#workforce-permissions).
 </Info>

 <Warning>
 Enabling the cloneable template option or any embed option (Chat UI or Chat Widget) makes your Workforce publicly accessible. The resulting link is a public URL that search engines can index and that anyone can share, so the Workforce may be discovered without you sending the link yourself — anyone with it can clone your Workforce or embed it on their site. Disable the option in the Workforce's share settings to revoke access.
 </Warning>

 ## Cloneable template

 You can learn how to share your Workforce as a cloneable template by following these steps: 

 <div style={{ width: '100%', position: 'relative', paddingTop: '56.25%' }}>
 <iframe src="https://app.supademo.com/embed/cmbfspjqz498wsn1r8t02b75k?embed_v=2" frameBorder="0" title="Relevanceai Demo" allow="clipboard-write; fullscreen" webkitAllowFullscreen="true" mozAllowFullscreen="true" allowFullscreen style={{ position: 'absolute', top: 0, left: 0, width: '100%', height: '100%', border: '3px solid #5E43CE', borderRadius: '10px' }} />

diff --git a/...s/give-your-agent-tasks/bulk-schedule.mdx → build/platform/tasks/bulk-schedule.mdx b/...s/give-your-agent-tasks/bulk-schedule.mdx → build/platform/tasks/bulk-schedule.mdx
diff --git a/...-agent-tasks/interact-with-your-agent.mdx → ...atform/tasks/interact-with-your-agent.mdx b/...-agent-tasks/interact-with-your-agent.mdx → ...atform/tasks/interact-with-your-agent.mdx
diff --git a/...s/give-your-agent-tasks/task-overview.mdx → build/platform/tasks/task-overview.mdx b/...s/give-your-agent-tasks/task-overview.mdx → build/platform/tasks/task-overview.mdx
@@ -12,7 +12,7 @@
   <Card title="Run tab" icon="play">
     The Agent and Workforce builders each have a Run tab showing that Agent or Workforce's Tasks, where you can also start new ones.
   </Card>
-  <Card title="Tasks page" icon="list-check" href="/build/agents/give-your-agent-tasks/tasks-page">
+  <Card title="Tasks page" icon="list-check" href="/build/platform/tasks/tasks-page">
     Every Task across all your Agents and Workforces in one list, for monitoring and acting in bulk.
   </Card>
 </CardGroup>
@@ -39,14 +39,14 @@

 The Task list has a filter builder for narrowing down to exactly the Tasks you need. You can filter by:

 - **Status** — Task state like Running, Completed, Paused, or Timed out
 - **Agent** — Tasks from a specific Agent
 - **Tool usage** — which Tools the Task used
 - **Errors** — failure type: **Agent has errored** (the Agent itself stopped on an error) or **Has active tool failures** (a Tool failed mid-run, even if the Agent kept going)
 - **Metadata, date, and more** — custom fields, time range, who triggered the Task, and other conditions

 Combine the two error filters to catch every kind of failure, including Tool failures that never surfaced as an obvious error.
 
 ## Viewing Tasks across all your Agents
 
-The views above each focus on a single Agent or Workforce. To monitor and troubleshoot every Task across all your Agents and Workforces from one place, head to the [Tasks page](/build/agents/give-your-agent-tasks/tasks-page). It's where you triage escalations, errors, and approvals, and act in bulk when a whole group needs the same fix. Selecting any Task there opens the same conversation (its messages and Tool runs) in a side panel.
+The views above each focus on a single Agent or Workforce. To monitor and troubleshoot every Task across all your Agents and Workforces from one place, head to the [Tasks page](/build/platform/tasks/tasks-page). It's where you triage escalations, errors, and approvals, and act in bulk when a whole group needs the same fix. Selecting any Task there opens the same conversation (its messages and Tool runs) in a side panel.
diff --git a/...ents/give-your-agent-tasks/task-queue.mdx → build/platform/tasks/task-queue.mdx b/...ents/give-your-agent-tasks/task-queue.mdx → build/platform/tasks/task-queue.mdx
diff --git a/...ents/give-your-agent-tasks/tasks-page.mdx → build/platform/tasks/tasks-page.mdx b/...ents/give-your-agent-tasks/tasks-page.mdx → build/platform/tasks/tasks-page.mdx
@@ -11,7 +11,7 @@
 Tasks from both Agents and Workforces appear here, and the same triage and bulk action flows apply to both.
 
 <Note>
-Each Task is a single run of work (a conversation or workflow) carried out by an Agent or Workforce. For what a Task is and how to read one, see [Tasks](/build/agents/give-your-agent-tasks/task-overview).
+Each Task is a single run of work (a conversation or workflow) carried out by an Agent or Workforce. For what a Task is and how to read one, see [Tasks](/build/platform/tasks/task-overview).
 </Note>
 
 ## Tabs
@@ -30,7 +30,7 @@
 Available bulk actions:

 - **Approve** or **Reject** pending approvals.
 - **Rerun** errored Tasks from the failing step.

 A confirmation modal shows how many Tasks will be affected before anything is sent.


diff --git a/...ents/build-your-agent/version-history.mdx → build/platform/version-history.mdx b/...ents/build-your-agent/version-history.mdx → build/platform/version-history.mdx
diff --git a/build/tools/create-a-tool.mdx b/build/tools/create-a-tool.mdx
@@ -36,7 +36,7 @@ This guide walks you through creating a Tool. For an overview of what Tools are
 6. Add **steps** — what should the Tool do with that data? Steps include LLM prompts, API calls, integrations, code execution, and more
 7. Define your **outputs** — what should the Tool return when it's done?
 8. Run individual steps to test as you build
-9. Give the Tool to an Agent or [share it](/build/tools/share-your-tool) as a standalone form
+9. Give the Tool to an Agent or [share it](/build/platform/sharing/share-your-tool) as a standalone form
 
 <div
   style={{
@@ -99,4 +99,4 @@ Once you've created a Tool, explore the rest of the build guides to refine it:
 - [Inputs](/build/tools/customize-tool/inputs) — configure what data your Tool receives
 - [Steps](/build/tools/customize-tool/steps) — chain actions together into a workflow
 - [Outputs](/build/tools/customize-tool/outputs) — define what your Tool returns
-- [Version history](/build/agents/build-your-agent/version-history) — every save creates a snapshot you can restore, so you can experiment without losing working versions
+- [Version history](/build/platform/version-history) — every save creates a snapshot you can restore, so you can experiment without losing working versions
diff --git a/build/workforces/create-a-workforce.mdx b/build/workforces/create-a-workforce.mdx
@@ -42,4 +42,4 @@ Once you've created a Workforce, explore the rest of the build guides to refine
 - [Add Tools](/build/workforces/build-an-ai-workforce/add-tools) — connect Tools directly within your workflow
 - [Add conditions](/build/workforces/build-an-ai-workforce/add-conditions) — create routing rules for smarter workflows
 - [Edge settings](/build/workforces/build-an-ai-workforce/edge-settings) — configure how connections between nodes behave
-- [Version history](/build/agents/build-your-agent/version-history) — every save creates a snapshot you can restore, so you can experiment without losing working versions
+- [Version history](/build/platform/version-history) — every save creates a snapshot you can restore, so you can experiment without losing working versions
diff --git a/changelog.mdx b/changelog.mdx
@@ -12,7 +12,7 @@

 The newest version of Invent is now available.

 Invent can create and edit Agents, Tools, Workforces, Knowledge tables, Triggers, and Evals, run tasks, pull your analytics, and much, much more. It has context over everything in your project and acts as a specialist who can help you create almost anything inside of Relevance AI.

 Open Invent from the badge tucked into the right edge of the screen, from the button in the bottom-right corner of the Home page, or from Invent in the left navigation menu. Invent is enabled per project: an organization admin opens Settings → Projects, selects the project, clicks Manage settings, and turns on the Invent toggle. See [Build with Invent](/build/invent/invent) for more information on using and configuring Invent.

@@ -22,27 +22,27 @@

 ## Concurrency visibility for project and organization admins

 ![Concurrency panel showing a seven-day usage chart with queued runs stacked in red above the limit line, 20 of 20 slots in use with 6 tasks waiting, and a live capacity by project bar with other projects anonymized](/images/changelog/changelog-concurrency-visibility.png)

 Concurrency monitoring on the Analytics page now covers queued runs, live slot counts, and a per-project capacity breakdown.

 Queued runs now stack in red above the limit line on the usage chart, live counters show slots in use and tasks waiting, and a per-project bar attributes running slots to the projects holding them. Between them you can see whether you're at the limit, how much is queued behind it, and which project is consuming the capacity. Project admins see the same charts with other projects' names and task details anonymized.

 Project admins find the chart on the Analytics page; organization admins can also view it on the Plan & Billing page.

 </Update>

 <Update label="June 29, 2026" description="Eval cost breakdowns and Workforce evaluations">

 ## Eval cost breakdowns and Workforce evaluations

 ![Eval run cost breakdown panel showing total credits and actions, with per-component rows for Scenario Runner, Agent Execution, and Checks broken down by AI Judge model and Tool Usage](/images/changelog/changelog-eval-cost-breakdown.png)

 Eval runs now show exactly where their cost goes, itemized per check, and cover full Workforce runs including sub-agent and tool calls.
 
 Each completed Eval run renders a cost breakdown panel that itemizes credit and action consumption per component. Checks account for 1 action per run across every check type, including LLM as Judge and Tool Usage, so the panel's totals reconcile to the exact source of every credit and action. Workforce runs that fan out to sub-agents or call tools record and evaluate each of those interactions, the same as individual Agent runs.
 
-To see the breakdown, open any completed Eval run; the panel appears alongside the results. See the [Evals documentation](/build/agents/evals/introduction) for full details.
+To see the breakdown, open any completed Eval run; the panel appears alongside the results. See the [Evals documentation](/build/platform/evals/introduction) for full details.
 
 </Update>
 
@@ -80,7 +80,7 @@

 ![Microsoft Teams trigger settings showing the new Outreach replies only toggle enabled](/images/changelog/changelog-teams-outreach.png)

 Microsoft Teams triggers now support an **Outreach replies only** mode that limits responses to direct replies on the Agent's own outbound DMs.

 The trigger distinguishes between inbound replies (replies to messages your Agent sent) and channel mentions. In outreach-only mode, only inbound replies route to the Agent — channel chatter doesn't trigger a run.

@@ -134,7 +134,7 @@

 You can now manage public sharing settings for all agents, workforces, and tools from one central location!

 Project-Level Public Agent Controls give admins the power to disable public cloning and embeddability across their entire workspace with a single setting. When you disable these features at the project level, they’re automatically turned off for all agents, workforces, and tools—and individual users can’t re-enable them.

 ➡️ Centralized control – Manage security settings for all assets from one place

@@ -182,7 +182,7 @@

 ![Agent Performance Observability](/images/changelog/changelog-observability.webp)

 You can now track how your agents perform in real-world scenarios with comprehensive production monitoring!  Just like software development has build → test → monitor stages, agent development now has the same complete lifecycle. After building your agents and testing them with Evals, you need visibility into production performance at scale.

 ➡️ **Automatic evaluation** – Set up LLM judges to continuously assess your agents on custom criteria like summary quality, hallucination detection, and workflow execution

@@ -194,7 +194,7 @@

 With Agent Performance Observability, you can catch performance degradations immediately—like when a model update changes behavior or agents start hallucinating—instead of discovering issues weeks later.

 🔐 **Permissions required:** Available exclusively for select Enterprise customers. Evals delivers the advanced testing capabilities needed for mission-critical AI deployments. This feature is not available on non-Enterprise plans.

 To access Agent Performance Observability, enterprise users can go to their agent’s dashboard and select the “Monitor” tab, then navigate to the “Test Suites” section. If you’re on an Enterprise plan and don’t yet have access, contact your Relevance AI sales representative to register interest.

@@ -253,13 +253,13 @@

 </Update>

 <Update label="March 10, 2026" description="Monitor organization concurrency usage with detailed analytics and timeseries data">

 ![Monitor organization concurrency usage with detailed analytics and timeseries data](/images/changelog/changelog-concurrency.webp)

 **Org Concurrency Timeseries: Track Your Organization’s Performance Analytics**

 You can now monitor your organization’s concurrency usage and limits with detailed timeseries data!

 View comprehensive analytics directly from your organization settings page under the Plan & Billing section, giving you complete visibility into how your team uses Relevance AI’s resources.

@@ -269,9 +269,9 @@

 ➡️ Usage limit monitoring – Keep track of your current usage against your plan limits to avoid unexpected throttling

 ➡️ Visual timeseries charts – Easy-to-read graphs show your concurrency patterns, helping you identify optimization opportunities

 With Org Concurrency Timeseries, you can make data-driven decisions about your AI operations, ensuring optimal performance and resource allocation across your entire organization.

 🔐 Permissions required: Organization Admin access to view billing and usage analytics

@@ -507,11 +507,11 @@

 ![Claude Opus 4.6 model now available in Relevance AI](/images/changelog/68faec2d3ffbd34e9c9295b9-changelog-claude.webp)

 **Claude Opus 4.6: Anthropic's Most Advanced AI Model Now Available**

 You can now access Anthropic's flagship Claude Opus 4.6 model directly in the platform, with an optional 1M context window variant for handling massive documents!

 Claude Opus 4.6 delivers exceptional performance on complex reasoning, coding, and advanced agentic tasks. This latest version brings Anthropic's most powerful AI capabilities to your workflows, with both standard and extended context options to match your specific needs.

 ➡️ Standard 200K token context window – Process lengthy documents and conversations with ease

@@ -519,7 +519,7 @@

 ➡️ Adaptive thinking support – Tackle complex reasoning and multi-step problem solving

 ➡️ Advanced image processing – Work with jpg, jpeg, gif, webp, and png files

 ➡️ Exceptional output quality – Benefit from improved reasoning and response generation

@@ -563,15 +563,15 @@

 </Update>

 <Update label="February 9, 2026" description="Test and validate AI agents with Evals: Enterprise-grade agent testing">

 ![Test and validate AI agents with Evals](/images/changelog/698a6f9d99180607d34d642c-changelog-evals.webp)

 **Evals: Test and Validate Your AI Agents with Confidence**

 You can now thoroughly test your AI agents with our powerful Evals feature, ensuring they perform exactly as expected in real-world scenarios!

 Evals provides a structured testing framework for your AI agents, allowing you to create test suites with multiple scenarios to validate functionality. Create golden test examples, simulate user interactions, and evaluate agent performance without triggering actual tool executions or external actions.

 ➡️ Create organized test suites – Group related tests together for better organization and management

@@ -583,9 +583,9 @@

 ➡️ Coming soon: Tool simulations – Test workflows with sensitive or expensive tools without triggering actual executions

 With Evals, you can confidently deploy agents knowing they've been thoroughly tested against a variety of scenarios, ensuring reliability and consistent performance for your users.

 **Available exclusively for select Enterprise customers**, Evals delivers the advanced testing capabilities needed for mission-critical AI deployments. To access Evals, enterprise users can go to their agent's dashboard and select the "Monitor" tab, then navigate to the "Test Suites" section. If you’re on an Enterprise plan and don’t yet have access, contact your Relevance AI sales representative to register interest. This feature is not available on non-Enterprise plans.

 Start building more reliable AI agents with comprehensive enterprise-grade testing today!

@@ -665,11 +665,11 @@

 Workforce Trigger Controls give you granular management over your automation workflows. Quickly pause specific triggers when issues arise, cancel problematic workflows, or pause an entire workforce at once—then resume operations when you're ready.

 ➡️ Pause individual triggers – Temporarily stop specific automations without affecting others

 ➡️ Cancel active workflows – Immediately terminate problematic processes

 ➡️ Resume paused triggers – Restart automations when issues are resolved

 ➡️ Pause entire workforces – One-click solution to halt all triggers during maintenance

@@ -783,11 +783,11 @@

 ![Control your meeting agent in real time with chat commands](/images/changelog/695a95a2a931a05c425b7b72-changelog-meeting-bot-real-time-commands.webp)

 **Meeting Agent Realtime Commands: Control Your AI Agent During Live Meetings**

 You can now trigger your AI meeting agent with custom commands during live meetings without interrupting the flow of conversation!

 Meeting Agent Realtime Commands lets you interact with your meeting bot during meetings by simply typing trigger words in the chat. Your agent springs into action when it detects these keywords, performing tasks like searching information, controlling recordings, or creating meeting artifacts—all while your meeting continues uninterrupted.

 ➡️ Use custom trigger words – Define specific phrases that activate your agent during meetings

@@ -799,7 +799,7 @@

 ➡️ Extend with any Relevance AI capability – Connect to Notion, Slack, or other tools for seamless workflows

 With Meeting Agent Realtime Commands, you can enhance your meeting productivity by leveraging AI assistance exactly when you need it, without disrupting the conversation flow.

 To set up your own meeting agent with custom commands, create a new agent from scratch, add the "Relevance AI Meeting Bot" under Triggers, add and configure your desired meeting bot tools (such as 'Pause Recording' and 'Resume Recording') and more general tools (such as 'Google Search' and 'Slide Builder') and trigger words.


diff --git a/docs.json b/docs.json
@@ -123,7 +123,6 @@
                       "build/agents/build-your-agent/alerts",
                       "build/agents/build-your-agent/memory",
                       "build/agents/build-your-agent/variables",
-                      "build/agents/build-your-agent/version-history",
                       {
                         "group": "Trigger Types",
                         "pages": [
@@ -167,27 +166,6 @@
                       }
                     ]
                   },
-                  {
-                    "group": "Evaluating Performance",
-                    "pages": [
-                      "build/agents/evals/introduction",
-                      "build/agents/evals/test-sets",
-                      "build/agents/evals/checks",
-                      "build/agents/evals/running-evaluations",
-                      "build/agents/evals/monitor"
-                    ]
-                  },
-                  {
-                    "group": "Running Tasks",
-                    "pages": [
-                      "build/agents/give-your-agent-tasks/task-overview",
-                      "build/agents/give-your-agent-tasks/tasks-page",
-                      "build/agents/give-your-agent-tasks/interact-with-your-agent",
-                      "build/agents/give-your-agent-tasks/bulk-schedule",
-                      "build/agents/give-your-agent-tasks/task-queue"
-                    ]
-                  },
-                  "build/agents/share-your-agent",
                   "build/agents/delete-agent"
                 ]
               },
@@ -207,7 +185,6 @@
                     ]
                   },
                   "build/tools/delete-tool",
-                  "build/tools/share-your-tool",
                   {
                     "group": "Tool Steps",
                     "pages": [
@@ -369,8 +346,7 @@
                       "build/workforces/workforce-features/workforce-task-view",
                       "build/workforces/workforce-features/approvals-and-escalations"
                     ]
-                  },
-                  "build/workforces/share-your-workforce"
+                  }
                 ]
               },
               {
@@ -391,6 +367,40 @@
                   "build/knowledge/knowledge-tool-steps",
                   "build/knowledge/use-snippets-for-quick-access"
                 ]
+              },
+              {
+                "group": "Platform",
+                "pages": [
+                  {
+                    "group": "Evaluating Performance",
+                    "pages": [
+                      "build/platform/evals/introduction",
+                      "build/platform/evals/test-sets",
+                      "build/platform/evals/checks",
+                      "build/platform/evals/running-evaluations",
+                      "build/platform/evals/monitor"
+                    ]
+                  },
+                  {
+                    "group": "Running Tasks",
+                    "pages": [
+                      "build/platform/tasks/task-overview",
+                      "build/platform/tasks/tasks-page",
+                      "build/platform/tasks/interact-with-your-agent",
+                      "build/platform/tasks/bulk-schedule",
+                      "build/platform/tasks/task-queue"
+                    ]
+                  },
+                  {
+                    "group": "Sharing",
+                    "pages": [
+                      "build/platform/sharing/share-your-agent",
+                      "build/platform/sharing/share-your-tool",
+                      "build/platform/sharing/share-your-workforce"
+                    ]
+                  },
+                  "build/platform/version-history"
+                ]
               }
             ]
           },
@@ -783,6 +793,62 @@
     }
   },
   "redirects": [
+    {
+      "source": "/build/agents/evals/introduction",
+      "destination": "/build/platform/evals/introduction"
+    },
+    {
+      "source": "/build/agents/evals/test-sets",
+      "destination": "/build/platform/evals/test-sets"
+    },
+    {
+      "source": "/build/agents/evals/checks",
+      "destination": "/build/platform/evals/checks"
+    },
+    {
+      "source": "/build/agents/evals/running-evaluations",
+      "destination": "/build/platform/evals/running-evaluations"
+    },
+    {
+      "source": "/build/agents/evals/monitor",
+      "destination": "/build/platform/evals/monitor"
+    },
+    {
+      "source": "/build/agents/give-your-agent-tasks/task-overview",
+      "destination": "/build/platform/tasks/task-overview"
+    },
+    {
+      "source": "/build/agents/give-your-agent-tasks/tasks-page",
+      "destination": "/build/platform/tasks/tasks-page"
+    },
+    {
+      "source": "/build/agents/give-your-agent-tasks/interact-with-your-agent",
+      "destination": "/build/platform/tasks/interact-with-your-agent"
+    },
+    {
+      "source": "/build/agents/give-your-agent-tasks/bulk-schedule",
+      "destination": "/build/platform/tasks/bulk-schedule"
+    },
+    {
+      "source": "/build/agents/give-your-agent-tasks/task-queue",
+      "destination": "/build/platform/tasks/task-queue"
+    },
+    {
+      "source": "/build/agents/share-your-agent",
+      "destination": "/build/platform/sharing/share-your-agent"
+    },
+    {
+      "source": "/build/tools/share-your-tool",
+      "destination": "/build/platform/sharing/share-your-tool"
+    },
+    {
+      "source": "/build/workforces/share-your-workforce",
+      "destination": "/build/platform/sharing/share-your-workforce"
+    },
+    {
+      "source": "/build/agents/build-your-agent/version-history",
+      "destination": "/build/platform/version-history"
+    },
     {
       "source": "/enterprise/org-project-controls-governance",
       "destination": "/enterprise/manage-projects-and-users-api"
@@ -1145,15 +1211,15 @@
     },
     {
       "source": "/evals",
-      "destination": "/build/agents/evals/introduction"
+      "destination": "/build/platform/evals/introduction"
     },
     {
       "source": "/build/agents/evals",
-      "destination": "/build/agents/evals/introduction"
+      "destination": "/build/platform/evals/introduction"
     },
     {
       "source": "/build/agents/build-your-agent/evals",
-      "destination": "/build/agents/evals/introduction"
+      "destination": "/build/platform/evals/introduction"
     }
   ]
 }