Your CivicClerk login experience will be changing in the coming weeks as we upgrade our identity server to improve security and performance. We are phasing the rollout of this new login, so specific timing for each organization is not available. We will begin this process on April 26, 2022. If you use another CivicPlus product, you may have already received this upgrade on another product. This update will change the login only for CivicClerk.
Your new login screen will look like this:
The login will change for all administrative users, including users who only log in to the CivicClerk Board Portal.
Frequently Asked Questions
Communicate with internal users (including elected and appointed officials that use the Board Portal) that their login screen will change, but they will still use the same email address and password they currently use and log in using the “Sign In” options on the left side of the page.
On the current login screen, all users should see a banner that says “Updated sign-in experience coming” and can click “More Information” to read an article about the new sign-on screen.
If you use a third-party identity provider (ADFS 3.0, ADFS 4.0, ADFS 5.0, Azure AD, or Okta) integrated with CivicPlus Single Sign-On, you should have received an email from CivicPlus Hosting and Security several months ago with instructions on how to update your setup and a deadline to do so. If you did not receive this email or aren’t sure if you completed this step, please reach out to CivicClerk Support and they can provide you with resources specific to your provider.
It depends on whether or not you use a Custom Identity Provider.
Users With Custom Identity Providers
This feature is not available if you are using one of our Custom Identity Provider integrations (ADFS 3.0, ADFS 4.0, ADFS 5.0, Azure AD, or Okta). If you use Custom Identity Provider integrations, users should continue to enter their email address and password on the left side of the screen and should not attempt to log in using the “Microsoft” button. If they attempt to log in that way, they will receive an error.
Example: Bob Thomas logs into the CivicPlus Single Sign-On (SSO) using a Custom Identity Provider integration (his connected city email and the same password he uses for his work email). He attempts to log in to the CivicPlus SSO and add a secondary log in with his Apple ID. He will not be able to add the Apple ID login to his CivicPlus account because his organization is managing all of their logins for the users via the integration.
If You Do Not Have a Custom Identity Provider
To be able to successfully use this feature, a user will need to set this up on their own CivicPlus SSO account by following these instructions.
Example: CivicClerk User Lily Roberts logs into her CivicPlus Single Sign-On account today using her work email firstname.lastname@example.org and a password she has created. She adds her Facebook account as a secondary sign-in option to her CivicPlus account. She can now log in to CivicClerk using her email@example.com email address and password or her Facebook account.
If a user attempts to create a new CivicPlus account using one of these new sign-in options and they haven’t connected that login method to the primary email address that they use to log in to CivicClerk today, that will result in them being unable to access CivicClerk using that new CivicPlus account until that connection step has been completed.
No, CivicPlus Single Sign-On (SSO) is only managing the login process. Adding a secondary login method will not change the user’s existing permissions in CivicClerk. For example:
CivicClerk user Mary Smith logs into her CivicPlus SSO account today using her work email firstname.lastname@example.org and a password she has created. She adds her Gmail account, email@example.com, to her CivicPlus account. Whether she logs in using her firstname.lastname@example.org login or her email@example.com login, her permissions in CivicClerk remain the same.
No. At this time, this change only affects CivicClerk administrative and Board Portal users.