Keys and the Vault

A key (an API key, a token, a password for a service) lives in the project's Vault, never in a message, a document or the code. Settings › Vault lists them, grouped by the service each belongs to.

Keys never go through the chat

If you paste a key into a message, the message box stops it before it is sent and offers Save to Vault and send: the key goes to the Vault, and the message says where it went. Send without it sends the rest. When Flexi needs a key, he puts a card in the space that saves straight to the Vault; he is told its name, never its value.

Your own documents, tables and drawings keep what you type in them.

In the Vault

• Add keys, the first row: one box takes NAME=value, a whole .env pasted, or the file; it says which service each lands under before keeping it. Dropping a .env file on the list does the same.
• Tap a key for what you can do with it: Show it, Copy it, Replace it and Take it out of the Vault.
• Export .env, the last row, downloads them all, for working on the code elsewhere.

A key saved, replaced or removed reaches the website and the agents by itself, in a few minutes: nobody needs to put anything live for it.

Keys that sign the phone app, or a login kept for a service, are the owner's to show or change.

Where next

• Connections
• Spaces