Short answer
Field-level security controls which users can see or edit specific fields on a record, such as tax IDs, commissions or account numbers, even when they can see the record itself. Salesforce sets it through profiles and permission sets; HubSpot uses property permissions on Enterprise editions.
Field-Level Security explained
Record access and field access are separate. A client service rep may need to see a client's record but not their full Social Security number; an advisor may need production figures that operations should not see. Field-level security enforces this everywhere the field appears, including reports, list views and the API.
Restricting fields is a simple, auditable control for need-to-know access in regulated firms.
How Vantage Point helps: we design field-level access for sensitive data and test it across reports, integrations and AI connectors.
Frequently asked questions
Can HubSpot restrict access to specific properties?
Yes. HubSpot Enterprise editions support field-level permissions on properties, so only selected teams can view or edit them.
Does field-level security apply to the API?
Yes. In Salesforce, a user or integration cannot read or write a field through the API if field-level security hides it from them.