Help center Core configuration Customers & support levels Configure company and contact field policies Updated Thursday, October 29, 2026 · Marc Staine Customer policies control which company or contact fields agents see and how those fields are ordered. Use role-specific layouts to reduce clutter while retaining the data each team needs. Applies to: Supportbench Core. Location: Settings → Customers → Customer policy. Access and available controls depend on your role and account capabilities. Before you begin You need editing access to Customer policy. Agent Roles in this editor select the staff layout audience.Decide whether the policy is for Companies or Contacts before arranging fields. A hidden field remains stored; layout is not a data-deletion or universal authorization rule.Review the saved result and a controlled example in the consuming workflow. Configuration, customer access and actual delivery or processing are separate checks. Configure and verify Open Settings → Customers → Customer policy and choose New Policy or open the intended policy.Enter Name and Description, then choose Type: Companies or Contacts. Changing Type resets the field selection and order to that type’s defaults.Review Agent Roles for the intended staff audience. Empty means the policy applies to all applicable roles.In Fields to Show, select at least one visible field. Use Field Order to arrange visible fields with dragging or the arrow controls. Hidden fields cannot be ordered until shown.Choose Save Changes and reopen the policy. Check the saved type, role scope, visibility and order.Open a controlled Company or Contact with an included staff role and an excluded role. Confirm each receives the intended layout and that needed work remains possible. Settings reference SummarySettingWhat it controlsHow to chooseNameRequired policy name; up to 50 characters.Identify the record type and intended team.DescriptionAdministrative explanation, up to 250 characters.Explain why the layout differs from the standard one.TypeCompanies or Contacts. Changing it resets visible fields and order to that type’s defaults.Choose the type before arranging fields.Agent RolesLimits the policy to selected agent roles. Empty means all roles.Use a role-specific policy only when that group needs a different layout. Fields to Show and Field OrderSettingWhat it controlsHow to chooseFields to ShowSelects type-specific standard and custom fields. At least one visible field is required.Include fields needed for everyday work; hiding a field does not erase its saved value.Field OrderArranges visible fields using drag or arrow controls. Hidden fields cannot be ordered until shown.Group related information and put frequent inputs first.AuditDisplays creation and update details.Use it to identify when a layout was changed. Company field choicesEach choice controls layout visibility; it does not edit the field value or grant access. Only visible fields can be arranged in Field Order.SettingWhat it controlsHow to chooseId / Name / SummaryCompany identifier, displayed name and summary.Keep identity and useful context easy to find.Parent / Status / Type / Support levelCompany hierarchy, classifications and support entitlement.Show the distinctions the role needs for routing and service decisions.Address / City / State/Province / Country / ZIP/Postal codeCompany mailing-address components.Keep related address fields together.Tags / PhoneCompany classification tags and telephone contact.Expose useful classifications without duplicating unrelated inputs.Account manager / Technical manager / Customer success managerThe three company management relationships.Include the owners the team actually consults.Health scoring active / Health score / Health risk / Health commentsConditional fields available when account health scoring is enabled.Keep the risk context visible alongside a score.Timezone / Sector and industryRegional and business classifications.Use where they inform contact timing or service context.Facebook page / Twitter page / Crunchbase page / Linkedin pageStored company profile links.Show only links maintained by your team.Domains / Twitter handles / RolesCompany domain, social-identity and customer-role associations.Review their operational meaning separately from their layout visibility.Revenue / Renewal / ActiveCommercial context and availability state.Show only to roles with an operational need.Company custom fieldsAccount-defined fields at the Company location.Select the actual fields required for this role and preserve their intended grouping. Contact field choicesSettingWhat it controlsHow to chooseId / Name / Bio / AvatarContact identity and profile context.Prioritize unambiguous identity.Company / Status / Type / Title / Department / Support levelCompany relationship, classifications and professional/service context.Use the contact values rather than assuming company values are identical.Email / Secondary emails / Phone / MobileContact communication channels.Keep frequently used channels together.Address / City / State/Province / Country / ZIP/Postal codeContact mailing-address components.Review company-address inheritance in the record editor separately.LDAP username / Tags / Roles / Company watcherDirectory identity, classification and supported access/notification associations.Hiding these fields does not revoke their stored settings.Account manager / Technical manager / Customer success manager / TimezoneContact-level managers and timezone.Distinguish these relationships from company managers.Facebook page / Twitter page / Googleplus page / Linkedin pageStored social profile fields. Googleplus is a retained historical field in the catalog.Use only maintained values offered by your released editor.Active / Contact custom fieldsContact availability plus account-defined Contact fields.Keep essential operational fields visible and arrange custom fields by task. Behavior to knowChanging the policy type resets its field selection and ordering.A hidden value remains stored; layout visibility is not a data-deletion operation. Recommended use Use terminology that agents and customers already understand. Explain the intended meaning in the description.Keep the initial configuration small enough for people to choose consistently. Add options when they represent a real operational difference.Review existing references before renaming, changing scope, or deleting. Where supported, deactivate an obsolete option before considering permanent deletion. Worked example Create a Contacts policy for a defined agent role.Choose Contacts before selecting fields.Include identity, contact information and the custom fields required by that team.Arrange the visible fields and save.Open a test contact with an included role and an excluded role to confirm each receives the intended layout. Troubleshooting ProblemWhat to checkThe layout changed after switching TypeType changes reset field selection and order. Reconfigure the intended record type before saving.A field cannot be reorderedMake it visible in Fields to Show first.No fields can be savedAt least one visible field is required.Every role receives the policyAn empty Agent Roles selection applies broadly; select the intended roles if narrower layout scope is needed.A hidden field’s value still existsExpected. Hiding a field changes the layout, not the stored data. Related configuration Organization → Configure agent roles and division accessCustomers → Manage companies and customer organization detailsCustomers → Manage contacts and customer portal accessConfiguration → Configure custom fields and dropdown choicesManage companies and contacts with the full support relationship in viewDesign, assign and verify agent roles for a B2B support team Was this article helpful? Yes No Thank you for your feedback.