New Admin Console for Adobe Analytics Permissions

Avatar

Avatar
Springboard
Level 7
jeff_bloomer
Level 7

Likes

146 likes

Total Posts

222 posts

Correct reply

16 solutions
Top badges earned
Springboard
Validate 10
Validate 1
Contributor
Shape 1
View profile

Avatar
Springboard
Level 7
jeff_bloomer
Level 7

Likes

146 likes

Total Posts

222 posts

Correct reply

16 solutions
Top badges earned
Springboard
Validate 10
Validate 1
Contributor
Shape 1
View profile
jeff_bloomer
Level 7

31-07-2018

I would have to say the transition from the admin console to manage group permissions in Adobe Analytics has taken a significant step DOWN.  The UI on Adobe Analytics, while clunky in its performance, at least gave us the ability to quickly interact with and understand the context for what choices were related to certain functionalities.  There is nothing intuitive in the choices provided in the newer interface, and worse, any new user to administrating user access will have no clue what certain choices relate to in the product.

Which is easier to understand, Screen A or Screen B?

Screen A:

1539201_pastedImage_0.png

Screen B:

1539221_pastedImage_1.png

PLEASE update the interface in Screen B, which is the current configuration of the Admin Console to help us manage our associates' access more efficiently.

  1. Please provide groupings for better understanding
  2. Please provide mouse over descriptions to aid understanding
  3. Do not reset the user to the top of the list every time they add an item
  4. Do not reset the user to the top of the list every time they search and add an item

Thanks!

2 Comments

Avatar

Avatar
Boost 3
Level 2
aliskink2
Level 2

Likes

3 likes

Total Posts

11 posts

Correct reply

1 solution
Top badges earned
Boost 3
Validate 1
Boost 1
Applaud 5
Affirm 1
View profile

Avatar
Boost 3
Level 2
aliskink2
Level 2

Likes

3 likes

Total Posts

11 posts

Correct reply

1 solution
Top badges earned
Boost 3
Validate 1
Boost 1
Applaud 5
Affirm 1
View profile
aliskink2
Level 2

24-08-2018

Totally, totally agree.

Having an item called "Image" means nothing, but with a sub-heading or prefix of 'Dashboard Items' it becomes clear that it relates to the provision of 'Images' as 'Dashboard Items' and you can then make an informed decision as to whether users should have access to that option or not.

A simple prefix e.g. 'Dashboard item: Image' would do fine if it's not feasible to break the list out into sub-sections.

Avatar

Avatar
Validate 1000
Community Manager
jantzen_belliston-Adobe
Community Manager

Likes

339 likes

Total Posts

2,331 posts

Correct reply

819 solutions
Top badges earned
Validate 1000
Springboard
Validate 500
Validate 250
Validate 100
View profile

Avatar
Validate 1000
Community Manager
jantzen_belliston-Adobe
Community Manager

Likes

339 likes

Total Posts

2,331 posts

Correct reply

819 solutions
Top badges earned
Validate 1000
Springboard
Validate 500
Validate 250
Validate 100
View profile
jantzen_belliston-Adobe
Community Manager

27-10-2020

 
Status changed to: Archived