DashboardFox Client Workspace Provisioning (Onboarding)

DashboardFox Client Workspace Provisioning (Onboarding)

1. 01

   Confirm the client's data source is on DashboardFox's native connector list before quoting the retainer.

   Supported engines are PostgreSQL, MySQL, SQL Server, Oracle, Snowflake, BigQuery, and Redshift. Anything outside that set needs an ODBC driver, and the driver count is capped by plan: 2 on Starter, 5 on Growth, 10 on Scale. A client on a niche warehouse can burn a Growth slot on day one.

2. 02

   Pick the plan tier against the client's monthly active user count, not their headcount.

   Starter at $99/month covers 5 monthly active users, Growth at $249/month covers 30, and Scale at $499/month covers 100. Email report recipients and idle viewers do not consume seats, so a 200-person client with 12 people who actually open dashboards fits on Growth.

3. 03

   Create the sub-account from the agency admin interface and attach the client's custom domain.

   The admin console manages up to 50 sub-accounts from one login. Starter includes 1 custom domain and 1 branding policy, Growth includes 3 domains and 5 branding policies, and Scale includes 10 domains. Map each client to a domain at creation so you never have to migrate a live portal later.

4. 04

   Connect the database through the native driver or an ODBC connection, then verify the schema reads correctly.

   DashboardFox queries the source directly with no ETL layer, so a misconfigured connection surfaces as a broken dashboard rather than a failed sync job. Run one test query per table the client cares about before building anything visual.

5. 05

   Build the first dashboard in the visual builder, then add SQL panels only where the drag-and-drop layer cannot express the metric.

   Both paths write to the same dashboard, so a mixed build is fine. Keep the SQL panels documented in the client handoff notes, because the next agency analyst will need to know which tiles break if a column is renamed.

6. 06

   Apply Data Tags for row-level security before the client's first login.

   Row-level security ships on every plan, including Starter, so there is no upgrade excuse for skipping it. Tag each user or group at provisioning time. Retrofitting tags after a regional manager has already seen another region's numbers is a trust problem, not a config problem.

7. 07

   Schedule the email reports the client asked for and confirm the recipient list against the active user count.

   Scheduled email delivery is included, and recipients who only read emailed reports do not count as monthly active users. This is the single biggest lever on the client's effective cost per report, so document the recipient list in the retainer scope.

8. 08

   Hand off with a recorded walkthrough and log the sub-account in the agency's client register.

   Record navigation, export, and filter behavior. Note the plan tier, domain count used, and ODBC driver slots consumed so the next provisioning decision for this client does not require re-reading the billing page.