Manage sensitive data
Control who sees your data in Soda Cloud, where Soda runs its queries, and which data leaves your data warehouse.
This guide shows the Soda Cloud settings that limit the exposure of sensitive data. Soda reads your data to verify contracts, profile columns, and collect failed rows. Each of these leaves a trace in Soda Cloud or in your warehouse, and each has a setting that controls who can see it or turns it off.
Most of these settings are in Settings > Organization and require the Manage organization settings global permission.
Data exposure and controls
Access to datasets and results
Datasets, checks, check results, and incidents, visible to users of the organization
Access to Soda Cloud
Sign-in from any network, with accounts managed in Soda Cloud
Queries and credentials
The Soda Runner that queries your data, and the data source credentials it uses
Roles and permissions
Soda Cloud grants access through roles at three levels:
Global roles set what a user can do across the organization, such as create data sources or manage organization settings.
Data source roles set who can see a data source and everything onboarded from it. A user without a role on a data source sees none of its datasets, checks, or results.
Dataset roles set what a user can do on one dataset. Users get a dataset role through the dataset's responsibilities.
Manage roles in Settings > Organization > Roles, on the Global Roles, Data Source Roles, and Dataset Roles tabs.
Two dataset permissions control access to data itself:
Access dataset profiling and samples
Profiling results of the dataset
Access failed row samples for checks
Failed row samples of the dataset's checks
The default Viewer dataset role includes both. For users who only need check results, create a custom dataset role without these two permissions with Add Dataset Role, and assign it on the dataset's Settings tab, under Responsibilities. The same tab lists your own permissions on the dataset under My permissions.
New datasets get the assignments in the Responsibilities panel of the Dataset Roles tab, under For newly onboarded Datasets. When the Everyone group has an assignment there, every user gets that role on each new dataset. To narrow this, give the Everyone group a role with fewer permissions, or remove the assignment.

For the permissions of each role and how to create custom roles, see Global and dataset roles.
Sign-in and network access
Single sign-on (SSO): Connect Soda Cloud to your SAML 2.0 identity provider, so users sign in with their company account and lose access when your IT team revokes it. See User and user group management with SSO.
SCIM provisioning: Let Microsoft Entra ID create and remove Soda Cloud users and user groups. SCIM is an opt-in feature on Enterprise plans. See User provisioning with SCIM.
IP allowlist: Accept requests to Soda Cloud only from a list of IP addresses or CIDR ranges, such as your corporate network or VPN. Requests from other addresses are blocked before authentication. In Settings > Organization > General, under IP allowlist, check Restrict access to specific IP addresses and add the addresses. See IP Allowlist.
Soda Runner and credentials
A Soda Runner connects to your data sources and runs the queries for contract verifications, profiling, and metric monitoring. Choose where it runs:
Soda-hosted Runner: Soda runs it in Soda's infrastructure. To reach your data, it needs network access to your data source, through an allowlist of its IP address.
Self-hosted Runner: You deploy it with Helm in your own Kubernetes cluster, so queries run inside your network. The runner reads data source credentials from Kubernetes Secrets, which you can back with an external secrets manager. See Deploy a Soda Runner.
A self-hosted runner sends check names, metrics, and aggregated results to Soda Cloud. It sends no row-level data unless failed row samples are on. See Data flows between Soda & user.
Once a self-hosted runner is in place, turn off the Soda-hosted Runner so that no scan runs outside your network. In Settings > Organization > General, uncheck Enable Soda-hosted Runner. Settings > Runners lists the runners of your organization. See Enable or disable the Soda-hosted Runner.
For data sources that you connect in Soda Cloud, store passwords, tokens, and keys as secrets instead of typing them into the data source configuration. Soda Cloud stores secrets encrypted, and the configuration keeps only a ${secret.NAME} placeholder. A credential typed as a literal value stays in the configuration, where users who can manage the data source settings can read it.
Add secrets with New Secret in Settings > Secrets, then reference them in the connection configuration. The list shows each secret's name and dates, never its value.

The Secrets section of Settings > Organization > General has an Enable Secrets option, which must be checked to use secrets.
To keep data source connections out of Soda Cloud entirely, verify contracts with the Soda Python libraries in your own pipelines. Their data source connections are configured in your environment. See Deployment options.
Dataset selection
Soda checks, profiles, and monitors only the datasets you onboard. When you onboard datasets from a data source, choose one of two selection strategies:
Manual: Pick the datasets one by one.
Rules-based: Add rules that include or exclude datasets by name, for example to leave out every table whose name starts with
pii_. The rules also apply to datasets created later.
Soda still runs a discovery scan on the data source once a day, which reads the names of its tables and schemas.
Profiling
Profiling computes statistics for each column of a dataset and shows them in Soda Cloud: distinct and missing counts, minimum, maximum, and mean, a histogram, frequent values, and extreme values. Frequent and extreme values come from the data itself, so on a column with personal data they show that data.
Turn profiling off at one of two levels:
Organization: In Settings > Organization > General, under Profiling, uncheck Allow Soda to collect column profile information. Soda then collects no profiling information for any dataset. Check and monitor results and the dataset schema are still processed.
Dataset: Open the dataset, go to the Profiling tab, click Update Profiling Configuration, and turn profiling off.

Profiling settings apply to the whole dataset, not to single columns. To hide profiling results from some users instead, use a dataset role without Access dataset profiling and samples.
See Profiling.
Failed rows
When a check fails, Soda can store the rows that failed it. Two settings decide where they go.
Diagnostics Warehouse
Diagnostics Warehouse stores failed rows in a schema of your own data warehouse, so they don't leave it. Soda Cloud shows a message on the check's Failed Rows tab that says where the rows are, and can show the failed rows query and a button that links to your own tool.
Set it up per data source with Edit Diagnostics Warehouse. Then, for each dataset, open the dataset's Settings tab and, under Diagnostics Warehouse Configuration, turn on Collect failed rows and choose a Storage strategy:
Store full failed rows keeps the whole rows.
A unique keys strategy keeps only the keys of the failed rows. To see the rows, run the failed rows query from the check's Failed Rows tab in your warehouse.
Under Guardrails, Protect against data floods and Limit failed row storage cap the number of rows that one check can store. AI features have no access to failed rows in Diagnostics Warehouse.

Failed row samples
Failed row samples store a subset of the failed rows in Soda Cloud, to show them on the check's Failed Rows tab. They are off until the Soda support team enables them for your organization. Once enabled, allow them per data source in Edit Diagnostics Warehouse > Failed Row Samples with Allow sending failed row samples to Soda Cloud, and override the setting per dataset under Diagnostics Warehouse Configuration on the dataset's Settings tab. The default sample size is 100 rows.
Failed row settings apply to a data source or a dataset, not to single columns. Leave failed row samples off for datasets with sensitive columns, and use a dataset role without Access failed row samples for checks for users who don't need them.
See Failed row samples.
Soda AI
Soda AI features send requests to a model provider, currently OpenAI. They don't send row-level data, with one exception: Contract Autopilot can send a sample of up to 100 rows to improve the contracts it generates. Soda does not use your data, metadata, or prompts to train AI models.
Admins control AI features in Settings > Organization > General:
On the Organization tab, under Soda AI Features, check or uncheck Enable Soda AI Agent, Enable Contract Copilot powered by OpenAI, and Enable Contract Autopilot powered by OpenAI.
For Contract Autopilot, leave Send row-level data to improve the quality of your auto-generated data contract unchecked to send dataset metadata and computed profiling metrics only.
On the AI tab, use Add provider to add your own OpenAI account (bring your own key), and choose it for each feature under Feature Configuration. Requests then go to your OpenAI project, under your retention settings.

Next steps
Review who holds which role on your most sensitive datasets in their responsibilities. See Dataset attributes and responsibilities.
Investigate failed rows inside your warehouse with Diagnostics Warehouse.
Last updated
Was this helpful?
