{"id":7872,"date":"2026-06-11T17:20:55","date_gmt":"2026-06-11T17:20:55","guid":{"rendered":"\/agile\/?post_type=ht_kb&p=7872"},"modified":"2026-07-14T13:12:04","modified_gmt":"2026-07-14T13:12:04","slug":"bolt-2-0-login-page","status":"publish","type":"ht_kb","link":"\/agile\/knowledge-base\/bolt-2-0-login-page\/","title":{"rendered":"Bolt 2.0 – Login Page"},"content":{"rendered":"\n

Feature Overview<\/p>\n\n\n\n

The new Bolt Login page provides a unified login experience for both MSS and ESS users while maintaining Classic functionality.<\/p>\n\n\n\n

Unlike Classic, Bolt uses a single login URL for both MSS and ESS users. After authentication, users are automatically redirected to the appropriate portal based on their access.<\/p>\n\n\n\n

FAQs<\/p>\n\n\n\n

Should I use the same credentials as I used before on the new Bolt login page?<\/strong><\/p>\n\n\n\n

Yes, your username and password have not changed, so the same credentials should be used on either the Bolt or the Classic login page.<\/p>\n\n\n\n

I have a bookmark of the Classic login page.  Is this still going to work? Do I need to change it?<\/strong><\/p>\n\n\n\n

The new Bolt login page replaces the Classic login page.  So an existing bookmark pointing to {company_name}.synerionagile.com will now direct you to the Bolt login screen.  If you\u2019d like to continue using the Classic login screen, you can click the \u2018Looking for Classic?\u2019 link, and bookmark that page.  The new URL for the Classic login page will be {company_name}.tz.synerionagile.com<\/p>\n\n\n\n

Bookmarks shoud point only to the {company_name}.synerionagile.com or {company_name}.tz.synerionagile.com URLs. Any bookmarks to specific pages that end in .aspx will no longer work.<\/p>\n\n\n\n

Why am I being redirected to the Bolt dashboard when logging in via the Classic login page?<\/strong><\/p>\n\n\n\n

This behavior is controlled by user preferences even though you are logging into Classic, in the system, your preference is set to Bolt, that\u2019s why you are redirecting to Bolt. To change the preferences,<\/p>\n\n\n\n

MSS Users:<\/p>\n\n\n\n

    \n
  1. Select the profile icon (top right of the screen)<\/li>\n\n\n\n
  2. Select Preferences<\/strong><\/li>\n\n\n\n
  3. Go to Login Settings<\/strong><\/li>\n\n\n\n
  4. Choose “Agile Classic”<\/strong><\/li>\n<\/ol>\n\n\n\n

    ESS Users:<\/p>\n\n\n\n

      \n
    1. Go to Setting<\/strong>s in the side dashboard menu<\/li>\n\n\n\n
    2. Scroll to Display Preferences<\/strong><\/li>\n\n\n\n
    3. Select “Switch to Agile Classic”<\/strong><\/li>\n<\/ol>\n\n\n\n

      Can I set my preference to stay on Classic?<\/strong><\/p>\n\n\n\n

      Yes.<\/p>\n\n\n\n

      MSS Users:<\/p>\n\n\n\n

        \n
      1. Select the profile icon (top right of the screen)<\/li>\n\n\n\n
      2. Select Preferences<\/strong><\/li>\n\n\n\n
      3. Go to Login Settings<\/strong><\/li>\n\n\n\n
      4. Choose “Agile Classic”<\/strong><\/li>\n<\/ol>\n\n\n\n

        ESS Users:<\/p>\n\n\n\n

          \n
        1. Go to Setting<\/strong>s in the side dashboard menu<\/li>\n\n\n\n
        2. Scroll to Display Preferences<\/strong><\/li>\n\n\n\n
        3. Select “Switch to Agile Classic”<\/strong><\/li>\n<\/ol>\n\n\n\n

          Can I go back to Classic while using the Bolt?<\/strong><\/p>\n\n\n\n

          Yes. MSS users can navigate to Classic by selecting the \u201cBack to Classic<\/strong>\u201d option available in the main sidebar menu.<\/p>\n\n\n\n

          How Login works<\/p>\n\n\n\n

            \n
          1. If a user has bookmarked the existing login URL, accessing it will automatically redirect them to the Bolt Login page.\n
              \n
            • Users who want to access Classic can click the \u201cLooking for Classic?\u201d<\/strong> link on the login page to open the Classic Login page.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
            • On the Bolt Login page, the user enters their username and password and clicks Login<\/strong> to authenticate.<\/li>\n\n\n\n
            • Based on the user credentials, the system identifies whether the user is ESS or MSS and redirects them to the appropriate application.<\/li>\n<\/ol>\n\n\n\n
              \"\"<\/figure>\n\n\n\n

              Forgot Password & Reset Password Flow<\/p>\n\n\n\n

              Like Classic, Bolt also supports a secure Forgot Password and Reset Password flow for non-SSO users, ported from Classic with improved validations and UI.<\/p>\n\n\n\n

              Flow<\/strong>:<\/p>\n\n\n\n

                \n
              1. On the Bolt Login page, user clicks \u201cForgot Password\u201d link<\/li>\n\n\n\n
              2. Enter username and email address and click \u201cSend Me Link\u201d<\/li>\n\n\n\n
              3. If entered credentials are correct, Reset link is sent to the registered email and Success message is displayed.<\/li>\n<\/ol>\n\n\n\n
                \"\"<\/figure>\n\n\n\n
                  \n
                1. User opens reset link from email<\/li>\n\n\n\n
                2. User enters New password and Repeat New Password<\/li>\n<\/ol>\n\n\n\n
                  \"\"<\/figure>\n\n\n\n
                    \n
                  1. User clicks \u201cReset<\/strong>\u201d<\/li>\n\n\n\n
                  2. Success message is displayed with a timer.<\/li>\n\n\n\n
                  3. User is redirected to login page after timer expires.<\/li>\n<\/ol>\n\n\n\n

                     Technical Notes<\/p>\n\n\n\n

                      \n
                    1. Forgot Password appears on Login page only if system setting ForgotPasswordEnabled<\/strong> is enabled.<\/li>\n\n\n\n
                    2. Forgot Password is not applicable for SSO users. Also, Change Password<\/strong> in the app is hidden for both ESS and MSS when accessing the app as a SSO user.<\/li>\n\n\n\n
                    3. Reset link is valid for one-time use only.<\/li>\n\n\n\n
                    4. Like Classic, enforces strong password policies.<\/li>\n\n\n\n
                    5. For users with both MSS and ESS access, a system setting \u201cBolt.Login.DualAccess.DefaultMode\u201d determines the default landing portal (default = MSS). Currently, switching between MSS and ESS depends on this value. In-app switching between MSS and ESS is planned for a future release.<\/li>\n<\/ol>\n\n\n\n

                      Login with SSO<\/p>\n\n\n\n

                      Now, Users can sign in to Bolt using SSO (if it has been configured). If SSO is already set up in Classic, users can continue using the same SSO experience in Bolt. The Bolt login flow supports Single Sign-On (SSO) for ESS and MSS using the OpenID Connect (OIDC) protocol with a secure Backend-for-Frontend (BFF) pattern. SSO requires additional configuration, which is not covered in this document.<\/p>\n\n\n\n

                      For Only SSO Mode (New in Bolt)<\/p>\n\n\n\n

                      A new system setting Bolt.ShowLoginInput.Enabled<\/strong> has been introduced in Bolt to control whether username and password fields are displayed on the login screen. When set to No, the login fields are hidden and users will see only the \u201cLogin with SSO\u201d option.<\/p>\n\n\n\n

                      SSO vs Force Password Change Handling<\/p>\n\n\n\n

                      In Bolt, similar to Classic behavior, users authenticated via SSO will not be prompted for a password change, since username\/password credentials are not applicable in this flow.<\/p>\n\n\n\n

                      When a user account has Force Password Change<\/strong> enabled, the system behavior depends on the authentication method:<\/p>\n\n\n\n

                        \n
                      1. If the user logs in using username\/password<\/strong>:\n
                          \n
                        • Enforce the password change flow as per Must Change Password rules.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
                        • If the user logs in via SSO<\/strong>:\n
                            \n
                          • Skip the password change flow, even if Must Change Password is enabled.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n

                            Mobile App installation QR codes (New in Bolt)<\/p>\n\n\n\n

                            On Bolt Login page, we have introduced the QR codes to install the Agile Mobile apps \u2013 iOS and Android. Clicking the link will prompt the QR code. User can scan it with their Mobile camera to install the apps.<\/p>\n\n\n\n

                            \"\"<\/figure>\n\n\n\n

                            Support of Custom Logo and Stock Images on Login Page<\/p>\n\n\n\n

                            A new system setting, Bolt.LoginPage.HideStockImagesWhenCustomLogo<\/strong>, controls the display of login page branding.<\/p>\n\n\n\n

                            When a custom logo is configured, users can choose to display only the custom logo or show both the custom logo and stock images. If no custom logo is configured, the stock image is displayed regardless of the setting value.<\/p>\n\n\n\n

                            NOTE<\/strong>: As we are supporting single login page for both MSS and ESS, ESS Custom logo section under Portal- Global options has been removed.<\/p>\n","protected":false},"excerpt":{"rendered":"

                            Feature Overview The new Bolt Login page provides a unified login experience for both MSS and ESS users while maintaining Classic functionality. Unlike Classic, Bolt uses a single login URL for both MSS and ESS users. After authentication, users are automatically redirected to the appropriate portal based on their access….<\/p>\n","protected":false},"author":5,"comment_status":"closed","ping_status":"closed","template":"","format":"standard","meta":{"_lmt_disableupdate":"","_lmt_disable":"","footnotes":""},"ht-kb-category":[130],"ht-kb-tag":[],"class_list":["post-7872","ht_kb","type-ht_kb","status-publish","format-standard","hentry","ht_kb_category-about"],"_links":{"self":[{"href":"https:\/\/help.synerion.com\/agile\/wp-json\/wp\/v2\/ht-kb\/7872","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/help.synerion.com\/agile\/wp-json\/wp\/v2\/ht-kb"}],"about":[{"href":"https:\/\/help.synerion.com\/agile\/wp-json\/wp\/v2\/types\/ht_kb"}],"author":[{"embeddable":true,"href":"https:\/\/help.synerion.com\/agile\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/help.synerion.com\/agile\/wp-json\/wp\/v2\/comments?post=7872"}],"version-history":[{"count":3,"href":"https:\/\/help.synerion.com\/agile\/wp-json\/wp\/v2\/ht-kb\/7872\/revisions"}],"predecessor-version":[{"id":7987,"href":"https:\/\/help.synerion.com\/agile\/wp-json\/wp\/v2\/ht-kb\/7872\/revisions\/7987"}],"wp:attachment":[{"href":"https:\/\/help.synerion.com\/agile\/wp-json\/wp\/v2\/media?parent=7872"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/help.synerion.com\/agile\/wp-json\/wp\/v2\/ht-kb-category?post=7872"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/help.synerion.com\/agile\/wp-json\/wp\/v2\/ht-kb-tag?post=7872"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}