Setup, Configuration, and Data Integrity
Core concepts
Configuration is layered: access levels define what a user can do globally, sharing defines access to a specific object, and layout templates control what they see (tabs, fields, sections) on that object. All three must line up for a user to work effectively - a missing field is usually a layout template issue, not a permission issue.
Groups and subgroups carry statuses, approval processes, layout templates, and sharing defaults. Companies associate users and clients. Custom statuses must equate to New, In Progress, or Complete. Custom forms and fields extend objects; calculated fields compute at the object level; sections organize fields on the form.
Other setup objects include schedules, timesheet profiles, job roles, exchange rates, system preferences, and blueprints.
Traps
- An access level does not grant access to a specific object, and sharing does not override a restrictive access level.
- Custom field deletion destroys the stored data and cannot be undone.
- A status in use cannot simply be deleted; it must be deactivated or replaced.
- Group admins manage only their group and its subgroups.
- Layout template assignment order matters - user, then group, then default.
Worked example
A planner cannot see the Planned Hours field on tasks. Check in order: access level and sharing (can they open the task?), layout template (does the task layout include the field?), then field-level visibility on the custom form. Fix the layout template at the group level so the whole team benefits.