An agent can only see what you can see, and only do what you can already do in Opus. It builds new drafts on its own, and asks for your yes before other changes.
This applies to the Primary Agent and every agent in the Agents section of your left navigation. Agents are for Admins, so an agent works with your Admin access and never more.
Table of Contents:
What Agents Can See
An agent runs as the Admin who is chatting with it. That means it uses your permissions, the same access you have when you sign in to the dashboard. It can read the same information you can:
Team members, Locations, Roles, and Departments
Assignments, completions, and reporting
Your Library, including Courses, Modules, Resources, and Opus Docs
Paths, including their steps and who's on each one
Checklist and Audit submissions
Files and Library items you attach to a message
Agents also follow the AI Assist details on your Settings › Brand page, like your business type, mission statement, and rules for AI-written content.
Agents can't see anything outside Opus, like POS, payroll, or scheduling systems.
What Agents Can Change
Agents can build drafts, which your team doesn't see until they're published. They can draft Courses, Modules, Paths, Check-ins, Checklists, Audits, and Opus Docs.
Agents can also make other changes you can make in the dashboard, like editing existing content, publishing, assigning training, deleting items, adding or removing team members, and creating items like a Location, Role, Tag, or Task. They ask for your yes first, as described in How Agents Ask for Approval.
Most changes can't be undone, so read what the agent plans to do before you say yes.
Agents can't send messages or announcements to your team.
➡️ Learn more:
How to Draft Training with Opus Agents: what agents can draft and how to review it
How Agents Ask for Approval
Agents follow the same approval rules for every Admin:
New drafts don't need a yes: the agent builds the draft without asking, because no one sees it until it's published. Adding or editing screens in the draft it's building, or in a Course you asked it to change, doesn't need a yes either. Those edits stay in the draft.
Big builds start with a plan: before it builds a new Course, Module, or Path, or a change that touches more than about 5 items, the agent shows a plan and waits. Click Approve & build, or reply with what to change. Approving a plan doesn't approve publishing or assigning.
Other changes need a yes before the first of each kind: the agent tells you what it plans to do and waits for your yes in the chat. Later changes of the same kind go ahead without asking again.
Publishing, assigning, and deleting always need a yes: the agent names the exact items and who they reach, even when you asked for them. Changing the name, description, cover, or settings of a published item works the same way, because your team sees it right away.
Removing existing screens counts as deleting: if the agent wants to remove screens or answer options that already existed, it names what goes and asks first.
Filling in or submitting a Check-in needs a yes.
Changing a Path that already exists needs a yes.
A yes in your request counts: if your message already approves a change and names what it covers, like "Archive these 10 Courses, I approve," the agent makes it right away. If the change reaches more items than you named, or includes publishing, assigning, or deleting your message didn't approve, the agent asks first.
Before it publishes, the agent lists every difference between the draft and the published version, including changes it didn't make. Publishing sends the whole draft, not only the agent's edits.
An agent also asks first before creating these, because each one has an effect beyond the chat, unless your request already approves that item:
A Task: the assignee gets notified.
A Location: Opus creates a signup code for it.
A Role: the Role could give someone Admin access.
In Voice Mode
In voice mode, agents answer questions but don't change anything, because a spoken yes isn't treated as approval. Type or dictate a request when you want an agent to change something.
Tracking What Changed
Ask an agent "What did you change?" to see a list of recent changes made through agents and Opus MCP, which connects Opus to AI assistants like Claude or ChatGPT. Changes made directly in the dashboard aren't included.
Every change is made under your name, so it shows up in Opus activity like any other change you make.
➡️ Learn more:
Getting Started: Opus MCP: connect Opus to Claude, ChatGPT, and other assistants
FAQ
Can an agent see more than I can?
No. It sees only what your permissions allow, and it can't do anything you can't do yourself.
Can other Admins see my chats?
No. Chats are private to each Admin. Agents themselves are shared, so other Admins can use and edit the same agents.
Can Managers or Trainees use agents?
No. Opus Agents are available to Admins. Managers and Trainees keep using Ask Opus as before.
Does an agent remember past conversations?
Yes, within your chat with that agent. Very long chats get summarized. If a Primary Agent chat gets too long to continue, click Start new chat. It doesn't carry what it learns in your chat into other Admins' chats.
Can I undo a change an agent made?
Most changes can't be undone. Ask "What did you change?" to see what the agent did, then fix it in the dashboard or ask the agent to change it back.
Is my data used to train other companies' models?
No. Learn more: How Opus Training Processes Your Company Data While Using AI: how Opus handles your data with AI.