Databook uses your organization's team structure — regions, verticals, functions, and reporting lines — to power team-level analytics across the platform. Rather than recreating that structure by hand, you can bring your organizational hierarchy into Databook directly from your CRM or from a hierarchy file you provide, making it available in Membership > Teams for analytics segmentation.
Note: Only Organization Owners and Organization Admins can view Membership settings and coordinate a hierarchy sync.
Why sync your organizational hierarchy
Once your hierarchy is in Databook, your teams, regions, and reporting lines become available across analytics — not just as a flat list of names, but as the structure your business actually runs on. In Asset analytics or Coach analytics, you can filter usage by team to see adoption across a specific region, vertical, or function, and roll up usage recursively across nested teams — so leadership can see adoption at the org level while managers drill into their own team.
Without a synced hierarchy, teams have to be created and maintained one at a time in the Admin Console, and any change to your org structure has to be repeated manually.
Two ways to bring your hierarchy into Databook
Databook supports two paths, depending on whether your organization has a CRM integration connected.
Method | How it works | Who keeps it up to date |
CRM sync | Once a CRM integration is connected, Databook automatically builds your team hierarchy from CRM role and reporting data and keeps it in sync on an ongoing basis. | Your CRM. Team names, structure, and member counts are read-only in Databook. |
CSV-based setup | If your organization doesn't have CRM sync connected, you provide your hierarchy using a Databook-supplied CSV template, which your Databook contact loads into your organization. | You, in the Admin Console — once loaded, the hierarchy behaves like any manually configured team and can be edited going forward. |
CRM sync
When a CRM integration is connected, Membership > Teams displays a Managed in CRM banner and shows your teams as a hierarchical tree that mirrors your CRM's structure. Because your CRM is the source of truth, teams can't be created, renamed, or reassigned from within Databook — changes made in your CRM sync through automatically.
See How to manage teams in your Databook organization for what this looks like in the product.
CSV-based setup
If your organization doesn't use CRM sync — or your CRM doesn't track the org structure you want reflected in Databook — you can provide your hierarchy using a CSV template. Ask your Databook contact for the template, fill in one row per person, and send it back to them to load into your organization.
The template captures:
Column | What to enter |
L0, L1, L2 | Your organization's hierarchy levels, from broadest to most specific (for example, region, sub-region, team). Your levels don't need to match another customer's — Databook maps them to your own naming. |
The person's Databook email address. | |
Name | The person's full name. |
Job role | Their job title. |
Sales org or business development org? | Whether the person sits in a sales or business-development function. |
Is Manager? | Whether the person is a manager within the hierarchy. |
Note: Once your hierarchy is loaded from a CSV, it's configured the same way as a manually created team — your admins can continue to manage team names and membership in the Admin Console going forward. This is different from CRM sync, where changes must be made in your CRM.
Analytics timing
Note: Whichever method you use, hierarchy and membership changes are reflected in analytics after the nightly batch run — updates made today appear the following day.
Getting started
To connect a CRM integration or provide your hierarchy by CSV, contact your Databook representative. They'll confirm which option fits your organization and coordinate the setup.