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 letting authentication hold your team up.
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 viewer
Demo interface — fictional codes.
Secrets encrypted at rest
OTP seeds are encrypted before they are stored.
Role-based permissions
Owner, editor or viewer: each with their own scope.
Record of every lookup
Each access to a secret can be recorded.
Token-secured API
Your internal tools reach the functions they are allowed to.
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
Shared access, without sharing everything.
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
Viewers 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
Find out who viewed which secret, and when.
Added in seconds
Scan a QR code, import a URI, or enter the details by hand.
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 you can point at
Control stays with the team.
OTP seeds are encrypted before they are persisted. 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
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 replaces neither a password manager nor an overall identity management strategy.
Roles and permissions
Everyone sees exactly what they need.
Viewer
- View and copy codes
- Source secret hidden
- No member management
Editor
- View codes
- Add and edit entries
- Import a QR code
- No billing 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.
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
AvailableGet a code without leaving the conversation.
Example
/otp aws-console
Code available: ••• •••
API
AvailableReach the permitted functions with a dedicated token.
Example
GET /v1/secrets/:id/code
Access granted for Studio North
The trademarks mentioned belong to their respective owners.
Access log
A lookup does not go unnoticed.
Demo dataMember
Maya Chen
Secret viewed
GitHub Production
Team
Studio North
Date
2 min ago
Source
Web
Member
Sam Rivera
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 you can read
Start small. Add capacity as the team grows.
Team
€6 / user / month
- Up to 50 secrets
- Unlimited members
- Roles and permissions
- Integrations
- Standard support
Business
€12 / user / month
- Unlimited secrets
- Unlimited members
- Access log
- Integrations and API
- Priority support
Billed monthly at team level. You can start on the free plan, with no card.
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 viewer can use the generated codes without reaching the seed that produces them.
Yes. Roles separate reading codes, managing secrets and administering the team.
An account can be added by hand, imported from an otpauth:// URI, or captured from a QR code.
Share Auth offers integrations for Slack, Discord and Microsoft Teams, plus a token-protected API.
Yes. The free plan covers up to three secrets with three members.
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