Identifying your learners (the end-users) is a crucial aspect of Strigo's Academy.
The end-users must be identified so Strigo can track their progress, in order to:
Allow the learners to see their own personal paths, courses, progress, etc.
Allow you to track their progress, completions, performance, etc.
Easy user identification
Tracking learners is naturally a common practice for any learning system.
Unlike classic learning systems, in Strigo learners don't have to sign up to an external system, and you don't have to deal with how to wire an external system into your identification processes (via SSO). Since Strigo is an embedded, in-product system, users are identified seamlessly behind the scenes, like they would with any other embedded widget (like Intercom, Zendesk, WalkMe, etc.)
How does it work?
Here are directions for an engineer about how to identify users.
In your code, identify the right place (on the server's side) where a user is being identified in your system - a sign-up, a login, etc.
Use this API in order to get a unique token for that user.
You will have to send basic identification information to Strigo's API - namely, an email address.
You can also enrich the user profile with more information, to your choosing.
You will get back a token that you can use in order to set up Strigo's Academy panel for that user.
It's a best practice to persist the user's token in your user management database/system.
Note: pay attention to authenticating your server against Strigo's API before you start using it, as explained here.
A user that has a token in Strigo via the API is now identified as a learner and can be managed through Strigo's admin console, on the Audience page.