User portal
Give your users a place to connect their own agents and see only their own activity
Your users need a place to connect their own agents and see what those agents did, without seeing anyone else's activity. In SecureAuth Agent Authority, that place is the user portal, a short menu of pages that show each person only their own agents, connections, and activity.
How the portal differs from the admin console
The user portal and the admin console are one application, not two. When someone signs in, the gateway looks at their permissions and picks a navigation to match: an admin gets Inventory, Policy Controls, Activity and Setup, and everyone else gets a short list of their own pages, the user portal. Same URL, different sidebar. That matters when you follow the steps in these docs and can't find a page: Quickstart exists only in the portal, so an admin reading a user's instructions won't find it.
Users are never asked to do anything but connect their own agents and see what those agents did. Everything governing them stays on the admin side: policies, data protection, and the org-wide Agent Trail.
The portal limits every page to the signed-in user, whatever their permissions. The org-wide view stays in the admin console.
Share the portal link
Open Agents & NHIs and click Copy portal link in the header, then send that link to your users.

The link opens the portal's Quickstart page, where each person picks the agent they use and follows the setup steps for it. For a walkthrough written for the people receiving that link, point them at Connect your AI agent.
What users can do in the portal
In the portal, users can see their own activity and spend, connect a new agent, manage their agents, connections and devices, and review what their agents did. Everything is limited to the signed-in person, so nobody sees anyone else's agents or calls. For each screen, see Portal screens in the User Guide.
The Activity feed is a restricted view of the audit log
It's the same audit log, run through two restrictions before anything reaches the page:
- Limited to the signed-in user. The feed only ever returns that user's own events. The admin Agent Trail filter bar isn't shown here: with nothing left to narrow by, the feed has no filter chips.
- Limited to a fixed list of actions. A user sees only the actions that carry their own user ID: tool executions and tool errors, agent created / updated / deleted / revoked / connected, and connection created / removed / revoked. Admin-only actions never appear, even though they're in the same log: policy edits, resource installs, and data-protection changes.
Payloads are stripped the same way. Any field not marked as the user's own is removed before the event is sent. Where an admin sees which redaction rules fired and how many matches each made, a user sees a single generic Content redacted pill. They learn that something in the response was redacted; they don't learn what your rules look for.
An empty feed offers a Connect an agent button pointing at Quickstart.
Why a user might see less than you expect
The portal is permission-driven throughout, so what a user sees depends on what your identity provider grants them.
If Connections is missing, they lack manage_connections.
If Activity is missing, they lack view_audit.
If the Dashboard reports "You do not have permission to view this dashboard." then they lack the analytics permissions behind it.
Check the grants coming from identity before assuming the page is broken.
Next steps
- Connect your AI agent. The guide written for the people you send the portal link to.
- Connect an agent. The Quickstart flow your users will follow.
- Connections. The per-user OAuth model behind the Connections page.
- Human identities. The admin view of the same person, with their agents, resources, and spend.
- Agent Trail. The full log the Activity feed draws from.
