Customization Overview

Customization allows administrators to adapt the Helpdesk to the organization's processes without changing the fundamental service model.

What can be customized

Depending on the available configuration, customization may include:

• fields
• layouts
• list columns
• module presentation
• ticket properties
• supported record settings
• other configurable user-interface behavior

Why customize

Good customization helps agents capture the information required for service delivery while keeping the interface focused and understandable.

Avoid unnecessary complexity

Every additional field, layout rule, or configuration choice increases the amount of information users must understand.

Only add customization when it solves a real operational requirement.

Governance

Changes can affect multiple teams and existing records.

Test significant customization before making it part of the production workflow.

Good practices

Use clear labels, consistent terminology, and documented ownership for customized configuration. Review unused fields and settings periodically so the Helpdesk does not accumulate unnecessary complexity.