Lock a resource with a key

A resource locked with a key can still be viewed and run as usual, but nobody can modify or delete it without entering the key. Use it to protect a workflow that already works, a published form, a dashboard the management team looks at, or a webhook an integration depends on.

In one sentence

The lock does not stop the resource from being used: it stops it from being changed or deleted by accident (or without permission).

Which resources can be locked

Workflows, forms, dashboards and webhooks.

What is prevented and what is not

With the resource locked…	Allowed?
View it and open it in the editor	Yes
Run it (manual, scheduled, by webhook or form)	Yes
Activate or pause a workflow	Yes
Duplicate it (the copy is new and not locked)	Yes
Save changes, rename it, schedule it	No, without the key
Move it to another folder	No, without the key
Publish it, link or unlink workflows, restore a version	No, without the key
Delete it	No, without the key

Who can lock

• The client administrator, on any resource.
• The resource owner (whoever created it), on forms and dashboards.

Workflows and webhooks

Workflows and webhooks do not record who created them, so only the administrator can lock them.

Lock a resource

1. Open the resource: the workflow editor, the form or dashboard builder, or the webhook panel.
2. Click the padlock in the top bar.
3. Type a key of at least 6 characters and repeat it.
4. Click Lock.

Keep the key somewhere safe. If it is lost, the administrator can remove the lock (see below).

Modify a locked resource

When someone tries to save or delete a locked resource, Floogos asks for the key. If it is correct, the operation is repeated automatically and that person can edit the resource for 30 minutes.

• The 30-minute window is personal: someone else still needs the key.
• You can also open it by hand from the padlock, and close it earlier with Lock again.
• After 5 wrong keys in a row, that user is blocked for about 10 minutes on that resource.

From scripts, MCP or integrations

Whoever changes the resource through the API can send the key in the X-Floogos-Edit-Key header. Without it, the request gets a 423 error with the code RESOURCE_LOCKED.

Change the key and remove the lock

From the same padlock, the administrator or the owner can:

• Change the key: edit windows opened with the old key are closed. The administrator can change it without knowing the current one.
• Remove the lock: the owner needs the key; the administrator can remove it without it. This way a resource is never locked forever.
• See the history: who locked, unlocked, changed the key, removed it, or tried to modify the resource without permission.

How it looks in lists

Locked resources show a padlock next to the name in the workflow, form, dashboard and webhook lists.

Security

• The key is never stored in plain text: only a hash is kept.
• The key is never displayed or written to the history.
• It protects against changes, not against use: it does not replace user permissions or webhook security policies.

What it does not cover

• Bulk backup restores and template uninstalls may affect locked resources.
• Deleting a folder does not delete the resources inside it, so it does not affect locked ones.

Keep reading

• Security
• Webhooks
• Dashboards
• Workflow versions