The 2FA vault built for teams
Share the codes.
Never the secrets.
Centralise the one-time codes for your work accounts, control who can reach them, and stop waiting on whoever has the phone.
No card required · Set up in minutes
Encrypted at rest · Role-based permissions · Logged access
Shared codes
3 entries- 482 913
- 731 204
- 096 475
Activity
- 09:41 Maya viewed GitHub Production
- 09:23 Sam viewed Stripe Finance
- 08:57 Alex was invited as a reader
Demo interface. The codes are fictional.
Secrets encrypted at rest
OTP seeds are encrypted before they are stored.
Role-based permissions
Owner, editor or reader: each with their own scope.
Access log
Website, API or messaging: every code given out is recorded with its source.
Token-secured API
Your internal tools reach only the functions you allow.
The everyday hold-up
The code is on their phone.
Your team is stuck.
When access to an account depends on one person, a few seconds of authentication can turn into hours of waiting.
Without a shared vault
- 09:14“Does anyone have the Stripe code?”
- 09:18“Léa is off today.”
- 09:21“The client payment still has to go out now.”
With Share Auth
- Open the vault
- Check the permission
- Copy the current code
- Get back to work
How it works
Share the access without handing out the secrets.
Step 01
Add the account
Scan its QR code or import its otpauth:// URI.
Step 02
Set the permissions
Invite members and decide who can view, edit or administer.
Step 03
Use the code
Every authorised member gets the live code the moment they need it.
Features
Everything you need to stop chasing a code.
A shared TOTP vault
Bring the one-time codes for your work services together in your team's space.
- GitHub Production 482 913
- Stripe Finance 731 204
- AWS Console 096 475
The code without the seed
Readers use the generated code without reaching the secret that produces it.
Permissions that fit each person
Separate viewing, editing and administration.
A trail of every lookup
Website, API or messaging: see who got which code, and when.
Migrate in minutes
Scan a QR code, import a Google Authenticator or Bitwarden export, or type the key.
Several teams, one account
Move between teams without mixing up access.
An API for your own tools
Reach the permitted functions with dedicated tokens.
Security
The team decides who sees what.
OTP seeds are encrypted before they are saved. Access to codes depends on the active team and on the user's role. A member can be allowed to view a code without ever receiving the source secret.
Encrypted before storage
Isolated per team
Explicit permissions
Auditable lookups
Two-factor sign-in to your account
New browsers confirmed by email
The path of a secret: the OTP secret is encrypted, then stored; the one-time code becomes visible only after authorisation.
Share Auth makes controlled sharing of OTP codes easier. It is not a password manager, and it does not replace an overall identity management strategy.
Roles and permissions
Everyone sees exactly what they need.
Reader
- View and copy codes
- Source secret hidden
- No member management
Editor
- View codes
- Add and edit entries
- See and export the source secret
- No deletion
Admin
- View codes
- Add, edit and delete entries
- See and export the source secret
- Billing management
- No member management
Owner
- Every permission
- Member and team management
- Access to the logs
- Subscription management
Integrations
Codes where your team already works.
Connect the collaboration channels and internal tools you use every day, and limit each channel to the accounts it needs.
Slack
AvailableAsk for a one-time code straight from your team channel.
Example
/otp github-production
Code available: ••• •••
Discord
AvailableA dedicated command for teams working on Discord.
Example
/otp stripe-finance
Access granted for Studio North
Microsoft Teams
On requestGet a code without leaving the conversation.
Example
/otp aws-console
Code available: ••• •••
API
AvailableReach the permitted functions with a dedicated token.
Example
POST /v1/secrets/:id/generate
Access granted for Studio North
Browser extension
AvailableThe code for the site you are on, found and filled into the page in one click.
Example
github.com/login
Code filled in: ••• •••
AI agents (MCP)
AvailableYour AI assistants get a code, never the secret.
Example
get_otp_code("GitHub")
Code: ••• •••
The trademarks mentioned belong to their respective owners.
Access log
Website, API or bot: no code goes unnoticed.
Demo dataMember
Maya Chen
Secret viewed
GitHub Production
Team
Studio North
Date
2 min ago
Source
Web
Member
Sam Rivera · as reported by Slack
Secret viewed
Stripe Finance
Team
Studio North
Date
18 min ago
Source
Slack
Member
Alex Morgan
Secret viewed
AWS Console
Team
Studio North
Date
yesterday at 16:42
Source
API
Pricing
Start small. Add capacity as the team grows.
Team
Most popular€6 / user / month
- Up to 50 secrets
- Unlimited members
- Slack and Discord integrations
- Access log: last 90 days
- Email support
Business
€12 / user / month
- Unlimited secrets
- Unlimited members
- Everything in Team
- Full access log history
- Priority email support
Enterprise
Custom quote
Your cloud. Your secrets. Your control.
For organisations with advanced security, sovereignty and infrastructure requirements.
- Single Sign-On (SSO)
- SAML 2.0 / OpenID Connect
- Hosting in your cloud (BYOC)
- Dedicated infrastructure
- Deployment with Terraform
- Secrets and keys in your environment
- Managed maintenance and updates
- Advanced audit
- Priority support
Billed monthly at team level. You can start on the free plan, with no card. The log never deletes anything: moving to Business shows the whole history.
Share Auth Enterprise
Enterprise-grade security. Your infrastructure.
Deploy Share Auth in your own cloud environment and keep the simplicity of a fully managed service.
Priced on quote, based on your hosting and support needs.
Enterprise SSO
Connect Share Auth to your company identity provider.
- SAML 2.0 / OIDC
- Centralised authentication management
- Works with your existing identity systems
Managed BYOC
Share Auth runs directly in your cloud environment.
- Deployment on Scaleway
- Infrastructure isolated per customer
- Data hosted on your side
- Secrets and keys managed in your environment
Terraform and managed operations
Keep control of the infrastructure without having to run it yourself.
- Documented Terraform modules
- Infrastructure as Code
- Controlled deployments
- Updates and maintenance by Share Auth
- Architecture sized to the load, serverless or classic cloud as needed
Your cloud. Your secrets. Our expertise.
With Share Auth Enterprise, your data and your TOTP secrets stay in your cloud environment. Share Auth provides the application, the deployment tooling and the maintenance; you keep control of your infrastructure and of production permissions.
The access Share Auth needs to maintain the instance is agreed with you, and you can revoke it at any time. The exact terms are agreed with you before go-live.
Share Auth
- Application and updates
- Terraform modules
- Support and technical monitoring
Controlled deployment
Customer's Scaleway infrastructure Your account
- Share Auth application
- Dedicated database
- Secure environment variables
- Audit logs
- Backups
Enterprise questions
The scope of each deployment is defined with you: users, hosting, level of support.
Request a demoManaged Bring Your Own Cloud means running Share Auth in your own cloud infrastructure, while Share Auth takes care of maintenance and updates.
Data and TOTP secrets are kept in your cloud environment. Encryption keys are set in the secure environment variables of your infrastructure, and you decide who can deploy code to it.
Yes. The offer includes access to the Terraform configuration used to provision and maintain the infrastructure.
Share Auth prepares and maintains the updates. They are rolled out through a controlled process, adapted to your company's requirements.
Managed BYOC is available on Scaleway. Other providers can be considered depending on demand.
Share Auth Enterprise is priced on quote, based on the number of users, hosting needs and the level of support.
FAQ
Frequently asked questions
Share Auth can protect its users' accounts with two-factor authentication, but that is not its main purpose: it stores the OTP seeds of external services and lets authorised members view their one-time codes.
It depends on their permissions. A reader can use the generated codes without reaching the seed that produces them.
Yes. Roles separate reading codes, managing secrets and administering the team.
By QR code (camera or image), by otpauth:// URI or by typing the key. A Google Authenticator export or a Bitwarden file imports several accounts at once.
Slack and Discord, with one-click connection, an extension for Chrome and Edge, plus a token-protected API, an MCP connector and a skill for AI agents. Microsoft Teams is available on request.
Anyone in the connected workspace who can run the command: team roles do not apply to bots. Per-channel restrictions limit the secrets available in each channel, and every code given out appears in the access log, with the name reported by the platform.
Yes. The free plan covers up to three secrets with three members, including roles, the API and the access log for the last seven days. It does not include support.
The app is available in English, French, German, Spanish, Italian, Dutch and Portuguese. Paid plans are billed monthly per user, the seat count follows people joining and leaving, and the Billing page can offer several currencies.
No. It is built for controlled sharing of OTP codes. It complements your team's access management practices.
Stop letting one 2FA code hold up the whole team.
Create your space, add your first accounts, and give everyone the right level of access.
Start for free3 secrets · 3 members · no card