This page assumes you’ve already added and configured connectors for the apps you want to make requestable, and — if you’re including AI tools — enabled AI access management.
One catalog
Apps, entitlements, and AI tools all surface in the same place. The App catalog on the Requests page lists everything currently assigned to a user or available for them to request, searchable by entitlement name even when they don’t know which app it belongs to. AI tools don’t get a separate catalog: access profiles containing toolsets appear in the catalog alongside app entitlements, each showing what tools it grants and what its approval policy is. What’s visible to a given user is scoped by access profiles — an Accounting employee and a Product Design employee see different catalogs, and each of them only sees what they’re allowed to request.Request from wherever you work
C1 supports requesting access from several places, not just the web app: the C1 app for Slack, the Microsoft Teams app, and the C1 CLI for anyone who’d rather stay on the command line. Conversational, agentic request filing is real too, through two distinct paths: ask the C1 AI assistant what’s available and request it, in the C1 web app or over Slack DM; or, for a coding agent like Claude Code or Cursor, install c1i as an agent skill so it can create and manage access requests from natural-language instructions.A word on MCP specifically. C1 MCP — the integration that lets an external AI client like Claude Desktop or Cursor query C1’s own data over the Model Context Protocol — is read-only: it can answer questions about access, but it can’t file a request on its own. For an agent to actually request or manage access on your behalf, use the C1 AI assistant or the c1i agent skill above instead.