docs(universal parser): document editing field mappings from the UI - #15583
Merged
Conversation
The editing section was written when the only way to do it was the API. There is a screen now, so describe it: where it lives, why it opens by asking for a sample file (nothing is retained from the file the parser was created with, so the available fields have to be read from a current one), and what the impact step shows before anything is applied. Also states the permission split, which the page did not cover: editing mappings needs Universal Parser Edit, while seeing the parsers only needs View.
blakeaowens
approved these changes
Aug 10, 2026
Maffooch
approved these changes
Aug 10, 2026
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
3 participants
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.
Universal Parser field mappings can now be edited from the UI. The docs page still
described the API as the only way to do it, so this updates the section to cover both.
What the page now says:
Mappings" from the menu on the parser's row.
someone: it is not the file the parser was created with. Nothing is retained from that
one, so the available fields have to be read from a current sample. The page says so
plainly, and explains what it means when saved mappings cannot be found in the sample
you upload — they are not pre-selected, and they are dropped if you save.
presentation-only or identity-relevant, which fields are changing split by whether they
reach identity, and how many findings exist under the parser's scan type. An
identity-relevant edit requires ticking a confirmation; a presentation-only one does not,
which is what keeps the confirmation meaningful.
requires Universal Parser Edit, while seeing the parsers only requires Universal Parser
View. A user who can see your parsers cannot necessarily change how they read a file.
mappings were previously changed without being recorded, and warns that findings imported
before that change have no previous generation to match from — something a later edit
cannot recover.
The existing API instructions are unchanged; the "check before you make it" section just
notes that the UI performs the same impact call as its third step.
Docs-only change — one file, no code touched.
Validated locally with a Hugo production build pinned to the version CI uses (0.153.4
extended): 790 pages built, and the new in-page anchor resolves.