Document view-only access pattern for model-driven apps #10798
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Dataverse Share dialog only displays security roles with Customize/Admin privileges by design. View-only roles like "Power Platform User SR" don't appear, causing confusion when granting read access to CoE apps.
Changes
New FAQ:
CenterofExcellenceResources/FAQ-GrantingAccessToCoEApps.mdUpdated README files: Added FAQ links under Administration section
Issue response template: Added reusable response for this common question
Correct Pattern
Instead of using the Share dialog (which won't show read-only roles):
The Share dialog is for app visibility; actual permissions are security role-based.
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.