Contributor keys
An agency runs on other people's accounts. Ask a client for the provider key you need, and get it without holding their password and without adding them as a dashboard user. One signed link, one field, no seat.
Ask for one key, not an account
From the Vault tab you name the person's email and the provider you need. They get a signed link that shows who is asking — your name, your organisation — and a single field. The alternative was a password in a chat window or a seat nobody wanted.
A request, not a credential
What travels is the ask. Their key never passes through a message, a shared document, or your hands.
Signed by a person
The invite carries the requesting admin's name and organisation, so your client knows who they are handing something to.
The contributor never enters your dashboard
The page they land on is not a limited view of your workspace and not a guest account. It sits outside the login entirely: the link is the only thing that gets them in, and it gets them in to one screen that does one thing.
No account, no password
They create nothing and remember nothing. Ninety seconds, then they close the tab.
Nothing else is reachable
The link grants exactly one action. There is no navigation out of it and into anything of yours.
The key is checked before it is kept
Every submitted key is tested against the provider first. A key that fails is reported on the page while they still have the provider's console open, and nothing is written. A vault of dead credentials is a worse outcome than an empty one.
Fails loudly, stores nothing
An invalid key never reaches your vault, so it can never sit there looking healthy.
Encrypted, then masked
What lands is encrypted at rest. The vault shows a masked preview and the name of whoever contributed it.
One link can collect a set
Most engagements need more than one provider. A single invite carries the whole list with a progress bar and closes only when the last key is in, so you send one message instead of four.
Idempotent by provider
Re-submitting a provider updates the key already there. No duplicates, no ambiguity about which one is live.
Cancel or resend
A pending invite can be pulled back or sent again. Every link stops working after 72 hours.