When you share a client portal link, the client can review their own record and suggest updates — a new address, a contact change, a corrected company number. Their submission becomes a change request queued for your review, so nothing changes in your records until you approve.

How the client experiences it

  1. The client opens the magic link you sent (see "How to share client access via magic link") and verifies via OTP.
  2. They land on a hosted form pre-filled with their current details.
  3. They edit any field — name, address, business activity, contacts, custom fields.
  4. They click Submit changes.
  5. They see a confirmation that their proposal is awaiting review by your firm.

How you handle it

  1. You receive a notification in the bell icon — "Client X submitted changes for review".
  2. Click the notification to jump to the client's detail page. A coloured banner at the top reads "Pending change request".
  3. Click Review changes.
  4. A side-by-side comparison opens — your current values on the left, the client's proposed values on the right, with the differences highlighted.
  5. For each field, choose:
  • Accept — replace your value with the client's.
  • Reject — keep your current value.
  • Edit — accept the proposal but tweak it (e.g. correct a typo before applying).
  1. Add an optional internal note explaining the decision.
  2. Click Apply changes.

Accepted fields are written to the client record immediately. The change request is closed and timestamped in the client's activity log so you can prove what was changed, by whom (you), and based on whose proposal (the client).

Reject the whole request

If the proposal is entirely off — for example a different person submitted it by mistake — click Reject all at the top of the review screen and add a brief reason. The client is notified.

Multiple requests

If the client submits a second request while one is still pending, the new submission queues behind the first. Review them in order so the audit trail stays linear.

Tip: Encourage clients to use the change-request flow rather than emailing updates. The audit trail is automatic, you don't have to retype anything, and the client gets a confirmation back — far cleaner than re-keying from an email and replying to confirm.

Note: Change requests respect the same field-level permissions as direct edits. Fields marked as private in your custom-field settings (see "How to configure custom client fields") are not shown to the client, and they cannot propose changes to them.