Auth0 SSO Integration
What Is Auth0 SSO?
Auth0 Single Sign-On (SSO) allows users to securely log in to BookYourPTO using external identity providers such as:
- Microsoft
- GitHub
Instead of managing passwords separately, authentication is handled through a centralized identity provider.
Before You Begin
Ensure you have:
- Executive access in BookYourPTO. SSO settings and SSO email domains are changed only by an Executive; administrators can view them.
- An active Auth0 account (tenant access)
Creating an Auth0 Application
- Log in to the Auth0 Dashboard.
- Navigate to: Applications → Create Application
- Configure the application:
- Name — e.g.,
BookYourPTO SSO - Application Type —
Regular Web Application
- Name — e.g.,
- Click Create.
Configuring Auth0 Settings
- Open your application: Auth0 Dashboard → Applications → Your App → Settings
- Copy the following credentials:
- Domain
- Client ID
- Client Secret
- Navigate to: BookYourPTO → Settings → Auth0 Integration
- Paste the credentials into the corresponding fields.
Configuring Application URIs
In the Auth0 application settings, scroll to Application URIs and configure:
Allowed Callback URLs
https://app.bookyourpto.com/auth/callback
Allowed Logout URLs
https://app.bookyourpto.com
- Click Save Changes.
Enabling Social Login (Optional)
To allow users to sign in with third-party providers:
- Navigate to: Auth0 Dashboard → Authentication → Social
- Enable desired providers:
- Microsoft
- GitHub
- Complete provider setup:
| Provider | Setup Location |
|---|---|
| Google Cloud Console | |
| Microsoft | Azure Portal / Entra ID |
| GitHub | GitHub Developer Settings |
- Save configuration.
Configuring BookYourPTO
Navigate to: BookYourPTO → Settings → Auth0 Integration
Enable Auth0
- Toggle Auth0 Authentication ON
Enter Credentials
Provide the following:
- Domain
- Client ID
- Client Secret
The Domain must be a public hostname: your Auth0 tenant (<tenant>.auth0.com, or a regional one such as <tenant>.eu.auth0.com) or a custom domain that resolves only to public addresses. A domain with a port, a path, an IP address, or an internal name such as localhost is refused when you save it, and checked again at every sign-in before the client secret is sent.
User Provisioning
Control how users are created during login:
| Option | Behavior |
|---|---|
| Auto-Create Users | New users are created automatically on first login |
| Manual Provisioning | Only existing users can log in |
Allowed Email Domains
Restrict access to specific organizations:
- Enter comma-separated domains: anhourtec.com, yourcompanyname.com
- Only users with matching email domains are allowed access.
- When you add and verify domains under SSO domains, only a verified domain is accepted.
- SSO sign-in is refused until at least one email domain is set up: "SSO sign-in is not available for this organization until an email domain is set up in Settings > SSO."
Adding, verifying and removing an SSO domain is Executive-only, like the rest of the SSO settings.
Verified email required
The identity provider must report the person's email address as verified. An unverified address is refused with "Your identity provider has not verified this email address. Verify it there, then sign in again." Verify it with the identity provider, then sign in again.
Authentication Modes
Define how users can log in:
| Mode | Description |
|---|---|
| Hybrid Mode | Users can log in via Auth0 or email/password |
| SSO-Only Mode | Users must log in using Auth0 only |
In SSO-only mode (or with email/password sign-in turned off), password sign-in is refused on the web sign-in page and the AI connector's sign-in page; people are told to use Sign in with SSO. The mobile app still signs in with email and password, so people can set or reset a password for it (how). This takes effect only once SSO is fully set up — enabled, with domain, client ID and client secret saved, and an email domain accepted — so a half-finished setup never locks anyone out. See Authentication.
Notes
- Configuration changes apply immediately after saving
- Incorrect credentials or URLs may cause login failures
- Only an Executive can change SSO settings or SSO domains
- Access and authentication behavior depend on configured settings and user roles
Expense Settings
The Expense Management section allows administrators to configure reimbursement settings, expense categories, per diem rates, mileage rates, receipt requirements, and approval policies for the organization.
Password & Authentication Policy
Learn how to configure password rules and authentication controls to secure access across your organization.