Requests
Requests is the admin’s inbox for approvals — the place where team members’ asks for tools, agents, and connectors come to be reviewed. It’s where the governance model becomes a daily habit rather than an abstract policy.
What lands here
Section titled “What lands here”When a team member needs something outside their approved set — an agent that isn’t yet approved, a tool to publish for others, a connector to a new system — the request routes here. Each one gives the admin the context to decide: what it is, what it touches, and who it’s for.
Reviewing a request
Section titled “Reviewing a request”The admin reviews and approves, or sends it back with feedback. Approving often benefits more than the requester — approve an agent once and it can join the whole team’s shelf, so the next person doesn’t have to ask. This is how a curated set of approved tools grows: driven by real demand, one reviewed request at a time.
Why it’s a feature, not friction
Section titled “Why it’s a feature, not friction”A good Requests flow is what lets an organization say “yes, and” instead of “no.” People can reach for what they need; admins keep the final say; and the approved catalog improves as it’s used. The alternative — locking everything down or opening everything up — is worse in both directions.
Related
Section titled “Related”- What team members request from → Adopting approved agents
- Publishing that routes here → Publishing an Agent
A quick example
Section titled “A quick example”Three people request the same summarization agent in a week. The admin approves it for the whole department, and the requests stop — because now it’s simply on the shelf.