[DOCS-6312] For custom roles, add information or examples for privileges not available in UI Created: 01/Oct/15 Updated: 11/Jan/17 Resolved: 27/Jul/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Cloud Manager, Ops Manager |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Roger McCoy (Inactive) | Assignee: | Bob Grabar |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 7 years, 29 weeks ago |
| Epic Link: | docs-users-roles |
| Description |
|
When creating a custom role, some privileges are not explicitly available in the UI, for example listCollections, listIndexes. As these privileges may be commonly needed for "read-only" roles, an example or more information would be helpful showing how to inherit them from read@db_name. |
| Comments |
| Comment by Emily Hall [ 27/Jul/16 ] |
|
Closed for housekeeping on 7/27/2016 by Emily Hall. |