Your KeySnap account
The same email address and password you use in KeySnap.
This page can see your account, the devices signed into it and the shared libraries you are in. It cannot see a single one of your shortcuts, and neither can the server behind it — unlocking those needs a key made from your password that never leaves KeySnap on your own computer. Signing in here does not change that.
Your KeySnap account
Your licence
Looking…
Licensing a computer that cannot reach the internet, or a whole fleet
Copy this and paste it into KeySnap on that computer, under Help → Licence → Enter a licence. It is signed, so KeySnap can check it is genuine without asking us — which is what lets it keep working offline, permanently, and whatever becomes of this website.
The same text licenses a whole fleet without anybody signing in. Put it in the
Group Policy setting KeySnap → Licence, or pass it to the MSI as
LICENCE="KEYSNAP-1…". Nothing about either route trusts the
registry or the command line: KeySnap checks the signature against a key inside
itself, so a licence that is wrong or invented licenses nobody.
People and seats
A seat licenses somebody's copy of KeySnap — unlimited shortcuts, protected snippets, no twenty-five limit. Shared libraries come with it and cost nothing extra; what you pay for is the people.
This is the only place anybody's role is set. An administrator hands out and takes back seats, and decides who is in each shared library. A member holds a seat and uses what they have been given. The owner is an administrator who also cannot be removed, and who is the only one able to hand the company on.
Being an administrator does not let anybody read a shared library they are not in. Reading needs the library's key, which has never been on this server, so it is handed over from KeySnap itself by somebody who already holds it. Deciding who is in a library and being able to read it are genuinely different things, and this is the one place that distinction is real rather than a wording problem.
Shared libraries
Folders of shortcuts everybody here can use. They are part of KeySnap Business and cost nothing extra — have as many as you like.
Nobody has a rank inside a library. A person is in it or not; they can change its shortcuts or only use them; and they either hold its key or are waiting for somebody to hand it over. Who is allowed to manage all of this is decided once, under People and seats.
If you forget your password
Nobody can reset a KeySnap password. The key to your shared shortcuts is made from it and has never left your computer, so there is no copy here to hand back — which is the same fact that makes it safe to keep your shortcuts on our server at all.
A recovery code is a second key to the same lock, and the only other one there is. It is made in the app rather than here, because making one needs the key. New accounts are given one while signing up; older accounts have to ask for it under Teams, then Your account.
Two-factor sign-in
Set up and turned off from KeySnap, under Teams then Your account.
Where you are signed in
What has happened here
Sign-ins from a machine this account had not been seen on, password changes, two-factor going on or off, devices signed out, and every change to your seat. Nobody but you can read this, and it is not something we can edit — each line is written by the thing it describes, at the moment it happens.
No addresses are recorded. Not the network address a sign-in came from, not a location worked out from one. KeySnap has never kept them and this is not the place to start — the name of the machine is what tells you whether a sign-in was yours.
Closing this account
Closing removes the account, every shared library you own, and your place in the ones you are in. The libraries you own go for everybody in them.
Nothing about it can be undone: the server holds only encrypted blocks it cannot read, so there is no copy anywhere to restore from. Shortcuts saved on your own computers are not touched.
If you want a copy of a shared library first, export it from KeySnap before closing. If you own one that other people rely on, hand it over from the shared libraries page rather than deleting it out from under them.