Removed permission create workspace - WHY?????

We too at NRG are feelign the pain of non restricted workspace creation. We went originally on a path of embracing teaching users and we found out that 80% learned enough to be dangerous and were.  They would learn a little, think they know how to do things and then create their own workspaces and share with business leaders who made decisions. The analytics were often incorrect more so than correct and we had no visibility to users doing this. no way to receive notifications, no way to know unless we just happenned to stumble on the reports or hear about them in a meeting and realize they were wrong. We would love and need to restrict our users from having "Create" Project permissions. We have tried share to anyone - which is fantastic but users can't bread down an existing report easily and neither can they "filter", sort yes, a table's data making it so hard to find data in a table. We also tried read only on a report but then they can't even change the date range wihtout it being a lot of work on us.  

Please enable a Create Project permission so we can remove that from users.

Hi Eric,

Thanks for reaching out.  In terms of this particular issue, I have to admit that losing this control has not been as bad as I thought it would be (Although, if Adobe's reading this I'd still like to get it back!)

From the start of our self-service journey communication with and education of the people we've been opening up workspace to has been key.  This put us in a good position to deal with this loss of control.  So although we have had some things crop up as a result, generally speaking we've been able to manage it.

And if by 'going down a similar road' you mean using Workspace to democratize your digital analytics data throughout your company, I would strongly encourage you to continue   Despite the odd frustration, it's worked really well for us.

eagerly waiting for a reply from https://forums.adobe.com/people/Andrew+Wathen  myself. As far as we use it, it is still far away from a perfect setup, but slowly getting better...

Andrew Wathen​ - how has the past 4 months been going? Is this still an issue that you are dealing with? I am curious because we starting to go down a similar road.

I don't think the Virtual Report Suite is the way to go as things stand.

I have created a virtual report suite that contains very few dimensions and metrics. This is for the specific purpose of allowing a partner company work with us.

I have discovered that they can view dimensions outside those defined within the VRS is they save as their own version. They can see and access a list "Non-Curated VRS Components"

Since my first post earlier this morning I've had a chance to investigate and reflect on this.

Unfortunately, I fear Adobe have broken our governance and operating model with this decision.

Up until this point the majority of our users couldn't create workspaces.  This forced those users to engage with us when they had new requirements which meant we had the opportunity to:

• Point them to existing workspaces if what they were requesting already existed (maintaining a single source of truth)
• Where needed, build new workspaces (or add to existing ones) maintaining a consistent standard
• Educate these users on the workspaces to ensure they were understood and used correctly

We have only been on the experience cloud login a couple of weeks and I can see that we've already had 20+ random workspaces created that my team were not aware of (and this is with all the mitigations suggested above already in place).

The issue isn't the "overwhelmingness" of workspace, it's the fact that casual users think they know what they are doing but they don't understand all the complexities.   It's about our ability to protect users from themselves and maintain a centralized version of truth which has unfortunately been significantly degraded by this decision.

I know you (Ben) has called for patience but it is difficult given that the longer this goes on the harder it will be to put a lid on this.

Oh no... you've effectively opened Pandora's box. :-(

Right from the start we have been very careful to only give this permission to trusted  users.  This permission was essential in preventing workspace becoming the mess that the old reporting & analytics interface was.

The other issue here is once people have access to something it becomes potentially politically difficult to take it away regardless of whether they can be trusted to use it.

Even if you do restore the permission, I dread to think of the clean up that will needed to do to restore order if this is left like this for any time.

I really hope this gets addressed soon.

Hey folks. Good discussion here and I like urs.boller​'s suggestion to create a Virtual Report Suite to restrict access to data. That's what I came out here to say, and he had already said. Urs is, as usual, one step ahead!

To answer the original question, we're not totally thrilled with the decision to remove the Create/Curate permission ourselves. Unfortunately, there were some issues with the way that permission was engineered, and it put us in a tough spot where we ultimately decided that the best course of action was to fall back to other permission options (restricting dimensions/metrics, VRS curation, etc.) but allow anyone to create a project. I understand the frustration as it sounds like you were using the permission the way we had hoped people would use it. I wish there had been a better way in the short-term. The good news is that Adobe Analytics Product and Engineering teams will be revisiting the permission model and sharing and curation workflows in a future release, so please be patient and hopefully the other options for limiting the "overwhelmingness" of blank Analysis Workspace projects will tie you over until then.