Custom Columns Per User
List views in business applications serve different users differently. A sales manager looking at the customer list wants to see deal value, last contact date, and account stage. A support agent looking at the same list wants to see open tickets, last response time, and escalation status. An accountant wants to see credit limit, outstanding balance, and payment terms.
All three are looking at the same object type. None of them benefits from seeing everything the others care about.
Custom columns let each user configure their own view of any list.
Pick Your Columns
A column picker in any list view shows all available fields for that object type. Users check the ones they want to see and uncheck the ones they don't. Drag to reorder columns into the sequence that makes the most sense for their workflow.
The change applies immediately. The list redraws with the new column set, in the specified order.
Preferences Persist
The column configuration is saved per user, per list view. Tomorrow, when the same user opens the same list, they see the same columns they configured. There's no setup step on every visit.
Different users on the same team can have entirely different column configurations for the same list. No one's view is affected by someone else's column choices.
Admin Defaults, User Overrides
Administrators can set default column configurations for each list view — the columns and order that appear for a user who hasn't customized their view yet. The defaults represent a sensible starting point for most users.
Users can override the defaults whenever they want. If the admin defaults change later, users who haven't customized see the new defaults; users who have customized keep their personal configuration.
Column Width
Columns can be resized by dragging the column divider in the header. Wider columns for fields with more content; narrower columns for short values like status codes or numeric IDs. Column widths are also saved per user.
Custom columns per user reflects a principle: the platform knows your data, but only you know how you work with it. Configure the view to match your workflow, and it stays that way.