At Quik!, we offer a flexible account structure that supports your business needs. Customers and partners can have multiple Quik! accounts that relate and roll up to one master, or “parent” account, with each sub-account being a “child” account. Whether managing multiple teams, clients, or offices, you can create Parent and Child Accounts to keep everything organized.

What Are Parent and Child Accounts

A Parent Account is your primary account—it can manage or oversee one or more Child Accounts underneath it.

A Child Account is a separate Quik! account that operates independently but is still connected to a parent for easier oversight, control, and reporting.

Why Use Child Accounts?

Keep different teams, offices, or clients separate.
Let each group have its settings, forms, users, and branding.
Consolidate usage and billing under one Parent Account.
Share or push settings (like form bundles or e-sign rules) from the top down.
Partners/resellers offering Quik! to their customers (partners are required to set up customers on their accounts, and it’s ideal to set them up as child accounts).

Setting Up Parent / Child Relationship

When you sign up for a new account on the Quik! website, it won’t automatically connect to a parent account. To link accounts:

Email us at support@quikforms.com and request the relationship setup.
Using our Partner API? If you’re using our Partner APIs to automate account set up, child accounts are automatically associated with your parent account when you create the new account using your credentials.

API vs. Quik! App Account Structure (Parent/Child Relationship)

Parent/Child relationships can be set up across any Quik! product. Because the relationship is at the account level and is not dependent upon the product. For example:

Setup Example	Description

Setup Example	Description
Parent Account with no product and child API accounts	Used for centralized reporting only
API Parent with App Child accounts	You offer a Quik! App account per client under your API integration
Quik! App Parent with App Child accounts, which facilitates managing settings from the top down	Manage settings across multiple teams or offices

This structure helps organize accounts by function, product, or audience—whatever works best for your needs.

Users vs. Accounts

An Account is tied to a customer record (called a CustomerID).
A User is someone who logs into Quik! to perform actions (e.g., generate forms, manage settings, etc.).

Depending on your workflow, each account can have as many users as needed.

API vs. App Users

API Users:

Most API setups don’t need end-users in Quik!.
Only a few admin users must manage forms, e-signature setup, and API settings.
End-users interact with your system, not Quik! directly.

App Users:

Each person needs their own login.
Ideal for tracking activity, managing permissions, and controlling access.
Designed for direct interaction with the Quik! App.

When Should I Create a Child Account?

Set up a Child Account when a group needs:

Their own forms, logos, or field rules.
Private CRM or customer data.
Their own billing (optional).
To be managed independently (like a different office or client).
A completely separate experience within Quik!.

📝 Example: A financial advisor and their team share data and settings, they use one account. A different advisor with unique clients and forms? They should have their own child account.

Setting Up Users

The way you set up users depends on which Quik! product you're using, API or App. Here's what we recommend:

For API Accounts

Most API customers don’t need to set up many users. The Quik! platform works in the background of your own technology, so your end-users never interact with Quik! directly.

Only a few admin users are needed to manage:
- Form subscriptions
- Creating and organizing form groups
- Enabling e-signature settings
- Configuring field rules and validations

Tip: API users are typically developers or administrators managing your integration.
Set up Quik! Forms Manager (QFEM) to manage account settings.Manage Account with the Quik! Forms Enterprise Manager

For Quik! App Accounts

For Quik! App customers, every person on the team should have their own user login.

This setup allows you to:

Manage access and permissions for each individual
Track and monitor activity by user
Control who can view, fill, or submit forms
Assign roles based on job function (e.g., Admin, Advisor, Processor)

Unique logins are essential for security, accountability, and a smooth experience inside the Quik! App.

Frequently Asked Questions

What Is an Account at Quik!?

An account is a customer profile in Quik! (known as a CustomerID). It holds settings, forms, user records, and more.

What’s the Difference Between Parent and Child Accounts?

Parent Account: The top-level account that manages or reports on child accounts.
Child Account: A linked but separate account with its own settings and users.

Can a Child Account Have Its Own Child Accounts?

Technically yes, but this setup is uncommon and not recommended for simplicity and performance.

Can a Child Belong to More Than One Parent?

No. A child account should only be linked to one parent account at a time.

How Many Users Can an Account Have?

There’s no hard technical limit. But we recommend:

Only adding users who need access.
Regularly removing or disabling inactive users.
Checking your product plan for billing limits.

Quik! API Guide

Understanding Parent & Child Accounts at Quik!