Rune
My feedback
16 results found
-
36 votesRune
supported this idea
·
-
6 votesRune
supported this idea
·
An error occurred while saving the comment -
21 votesRune
supported this idea
·
-
2 votesRune
shared this idea
·
-
7 votesRune
supported this idea
·
-
66 votes
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
An error occurred while saving the comment 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?
An error occurred while saving the comment 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.Rune
supported this idea
·
-
49 votesRune
supported this idea
·
-
24 votesRune
supported this idea
·
-
491 votesRune
supported this idea
·
-
15 votes
Thanks for the suggestion Thomas – we are planning on implementing this later this year.
Rune
supported this idea
·
-
15 votes
Thanks for the feedback Eric. Your scenario is very valid and we’d like to support this. We’d like to integrate this into the Atlas permissions model properly, rather than make it a Charts-only thing, so it may take us a little while to sort this out.
Rune
supported this idea
·
-
39 votes
We are planning to start work on a Dark mode in Charts in the first half of next year.
Rune
supported this idea
·
-
4 votesRune
supported this idea
·
-
96 votesRune
supported this idea
·
-
38 votesRune
supported this idea
·
-
10 votesRune
supported this idea
·
I agree with this suggestion. Ideally, I’d like to see granular permission controls at the individual dashboard level. For instance, in our production database environment, we use Charts with the following policy:
* A small group (Chart Authors) has permission to explore data and create charts.
* Most developers and managers are restricted to Viewer roles, with exporting disabled.
Certain charts, such as those displaying detailed customer information, should always have export functionality blocked to protect sensitive data. However, other charts—like those showing general statistics, graphs, or counts with no sensitive details—could benefit from allowing Viewer roles to export. This level of flexibility would greatly enhance usability while maintaining security.