Connect an agent
What a school owner or admin sees when approving an AI agent, from entering a device code to choosing access, plus how to disconnect it later.
An AI agent reaches a school’s data only after an owner or admin approves it. This page walks through the approval screens, in the words Soljio shows, so you know what to expect and what to tell the person approving. For the protocol behind it, see Agents and MCP.
Only an active owner or admin of a school can approve an agent for that school. A person who holds another role sees: Only school owners and admins can connect an agent. Ask an owner or admin of your school to connect it.
Two ways to arrive
An agent that opens a browser. The agent sends the person to the Connect an agent page with a request attached. They sign in if needed and land directly on the approval screen.
An agent that cannot open a browser. The agent shows a short code and a sign-in link. The person can follow the link, or open the Connect an agent page themselves and type the code.
A request from the agent stays valid for 10 minutes. After that, the page reads This request has expired with the note Start again from your agent.
Approve an agent
Sign in
If the person is not signed in, the page reads Connect an agent with Sign in with the account you use to run your school. The Sign in to continue button returns them to the same request afterward.
Enter the code, if the agent showed one
The page asks to Enter the code your agent is showing. The field is labelled Code from your agent, with the example ABCD-EFGH. Select Continue.
If the code is wrong, the page says That code didn’t match. Check the code your agent shows. After too many wrong attempts it says Too many attempts. Try again in a few minutes.
Review the request
The heading reads Connect followed by the agent’s name, or Connect an AI agent when the agent did not give one. The page says: Choose what it can do in your school. It can never do more than you can, and you can disconnect it from Settings at any time. For an agent that opened a browser, it adds where the person will return to afterward.
If the person belongs to more than one school, a School menu chooses which one the agent will use. With a single school, the page shows School: and its name.
Choose what the agent can do
The page lists the areas of the school the person is allowed to grant: Organization, Programs and offerings, Schedule, Participants, Enrollment and attendance, Progress, Communications, and Administration. Each area has up to three levels:
| Level | What it grants |
|---|---|
| None | Nothing in that area |
| Read | The area’s read scopes |
| Write | The area’s read scopes and its write scopes |
By default each area is set to the highest level the agent asked for. The person can lower any area. An area whose selected level includes sensitive access, such as participant or payment data, shows a Sensitive label. Opening What this includes lists the permissions in that area by name.
Areas the person’s own role cannot grant do not appear. An admin does not see owner-only access. The scopes behind each permission are on the Scopes page.
Confirm the code, for a device request
For an agent that showed a code, a checkbox reads My agent shows the code followed by the code. The person must tick it to continue. This guards against approving a request that a stranger started.
Allow or deny
Select Allow access to approve, or Deny to refuse. Allow access stays disabled while every area is set to None.
After approval the page confirms Your agent is connected. Return to it to continue. An agent that sent the person from a browser is redirected back to it instead. After a denial the page says Access denied. You can close this page.
If the person opens an old link, they see This request was already answered with the note Return to your agent, or start again from it.
What approval creates
Approving creates an agent connection for that school with exactly the permissions chosen. The connection acts for the person who approved it, and it can never do more than that person’s role allows. If the person is no longer an owner or admin, the connection stops working until someone connects the agent again.
Approving is recorded in the school’s Audit log.
Review and disconnect agents
Open Settings in the dashboard and go to Connected agents. The section reads: AI agents act for the person who connected them, with only the access they chose.
Each agent shows its name, who connected it and when, and when it last ran, or Never used. A summary reads Full access or Access to a number of areas. Open it to see each area and the permissions in it.
| Badge | Meaning |
|---|---|
| (none) | The connection is working |
| Paused | The person who connected the agent is no longer an owner or admin, so it cannot do anything until someone connects it again |
| Expired | The connection’s lifetime ended |
| Disconnected | An owner or admin disconnected it |
To disconnect an agent, select Disconnect on its row and confirm with Disconnect agent. The dialog says: The agent loses access immediately. It can only return if someone connects it again.
If no agent has been approved yet, the section reads No agents connected. When an owner or admin approves an AI agent, it appears here.
Troubleshooting
- The approval screen says the request has expired. Requests last 10 minutes. Start again from the agent.
- The person approving sees no schools. They are not an active owner or admin of any school. Ask an owner or admin to approve the agent.
- The agent asks to connect again. Its connection may have been disconnected, expired, or paused. Check Connected agents and approve it again.
- The agent lacks access it needs. Connection access cannot be edited. Disconnect the agent and approve it again with more access.