Page personalization in Business Central

Business Central users can reshape the pages they work with daily — hiding columns they don't need, moving FactBoxes, adjusting layouts, all without admin or developer involvement. This personalization is per-user, persistent, and one of the underrated productivity features in BC.

What's personalizable.

• Column visibility and order in list pages.
• Field visibility on card pages.
• FactBox visibility on the right pane.
• FastTabs collapse / expand default state.
• Action visibility in the ribbon.

A user removing 10 unused columns from the Sales Orders list page sees only what they care about.

How to personalize.

1. Settings → Personalize (or top-right gear icon).
2. The page enters personalization mode — controls highlight.
3. Click on items to hide / show / move.
4. Clear personalization to revert.
5. Personalization saved per user, per page, per role.

Personalization vs customization vs extension.

• Personalization — per-user; the user's own view.
• Customization — per-role / per-company; visible to all users with that role.
• Extension — per-tenant or app-source level; modifies the application.

Three layers, three audiences, three lifecycles.

Customizing for a role. Admins can:

• Use Customize mode to change defaults for a role centre.
• The customization applies to all users with that role.
• Users can still personalize on top of customizations.

The layering: extension defines defaults → role customization overrides → user personalization further overrides.

Profile management.

• Each user assigned a Profile (Role Center).
• Profiles can be customized for the company.
• New users get the profile's customized state as their default.

For organisations with distinct roles (warehouse worker vs finance manager), profile-based customization standardises starting state per role.

Configuring page parts visibility.

• Some FactBoxes are always heavy (related entries with summary). Hiding them improves page load.
• Some users prefer wider main area, less side content.

Personalization gives each user control without affecting peers.

Clearing all personalization.

• Clear personalization action removes user's per-page personalizations.
• Useful when a user has accidentally hidden critical fields.
• Admins can clear personalizations for any user.

Reset application area. Application areas are a related concept:

• Basic — minimal feature set.
• Essential — standard.
• Premium — all features.

Set on the Company Information page; affects which fields and pages appear. Different from personalization but conceptually similar — controls what's visible.

Personalization in mobile apps. The BC mobile app has more limited personalization:

• Some column visibility.
• Less rearrangement.
• Reflects desktop personalization where possible.

Common pitfalls.

• Critical fields hidden. User can't find them; thinks system is broken.
• Personalization across role changes. User moves to new role; their personalizations from old role linger.
• No reset training. Users don't know they can clear; suffer broken layouts.
• Mistaking personalization for customization. Changes apply only to one user; others ask why their view differs.

Audit considerations. Personalization changes aren't typically audit-tracked — it's user UI state. For regulated environments, customizations and extensions are tracked; personalization isn't.

Strategic positioning. Personalization is a quiet productivity feature. Mature BC deployments train users to use it deliberately — making the system feel tailored to each role without admin overhead. The investment is brief training; the payback is daily productivity. Underused in most deployments; worth surfacing as part of onboarding and ongoing tips.