How do I connect an AI agent to my identity provider with OIDC?

Authority is part of the systemidentity and limits attached
Declare who may enter, which resources the App can reach, and who may approve work.

#The question

Register your identity provider on organization Auth and inherit it in a project, or configure it directly on project Auth, configure its project-specific audience, and exchange an IdP JWT for a short-lived Swirls credential bound to that project.

#Who's asking

Platform / infra engineer. Owns how things run in production. Cares about durability, isolation, audit, and repeatable deploys.

#Why Swirls is a fit

Configure inbound identity federation in the project Auth page or SDK. Fabric verifies your IdP JWT and issues a credential confined to that project. Deployed role and policy blocks can further narrow what the identity may execute. See OIDC federation.

Every agent execution runs with its own identity. Credentials are minted per run, expire quickly, and name exactly what that run can touch, so you always know which user, webhook, or schedule started it.

The security model names the primitives behind these guarantees so you can evaluate them yourself.

Add the people, data, authority, and decisions around this job.

Keep this solution beside the Apps, records, rules, connections, and reviews it depends on in one .swirls project.