10 November 2026 — Sign-in, organisations and setup improvements

This update is deployed at tape-vault.jmc.tools. It brings together the recent improvements made during testing. No separate Version 2 launch is being announced.

What changed

A clearer starting point

  • The product is now Tape Vault — Change history and recovery for Tape, with updated branding and a browser icon.

  • After signing in, you land on Your organisations rather than going straight into one organisation.

  • Organisation cards show recent activity, monitored apps and setup items needing attention. Your current or last selected organisation is marked.

  • Open organisation takes you to its overview; Your organisations brings you back.

Sign-in and organisation switching

  • Improved one-time-code handling and clearer messages for unavailable or replaced attempts.

  • Separate admin and normal-user logins can coexist in the same browser.

  • Fixed blank responses affecting sign-in redirects and audit detail pages.

  • Organisation switching keeps your user login active. Out-of-date forms ask you to reload before acting on a different organisation.

  • An account with no eligible organisations now shows a useful explanation instead of a dead-end organisation link.

Clear access roles

  • Added Reader, Recovery and Organisation admin roles for each organisation.

  • Readers can view history; Recovery users can also recover records; Organisation admins can manage apps and members too.

  • New members start as Readers. Existing members retained their access.

  • Role changes take effect on the next request. Losing one organisation does not sign you out of the others.

  • The last organisation admin cannot be removed or demoted.

PAT support and setup retries

  • Setup now explains the Tape PAT capabilities and workspace selection needed for audit history, with record editing optional for recovery.

  • Existing user API keys remain supported.

  • Permission, credential, rate-limit and connection failures have clearer messages.

  • Setup saves its related changes together, reducing partial setups that block another attempt.

  • Reopening the same valid invite resumes its saved step. Saved provisioning has a Retry setup control.

  • Unfinished setup can accept a validated replacement token for the same Tape organisation.

  • Retrying a saved selection reuses its saved provisioning job.

Audit history and connections

  • Corrected a compatibility issue that prevented some Tape lookups from running.

  • A failed optional team lookup no longer prevents stored history from loading.

  • Audit differences show a useful failure message if Tape cannot be reached.

  • Incoming notification checks are stricter while existing verified webhook addresses remain unchanged.

  • Newly created webhook connections use additional URL protection.

  • The contact form works with the current Tape Vault domain.

Important coverage reminder

Trigger automations and Trigger webhooks are separate Tape action settings. An automation update with webhooks switched off may not appear in Vault. Enabling it affects future updates; it does not send earlier omitted events.

Recovery still has field-type and deleted-record limitations. Some previous empty values are not restored by rollback. Recovery buttons apply changes immediately, so read the recovery guide before testing them.

Automation-definition backups are not included in this update.

Suggested checks for the current tester

  1. Request a fresh login code and confirm that Your organisations appears.

  2. Open an organisation, view its audit timeline and open an audit item.

  3. If you have several organisations, switch between them and return to Your organisations.

  4. Check that the controls shown match your Vault role.

  5. If testing a new setup, use a valid invitation and the PAT guidance. Reopen the same invitation if interrupted.

  6. Make an ordinary change in a monitored Tape app and check that it appears. For automation changes, check the update action's Trigger webhooks setting.

  7. Test recovery only on a record you intend to change; a disposable test record is preferable.

Expired invitations and login codes remain expired. Ask for a fresh invitation or request a new login code rather than retrying an old link.

Related guidance