Repository navigation
Fix indirect permission letters: ri is indirect read plus insert - #199
Merged
Jesper Schulz-Wedde (JesperSchulz) merged 1 commit intoSep 29, 2026
Conversation
…access Each letter of a permission value is one permission, so `ri` is indirect read plus indirect insert. The good sample granted a read-only "Report Runner" role indirect insert on G/L Entry. Use `r` in the sample, name the lowercase letters in Best Practice, replace the ri/ii/mi/di keywords and cite the Microsoft Learn pages that define the letters. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Nikolaj Jakobi Nøttrup (Nikolaj1407)
requested review from
Aleyenda,
Wael (WaelAbuSeada),
Darrick (darjoo) and
Bugsy (pchriste-microsoft-com)
as code owners
September 26, 2026 20:47
Contributor
Author
|
@microsoft-github-policy-service agree company="Allnet Nordic A/S" |
Jesper Schulz-Wedde (JesperSchulz)
approved these changes
Sep 28, 2026
Jesper Schulz-Wedde (JesperSchulz)
left a comment
Contributor
There was a problem hiding this comment.
Reviewed f31552f5dba1082ab1e0fe78852c85c3825cec24. The correction is sound: r grants indirect read, while ri grants indirect read plus indirect insert. The article and good sample now agree with Business Central permission-letter semantics, and no related erroneous guidance remains.
Jesper Schulz-Wedde (JesperSchulz)
merged commit Sep 29, 2026
130d5de
into
microsoft:main
7 checks passed
4 of 5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What is wrong
microsoft/knowledge/security/indirect-permissions-for-elevated-access.mdpresentsri,ii,mianddias the indirect-permission tokens (in Best Practice and in the keywords), and its good sample gives a read-only "Report Runner" role:Permissions = tabledata "G/L Entry" = ri;Every letter of a permission value is one permission:
R/rread,I/iinsert,M/mmodify,D/ddelete, uppercase for direct and lowercase for indirect (Permissions property, Permissions on database objects). Soriis indirect read plus indirect insert,iirepeats insert, andmianddieach add indirect insert. The good sample therefore grants a read-only role indirect insert on G/L Entry, which is the kind of over-grant the article warns against. An author or reviewer following the article would reproduce it.The change
r,i,m,d, shows the read-only grant= r, and states that each letter is one permission.lowercasereplacesri, ii, mi, di.tabledata "G/L Entry" = r;The letters have meant the same thing since runtime 1.0, so this applies to all BC versions. The security domain owns it: this corrects the existing security article in place.
Checks
On this branch:
validate_frontmatter.py(0 errors, 0 warnings),Test-KnowledgeIndex.ps1,Test-SkillIndex.ps1,Test-ReviewFixtures.ps1(108 cases, 20 leaf domains) andTest-ReviewContract.ps1all pass.🤖 Generated with Claude Code