Skip to main content

​
Org-Wide Visibility

The Data Share provides org-wide visibility into your Affinity data. Unlike the Affinity API, which enforces per-user access controls and permissions, the Data Share bypasses application-level ACLs entirely. This means that all organization data is visible to anyone with access to the share — regardless of role-based access restrictions configured within Affinity.
Grant access to the share only to users who are authorized to view all organization data. There are no per-user or per-role visibility filters applied at the share level.

​
What This Means in Practice

  • All records are included: Persons, companies, opportunities, list entries, and associations are all visible in the share regardless of Affinity-level permissions.
  • Custom field values are included: The custom_fields JSON column on entity tables contains all custom field values, including fields that may be restricted in the Affinity UI.
  • No row-level security: Data Share views expose the full dataset. If you need to restrict access, apply platform-native access controls — Snowflake row access policies or Unity Catalog table ACLs on Databricks — or control share access at the account/role level.

​
Email Subject Lines

The subject column on the emails table is NULL by default. Affinity encrypts email subject lines at the application level, so the share does not include them unless an admin opts in. To include them, an Affinity admin opens the Snowflake or Databricks configuration under Settings → Integrations and selects Include email subject lines. The setting applies to every data share the organization has. Turning it on for one Snowflake or Databricks configuration includes subjects in all of them. Subjects appear on the next refresh after the change is saved. Every email in the organization gets a new last_updated_at at that point, so an incremental pull that filters on last_updated_at picks up the subjects of older emails too. Selecting Do not include email subject lines returns the column to NULL on the next refresh.
Including subject lines removes the application-level encryption for this share. The data stays encrypted at rest and in transit.
A subject stays NULL when a participant’s privacy settings withhold it, even for an organization that opted in. If a participant hides their emails after a subject was shared, the subject returns to NULL on the next refresh and the email gets a new last_updated_at. If they show their emails again, the subject comes back the same way.