Is your feature request related to a problem? Please describe.
We are deploying a separate instance of Open Metadata to be shared with external customers. While setting up roles & policies to fully isolate the metadata from the instance, any changes performed to a data asset gets tracked in the Version History of data asset (glossary, glossary term, table, schema, ingestion connector etc).
Due to GDPR requirements, internal employee names cannot be shared with customers outside the organization.
Describe the solution you'd like
a way to fully isolate/mask usernames from Version History window(e.g. ability to choose to show user id instead of username).
Also, same username gets displayed when a change is done in a description of a data asset:
confirmed with support team below:
1.13.1, there is no native way to hide the Version History view or the person attributed to a change through policies, roles, or personas, and setting a display name does not mask it, which matches what you are seeing. The clean fix is a product change: a way to hide version history, or mask the change author, for external-facing use.
Describe alternatives you've considered
We have tried personas, roles, policies, editing Display name of the Admin users.
Partially works when Editing Display Name, but if you hover over Display Name in Version history, you get also the username:
Additional context
fullfil GDPR requirements
Pre-submission checklist
Is your feature request related to a problem? Please describe.
We are deploying a separate instance of Open Metadata to be shared with external customers. While setting up roles & policies to fully isolate the metadata from the instance, any changes performed to a data asset gets tracked in the Version History of data asset (glossary, glossary term, table, schema, ingestion connector etc).
Due to GDPR requirements, internal employee names cannot be shared with customers outside the organization.
Describe the solution you'd like
a way to fully isolate/mask usernames from Version History window(e.g. ability to choose to show user id instead of username).
Also, same username gets displayed when a change is done in a description of a data asset:
confirmed with support team below:
1.13.1, there is no native way to hide the Version History view or the person attributed to a change through policies, roles, or personas, and setting a display name does not mask it, which matches what you are seeing. The clean fix is a product change: a way to hide version history, or mask the change author, for external-facing use.
Describe alternatives you've considered
We have tried personas, roles, policies, editing Display name of the Admin users.
Partially works when Editing Display Name, but if you hover over Display Name in Version history, you get also the username:
Additional context
fullfil GDPR requirements
Pre-submission checklist