Can a reseller adapt terminology for customers without changing the task's meaning?

**Can a reseller rename teams or statuses?**

Ask whether the proposed licence permits those transformations. If it does, distinguish display terminology from changes to authority or process. Renaming a receiving queue can be straightforward; turning a coordinator role into an approver changes what actions the role may perform.

**What can go wrong with status labels?**

A customer may use accepted to mean receipt acknowledged, while the generated policy uses it to mean responsibility assumed. Replacing labels without checking that distinction can invalidate expected answers and mislead agents trained on the adapted pack.

**What should an adaptation pilot contain?**

Request a terminology map, role definitions and tasks that exercise the changed terms. Preserve stable internal identifiers where practical, so presentation changes do not break record links. Review any wording that affects permissions or transition conditions.

**What remains uncertain until scoped?**

The permitted adaptations, required notices and responsibility for validating modified outputs need to be clarified. A reseller should not assume that permission to redistribute includes permission to alter every component, or that the original evaluation results still describe a customer-specific version.