Field Groups & Layouts
Some Fields Aren’t for Everyone. Close the Section Once.CRM field-level security set per section, not one field at a time.
Put related custom fields in a section, then decide for each permission profile who can view or edit what is in it. Close one section instead of a hundred fields, one by one. And keep a section off the list view while it can still be edited on the record.
- View and edit per profile
- Open until you close it
- Included on every plan
How it works
- Create a sectionName it and add your custom fields
- Set access per profileView, edit or delete, on the whole section
- Profile without accessValues kept off the record and the listProfile with accessSees and edits as usual
Private Values Stay Private. Setup Stays Simple.
Set access once on the section for each profile, and every field in it follows.
A withheld section keeps its values off the record page and out of the list for that profile.
With no entry, a section is fully open. You only close what needs closing.
Keep a section off the list view and still edit it on the record, with one switch.
Field Access, Set in Three Steps.
Create Your Sections
Name a section and move custom fields into it. Each field sits in one section, or in none.
Set Access per Profile
For each permission profile, choose view, edit or delete on the section. No entry means full access.
Choose Where It Shows
Keep a section on the record but off the list view, so reps see it when they open a lead.
Three Levels of Access, Set per Section.
Set them for each permission profile. A section with no entry stays open.
No entry means full access. Fields outside any section stay open too.
The profile can read the values but not change them.
No view, so the values are kept off the record and out of the list for that profile.
What Is CRM Field-Level Security, and How Do Field Groups Do It?
CRM field-level security controls who can see or change particular fields on a record, so a rep can work a lead without seeing, say, its income details. In Adoptiv you set it per field group: a section of custom fields that each permission profile can view, edit or not see at all.
Field groups are sections you draw yourself, and a new workspace starts with none. Each custom field sits in one section or in none, and a field outside every section stays open. Built-in lead fields aren’t grouped this way, so field-level security covers the custom fields you add.
Access starts open. With no entry, a profile has full access to a section, and you restrict access to sensitive fields by closing the section once for the profiles that shouldn’t have it, instead of hiding fields from users one at a time. Profiles and their field permissions are set up under roles and permissions.
A withheld section keeps its values off the record and out of the list. The field names and their options aren’t secret, so name sections plainly. Sections also shape your CRM record layout: keep one off the list view and still edit it on the record, and reorder or recolor sections without changing who can see them. Deleting a section removes its fields and their values.
Field Permissions, Without the Busywork.
Group related custom fields under a name and a color.
View, edit or delete, set once per section for each permission profile.
No entry means full access, so you only close what needs closing.
Closed sections keep their values off the record and out of the list.
Keep a section off the list view and still edit it on the record.
Move or recolor sections without changing who can see them.
For Teams Holding Data Not Everyone Should See.
Field Groups vs Setting Access Field by Field.
| What | Field-by-field access | With Adoptiv |
|---|---|---|
| Restricting a set of fields | Field-by-field access: Change every field for every profile | With Adoptiv: Close the section once per profile |
| Default access | Field-by-field access: Depends on each field’s setting | With Adoptiv: Open until you close a section |
| What a withheld profile gets | Field-by-field access: Depends on the setup | With Adoptiv: Values kept off the record and the list |
| List views | Field-by-field access: Every field crowds the table | With Adoptiv: Keep a section on the record but off the list |
| Field names and options | Field-by-field access: Depends on the setup | With Adoptiv: Visible to all; only the values are withheld |
Field Groups & Layouts Questions, Answered.
What are field groups?
Sections that collect related custom fields under one name, so you can lay out your records and control access to the whole group at once.
What is field-level security in a CRM?
Control over who can see or change particular fields on a record. In Adoptiv it is set per section: each permission profile gets view, edit or delete on each section of fields.
Does closing a section hide the field names too?
No. Withheld values are kept off the record and the list, but the names of the fields and their picker options are not secret, so name sections plainly.
Does a new workspace come with sections?
No. A new workspace starts with none, so you create the sections you need. Fields outside every section stay fully open.
Can I restrict built-in fields this way?
No. Sections cover the custom fields you add. The built-in fields on a lead are not grouped this way.
Can a field belong to more than one section?
No. A field sits in one section or in none, and a field outside every section stays open.
What happens if I delete a section?
Its fields are removed, and the values they held are cleared from your records. Moving or recoloring a section changes nothing about access.
Can I keep a section off the list view only?
Yes. One switch keeps a section off the list view while it can still be edited on the record.
How do I hide fields from users?
Put the fields in a section, then take view access to that section away from the permission profile those users have.
Still have a question? A real person replies in under 60 seconds in US business hours. Talk to our team →
14-day free trial
Close the Fields That Need Closing.
Set up sections and profiles in the free trial. Free for 14 days, no credit card.
14-day trial · no card · migration included