Customization per user
There is any plan to develop customization per user?
Define what dashboard a user enter by default - for each user.
Define what ui element a user can visualize - for each user.
Define what features a user can use - for each user.
In other word, a servers.json, with one stanza per user.
Currently, if I modify features or ui element, the same happens both for admin, and any other user.
I think it is obvious having in a working business context, different level of needs about type of access and services provided.
-
Thank you, and just for the sake of argument, and describing my point of view, I'd say that for each medium-to-high complex and organized company, there are different types of end-user:
- No tech and operative people (Those who takes action on the company ERP based on Immerse useful aggregations and info, or no tech managers able to exploit the features of HeavyIQ).
- Low level tech people (Those who could modify dashboards, BI attendant, with limited DB and dashboards permission).
- Medium level tech people (Able to operate on user, permission, checking data, build dashboards)
- SYSAdmins (full control over HeavyAI ecosystem, power user python notebook with ML, ETL and scripting for data ingesting, and all)
One single definition in the servers.json does not adapt to all the scenarios, and could lead to a user that inappropriately modify some dashboards, or touch tables or confguration, or, on the other side, tech user not able to use part of the ecosystem, depending on what is defined as hidden or visibile in the servers.json conf.
Please sign in to leave a comment.
Comments
2 comments