Site
A Site is the main workspace and permission scope for a set of Flowgear solutions. It groups the Workflows, Connections, Environments, API Keys, users, configuration, and operational history that belong together.
Use a Site to separate solutions that have different owners, access rules, operational responsibilities, or subscription allocations. Use Site Environments to move the same solutions through test, intermediate, and production stages within that Site.
A Site is a logical partition, not a security boundary. A user who can write Workflows can design logic that can access and change resources in other Sites.
What a Site contains
| Area | Site relationship |
|---|---|
| Workflows | Workflow definitions, folders, revisions, triggers, status, and logs are associated with a Site. Published revision and status can differ by Environment. |
| Connections | Connection definitions and folders belong to a Site. Their endpoints, credentials, and other values can differ by Environment. |
| Environments | Every Site has an ordered Environment list. New Sites start with Test and Production. |
| API Keys | Keys belong to a Site and one of its Environments. They authorize selected Workflows and, for user-based keys, selected users. |
| Users and permissions | Site roles control which Site features a user can access. Optional Environment-scoped permissions further restrict the Environments available to that user. |
| Configuration and operations | Configuration variables, key-value data, relationships, metrics, logs, and audit records carry Site context. Environment-aware state also carries an Environment key. |
Apps are owned by an Account and assigned to Sites. Assigning an App makes it available in that Site's Console navigation; it does not transfer App ownership or grant access to every Workflow.
Site, Tenant, Account, and Environment
A Tenant contains one or more Sites and provides the wider identity and platform context. An Account subscription allocates licensed features and capacity to Sites. A Site then provides the working boundary for the solutions that use that allocation.
An Environment is not a smaller Site. It is a stage within a Site. Workflow and Connection identities remain Site-scoped, while values such as published Workflow revision, status, Connection credentials, API Keys, hostname, and allowed browser origins are Environment-specific.
Access and isolation
Site permissions determine whether a user can list, read, change, or administer Site objects. Security Groups collect those permissions into roles that can be assigned to users.
When Environment-scoped permissions enabled is off, a user's Site role applies across the Site's Environments. When it is on, the user must also be assigned access to the relevant Environments. This additional scope affects the Console and user-based API authorization.
Keep Workflow and Connection permissions least-privileged even when a Site has a small user group. An App assignment, shared folder, or Environment name is not an authorization grant.
Site identity and settings
Every Site has an immutable Site key used in routes, tools, and persisted relationships. The editable Site name is for people and does not replace the key. A Site also stores a description, time zone, version-control configuration, Release Management mode, and its Environment list.
Open Settings → Site settings to manage these values. See Site Settings for every field and action.