Gateway settings and files

Gateway Options and File Manager hold workspace-level configuration and resources. Review their scope before changing settings used by several workflows or apps.

Gateway Options#

Open Settings → Gateway Options to inspect the controls available to your account. Record the current values and identify which clients, environments, and services depend on a setting before changing it.

For public API behavior, keep a representative request available so you can verify the effect after saving. Check both the gateway response and the matching execution log.

Dedicated access controls remain in their own screens: API Key Access, Origin Validator, and CORS Origin under Workflows. Use those pages for their specific policies rather than searching for a single universal access switch.

File Manager#

Open Settings → File Manager to manage files exposed through the account's supported storage tools. Name files clearly and organize them so the app or workflow that owns them is identifiable.

Before uploading or replacing a file, check its intended audience, size/type requirements, and how the consuming app references it. A file path or identifier can be part of a released app's contract.

Replace or remove a resource#

Search for references in the relevant app, page, workflow, or documentation before removing a file. Preview the replacement and verify its URL from the intended user's context.

Deleting a file can break existing links even if the latest editor no longer uses it. Keep a recovery copy or use versioned naming when clients need time to move to a replacement.

Know the storage boundary#

Application uploads, workflow databases, support-ticket attachments, and platform-managed files can have different permission and lifecycle rules. Use the supported feature for each resource rather than treating every stored file as interchangeable.

For operational recovery, see database backups. For ticket material, see support evidence.