Hi @km1837,

Databricks AI/BI Dashboards have solid theming and organisational capabilities that should cover most of what you are used to in Power BI.

AI/BI Dashboards don't have a "template file" concept the way Power BI does with .pbit files, but you can achieve the same consistency through two features (Workspace themes and Text widgets with images) working together.

Workspace Themes are the closest equivalent to a Power BI template for branding. A workspace admin can define a default theme that controls fonts (family, colour, size, weight, and case per text category), canvas background colour, widget styling (background, border, corner radius, padding, margin, shadow), visualisation colours (axis, grid lines, categorical and continuous colour palettes), and textbox alignment. Every new dashboard in the workspace automatically inherits this theme, so once it's set up, your team gets consistent branding without any extra effort. You configure it under Settings > Appearance > AI/BI > Theme. See the example below. 

Text widgets with images handle the header/banner part of your Power BI template. You can drag a text widget onto the canvas and use the formatting toolbar or raw markdown to add your company logo (via image URL or path), styled header text, links, and tables. This gives you the equivalent of a branded header on each page.

For a practical "template" workflow, I'd suggest: set up the workspace theme for your brand colors and fonts, then build one dashboard with your standard header layout, page structure, and any boilerplate text widgets. Export it as a .lvdash.json file (kebab menu > File actions > Export), and use that as your starting point for new dashboards by importing it and swapping out the data. You can even edit the JSON directly for bulk changes.

With regard to your question about organising by departments, You don't need separate workspaces for Operations, Finance, and Sales. Within a single workspace, you can organise dashboards into folders in the workspace browser, just like you would with any file system. Create a folder structure like /Dashboards/Operations, /Dashboards/Finance, /Dashboards/Sales and manage access through folder-level permissions. 

If your organisation does want stronger isolation (separate compute, separate access controls at the workspace level), you can use multiple workspaces and transfer dashboards between them using the export/import workflow or the Workspace API. But for most BI teams serving multiple departments, folders with permissions within a single workspace are simpler and easier to manage.

By the way...you can now import .pbit(Power BI template) files directly into Genie Code, and it will build an AI/BI dashboard that replicates your visualisations. It also creates metric views that mirror the underlying business logic and detects relationships from the source file. This is a great option for migrating existing reports, but there are a couple of things worth noting for your scenario. The import focuses on recreating the data model and visualisations, not the branding layer (headers, logos, colour themes). So even after importing, you'd still want to set up a workspace theme and add your branded text widgets. It also requires partner-powered AI features to be enabled on both the account and workspace.

The workflow is straightforward: go to Dashboards > Create > Import from Power BI, attach the .pbit file, and Genie Code builds the dashboard.

You can also use the /importBI command within Genie Code if the file is stored in a Unity Catalog volume.

Hope this helps.

If this answer resolves your question, could you mark it as “Accept as Solution”? That helps other users quickly find the correct fix.