- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Workspace Setup recommendation in Service
Hi All,
We are trying to setup workspace and wanted to know your recommendation.
Do you suggest creating
Approach 1:
Dev, QA and Prod workspace and publish the contents on each depending on where we want to publish. So if we are in development phase we can publish it to Dev Workspace and once we want to open it for QA testing, we can publish the same to QA Workspace. And similarly for Prod.
OR
Approach 2:
Create workpace for various data categories like
for HR, we create HR Dev, HR Qa and HR Prod
For Marketting team, we create Marketting Dev, Qa and Prod
and so on.
You can suggest any other approach if you have.
Regards,
Akash
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That really depends on your security considerations, does it matter if HR people see all of the dashboards/reports? If so, then use the second approach, otherwise I always believe that simpler is better.
Follow on LinkedIn
@ me in replies or I'll lose your thread!!!
Instead of a Kudo, please vote for this idea
Become an expert!: Enterprise DNA
External Tools: MSHGQM
YouTube Channel!: Microsoft Hates Greg
Latest book!: Power BI Cookbook Third Edition (Color)
DAX is easy, CALCULATE makes DAX hard...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes we don't want HR people to see other dashboards. But can't we control the access at individual dataset and dashboard level even if we have everything on Dev workspace ?
I just want to understand best practice followed in other real time projects.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
While you could, again, going back to simplicity, I would do it by workspace.
Follow on LinkedIn
@ me in replies or I'll lose your thread!!!
Instead of a Kudo, please vote for this idea
Become an expert!: Enterprise DNA
External Tools: MSHGQM
YouTube Channel!: Microsoft Hates Greg
Latest book!: Power BI Cookbook Third Edition (Color)
DAX is easy, CALCULATE makes DAX hard...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
So you suggest approach 2. But will not end up having too many workspace if we have various BUs like HR, Finance, Marketing, Consulting etc..
Also how do we deploy the code from one workspace to other. Lets say we develop something on HR Dev Workspace. Now I want the infrastructure admins to deploy the code from Dev workspace to Prod workspace.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That all depends on how you are doing your development. If you are using Desktop and then Publishing, you would just publish to a different workspace.
Follow on LinkedIn
@ me in replies or I'll lose your thread!!!
Instead of a Kudo, please vote for this idea
Become an expert!: Enterprise DNA
External Tools: MSHGQM
YouTube Channel!: Microsoft Hates Greg
Latest book!: Power BI Cookbook Third Edition (Color)
DAX is easy, CALCULATE makes DAX hard...

Helpful resources
Subject | Author | Posted | |
---|---|---|---|
01-27-2025 02:18 AM | |||
02-06-2025 08:39 AM | |||
02-18-2025 06:52 AM | |||
01-03-2025 12:36 PM | |||
02-17-2025 08:25 AM |