Aeion BI Data Governance & RBAC
Most BI tools treat data governance as an add-on — separate licensing tier, separate admin UI, separate audit log. Looker Models, Tableau Permission Sets, Sisense Data Security all require ongoing maintenance to stay synchronized with the source system's RBAC. Aeion BI inherits governance from the underlying platform by construction. Every query runs inside your tenant's security context. Every report respects your collection-level access rules automatically. Every export logs to the platform audit trail. No parallel governance system to maintain.
Tenant Isolation by Construction
Every request to Aeion resolves a tenant (from a header, subdomain, or JWT) and an authenticated user before it reaches any BI query. That resolved identity travels with the request end to end — the BI engine never runs a query without it.
Row-Level Security
Row-level access rules are defined once, on the underlying data — not duplicated in a separate BI permission layer. A typical rule for a sales pipeline might read:
Field-Level Masking
Individual fields can be classified by sensitivity — PII, restricted, or confidential — with their own access rule independent of row-level access. A customer record might mark SSN as restricted (admins with PII clearance only), email and phone as PII (internal users only), and lifetime value as confidential (admin, CFO, VP Sales only).
Audit Trail
`
Compliance Frameworks
`
FAQ
No. Every query is automatically scoped to the requesting tenant at the database layer — there's no code path that can accidentally query across tenants.
Three layers: collection-level access rules, field-level masking for sensitive data, and aggregate-level authorization — so even a sum or average respects what each user is allowed to see.
Yes. Assign a dashboard library per role, with optional limits on chart types and date ranges for lower-privilege roles.
Yes. A view-only role flag disables saving and exporting; combine with embedded-only access to lock a user to a single dashboard.
Yes, on Pro. Configure an export policy that requires approval for classified data, with a defined approver workflow.
Tag a field's sensitivity once; BI checks the viewer's access on every read and applies the display rule — masked, redacted, or full — automatically.
Yes. Per-user query velocity and export volume are baselined, and spikes (potential scraping or exfiltration) trigger a security alert.
The embedding token binds the session to one tenant; every dashboard view and query within it inherits that tenant's scope and the viewing user's RBAC.
Starter: 30 days. Pro: 1 year, configurable up to 7 years for compliance-heavy tenants.
Yes — Splunk, Datadog, Elastic, or a custom destination, with configurable event format.
No. PHI/PII fields are stripped before any prompt is sent to the AI provider — it works from anonymized aggregates only.
Authorization happens at the metric level — an aggregate is only shown if the viewer has read access to a sufficient share of the underlying rows.