◆
◆
SharePoint◆◆◆SharePoint◆◆◆SharePoint◆◆◆SharePoint◆◆◆SharePoint◆Faster, safer, more transparent data access across the entire organization.
Faster access
Provision Databricks, Snowflake and SharePoint grants from one place. Requests go out in minutes, not a week of tickets.
Standardized by default
Everything in one place. No more orphaned grants hiding in a platform nobody audits.
Transparent to every team
Engineers, data owners and auditors see the same picture — who has access to what, and why.
Anomalies, caught early
Behavioural baselines highlight abnormal access and malicious patterns before they become an incident.
What UDAL actually does on day one.
Add or remove grants the way that fits the job. Three paths, one permission model — all captured in the same audit log.
Request-based
Two modes of operation depending on whether UDAL sits inline with every call or configures permissions upfront.
Used for quick action to decide if a person is allowed to perform an action on a API - request goes through UDAL.
UDAL updates policies when a change occurs. Not intercepting every call — UDAL sits outside the Policy Decision Point.
Policy-based
Define rules once — role, team, or attribute-based — and UDAL enforces them across every connected platform.
What UDAL is not.
UDAL is an authorization and audit layer. It sits alongside the tools you already run — it doesn't replace them.
A data catalog
UDAL doesn't describe or document your data — point it at your catalog and it will honour the tags you already maintain.
→ Use Unity Catalog, Collibra, or your own.An identity provider
UDAL doesn't manage your users or groups. It connects to Okta, Azure AD, or whatever you already have.
→ Bring your existing SSO/IdP.An ETL tool
UDAL doesn't move or transform your data. It governs who can reach it, not how it gets there.
→ Keep your dbt, Airflow, Fivetran, Spark.