feat: add MROS reporting module#3606
Merged
TaprootFreak merged 3 commits intodevelopfrom Apr 23, 2026
Merged
Conversation
Adds MROS (Meldestelle für Geldwäscherei) module for compliance dashboard. Tracks suspicious activity reports linked to UserData with status enum (Draft, Submitted, Confirmed, Closed), submission date, authority reference and case manager. Exposes admin-only CRUD endpoints.
Switches MrosController guards from ADMIN to COMPLIANCE so compliance operators can use the reporting dashboard. ADMIN and SUPER_ADMIN keep access via the additional roles chain.
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
1 participant
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.
Summary
Mrosentity undersubdomains/supporting/mros/for compliance dashboardUserDatastatus(enum: Draft/Submitted/Confirmed/Closed),submissionDate,authorityReference,caseManager(free text)POST /mros,PUT /mros/:id,GET /mros,GET /mros/:idmrostable with FK onuser_data(id)Notes
PK_mros,FK_mros_userData, …) because it was hand-written. If preferred, regenerate vianpm run migration:generateto get the hash-based names consistent with the auto-generated repo style.Test plan
mrostable + FK created/mroswith valid payload → 201, row persistedstatusvalue → 400/mros/:idupdatingstatus→ row updated/mros→ returns list withuserDatarelation/mros/:id→ returns single entry, 404 if missing