A long Console form saves what you type in your own browser while you type, and offers the entries back when you reopen it, so a reload, a closed tab or an idle sign-out does not throw the work away. Signing out yourself deletes it. The draft belongs to one user, one organisation and one form, it lives only in the browser that holds it, and it expires after seven days.
These forms keep drafts for every signed-in user, with nothing to switch on:
- Chapter flows, forms split into steps you move through in order: creating a vote, creating an XvP settlement, creating a token sale offering, listing an instrument, provisioning a trading venue, adding a compliance provider, and the corporate action composer for a buyback, burn, split, bonus issue, rights issue, spin-off or in-kind payment.
- Sheets and panels: the terms of a corporate action declaration, adding or editing a network, creating or editing a webhook, creating a data feed, adding a price source, creating or editing a reporting obligation, enabling a custody provider, and the custody approval policy and fee schedule panels.
A form that ends in a signed operation leaves that operation on Actions once it is signed. Transaction lifecycle describes what happens after you sign. The asset designer, the policy designer and the instrument template designer keep their drafts on the server, apart from the browser draft this page describes.
The composer keeps one draft per menu and token. Continuing a stopped corporate action keeps a draft of its own, so it starts from the stopped run's terms and leaves the draft of a new action on that menu as it was.
Read the draft state
Once a chapter flow holds a draft, its page header shows “Draft saved” or “Draft restored” beside the network name, with a Discard draft button at the end of the header. A sheet shows the state on one line above its fields, with its own Discard draft button, and announces a change of state to a screen reader.
A form you have not changed stores nothing and shows no draft state. A form you change back to exactly how it opened deletes its draft.
Discarding cannot be undone. Discard draft asks “Discard this draft?” and states “Your entries will be removed from this browser. Nothing has been signed.” Choose Discard draft to delete the entries, or Keep draft to go back to the form. In the corporate action composer, discarding starts the flow over on its first chapter. In the other chapter flows, discarding from the header also closes the flow.
Resume a saved draft
Reopening a form with a stored draft shows “Saved draft from 27 Oct 2026, 14:02 UTC”, a second line “Kept in this browser until 3 Nov 2026. PINs and codes are never saved.”, and two buttons, Resume draft and Discard. The saved time carries the UTC label in every language, and the expiry date is the UTC date whatever time zone the browser is in.
- A sheet asks before it fills. Resume draft fills the form, and Discard deletes the draft.
- A chapter flow restores on entry instead, because a chapter you have not reached sends you back to the first chapter, which would break a link to a later chapter. It shows “Resumed your draft from 27 Oct 2026, 14:02 UTC” with Discard. Discard there starts the flow over on its first chapter with empty fields, without a reload.
- Typing before you answer the offer does not overwrite the stored draft. Resume draft loads the stored entries. Discard deletes the stored draft and keeps what you typed since as the new draft.
- An idle or expired session keeps the draft on this computer for up to seven days. Sign in again and reopen the form to see the offer.
- A successful submit deletes the draft, and so does Discard. A chapter flow that has just submitted stays on the chapter that shows its outcome.
- Signing out yourself deletes every draft of the user who signed out, in every organisation, and leaves other users' drafts in the same browser alone.
What a draft never holds
The Console decides from each field's name in the form, not from its label or from what you type: a field whose name reads as a credential or a code is never written. The words that block a field are PIN, OTP, TOTP, password, passphrase, passcode, secret, mnemonic, credential, passkey, WebAuthn, JWT, bearer and step-up. The word pairs are private key, API key, API token, app token, access token, refresh token, auth token, session token, CSRF token, ID token, one-time, verification code, recovery code, backup code and seed phrase. A form that holds any one of them is refused as a whole, so the state reads “Not saved in this browser” rather than keeping a partial draft. A secret typed into a field with another name, such as a token inside a webhook URL, is stored with the draft.
When a draft expires
A draft expires seven days after it was last saved. An expired entry is deleted when the form reads it, and expired entries are cleared whenever a form with drafts first opens. An entry that no longer fits the form's fields is deleted when read, so a form that gained or lost a field starts clean instead of half filled.
Where the draft lives
The draft sits unencrypted in the browser's local storage, under a key built from the user, the organisation and the form. The Console offers a draft only to the user and organisation it belongs to, but anyone with access to this browser profile can read the stored entries. The Console never sends the draft to the server, so it does not follow you to a second device or a second browser, and clearing site data removes it. On a shared computer, sign out yourself, which deletes your drafts, rather than leaving the session to expire.