Features
Send a password as a link that opens once. Ask someone for a credential without giving them an inbox to paste it into. Then, when there is a team involved, decide the rules for everyone and keep a record of what happened.
The timer sets how long the link stays valid, and how many times it can be opened. After that the secret is permanently deleted.
Why a link
An emailed password can be read by the mail admins at both ends, everyone on CC and the distribution list, whoever it is forwarded to, every phone and laptop the mailbox syncs to, and the backups and archives that keep it for years. Chat is no better. The guide why not to send passwords over email or Slack has the full list.
A ShareShield link turns “everyone who can ever read this mailbox” into one person, once, before it expires. The email can still carry the link. It just doesn’t carry the password any more.
02Request
When you need a credential from someone else, the usual result is a password in an email thread that nobody deletes. A secret request turns it round. You ask, they fill in a one-time form, and the answer arrives in your ShareShield account.
Need a password, key or other secret from a colleague or client? Send them a request: they get a one-time link to a form, and their answer comes back to you as a secret link.
The request link expires after
1 day3 days7 daysPriya Shah (priya@acme.example) is asking you for a secret
Available for
1 day3 days7 daysEnter what you need and who you are asking. ShareShield emails them a link to a form. They paste the credential or attach a file, and it becomes a secret owned by you, with your organisation’s rules applied. The request comes from your account, so they can see who is asking.
The person filling in the form doesn’t need an account. A request stays open for up to 7 days, and the link stops working once it has been used.
Write your note on the request as if it might be forwarded: it appears in the email and on the form, so it should say what you need and never contain a secret itself.
Anyone can fill in a request. They can answer with a file only if your organisation is on an active paid plan that includes files. Sending a request needs a ShareShield account.
03Control
One person sharing carefully is easy. Twenty people sharing carefully needs rules that apply whether or not anyone remembers them. Organisations in ShareShield have roles, enforced policies and sign-in controls.
Invite your team as owners, admins, members or viewers. Viewers can see but cannot create secrets, requests or API keys.
Owners and admins get an organisation-wide view of every member’s secrets and requests, with metadata only, never the contents, and can burn any of them.
Team members
Owners set the limits for every secret in the organisation:
Policies apply to every secret anyone in the organisation sends. A policy can only tighten your plan’s limits, never loosen them.
Members can protect their accounts with any TOTP authenticator app, with backup codes for when a phone goes missing. An organisation can require it for every member.
Connect your own OpenID Connect identity provider, starting with Microsoft Entra ID. Prove you own your domains with a DNS TXT record, then require SSO for everyone on them.
Owners keep a password sign-in as a break-glass route in case the identity provider is down. New people who sign up on a verified auto-join domain land in your organisation automatically.
Secret policy
Rules enforced on every secret your organization creates. Limits can only tighten what your plan allows.
The timer sets how long the link stays valid, and how many times it can be opened. After that the secret is permanently deleted.
04Prove
When an auditor, a client or your own incident review asks how a credential was handed over, you need an answer that doesn’t depend on someone’s memory or their sent folder.
Audit log
Security-relevant activity across your organization
| Time | Actor | Action | Target | IP |
|---|---|---|---|---|
| 3 Oct, 10:15 | usertom@acme.example | Member role changed | user: sam@acme.example | 203.0.113.9 |
| 3 Oct, 09:52 | anonymousAnonymous | Secret opened | secret: k7mq2vxr9t | 192.0.2.88 |
| 3 Oct, 09:51 | anonymousAnonymous | Recipient verified by email code | secret: k7mq2vxr9t | 192.0.2.88 |
| 3 Oct, 09:41 | userpriya@acme.example | Secret emailed to recipients | secret: k7mq2vxr9t | 203.0.113.24 |
| 3 Oct, 09:41 | userpriya@acme.example | Secret created | secret: k7mq2vxr9t | 203.0.113.24 |
Every step in a secret’s life is recorded: created, emailed, opened, burned, failed passcode, locked out. So are requests, member and role changes, API keys, policy edits, billing changes, sign-ins, 2FA and SSO events.
The Audit page in the dashboard filters by category, action, kind of actor (a person, an API key, an anonymous visitor or the system) and date, with a text search. The log records what happened, never the secret itself. IP addresses in it are cleared after 90 days.
Professional and Enterprise organisations can export the log as CSV.
Turn on notify-on-open and up to five people get an email the moment a secret is opened. The audit log records when a secret was emailed to its recipients and when it was opened.
05Integrate
If a pipeline, a provisioning script or a helpdesk workflow creates a credential, it can hand it over through ShareShield too, under the same plan limits and organisation policies as the web app.
A REST API with an OpenAPI 3.1 description and reference documentation. Create secrets and file secrets, check or burn them, and send and list secret requests.
API keys belong to one organisation and carry only the scopes you give them, such as secrets:create, secrets:burn or requests:create. They can expire after 1 to 365 days and can be revoked by their owner or an admin. Keys can’t manage users, settings, billing, SSO or other keys, so a leaked key can’t invite anyone or mint a new key.
Revealing a secret through the API is POST-only, so chat apps and email scanners that preview links can’t use up a view.
- name: Send the staging database password to the on-call engineer
env:
SHARESHIELD_URL: https://app.shareshield.net
SHARESHIELD_API_KEY: ${{ secrets.SHARESHIELD_API_KEY }} # a key with only secrets:create
DB_PASSWORD: ${{ secrets.STAGING_DB_PASSWORD }}
run: |
jq -n --arg content "$DB_PASSWORD" \
'{content: $content, expiryHours: 4, maxViews: 1, recipients: ["oncall@example.com"], recipientsOnly: true}' \
| curl -sS --fail-with-body -X POST "$SHARESHIELD_URL/api/v2/secrets" \
-H "x-api-key: $SHARESHIELD_API_KEY" \
-H "content-type: application/json" \
--data @- \
| jq '{expiresAt, recipients}'The key carries one scope, secrets:create. The step prints the expiry and the delivery report, never the link.
Sending a one-off secret needs no account, and anonymous links are limited to two a day. A free account gives you a dashboard, requests, and a team of up to 5 people.