Field Level Governance for Accounts and Prospects

Created by Somak Bhattacharyya, Modified on Thu, 11 Jun at 4:38 AM by Aye Myat

Objective

Field Level Governance (FLG) gives Outreach admins control over visibility and edit permissions on individual fields inside Prospect and Account records.

Applies To

Outreach Admins
Outreach Sellers

Before You Begin

Make sure you understand how to assign and manage Governance Profiles.

Overview

Field Level Governance is an enhancement to the existing Role-Based Access Control (RBAC) Profile-based governance system. It provides granular control over data visibility (view, edit, or hide) at the field level, while RBAC continues to control access to the overall Prospect and Account record.

Because FLG is implemented using Profiles, admins retain full governance control over end user workflows, data, and platform hygiene. Different roles — like SDRs, AEs, and CSMs — can be given access to the fields relevant to their workflow and restricted from others.

This is also an extension of the previous FLG for opportunity amount. Existing customers using FLG to govern that field will continue to be supported.

Always Viewable Fields

Some fields are designated as Always Viewable. For these fields, view access is always enabled and cannot be disabled in FLG configuration. Edit permissions remain configurable where the field is editable. The admin UI displays disabled controls for the view permission on these fields, along with explanatory messaging.

Setup

Log in to Outreach as an Admin.
Click Administration > User management > Access control.
Select a Profile and navigate to the Account or Prospect section.
Click Manage field permissions. The FLG Management dialog will open.

FLG Management Dialog

The FLG Management dialog allows you to set per-field permissions. You can scroll or search for any field you want to configure. Each field supports the following permissions:

Permission	End user UI	Checkboxes checked
None	Field is hidden from the UI	Both unchecked
Can view	Field is read-only in the UI	Only Can view checked
Can edit	Field is editable in the UI	Both checked

Once you have finished making changes, click Save changes. FLG is enforced immediately for users assigned to that Profile.

RBAC vs. FLG

FLG enforces per-field permissions. For it to apply, the user must already have access to the underlying record (Account or Prospect) through their Profile. Set up Profile-based RBAC access first, then configure FLG on those record types.

Outreach recommends periodic permissions reviews, especially after updating RBAC or FLG settings, to ensure end users have the access they need.

Interplay with Team Selling

FLG governs permissions through Profiles only. Customers using Team Selling (Account Teams or Multi-User Assignment) should implement FLG using Profiles, the same way RBAC-based permissions are managed today.

FLG for Required Fields

FLG cannot be applied to fields marked as Required. If a field is marked Required after FLG has already been configured, admins must ensure that field has both view and edit permissions across all user Profiles before making it Required. Users without edit permissions will be unable to create or update records if this is not done.

If a field is no longer marked Required after FLG has been set up, the field's permission is automatically reset to reflect the RBAC permission of the parent object.

End User Experience

FLG Permission	End user UI
None	Field is hidden from the UI. Any sorts or filters using that field are removed from the UI.
Can view	Field is read-only. Inline editing is disabled. Users can continue using filters and sorters that reference the field.
Can edit	Field is editable. Inline editing is disabled. Users can continue using filters and sorters that reference the field.

Frequently Asked Questions

What levels of permission can I control per field?

Admins can set None, View, or Edit permissions for fields on any supported object. None hides the field. View means read-only access. Edit allows end users to modify the field.

Can I configure Prospect or Account field permissions differently for different users?

Yes. Fields are governed per Profile. Create different Profiles with the required field permissions and assign them to the appropriate users.

Which fields are available to govern using Field Level Governance?

Most fields are supported. This release expands coverage to previously excluded fields, including:

Prospect: opt-out and compliance fields, persona and stage fields, tags, ownership and assignment fields, identity and contact information, and account linkage fields.
Account: ownership and assignment fields, the Name field, and tags.

To see the full list, go to any Profile, scroll to Account or Prospect, and click Manage field permissions. The FLG dialog lists all supported fields for that object.

What does "Always Viewable" mean?

Always Viewable fields cannot be hidden in FLG configuration. View access is always enabled for these fields. Edit permissions remain configurable where the field is editable.

Why can't I disable view access on some fields?

These fields are designated as Always Viewable. The admin UI displays disabled controls for the view permission on these fields, along with an explanation of the restriction.

Can I still restrict edits on Always Viewable fields?

Yes. View access is enforced, but edit access remains configurable for editable fields.

Will existing FLG configurations change automatically?

No. Existing configurations remain unchanged. Newly supported fields become available for governance configuration but are not automatically configured.

Does this change how fields behave elsewhere in the product?

No. This release only changes governance capabilities. It does not affect field calculations, synchronization behavior, compliance logic, or product workflows.

Does this affect my existing Profile permissions?

No. FLG is fully backward compatible. Existing Profiles continue to work, and FLG picks up relevant field permissions from existing RBAC permissions unchanged.

Is this a paid feature?

No. Field Level Governance is available to all customers.

Is this feature opt-in or enforced by default?

Opt-in. Admins must configure FLG permissions in Profiles before FLG is enforced for end users.

How does this affect Required fields set up for Prospects and Accounts?

FLG cannot be applied to fields marked as Required. All users with record create and edit permissions must have both view and edit permissions on those fields.

Will APIs respect FLG?

Yes. APIs respect Profile permissions. If you are using APIs to manage Accounts and Prospects, FLG permissions will apply.

Can I sync with Salesforce Field Level Security?

In this release, admins manage permissions using Outreach Profile permissions. Salesforce Field Level Security sync is not supported.

Are there any limitations I should be aware of?

FLG is supported inside Outreach-controlled experiences and APIs only. Fields may still be visible through customized UI that Outreach does not control, integration endpoints, or plugins. FLG is also not enforced in scenarios where a field is used for backend calculations such as Forecasting or Pipeline Summaries.

For Opportunity records, only the amount field is supported in this release.