Multi-tenancy and Regions

AuthAction uses a multi-tenant architecture. Each tenant has its own isolated data: users, applications, connections, and configuration.

Tenant vs. Region

• Tenant: Your unique tenant identifier (e.g. acme, mycompany). All your applications, users, and settings belong to a tenant.
• Region: The data center or geographic region where your tenant runs. Regions affect latency and data residency.

URL Structure

All AuthAction endpoints use this base URL format:

https://<tenant>.<region>.authaction.com

Examples:

• https://acme.eu.authaction.com – Tenant acme in the EU region
• https://myapp.us.authaction.com – Tenant myapp in the US region

Supported Regions

Code	Region
au	Australia
ca	Canada
cn	China
eu	Europe
in	India
jp	Japan
us	United States

Use the region code in your tenant URL and in API requests.

Key Endpoints by Tenant

All OAuth 2.0 and OpenID Connect endpoints are tenant-specific:

• Authorization: https://<tenant>.<region>.authaction.com/oauth2/authorize
• Token: https://<tenant>.<region>.authaction.com/oauth2/token
• Discovery: https://<tenant>.<region>.authaction.com/.well-known/openid-configuration
• JWKS: https://<tenant>.<region>.authaction.com/.well-known/jwks.json

The AuthAction Dashboard is accessed from the home page. After signing in, you select or switch tenants from within the dashboard. The Management API uses tenant-specific URLs for API requests.