Changelog

What's new

What has changed in Share Auth, month by month: access log, chat bots, browser extension, account security and billing.

Changes visible in the application, from newest to oldest. Internal fixes and security updates to dependencies, applied continuously, are not listed.

October 2026

The browser extension is available. It is published on the Chrome Web Store: on the sign-in page of a shared account, it finds the team’s code and fills it in with one click. See the extension page.

One access log for every channel. Codes and lists handed out by the Slack, Discord and Microsoft Teams bots now appear in the access log, alongside the website and the API, with the name declared by the platform. The channel filter offers each platform.

Log history by plan. The log can be viewed over 7 days on Free, 90 days on Team and without limit on Business. Nothing is deleted: moving to Business shows the full history.

Browser extension sign-in. The extension signs in through a Share Auth window, with your session and your second factor.

September 2026

Sites for every secret. The Sites field links a secret to the domain names where it is used, subdomains included. The API can find a secret from a domain, which the browser extension will rely on.

A skill for AI agents. The 2FA skill joins the MCP connector on GitHub: an agent that reads skills, such as Claude Code, can get a 2FA code. See the AI agents (MCP) page.

August 2026

Bots that are easier to use. /otp finds an account from a few words of its name, its issuer or its description. /otp-list shows one button per account, and every code comes with a button to get the next one. An integration’s activity shows who a code was handed to, and for which account.

No more duplicates. A team can no longer save the same secret twice; an import skips accounts already present instead of failing.

Promotion codes. An active subscription can take a promotion code from the Billing page.

Confirming new sign-ins. An account without an authenticator app confirms each new browser by email, through a link or a code. A confirmed browser is recognised for 30 days.

Per-channel restrictions. The owner can limit each Slack, Discord or Teams channel to the secrets it is allowed to obtain.

Scoped API tokens. Each token carries its own permissions and a validity period.

Multiple currencies. The Billing page can offer several currencies; the one chosen at sign-up stays the subscription’s currency.

New pricing. Free (3 secrets, 3 members), Team (50 secrets, unlimited members) and Business (unlimited secrets). See pricing.

Seven languages. The application is available in French, English, German, Spanish, Italian, Dutch and Portuguese.

Access log. The owner sees who obtained which code, when and from which address, on the website and through the API.