There are cases where customers want to do all the setup work in Quik! on behalf of their users. Perhaps the firm wants to offer a white-glove-like service to onboard their users to ensure the users make the necessary changes and adopt Quik!. Or perhaps there is a need to control what users can do in order to enforce compliance rules. This article discusses the approach of onboarding users.

First, Set Up The Parent Account

The parent account is the top-most account that is managed by the enterprise. This account is where you make all your settings including (some of these settings must be manually configured to replicate down to child accounts, so please contact your Quik! implementation manager for assistance):

• Application Settings (which will copy any parent account application-level settings down to the child accounts)

• Public Form Bundles (which will appear as Public Form Bundles in child accounts)

• Restrict to Subscribed / Followed Companies (limits which companies child accounts can see in the All tab of the search screen)

• Copy Followed Companies (will copy followed companies from the parent to the child’s followed companies list - it should not be used with the above feature that restricts the search to the followed companies

• Copy E-Sign Credentials (which can be used to deploy e-sign settings down to child accounts)

• Copy E-Sign Default Recipients (which will copy any default recipients, like back-office email accounts, down to the child accounts to ensure routing of e-signed documents)

• Copy E-Sign Enablement Settings (which will copy any e-sign enabled companies and forms on the parent account down to the child accounts)

• Copy Field Attributes (which will copy any field rules, validations and settings set on the parent account down to the child accounts)

Child Account Setup

There are two ways a child account gets set up:

1. The user signs up and their account is associated to your parent account.

2. You or someone at Quik! sets up the child account.

User Signs Up

Having the user sign up is the easiest approach since it delegates the work to the user. However, there are still some decisions to be made in the account set up.

1. Which set of users will work together? Typically a single office with one or more users uses a Quik! account. Since a single account will have data access and settings that potentially all users can see and share, it’s important to not group users together who are not allowed to see each other’s data or share their settings.

2. Will one user need access to multiple accounts? Let’s say you have two reps supported by one staff person. If each rep needs their own Quik! account (because they have private CRMs or proprietary forms) then the staff person will need to log into two different accounts (which will result in 2 users on each of 2 accounts in this scenario). If the two reps can share a single Quik! account (e.g. they each set up their CRM as private to themselves) then the staff person can simply be another user on that Quik! account, resulting in 3 total users.

   1. If the staff person needs to access each of the reps data sources, which were set up as private by each rep, then the staff person will also need to set up each CRM connection as private. The staff person should also be an Admin role while the reps are User roles.

Manual Set Up

If you wish to make it super easy for users to onboard by doing all the user set up yourself, then you’ll need to:

1. Organize your users into groups.

2. Decide which users can see other user’s CRMs

3. Sign up for the child account (and have our support team associate it to your parent account)

4. Add users to the child account in the Settings section.

5. (Optional) Configure user-specific settings

   1. If you retain the user’s credentials, log into each user’s account to configure private CRM settings (optional)