> For the complete documentation index, see [llms.txt](https://docs.datalogz.io/guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datalogz.io/guides/organizational-setup/connector-onboarding-guide.md). # Connector Onboarding Guide Connect each of your BI platforms to Datalogz Control Tower once; everything else, from inventory to monitoring, follows automatically. This page is the starting point: pick your platform, see what to prepare, and know what to expect after connecting. {% hint style="info" %} An active Datalogz account and license are required before starting these guides. Contact if you do not have one yet. {% endhint %} ### Choose your platform Each platform guide lists exactly which credentials to prepare and which settings to apply. Have the right person from the Getting Started roles available; creating credentials usually requires an admin of the platform. | Platform | Authentication | Which metadata Datalogz reads | | ---------------------------- | ------------------------------------------------- | --------------------------------------------------------------------------------------------- | | Power BI | Microsoft Entra service principal | Workspaces, reports, dashboards, semantic models, dataflows, apps, capacity and activity data | | Tableau | Personal access token (per site) or Connected app | Sites, projects, workbooks, views, data sources, usage | | Qlik Sense | Virtual proxy with header authentication | Streams, apps, sheets, tasks, activity logs | | Sigma | OAuth client credentials | Workbooks, data models, connections, members | | Spotfire | Oracle repository database connection | Library content, lineage, activity | | Databricks (Private Preview) | Account-level service principal (OAuth M2M) | Workspaces, Unity Catalog, Genie Spaces, SQL warehouses | | SharePoint (Private Preview) | Microsoft Graph (app or user mode) | Sites, document libraries, Excel workbook inventory | ### Setup is the same shape everywhere 1. Create credentials in your BI platform. Your platform's guide shows how, step by step. 2. In Control Tower, go to **Settings > BI Connectors**, click **New Connector**, and select your platform. 3. Enter the credentials. Control Tower tests them before saving, so a typo never becomes a broken connector. 4. Name the connector, choose the sync schedule (for example Daily or Weekly), and scope what to monitor. 5. Confirm. The first sync starts immediately. ### After you connect * The first sync builds your inventory, and default monitors activate automatically. Alerts begin appearing on the Home dashboard. * Syncs run on the schedule you chose. You can trigger a manual refresh anytime from the connector's detail page, where you can also follow sync status and history. * When a credential is about to expire (for example a client secret or personal access token), re-authenticate from the connector's detail page. We recommend setting expiry reminders when you create credentials. ### Troubleshooting * Check the connector's sync history and logs on its detail page; failed runs show which step went wrong. * The most common causes are an expired secret or token, missing tenant settings (Power BI), a wrong API host (Sigma), or a firewall blocking Datalogz. The IP addresses to whitelist are in the Getting Started guide. * Still stuck? Contact with the connector name and the time of the failed sync. Connectors read **metadata only**. They never access the data inside your reports, dashboards, or files. ### Identity and asset mapping Two more connections enrich everything the BI connectors collect by tying it to your organizational structure: | Connection | How it connects | What it adds | | ------------- | ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Entra ID | Microsoft Entra service principal with read-only directory access | Maps BI users to their departments, so adoption, activity, and ownership roll up by department in the inventory and BI360 | | Asset Mapping | Mapping file upload (CSV or XLSX) | Maps assets to your sectors, business units, domains, or other logical groups, so health, usage, and cost roll up by the part of the business that owns the content | Set up the user mapping with the Entra ID guide, and see Asset Mapping for the file format and upload steps. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.datalogz.io/guides/organizational-setup/connector-onboarding-guide.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.