Flow Console
The console is the interactive interface for Flow. The management CLI and API expose many of the same resource operations for scripts and CI.
| Page | Purpose |
|---|---|
| Dashboard | Recent runs, charts, execution heatmap, and outcome summaries. |
| Functions | Uploaded releases, code/schema/permission inspection, copy, deprecation, and deletion. |
| Executables | Schedules, args, profiles, secrets, runtime settings, storage, and run history. |
| Profiles | Execution identities, Roles setup and scope changes, verification, and lifecycle. |
| Secrets | Write-only project credentials and rotation. |
| API Keys | Personal and scoped credentials; shown-once creation and revocation. |
| Usage & Billing | Workspace usage, gas costs, credits, and payment operations. |
Resource scope
Functions, executables, profiles, and secrets belong to a project. Select the correct workspace and project before creating or editing them. A release and profile bound to an executable must belong to that project.
The dBank credit balance belongs to the workspace and is shared across its projects. A personal upload key belongs to its user; workspace management credentials also carry a workspace binding and explicit scopes.
Roles and permissions
Owner and admin roles operate cloud resources and approve workspace management access. Member access is read-oriented where supported. A billing-only role manages payment concerns and does not grant access to Flow's operational pages. API calls also need the corresponding credential scope; having a key does not bypass the user's workspace role.
Connecting a wallet is a separate action from logging into the console. Safe-owner signatures authorize on-chain permissions; account sign-in and API consent authorize access to Flow resources.
Start with creating an executable, then use monitoring and profile operations.