User management - Enterprises may want to leverage their existing user authentication methods (e.g. Active Directory) and use SSO to allow users to access Quik!, as well as to add or remove Quik! users.
User control - Enterprises may want to control what a user can and cannot do in the Quik! App. For example, enterprises may not want users to be able to access the Settings page of the Quik! App.
Group users - Enterprises may want the ability to group users together to share private form groups, data, and settings. Many enterprises group users into a hierarchy for reporting and to organize users along their actual office setup (i.e., 2 reps plus 2 staff working in one office want to work together within Quik!).
Database connections - Enterprises may want to use their existing data source (e.g. SalesForce) or provide Quik! with a custom one to prefill forms. In some cases, enterprises may even want the ability to connect to multiple data sources.
Advisor data - Enterprises already have rep records in their system and would like to use those records to prefill. This gives enterprises the benefit of managing rep data in one place and giving them the flexibility to tell Quik! which rep record to use for the logged in user.
User experience changes - When data is sent to Quik! via SSO, enterprises may want to modify the user experience to simply workflows for their users. Below are some examples of this:
FormIDs, FormGroupIDs
The forms shopping cart will be prefilled with FormIDs
The user will automatically be taken to the client screen (skip the home page and form searches)
ClientIDs
The client screen will hide the select database dropdown
The client search results should show the people passed as ClientIDs (i.e. lookup the Client IDs and return their names)
RepIDs, Rep Numbers
The rep drop-down on the launch page should be prefilled with the rep name(s) and rep number(s)
Form Viewer Configurations
Various aspects of the Form Viewer can be customized based on attributes sent to Quik! via SSO