Configure row-level security (RLS)
Row-level security is the rule engine that decides which rows of a subject area a given user can see. Filters are defined per role and applied automatically across every surface: Athena answers, Storyboards, AI Briefings, and the autonomous-agent actions that read from the underlying data. RLS is the foundation of the Controlled Autonomy framework — Athena's autonomous actions inherit the same data boundaries the user delegating them has.
⚠ Procedure steps below need UI capture against the staging platform. The shape is in place; the actual click-paths and screenshots are TBD.
Before you start
- A ConverSight account with the Data Administrator role.
- At least one subject area already configured (see Configure a subject area).
- A clear policy: which roles should see what slice of the data? (Typical patterns: by region, by business unit, by customer tier, by data classification.)
Steps
- Step one — what to click and what to see.
- Step two.
- Step three.
Verify
A test user with the wrong region/unit sees zero rows in the subject area. A user with the right scope sees the expected subset. The same RLS rule shows up applied in Storyboards, in Athena query results, and in the audit log of any agent reading from that data.
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| User sees all rows when they should see a filtered subset | RLS rule not assigned to the role | Re-check role assignment in Users & Roles |
| RLS rule blocks too much data | Filter expression is too restrictive or has a typo | Test the filter expression against the underlying table directly |
| Different surfaces show different filter results | Multiple subject areas with inconsistent RLS | Audit the RLS rules per subject area; consolidate where possible |
Related
- Feature: Users & Roles — the broader access framework
- Why this matters: Why ConverSight → Controlled Autonomy
- Persona: Data Analyst