Safer team changes, smarter agent setup, and a review step before you publish

Review team role changes before they take effect, set up Operations agents step by step, check your form before publishing it, and update payment details without losing your place.

What's new in Hub

This update focuses on giving you more confidence at the moments that matter most — changing who can do what, setting up automation, publishing a form, and managing your subscription. Each of these actions now includes a clear review step so you can check everything before it takes effect.

Review team role and access changes before saving

Changing a team member's role or revoking their access is a significant action. Hub now makes sure you can see exactly what you're doing before anything is committed.

When you change a member's role, you'll see:

Their current role — so you know what's changing
Billing and admin consequences — at a glance, before you confirm
Save and Cancel controls — so nothing applies until you're ready

Revoking or restoring access, and revoking an outstanding invitation, also go through a focused review. The screen names the person, shows a before-and-after summary of what they'll be able to do, and asks for explicit confirmation.

If the member's details have changed between when you opened the review and when you try to save — for example, if someone else on your team made an edit — Hub detects the conflict and rejects the stale change, so you never accidentally overwrite a concurrent update.

Pending invitations now correctly show their provider-approval status rather than offering options that don't apply.

Set up new Operations agents with guided steps

Creating a new Operations agent used to drop you straight into a dense settings editor. The setup now follows a clear, guided path:

Job — what the agent does
Sources and permissions — which collections and repositories it can read or write
Schedule — when it runs
Review and create — a final check before activation

You can move Back through earlier steps without losing your answers. If a validation issue stops creation, your draft is preserved so you can fix it and try again without starting over. Activation and record permissions are surfaced explicitly at the review stage — so you can make an informed decision before enabling the agent.

Review your form before publishing it

Publishing a form is no longer a one-click action. Before it goes live, Hub now shows you a complete review:

The form and its fields — as visitors will see them
Submission destination — where responses are going
Public address — the URL the form will be accessible at

You review everything together, then confirm. Any pending edits to the form and its submission settings are saved at the same time as publication — so what you reviewed is exactly what goes live. There's no risk of a setting being saved separately at a different moment.

Unpublishing preserves any unsaved edits and existing responses, so you can take a form offline for revisions without losing anything.

Choose a plan or update your payment method without losing context

Two improvements make subscription management less disruptive.

Plan selection now follows a guided flow: compare options, review pricing, confirm, then see the result. If you go Back or if a request fails, your selected plan is retained — you won't have to re-choose where you left off. Payment updates remain accessible during the review, and failed confirmations explain clearly what happened rather than showing a success message.

Updating your payment method now opens in a focused dialog. When you're done — whether you save, cancel, or get redirected back from your bank — Hub returns you to your offer review exactly where you were. Previously, opening the payment editor would dismiss the offer you were reviewing entirely. After a Stripe redirect, Hub restores a fresh authoritative offer review without automatically confirming a purchase.

Finance dialogs protect your work while you edit

Three finance dialogs — cash verification, categorisation rules, and internal transfers — now share the same robust save behaviour used elsewhere in Hub:

Unsaved drafts are protected — if you try to close without saving, you'll be asked to confirm
Inputs lock while saving — so you can't accidentally submit twice
Save errors keep your draft — a failure doesn't wipe out what you've written
Invalid submissions explain why — instead of leaving a disabled Save button with no explanation

Existing transfer currency restrictions and cash verification revision handling are unchanged.

Deployment note: These improvements are part of a Hosting-only release that is pending final deployment confirmation. Features will be available once deployment is complete.

More improvements are in progress. We'll keep you updated as they roll out.