Set up single sign-on (OIDC or SAML)
Let staff sign in with Microsoft Entra ID, Google, Okta or another identity provider.
For administrators · Updated
Open Integrations → SAML / OIDC single sign-on → Set up.
OpenID Connect (recommended)
- In your identity provider, create a web application. Register the Redirect URI shown in the setup dialog.
- Copy the issuer URL, client ID and client secret into the dialog. Examples of issuer URLs:
https://login.microsoftonline.com/<tenant-id>/v2.0(Microsoft Entra ID) orhttps://accounts.google.com. - List your email domains (for example
yourtown.gov). - Save. Civicade reads your provider's configuration to confirm it.
SAML 2.0
Enter your IdP's entity ID, single sign-on URL and signing certificate (PEM). Give your IdP our entity ID and ACS URL from the dialog. Turn off assertion encryption. Your server needs the xmlsec1 tool; the dialog warns you if it's missing.
Who can sign in
Only people who already have access to your municipality can sign in, unless you tick Create accounts automatically; then anyone with an email in your listed domains gets an account with no permissions until an administrator assigns roles.
Require SSO
Tick Require single sign-on to refuse password sign-in for staff who belong only to your municipality. Staff see Sign in with your organization (SSO) on the sign-in page.
Before relying on it
Test with one account first. Sign-in attempts and failures are recorded in the audit log.
Was this article helpful?