Hi, admin users need to quickly open multiple sections of Adobe UI at the same time. For instance we are working on settings (admin section) and we need to quickly check data (workspace section). Today the top menu does not allow to use the "open in a new window" command in browser, so we struggle with this UX issue. Can we change this behaviour please?

Hi all, I think this is one of the critial issue every one has with the Adobe Analytics credential system. We use “product profile” for sharing workspace because Adobe shows “product profile” instead of “user group” in the box selection for sharing assets. That makes absolutely no sense and it’s not correct from a credential-strategy point of view.I need to share a report with a TEAM (user group), no with a CREDENTIAL SETTINGS SETS (product profile). We need to immeditalety bring to engineer/arc...

When we have to manage hundreds of users, it becames relly difficult to remember roles and understand why of some credentials granted.Why we (Admins only) dont have a simple field at user level, where we can add our notes about the above information?Otherwise we have to rely to a spreedsheet for managing credentials, which is no-sense....

Ok, you added the color palette... but we dont use it, coz they are pre-set of colors where we dont understand how they are referring to workspace elements....So, I raise again my idea.For every element of workspace an IDs (class name) should be available and and we want to add/edit CSS code for customization of his style.At the top of workspace you should also make available all the CSS code we set into the workspace, as a general and global recap.Advanced workspace are made by technical analys...

I notified Adobe support team many times about errors we have in the real time report. No way to bring them to the fix. So here the workaround we need:give in real time settings the possibility to1) hide comparison to previous periods (since it's wrong most of the times)2) exclude duplicated hits. In other words, give the possibility to count once per visit (since end-users dont understand that counting hits needs to be extremely careful, before giving any conclusion)

There is a point where workspace becomes extremely slow... for sure due to the number or structure of queries. Could you add a small box to log the list of queries with status (ready / loading data / processing) and last performance in terms of sec? So we can understand where is the problem...