Chad
My feedback
15 results found
-
8 votesChad supported this idea ·
-
28 votesChad supported this idea ·
-
22 votesChad supported this idea ·
-
10 votesChad supported this idea ·
-
61 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
Chad 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.
Chad supported this idea · -
8 votesChad supported this idea ·
-
21 votes
An error occurred while saving the comment Chad supported this idea · -
42 votesChad supported this idea ·
An error occurred while saving the comment Chad commentedIt would also be nice if Organization Read Only role allowed for viewing of Teams.
-
455 votesChad supported this idea ·
-
15 votes
An error occurred while saving the comment Chad commentedWhat we are really looking for here is a single, consistent process for index management in Atlas. Rather than doing part of the process one way and the rest of the process another way.
An error occurred while saving the comment Chad commentedHi Andrew,
Our Change Management procedures require that any new way of implementing a change go through separate scrutiny. (i.e. testing, documentation, approvals, etc.). Since creating an index via the API would be different than creating an index via scripting the change to be run directly connected to the cluster, each process would have to go through separate Change Management approval. The same goes for index deletion. If all the index management can be done via the API, it all only needs to go through approvals once. Plus, we don't have to code something different for managing indexes. It can all be handled in one piece of functionality.Chad shared this idea · -
3 votesChad shared this idea ·
-
14 votesChad supported this idea ·
-
37 votesChad supported this idea ·
-
40 votesChad supported this idea ·
Would also like a connector for xMatters and Microsoft Teams.