Add more specific roles for Charts
It will be great to have more specific roles to Charts totally separate from other Altas roles.
Currently if you want to have one team member allowed to configure charts,
you have to give him access (at least read only) to everything outside of Charts space, as cluster and database informations or even Stitch configuration.
nicolas
shared this idea
Hi everyone,
We have some exciting news for you all, we are commencing work on Charts specific roles this month!
We will be launching the following x2 new roles:
Charts Author - these users can view/create charts and dashboards in Charts as long as they have access to the underlying data sources.
Charts Viewer - these users can view charts and dashboards in Charts as long as they have access to the underlying data sources
Both roles will have reduced permissions at the Project level and will have access to only Charts resources.
This is expected to go live in Q1 of next year.
Thanks
Emma
-
Rune
commented
Thanks for addressing this. Now, lets assume I'm a Charts Author and I want to create a chart across multiple collections (using $lookup).. As we all know $lookup is for whatever reason not supported in Charts. Will the new Charts Author be able to create new DB Views or would I still be required to manage view creation/deletion separately?
-
AdminEmma
(Admin, MongoDB)
commented
Hi everyone,
We have some exciting news for you all, we are commencing work on Charts specific roles this month!
We will be launching the following x2 new roles:
Charts Author - these users can view/create charts and dashboards in Charts as long as they have access to the underlying data sources.
Charts Viewer - these users can view charts and dashboards in Charts as long as they have access to the underlying data sourcesBoth roles will have reduced permissions at the Project level and will have access to only Charts resources.
This is expected to go live in Q1 of next year.
Thanks
Emma -
Systems
commented
It is confusing for users to have to log into Atlas, and see a main "Admin" type of Atlas interface, and then have to know to navigate to Charts to see what they need. They should not see Atlas Admin stuff, and only see the Charts area.
Granular controls for other things like "Export/Save", or "Duplicate", or "Refresh", etc. would be prudent.
-
Rune
commented
Agree. It would be great with at least two Charts Roles:
* Charts Viewer - this user should _only_ be able to see Charts, all other items inside the Atlas Console should be hidden/restricted. This user should also not be able to configure Chart Scheduling.
* Charts Admin - this user should _only_ be able to Modify Charts, all other items inside the Atlas Console should be hidden/restricted. -
denys [not provided]
commented
I fully support the idea of creating more granular roles for chart configuration that are separate from other Atlas roles. This would allow us to address your specific use case effectively. With these new roles, we can enable users to configure charts for their respective branches without granting them access to cluster and database information, which is crucial for maintaining data security and integrity.
By implementing these more specific roles, we can ensure that each branch's data remains confidential and secure, with the ability for branch-specific users to configure charts for their own data without affecting other branches. This approach aligns with best practices for data access control and will provide a more robust and secure environment for our organization.
-
Alistair
commented
Could not agree more. I wanted to use this to share specific data and filters directly from our database to other people in the company however there is no way I will let anyone in the oranisation see the other details that I have to give them read only access to. i.e dates and times of backups, configuration of the cluster, etc, etc, etc
-
Ola
commented
I would like to report this feature as well, would be great if we could differentiate and give access for Charts only for people who should have no access to App Service/Atlas itself
-
Otto
commented
Agreed, a user role that gives access to Charts only would be useful. Another solution would be to segregate the Charts access management from Organization Access Manager entirely.