Workspace Settings¶
A workspace's General settings are where you set what it is and what becomes of it: the name that tells it apart from your others, the credentials that let outside systems drive its flows, and how to delete it for good. You reach them from the General page, under Workspace settings in the left navigation.
Name and credentials¶
A workspace's name is how you and your team tell it apart from the others you keep open - it is the label in the workspace switcher and across the app. Rename it when its purpose has drifted from its name: a "Test" space that quietly became production, a project that grew into a product. The name should still say what is inside. You change it in the Workspace Info section: edit the Name and click RENAME.
A flow's instances do not have to be launched from the editor, and the Credentials section is what opens them up to the outside. It holds the two values another system needs to drive this workspace on its own - the Workspace ID that names it and the workspace's API Key. With them, a Call Flow invocation, a trigger activation, or any program you write can start instances of your flows from anywhere, not only from inside FlowRunner™. The key is part of every URL the console writes for you, so treat those URLs like a password and keep them private. A program can send the key in an FR-Access-Key header instead - see Call Flow (Blocking).
The refresh icon beside the field issues a new key; because the key belongs to the whole workspace, every URL built on the old one has to be rebuilt with the new key. The confirmation says so: Any client application using the API Key WILL STOP WORKING when the key is regenerated. Two kinds of address are easy to miss:
- Callback URLs. Each External Callback block's Callback URL changes to carry the new key, so any system you gave the old URL needs the new one. A run already waiting at a callback continues when it is called at the new URL with its execution id; the old URL is refused.
- Webhook triggers from custom extensions. The address such a trigger registered with the outside service still holds the old key, and every delivery to it is refused. Stop and start each LIVE flow that uses one, so it registers its new address.
Deleting a workspace¶
When a workspace's work is finished or abandoned, deleting it clears it out completely. It removes the workspace and everything in it - flows, forms, knowledge bases, connections - and the screen says so plainly: the operation is irreversible. DELETE WORKSPACE carries it out once you confirm, so reach for it only when you are certain nothing inside is still needed.
