Contact Custom Field Permissions
M
Michael LaRosa
Need the Ability to Remove certain Contact Fields or at least RESTRICT certain Contact Fields or Folders from specific Users. This prevents errors with changing key information on the contact or unwanted triggering of workflows
Similar to this post:
https://ideas.gohighlevel.com/users-permissions/p/make-custom-fields-lockable-at-an-individual-level
Easiest way would be on the FOLDER directly by toggling a dropdown (multiple) of each user you want within the custom fields settings page.
Log In
J
Joe Mahallati (WiseActionMarketing.com)
Agencies need the ability to hide, lock, and control access to custom fields and folders across Contacts, Opportunities, and Smart Lists. This should include role-based permissions, conditional visibility, and API-only access, enabling a cleaner interface, protecting sensitive data, and tailoring what each user or team sees. Benefits are very much needed and would...
- Reduces clutter for large accounts and multi-team agencies.
- Protects sensitive information (human resource-related data, commissions, fees, automation data).
- Improves user experience for clients, sales, marketing, and operations.
- Enables cleaner, more organized pipelines and contact records.
NEEDED...
- Hide/Show Fields & Folders: Option to hide specific custom fields or entire folders from users or clients.
- Role-Based Access: Granular permissions by role, user, or group. Admins can view/edit all, while others see only relevant fields.
- Lock & Read-Only Fields: Fields can be made read-only or locked while remaining accessible via API.
- Conditional Visibility: Show/hide fields based on pipeline, stage, contact type, or other automation-driven conditions.
- Archive Old Fields: Move outdated fields into hidden folders to declutter UI while retaining data.
- Smart List & Column Control: Hide fields from Smart Lists and opportunity/contact views while allowing export or workflow usage.
This enhancement would streamline CRM usage for agencies, support multi-role teams, and prevent accidental edits of critical data — addressing a long-standing, widely requested improvement.
P
Pallavi Kothari
Merged in a post:
Hide certain custom fields for specific users
C
Chris Agency
Have the Ability to hide custom fields that may contain sensitive information from specific users.
M
Mike Lovelady
This is needed. We need to be able to provide view, update access at the user level to custom fields. Default can be full access, but we need to be able to restrict or even hide content at the user level.
C
Caleb Christopher
100%
There is plenty of data I don't want certain users to see.