Ability to administer dashboard charts shown to users or groups

[michael.pares.old]

We would like the ability to establish default or role-based configuration of a user's dashboard, so that pre-selected charts are displayed upon login and we don't have to provide instructions to each and every user about how they should set up their dashboard.

One should also be able to configure which areas are expanded or collapsed by default on a user's dashboard page.

Thanks,

Michael

[fhmurray]

I second both of these, along with the suggestion that dashboard charts can be set to be visible on login: please see my post on this at: http://forums.autodesk.com/t5/Autodesk-PLM-360-IdeaStation/Dashboard-charts-to-be-able-to-be-set-to-...

Regards,

Fiona

[nguyentru]

HI Michael, This is an interesting request. I need a little bit more details. 1. The administrator will need to set all the different views. For example if there are 10 groups, 10 setups will be require. 2. Who will determine which groups require which dashboard view for the different charts. For example if sales, you will need to activate Sales Quote, Customer, RFQ, Tasks and Projects. 3. How will you handle the scalability and maintenance. If you have 200+ users, you will need to determine each time you add a new users to know which category and what groups that belong to. 4. What if there's overlapping? Or certain individuals require additional charts, do you allow access, or the administrator will need to add the requirements. This feature request sound good, but we need to understand how to manage the roles/groups and scalability for big accounts. thanks, Trung

[michael.pares.old]

Hi Trung,

Thanks for the follow up.  What has worked for us in other software implementations is that the administrator establishes one or multiple dashboard configuration as an independent entity from the security groups.  The administrator would only be able to assign a single configuration to a user, so there would be no possible overlapping of selected charts even though the user may be in multiple security groups.  A best practice for the administrator would be to create a simple default dashboard configuration, which could be used for most users and use cases and which would make sense even if the administrator forgot to apply a configuration to specific user or was not very good at maintaing the user setups.   For a new user, if the administrator has assigned a dashboard configuration, the user's dashboard would be pre-packed with dashboard charts, but would not continue to be controlled or validated against the assigned configuration.  The user should thus be able to manipulate their dashboard as they see fit from that point forward, adding and removing charts that are most pertinent to them.  The benefit for the user and the organization is that they will not need to push out the expected or standard dashboard configuration in any other manner, such as through training, pestering emails, auditing, or setting up dashboards for each individual of the 200+ users one by one.  Additional ideas you may want to consider would be

• allowing the administrator to change which configuration is assigned to a user, which would overwrite the user's current configuration.  
• allowing the user to select a different configuration to quickly apply a new set of charts to their dashboard.
• ability to see which users are assigned to a specific configuration, in addition to seeing which configuration is assigned to a user
• ability to see which users are not assigned to a configuration

security on workspaces should take precedence and since the dashboard configuration would be independent of security, applying a configuration to a user should only pack their dashboard with the charts that are attached to workspaces that the user has access to.  

Please let me know if I have not answered all of your questions and I will be happy to make further comments.

Thanks,

Michael

[giliar.defriesperez]

Thank you for submitting your idea. The timing isn't quite right for this to be a priority for development consideration. As such, we will put this on the back-burner to revisit at a later date in the context of Modern. Please continue to comment and add your support.

Giliar Perez
Product Owner - Fusion Lifecycle
Autodesk Canada Co.

[benderk]

Thank you for submitting your idea. Have you tried the Modern Interface lately? We request that you review your idea in the context of the Modern interface. If your idea is not addressed, we invite you to create a new Idea in the context of Modern so that it can be addressed accordingly. Sincerely, Keri Bender | Global GTM Business Strategy Manager, Product Lifecycle Management