Hi,
We want to teach our less experienced colleagues with Adobe Workspace, but wanted to start with basic. I tried to create a curated workspace environment, where I would allow users to see only a couple of metrics, dimensions, segments, and then continue with more.
I used a test account – took away all previous rights and applied a new product profile with only few items available, to test it.
This is what I allowed:
However, when I login as the test user, I still see more dimensions or metrics than I allowed in the profile.
I didn't find out why I see the items I didn't allowed and also didn’t find the way how to remove it.
The tester is not having rights via any other profile, nor is member of any other group.
Can you help me find the way to "clean" the workspace for the test user?
I don't want to use project curation. VRS curation is also not the best solution for our case.
Creating new users is also not a solution as we have accounts for our colleagues already set.
Thank you
Alena
Solved! Go to Solution.
Views
Replies
Total Likes
I would recommend creating a test VRS specifically just for this test group and adding that VRS to their Product Profile.
In the Components setting of the VRS, only include the metrics (and dimensions and segments) you want them to be able to use (right now I see the others included which is why you are seeing those in the Workspace). The components you exclude in this particular VRS should not affect the source report suite or other folks who have access to other Product Profiles.
Views
Replies
Total Likes
Hi @alenai48070615 -- A lot of those extra components seem to be OOTB or calculated metrics that -- for some reason -- evade the hide settings in Admin Console, and I think it may have something to do with the report suite associated with the Product Profile. If project curation is not an option, creating a VRS for the test group would be the best solution. You should be able to limit the components they can access within Workspace more effectively using that.
Views
Replies
Total Likes
Hi Kaya, great to talk to you about this! Yes, the VRS curation would do, but we give users rights to different vrs (so we would need to curate all of them - and there are plenty) plus it would limit our own (analytics team) usage of these vrs.
Or did you mean the other way round, remove these "evaded" metrics from all services vrs? Tested it and this vrs curation overrides the product profile setting, so it boomeranged back to above.
Tried to create a test VRS, it was populated with the same metrics, so it is something above
I was thinking that the projects shared to "all" might have made these metrics visible, but it is probably not the case.
Views
Replies
Total Likes
I would recommend creating a test VRS specifically just for this test group and adding that VRS to their Product Profile.
In the Components setting of the VRS, only include the metrics (and dimensions and segments) you want them to be able to use (right now I see the others included which is why you are seeing those in the Workspace). The components you exclude in this particular VRS should not affect the source report suite or other folks who have access to other Product Profiles.
Views
Replies
Total Likes
Hi, understood. This works, yes. There can be a dummy VRS for that, and that only includes the selected metrics and dimensions without the invaded components.
For our colleagues, I'd like to use already existing VRS (service-language or service all), to which they already have accesses and for which they have dashboards set. I reckoned it would make more sense for us to edit the components via product profiles.
Views
Replies
Total Likes