Core Web App

Anonymous

Please review board options and verify that your request doesn't already exist. Thank you!
Field-level Data anonymization for API and MCP responses (asset fields + KB articles)
Summary: Add the ability to mark data as "anonymized" so that the real value is replaced with a configurable placeholder whenever the content is retrieved via the API or the Hudu MCP server, while the actual value remains visible in the Hudu web UI as normal. This should work in two places: as a per-field setting in Asset Layouts, and as an inline syntax in Knowledge Base articles. Part 1; Asset Layouts: In the Asset Layout editor, each field gets a new boolean setting, e.g. "Anonymize via API/MCP". When enabled, an "Anonymized value" template can be defined per field, for example: - Real value: "Anders Andersson" → API/MCP returns: "[firstname lastname]" - Real value: " anders.andersson@company.se " → API/MCP returns: "[email]" The placeholder text is fully configurable per field in the layout. Part 2; Knowledge Base articles: KB articles are free text, so a per-field toggle doesn't work there. Instead, support an inline markup syntax that pairs the real value with its placeholder, for example: ((Anders Andersson)[firstname + lastname]) Behavior: In the Hudu web UI, the article renders the real value: "Anders Andersson" Via API/MCP, the article body returns the placeholder instead: "[firstname + lastname]" This lets us write articles naturally (e.g. "Contact ((Anders Andersson)[firstname + lastname]) at ((070-123 45 67)[phone]) for access requests") while keeping personal data out of API/MCP responses. The exact syntax is open for discussion — the key is one expression containing both the displayed value and the masked replacement. API Keys are toggled with data anonymization: true/false Optional enhancements: A scope setting (anonymize for MCP only, API only, or both), since AI/MCP use cases often have stricter requirements than internal API integrations. A permission or API-key-level flag to allow specific trusted integrations to receive unmasked data. Why this matters: AI/MCP integrations: With the Hudu MCP server, asset and article data can now be passed to LLMs. We want to use this for troubleshooting and automation without exposing personal data (names, emails, phone numbers) to AI models. GDPR compliance: As an MSP operating in the EU, we must apply data minimization. Would be HUGE for our AI-journey. Maps in to AIUC-1 Controls - Domain A Expected outcome: We can flag sensitive data once — per field in layouts, or inline in KB articles — and every API/MCP consumer automatically receives masked values, while technicians working in the Hudu UI still see the real data they need.
0
·
UI & usability
Load More