Row-level security and access

AutessaDB row-level security and column masking apply to every caller, person, agent, app or API key, with sharing levels and a row-level access log.

When agents, apps and API keys all read the same data, security has to live in the database. AutessaDB evaluates row rules, column masks and edit checks on every request, and records reads, changes and reveals of protected data.

Who works here

Table admins write roles and share tables; company admins and table admins read the access log; everyone else simply sees what their roles allow.

In one sentence each

• Row-level security · Row rules decide which rows each caller sees, with placeholders for the current user, teams, roles and app visitors, and edit checks for changes.
• Column masking and hidden columns · Per role, a column is visible, masked (fully redacted, last four, or a consistent code) or hidden, and masked columns are stored encrypted.
• Security roles · A role bundles table policies (row rule, edit check, column rules) and is assigned to people, teams, company roles, everyone, custom apps or API keys.
• Sharing and access levels · Tables start private and are shared at READ, WRITE, PUBLISH or ADMIN, with a default security role applied to everyone you share with.
• Data access log · Every read, change and reveal of protected data is logged by table and row, with a chain integrity check and filters by date and action.