User keys

Every device signs in with a user key that starts with ck_. The key page is where those keys come from: one key per person, pasted into their Obsidian plugin (or the command-line tool).

The list

One row per user: the name, the key (masked, with a copy action), the vaults the key owns against its allowance, the storage it uses against its limit, the day it expires, and the actions for that row.

Create a key

1. Click New key.
2. Type the person’s name.
3. Pick how long it lasts: 1 year, 90 days, 30 days, forever, or a date of your own.
4. Set the limits you want (below), or leave them as they are.
5. Click Create key and copy the whole ck_... to the person. It stays available from the list afterwards, so a lost message is not a lost key.

The limits behind a key

• Validity — after this day the key cannot sign in or sync.
• Vaults — how many remote vaults the key may create. The default is 1.
• Storage limit — once the account reaches this, new content is refused.
• History — how many days of versions and deleted files are kept. 0 days keeps only each file’s latest state, and a deleted file then cannot be restored.
• Max file size — files larger than this are not uploaded. The default is 50 MB.

The form refuses a limit below what the account already holds: a storage cap under its usage, a vault allowance under the vaults it owns, or an expiry before today.

Disable, enable, delete

• Disable stops that account’s devices at once, and keeps the key, the vaults and every version. Enable brings it back; syncing picks up where it stopped.
• Delete removes the account — and with it the vaults it owns, their version history and everything uploaded. It cannot be undone.
• Expired deletes nothing: current files stay, old versions still follow the history limit. Reactivate gives the same key 30 days, 90 days, a year, or forever.