You can create / update users in EchoInk in three ways, or through a combination of approaches.
When is each user management approach optimal?
Questions to ask yourself…
- Are the end users part of an IDP system (Okta, Azure, OneLogin, GSuite, AD FS,…)?
- Is the ADP system configured to allow user provisioning via SAML SSO or just authentication? If not, you can still achieve single-sign on for end users but will need to create users via a data feed approach.
- Does your IDP have enough user data in it to define learning audiences as required by the business? If not, SAML for user provisioning is still an option but could be supplemented by a data feed to get richer data attributes about end users.
- Is your end user data accessible in a centralized system?
- Is the management of your end user data fully distributed (i.e., to stores, franchises, regions, affiliates)?
What is the Distributed User Admin App (DUAA)?
The EchoInk Distributed User Admin App provides user management when end users are not managed by the central HRIS system.
This is useful for franchises and the extended enterprise, where the end user may be a customer, an employee, an employee of a supplier, or an employee of an affiliate or franchise. Our Distributed User Admin App provides employee creation and management limited to a specific organization or set of users, and supports manual account creation and management at local levels within the extended enterprise. The user data created in the app will synchronize with the Customer's EchoInk instance to create, update, and disable users.
DUAA Use Cases
- Corporate does not maintain employee data for franchisees.
- Corporate has franchisee employee data, but it is unreliable.
- Inkling end users are not direct employees of Inkling’s customer: They may be employees of partners, distributors, suppliers, or end customers.