Rumatadocs
SupportOpen Rumata
Browse documentation

Secret controls

Open MarkdownOpen JSON

Add or update secrets, manage access, and find the references your workflows use.

4 min readUpdated Sep 6, 2026

Step-by-step guidance.

Before you start

  • Open the named screen in Rumata. Available controls may depend on your account, permissions, and resource state.

Find a secret

Open System Explorer → Secrets. Secret values are write-only: after saving, the screen shows a protected placeholder rather than the original value.

ControlWhat it does
Search secretsFilter by name or description. It cannot search the protected values.
Add SecretOpen a new-secret form. A project must be selected.
Edit pencilOpen an existing secret’s metadata and an empty field for an optional replacement value.
Manage accessOpen group-level permissions for this secret.
Protected value displayIndicate that a value has been stored. It is not a reveal or copy-value control.
Reference capture from the separate Sabai Talk Thai application (September 8, 2026). The system-managed value stays hidden. Workflows refer to the secret by its reference rather than placing its value in documentation.

Add or edit a secret

Use a recognizable name such as PAYMENT_API_KEY and a description that explains its purpose without including the credential itself.

ControlWhat it does
NameSet the identifier when creating the secret. It is required and cannot be renamed in the edit form.
TypeClassify the secret, for example api-key, database, auth, payment, or email. This is a text field, not a provider connection wizard.
DescriptionExplain where the secret is used.
ValueEnter the credential for a new secret, or a replacement when editing. Leave it blank during editing to keep the current value.
Add Secret / SaveCreate the secret or save your edits. If a field or server error occurs, the form shows the error instead of a success message.
Cancel / CloseDismiss the form without submitting the pending changes.
Reference capture from the separate Sabai Talk Thai application (September 8, 2026). Add Secret opens a form. Review the name and value before saving; this empty form was cancelled.

Deletion and the system JWT secret

Workflows can depend on a secret by name. Deleting one can stop those workflows from working.

ControlWhat it does
Delete secret / trash iconOpen a confirmation identifying the secret to remove.
Delete secret in the confirmationPermanently remove the secret from Rumata and the project runtime. This cannot be undone.
Cancel in deletion confirmationKeep the secret. Confirmation controls are disabled while deletion is pending.
Copy factory JWT workflow referenceCopy the system-managed signing secret’s workflow reference. It copies a reference, not the secret value.