Created by Miki Yanagi, last modified on May 01, 2023

The primary purpose of Workspace is team collaboration. The end user request via form to create their workspace, and then Power BI administrator will create the workspace.

Workspace should not be too board, nor too narrow. It become difficult to navigate once there are 20-30 reports. Once workspace is created, the users can publish an app.

Naming Conventions for Workspace:

 Business Unit - Functional purpose -Data Ownership

Token Meanings:


MeaningsExamples
Functional purposeThe subject area or topic as an abbreviation
  • Students
  • Finance
Data Ownership

Department name. Omitted indicates user-managed content

  • DSIT
  • IR
Business UnitBusiness unit for or by whom the workspace is maintainedUMS01- 08
Workspace Type
  • Data – indicates dataset only workspace
  • Reports  – indicates reports only workspace
  • Omitted – indicates workspaces containing both datasets and reports
  • Data
  • Reports


Environment
  • Dev -  indicates development
  • TST -  indicates test
  • Omitted indicates production
  • DEV
  • TST


Suggestions for Workspace Objects:

There is not a policy or naming convention for naming dashboards, reports, workbooks, datasets, or dataflows. This is left up to the individual Power BI author. Suggestions are as follows:

  • Be short, brief, and clear as to the topic.
  • Be consistent. For example, if there are multiple YTD reports then use a consistent YTD prefix rather than Year-To-Date.
  • Do not include the word 'report' in a report name. It is redundant, and a dashboard inherits the report's name so it can become confusing.
  • Do not use the word 'dashboard' in a report name. Because dashboards are a specific type of object in the Power BI Service, naming a report as a dashboard can be very unclear for report consumers.

Request Forms: