SwiftComply Stormwater supports single sign-on so users can log in with their organization's identity provider (for example, Okta) instead of a SwiftComply-specific username and password. SSO setup is handled by the SwiftComply team; this article covers the user login experience once it's enabled.

For information on how SSO is configured for an organization, see SSO, Compliance Status Types, and Billing Settings.

On your first SSO login, the system creates your account automatically using your identity provider profile (email, first name, last name). If the instance user limit has been reached, you'll see an error and your account won't be created. Contact your SwiftComply representative if that happens.

Q: Can I use both SSO and password login?

A: Users created via SSO log in through their identity provider. Local users created manually in the admin panel log in with a SwiftComply username and password. The two methods serve different user accounts.

Q: How do I set up SSO for my organization?

A: SSO is configured by the SwiftComply team. Contact your SwiftComply representative to enable SSO with your identity provider. See SSO, Compliance Status Types, and Billing Settings for the customer-facing summary.

Q: My SSO login fails with a user limit error. What should I do?

A: Your account couldn't be created because your instance has reached its user limit. Contact your SwiftComply representative to request additional seats.

Q: I'm a deactivated user. Can I still sign in with SSO?

A: No. Deactivated users can't log in through SSO or any other method. An administrator must reactivate your account first.