Overview
By default, any user with access to a deal card can see all fields on it — including sensitive financial data like purchase price, EBITDA, and deal multiples.
Field-level permissions let admins restrict visibility and edit access at the field group level, per permission group. A restricted user sees the deal card normally — hidden fields simply don't appear.
Requirements
You must be an org admin to configure field-level permissions.
Field-level permissions apply to custom field groups in the pipeline. They do not affect individual deal fields.
How to set it up
Step 1 — Go to Permission Groups
Navigate to Settings → Pipeline Access and select the three dots next to the group you want to configure.
Step 2 — Open the Field Groups tab
Inside the permission group, select the Restrict access to deal field groups button. You'll see a list of all custom field groups in your pipeline.
Step 3 — Set visibility and edit access
For each field group, you can independently control:
Visible — whether users in this group can see the fields at all
Editable — whether users in this group can make changes
Toggle each setting on or off per field group. Changes take effect once you select save.
Step 4 — Repeat for each permission group
Configure access for each role in your org — integration team, regional managers, outside brokers, functional reviewers, etc.
Default behavior
When a new field group is created, it is hidden by default for any permission group that has field restrictions enabled. You must explicitly grant access.
This means adding new fields to your pipeline will never accidentally expose data to restricted users.
What restricted users see
Users in a restricted permission group see the deal card as normal. Field groups they don't have access to are not displayed — there are no lock icons or error messages. The experience is clean and scoped to what they need.
They retain full access to everything else on the card: tasks, documents, comments, and any field groups they've been granted access to.
AI content and field restrictions
If a user has any field-group restrictions, the following AI-generated content will not display for them:
Deal Overview — the AI-generated summary on the deal card
Deal Update suggestions — AI-recommended field updates
This is intentional. DealRoom will not surface AI content that may reference or derive from fields the user cannot see.
Users with full field access are not affected.
Common configurations
Integration team visibility Grant access to deal stage, key dates, and task status. Restrict access to financial field groups (valuation, purchase price, EBITDA).
External brokers Grant access to deal description and stage. Restrict all internal financial and notes field groups.
Regional managers Grant full visibility but restrict edit access on financial fields to prevent accidental changes.
FAQ
Does this affect which deals a user can see? No. Field-level permissions only control which fields are visible within a deal card. Deal-level access is managed separately through “Deals matching the following criteria”.
Can I grant edit access without visibility? No. Edit access requires visibility. You cannot allow a user to edit a field they cannot see.
What happens if I remove a field group restriction? The field group becomes visible to that permission group immediately. No data is changed.
Does this apply to pipeline list views? Yes. Hidden field groups will not appear as columns in pipeline list views for restricted users.
Can I set field permissions for individual users rather than groups? Not currently. Field-level permissions are configured at the permission group level. But given the way we create seats, you can create a unique permission group for a singular user.
Need help with setup?
Contact your Account Manager they can walk through the configuration for your org's specific role structure.