Creating authentication pathways (SSO and Local Login)

To give users access to your new Spark program, we will need to ensure they are able to log in to the Spark site.

To ensure we set up the right authentication methods for your organization, it’s important you understand what we’re trying to accomplish and who we need to involve to get there.  


Once user accounts have been set up in your Spark site (via the demographic data feed), we will need to make sure users are able to log in. Users will access Spark either through the site URL or through an SSO tile, if applicable. Your technical team can help you determine which of these methods makes the most sense for your organization.  

Organizations will use one of the following authentication methods to grant user access to Spark: 

  • Single sign-on (SSO) (recommended): SSO is an authentication method used by the majority of our clients. This allows users to log in to one system (their SSO system) and then automatically be authenticated into other systems (e.g., Spark).
  • Local log-in (LLI): If your company doesn’t have SSO, then we will set up local log-in for your users. This means users will go to your Spark site via the URL and input a username and password to log in.
  • Combination: If you have SSO for some user groups but not all, then we can explore enabling both authentication methods. This happens commonly when companies have some teams that work predominantly in an office and others in a non-office environment (e.g., a manufacturing plant or warehouse). The users who work in a non-office environment may not have SSO capabilities.


Who to Involve

To set up your demographic data, you will need to involve a few teams and people on your end to complete activities during different phases of the Implementation. A summary is below, along with the typical effort required, and which Implementation Phases they can expect to be involved in. 



To learn more about the project phases, check out the Implementation Overview.



Implementation Activities

The information below provides a summary of what the Program Owner and Project Manager can do to help your Technical Representatives get started. 

Tips and Tricks


Program Owner


Project Manager




We find that our clients have the best post-launch experience when they consider Benevity’s best practices and recommendations. Here are some related to authentication: 

  • SSO is recommended, not only because it creates a better end-user experience, but it also provides additional security by giving your organization more control over which users have access to Spark.
  • If local log-in is enabled for “unplugged workers” (users without an email address in the system generating your demographic data), it’s important to consider how we can securely communicate with these users about the new program, and how they can log in for the first time.


Next Steps

These helpful Implementation Guides help to you get a better understanding of each component and the related work for each phase. These guides are great resources for you to review while you’re getting your teams prepared for the upcoming Implementation. 

Share the Technical Guide with your Technical Representatives

Now that you understand Spark Authentication and how we will use it to implement and manage your Spark site, please share your program information and the Authentication Technical Guide with the Technical Representatives listed above to get started.


Was this article helpful?
0 out of 1 found this helpful

Articles in this section

See more
We're enhancing B-Hive!
Take a quick survey and tell us what you think of the new experience.
Stay up-to-date on what's happening at Benevity.