Guides
Identity
How an agent acts in Ramp, as the user who connected it or as its own identity.
MCP and CLI actions run as the Ramp user who authorized the connection, with that user's permissions. If Sarah connects Ramp, her agent sees the same businesses, cards, funds, and workflows Sarah can access, and Ramp attributes its actions to her.
| Merchant | Cardholder | Amount | Date |
|---|---|---|---|
Notion Software | ![]() Claude On behalf of Dana | $486 | Aug 12, 2026 |
Access controls
- Who can connect: the Manage connections to Ramp via MCP, CLI and other AI connectors role permission. Owner, Admin, and IT admin have it at Global; Accounting and Employee have it at Only their own; custom roles start without it. Changing roles requires Ramp Plus, and changes take effect immediately: once none of a user's roles include the permission, their connections stop working.
- Access level: on the consent screen, the user chooses Full access or Read-only.
- Expiry: connections expire after 30 days. Reconnect to renew.
- Revoking: admins can revoke a connection in Settings → Developer → Connected AI tools. A user's AI tools can share one connection, so revoking it cuts off every tool that uses it.
See Manage connected AI tools for the admin guide.
Agents with their own identity
A standalone agent has its own Ramp identity, owned by the business rather than by one employee. Use one for shared or background work, such as first-level bill review: the agent approves clean bills and sends mismatches to a person, and it shows up in the approval chain under its own name.
Approval
Google Ads invoice
Bill · Advertising · Due Sep 15
$2,400.00
USD
Approval chain
- Invoice Review AgentAgentOwned by Dana MeyerDoneCoded + matched invoice
Dana MeyerOwnerGrowth LeadPendingAwaiting approval- FinanceFinal review · pays billUpcomingAfter owner approval
Set one up
An admin creates the agent in Company → Agents with a name, one or more custom roles, and an owner: the employee responsible for it, which defaults to the admin who creates it. Ramp shows the agent's Client ID and Client secret once. Store them in a secret manager, and use them to connect your runtime. Actions then run as the agent, not as a person.
Controls
- Permissions: the agent can do only what its custom roles allow. Adding it to an approval chain doesn't give it authority on its own.
- Lifecycle: admins can pause, reactivate, or delete the agent, change its roles or owner, and rotate its secret. Rotating revokes access granted with the old secret.
Want early access to standalone agents? Talk to the team.