[DOCS-16421] [Server] Create a specific doc page/blog for "security views" which are hidden as a example in $setIntersection Created: 04/Oct/23 Updated: 30/Oct/23 Resolved: 05/Oct/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Robert Jones | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | proactive | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 17 weeks, 6 days ago |
| Description |
|
We have a decent document for creating security views using $$USER_ROLES to dynamically determine if a user is authorized to access certain documents/fields in a collection. I'm referring to this:
Unfortunately, this seems to only appear as an example in the use of $setIntersection and I would think that security views using $$USER_ROLES deserves its own document detailing this capability. |
| Comments |
| Comment by Sarah Olson [ 05/Oct/23 ] |
|
We have a fair bit of documentation on this here: https://www.mongodb.com/docs/manual/core/views/create-view/#retrieve-budget-documents-for-roles-granted-to-the-current-user It's also linked to here: https://www.mongodb.com/docs/manual/reference/aggregation-variables/#mongodb-variable-variable.USER_ROLES Based on this I'm going to close this ticket as WONT DO. Please give me or ashley.brown@mongodb.com a shout if you have any concerns!
|