Account Setup Guide: Enterprise Customers, Partners, & Integrators

Quik! supports a variety of account structures to meet the needs of different customer types, from enterprise firms and platform integrators to resellers and advisors. Whether you're onboarding a large salesforce, embedding Quik! into your technology stack, or managing clients under one umbrella, we offer flexible options to help you set up accounts in a way that’s secure, scalable, and easy to manage.

This guide will walk you through the different ways Quik! accounts can be structured, including:

• When to use Parent vs. Child Accounts

• Which account types apply to Enterprise, Partner, and Integrator scenarios

• How to manage users within each type of account

• Best practices for testing, scaling, and customizing your Quik! setup

Not sure what applies to you? No problem, each section is clearly labeled, so you can find the structure that fits your business model.

How Many Accounts Do I Need at Quik!?

Great question—and one we hear often from partners, integrators, and enterprise customers.

There’s no one-size-fits-all answer. Instead, Quik! offers flexible options that fit how you operate. Whether you're managing multiple teams, clients, or locations, we help you set up accounts in a way that keeps everything organized and scalable.

For Enterprise Customers: 1 Parent Account + Optional Child Accounts

Enterprise customers typically fall into one of two groups:
API Customers or Quik! App Customers

Your account setup depends on how you use Quik!:

API Customers

Most API customers only need one Quik! account. Since you're embedding Quik! into your own platform, your users interact with your system, not Quik! directly.

A single account is usually enough unless you need to:

• Support multiple subsidiaries or legal entities

• Give each client or firm their own settings, forms, and rules

• Segment users who operate independently (e.g., advisors or offices)

• Enable private forms and isolated CRM data per group. (Some partners work this way)

In these cases, you may choose to create child accounts to keep things separated and scalable.

Quik! App Customers

Most Quik! App enterprise customers benefit from having a Parent Account plus multiple Child Accounts—especially if your users work in different offices or operate independently.

This setup allows you to:

• Give each office or team its own forms, branding, and rules

• Manage users and permissions more efficiently

• Keep data and workflows organized by group

• Push shared settings from the parent account to all child accounts

A Common Setup for Quik! App Enterprise Customers

Most enterprise customers use the Quik! App choose to have:

• One Parent Account to manage shared settings and reporting

• Multiple Child Accounts, typically one per office or team

Each Child Account can be shared by a single user or an entire group (such as a branch office or advisor team). This setup allows each office to:

• Access their own set of forms

• Customize their branding and user permissions

• Manage users independently without affecting other teams

💡 This structure gives your organization flexibility while keeping things organized across multiple offices, regions, or business units.
API Customers

See this page for more: Understanding Parent & Child Accounts at Quik!

For Partners: 1 Parent Account, Many Child Accounts

If you're a reseller, distributor, or integration partner, you’ll likely need one primary Parent Account and separate Child Accounts for each client. This setup helps you manage everything efficiently while keeping each client’s experience isolated and customized.

How It Works

1. Your Parent Account

   • This is your primary account at Quik!.

   • It serves as the top-level account where:

     • Usage, billing, and pricing can be rolled up for reporting.

     • Settings can optionally be pushed down to all child accounts (we’ll help you decide which apply).

   • If needed, this account can also be your Sales Demo or internal use account.
     
     

2. Do You Need the UAT Environment?

   In most cases, you won’t need to use our UAT (User Acceptance Testing) environment for development, implementation, or testing.

   Instead, you can safely use Draft Mode in the production environment. This allows you to:

   • Test form generation

   • Preview how data fills into forms

   • Validate your customer’s actual configuration and settings

✅ Testing in production (using Draft Mode) reflects real customer settings and is usually the most accurate way to ensure everything works as expected.

⚠️ Important: Any changes made in UAT do not transfer to production. You’ll need to manually reapply those settings in the live environment if needed.

3. Child Accounts for Clients and Use Cases

Each of your clients should have their own Child Account.

You can also set up additional accounts for:

• Sales demos

• Development/testing environments

• Internal QA or training

You can create these through our team or automatically using our API/web services.

Why Use Child Accounts?

Each child account is a fully independent Quik! account with its own:

• Form library (including private forms unique to that client)

• Custom branding (logos, labels, etc.)

• Field rules (required fields, formats, masks)

• Form groups (bundled sets of forms)

• User access and controls

This structure ensures complete separation between your clients while allowing you to manage or oversee them as needed.

Suggested Account Setup for Partners

Why This Structure Works

Every child (or sub) account at Quik! is a fully functional account, just like the parent. This means:

• Each client can have their own private forms, which are visible only in their account.

• You can apply unique field rules, like required fields, input formats, or data masking.

• Form groups (bundled sets of forms) can be tailored to the client’s workflows.

• Each account can feature custom branding, such as logos or headers.

This structure provides flexibility and control while helping you manage multiple customers efficiently.

For Integrators: Typically 1 Partner Account

If you're an integrator, like a CRM provider, financial platform, or software system embedding Quik! you’ll likely only need one Quik! account.

Most integrators, such as CRM platforms or other technology providers, only need one Quik! account.

This account is used for:

• Setting up Single Sign-On (SSO) through your platform

• Testing and validating how Quik! works with your systems

• Managing your own form subscriptions and settings

If you are not:

• Provisioning users or clients inside Quik!

• Reselling Quik!

• Handling customer signups (i.e., customers sign up directly with Quik!)

...then one Partner Account is all you need.

You’ll typically use a Referral Account with SAML integration to support SSO, allowing your users to access Quik! seamlessly through your platform.

Need help with SAML setup or account provisioning? Contact our support team at support@quikforms.com.