Data permissions

Permission in data systems has traditionally been understood as access control: who can read or write a file or database record. Data permissions in the governance sense go further. They encode not just who can access data, but what that data can be used for. A record might be accessible to a system without being permitted for a specific use case.

Data permissions operationalize the answer to the question enterprises face with every data initiative: 'Can I use this data?' The answer depends on:

• How the data was collected.
• What consent or legal basis applies.
• Whether the intended use is compatible with that basis.
• Whether any restrictions, contractual, regulatory, or preference-based, limit the permitted uses.

As organizations build AI systems, launch personalization programs, and share data across internal teams and external partners, data permissions must be encoded at the data layer, not just documented in a policy. A permission recorded in a spreadsheet has no effect on a data pipeline that doesn't check it. Permissions embedded directly into the systems and workflows that process data are the only scalable approach to governing data use at enterprise scale.