Have you heard about the new apps yet? Apps are the new way to distribute content to large audiences in Power BI. We recommend using apps instead of organizational content packs or read-only workspaces. Learn more about apps.
Do you regularly distribute reports by email to your team? Try this instead: Package up your dashboards, reports, Excel workbooks, and datasets and publish them to your team as an organizational content pack. Content packs you create are easy for your team to find they are all in AppSource. Because they're part of Power BI, they leverage all the features of Power BI, including interactive data exploration, new visuals, Q&A, integration with other data sources, data refresh, and more.
Creating content packs is different from sharing dashboards or collaborating on them in an app workspace. Read How should I collaborate on and share dashboards and reports? to decide on the best option for your situation.
In AppSource, you can browse or search for content packs published to the entire organization, to distribution or security groups, and to Office 365 groups you belong to. If you aren't a member of a specific group, you won't see content packs shared with that group. All members of the group have the same read-only access to the content pack data, reports, workbooks, and dashboards (unless it's a SQL Server Analysis Services (SSAS) data source, in which case your privileges are inherited with the data source).
The dashboards, reports, and Excel workbooks are read-only, but you can copy and use the dashboards and reports as a starting point for creating your own personalized version of the content pack.
Organizational content packs are only available when you and your colleagues have Power BI Pro.
Publishing an organizational content pack adds it to AppSource. This centralized repository makes it easy for members to browse and discover dashboards, reports, and datasets published for them.
Read more about finding and opening organizational content packs.
Any Power BI Pro user can create, publish, and access organizational content packs. Only the content pack creator can modify the workbook and dataset, schedule refresh, and delete it.
The lifecycle looks something like this:
In Power BI Pro, Nate creates a content pack and publishes it to the Marketing distribution group. The refresh settings are inherited with the dataset and can only be changed by Nate.
If Nate creates the content pack from within a Power BI app workspace he belongs to, then even if he leaves the workspace, others in the Power BI workspace can take over ownership.
Nate sends mail to the distribution group, telling them about the new content pack.
In Power BI Pro, Jane, a member of the Marketing distribution group, searches for and connects to this content pack in AppSource. She now has a read-only copy. She knows it's read-only because in the left Navigation Pane, there is a sharing icon to the left of the dashboard name and report name. And when she selects the dashboard, a lock icon lets Jane know she is looking at a content pack dashboard.
Say she decides to customize it. She now has her own copy of the dashboard and reports. Her work does not affect the source, the original content pack, or other distribution group members. She is now working on her own copy of the dashboard and report.
Nate makes updates to the dashboard and when it's ready, he publishes a new version of the content pack.
Say Nate changes the security settings. Julio and Jane no longer have access to the content. Or say they're removed from the Marketing distribution group.
Or Nate deletes the content pack.
All distribution group members have the same permissions to the data as the content pack creator. The one exception to this is SQL Server Analysis Services (SSAS) on-premises tabular datasets. Because the reports and dashboards are connecting live to the on-premises SSAS model, the credentials of each individual distribution group member are used to determine the data he or she can access.