For Support

What users will ask

"Why can't I change the date on this expense / salary adjustment anymore?"

This is the ticket you'll see most. The date field used to be freely editable for anyone who could add or edit the record; now it requires a separate permission. Check:

1. Ask which clinic/company and which permission group the user belongs to.
2. In Settings → Permission Groups → [their group] → Settings tab, look

at the Change Creation Date column for the Expenses or Salary Hub row.

1. If it's unchecked, that's expected — the field will show as disabled with

a tooltip/hint reading "You don't have permission to change this date" (web) or "You don't have permission to change this date" (mobile, shown as inline help text under the field).

1. To grant it: check Add New for that row first if it isn't already

checked (the date checkbox is disabled until Add New is on), then check Change Creation Date, then Save.

"I created an expense and it's dated today instead of the date I entered."

Expected if the user's group lacks the permission — the date they typed client-side was silently ignored server-side and replaced with today. This is intentional (see Expenses), not a bug. Grant the permission if they need to backdate expenses.

"I edited a salary adjustment's amount and the date changed / didn't change."

Editing without the permission never touches the date field — whatever date the record had before the edit, it keeps. If the user expected the date to update to "now," that's not how it works; the date only changes if they explicitly picked a new one and have the permission.

"The 'Change Creation Date' checkbox is greyed out in Permission Groups."

That column is only enabled once Add New is checked for that row. Check Add New first.

"Why does the payment date field allow changes now — it used to be locked to owners only?"

Expense payment dates (Add Payment on an expense, and bulk expense payments) used to be an owner-only (doAll) capability. This PR moved them onto the same EXPENSES_CREATED_AT permission as the parent expense, so any group with that permission — not just owners — can now set payment dates. This is an intentional widening, not a regression.

Fast diagnostic checklist

• Confirm the exact screen: New Expense, Edit Expense, Add Payment (expense),

New/Edit Salary Adjustment — the underlying permission differs (EXPENSES_CREATED_AT vs SALARY_ADJUSTMENT_CREATED_AT).

• Confirm platform (web vs mobile) — behavior is identical, but the tooltip

presentation differs slightly (hover tooltip on web, inline help text on mobile).

• Owners (DO_ALL permission) always bypass this check — if an owner reports

the field is disabled, that's a genuine bug worth escalating, not expected behavior.