Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.circuit.ai/llms.txt

Use this file to discover all available pages before exploring further.

Circuit supports single sign-on (SSO) through Google and Microsoft identity providers. Users sign in with their existing corporate credentials. No separate Circuit password is needed.

Supported identity providers

ProviderProtocolNotes
GoogleOAuth 2.0 / OpenID ConnectGoogle Workspace accounts
MicrosoftOAuth 2.0 / OpenID ConnectAzure AD / Microsoft Entra ID accounts

How SSO works in Circuit

1

User navigates to Circuit

The user opens the Circuit application in their browser.
2

Choose sign-in method

The user clicks “Sign in with Google” or “Sign in with Microsoft.”
3

Authenticate with identity provider

The user is redirected to their identity provider’s login page (if not already signed in). Standard corporate authentication policies apply: MFA, conditional access, etc.
4

Access granted

After successful authentication, the user is redirected back to Circuit with an active session. Their workspace membership and permissions apply immediately.

User provisioning

When a user signs in for the first time:
  • If they were previously invited to a workspace, they are automatically linked to that workspace
  • Their name and email are populated from the identity provider
  • They receive the permissions assigned during their invitation
Circuit uses just-in-time provisioning. Users are created in Circuit on their first sign-in. You do not need to pre-create user accounts (beyond sending the invitation).

Security policies

Circuit respects the security policies configured in your identity provider:
  • Multi-factor authentication (MFA): if your IdP requires MFA, users must complete it before accessing Circuit
  • Conditional access: Azure AD conditional access policies (device compliance, location restrictions, etc.) are enforced at the IdP level
  • Session management: session duration and sign-out behavior follow your IdP configuration

Revoking access

To revoke a user’s access to Circuit:
  1. Remove them from the Circuit workspace: this immediately removes access to all workspace resources
  2. Disable their IdP account: this prevents them from signing in to Circuit entirely
Both approaches are effective. Removing from the workspace is sufficient if the user should retain their IdP account for other applications.