One trade blotter, nine people, nine views: how ATX AnalyticsTable applies row-level security, column masking and pseudonyms to the same data.
One trade blotter. Nine people. Nine different views.
The EMEA sales desk sees only EMEA trades. Commission is empty, traders are pseudonyms, client e-mails are masked. Risk sees every trade, with counterparties pseudonymised, so exposure can still be grouped. Internal audit sees every trade too, but commission and contacts simply aren't there. HR sees salaries. A manager sees every colleague's name, but pay only for their own department. Someone the policy doesn't name sees nothing at all.
That is row- and column-level security in ATX AnalyticsTable, and it's now in our handbook with a step-by-step training video.
What matters most to us is where it's enforced. The policy isn't a filter someone forgot to switch on in the window. The server applies it to every query, sheet, pivot, chart and export, and to the AI assistant's answers too. Nothing in the window can switch it off, and administrators aren't exempt.
In the 80-second video you'll see:
Roles and groups come from Entra ID, and the policy is a JSON file versioned with the project, so access rules get the same review as code.
Video: Row- and column-level security.
This site needs JavaScript for the full experience. Every page above is reachable without it.