Admin controls
Approved context
Trust & Boundaries
Separate private control from public agent experiences.
The person configuring an agent, the user working in its dedicated workspace, and a website visitor need different levels of access. AgentShelf treats them as separate operating contexts and helps evaluators inspect the controls supported for each experience.
Operating contexts
Website visitors
Scoped answers
Different actors. Different access.
A public conversation should not become access to private controls.
A platform user may configure instructions, knowledge, tools, model behavior, and limits. A website visitor should receive only the public experience prepared for that surface.
How the contexts relate
Keep management, workspace use, and public interaction distinct.
Authenticated management
The platform user configures the agent, approved resources, deployment settings, model behavior, and applicable controls.
Dedicated workspace
The authenticated user works with the focused agent, its context, tools, conversations, results, and available activity.
Surface-specific configuration
A public or embedded experience receives only the settings and capabilities prepared for that surface. It does not expose the private management experience.
Public or embedded session
A visitor or application interacts through the interface prepared for that experience.
Connected operating records
Available model, usage, event, error, and result information can return to the platform for review.
Configuration, access checks, records, retention, and behavior depend on the implemented interface and deployment.
What to evaluate
Review the controls for the experience being deployed.
- 01
Who owns the experience?
Which user, agent, workspace, widget, or application owns the configuration and request?
- 02
How is the surface recognized?
Which session and origin checks apply to this public or embedded experience?
- 03
What can the agent access?
Which information and capabilities are available on this surface?
- 04
Which rules apply?
Which validation, throttling, limits, and model behavior govern the experience?
- 05
What can be reviewed?
Which events, errors, model details, usage, cost, and results are available?
- 06
Who handles exceptions?
What is retained, what depends on customer configuration, and who responds when the workflow fails?
Review the boundary for the agent experience you plan to launch.
Walk through the controls, dedicated workspace, public or embedded session, permitted tools, and available records.