Site Settings

Use Site settings in the Console to change Site identity, time-zone and security settings, manage Environments, and configure version control and Release Management.

Open Settings → Site settings. You need permission to read the Site to open the screen and permission to write the Site to save changes. Changing the Environment list also requires the relevant Environment administration permission and access to all current Environments.

Page actions

Action	Behaviour
Save changes	Saves the Site and its current Environment list. The action is available after both records have loaded.
Audit trail	Opens the Site's audit trail in a new tab. Use it to review recorded changes to the Site settings.

Site details

Field	Description
Site name	Required display name for the Site. The name is not used as the Site's persistent identity.
Site key	Read-only unique identifier. Use the copy control when a URL, API, or agent tool requires the Site key.
Description	Optional explanation of the Site's purpose or ownership.
Time zone	Time-zone selection used by time-based trigger Nodes. Trial Sites can receive a regional default; other provisioning paths can use UTC. Check the selected value before enabling time-based triggers.

After changing Time zone, allow five minutes for the change to take effect. Restart Workflows that use time-based triggers after that delay.

The Site name does not need to be unique within a subscription or across Flowgear; Enterprise Sites commonly use the company name. Workflow Logs always display times in the browser's local time zone rather than the Site time zone.

v1 Runtime time-based scheduling includes the Day Scheduler, Week Scheduler, and Month Scheduler Nodes.

Security

Environment-scoped permissions enabled adds Environment access to the Site's role-based permissions.

When you enable it:

• Your administrator user is granted access to every current Environment so you can complete the rollout.
• Other users need Environment assignments under Settings → Site users.
• Affected users must sign out and sign in again before the new permission scope takes effect.

This setting can depend on the Site's subscription features. See Site Environment for how the additional scope affects Console access and user-based API Keys.

Environments

The Environment list is shown in rank order. Each row displays its position, name, and hostname, or No host name when none is configured.

Available row actions depend on the Environment:

Action	Availability
Move up	Intermediate Environments can move toward the first Environment without replacing it.
Move down	Intermediate Environments can move toward Production without replacing it.
Remove Environment	Available for intermediate Environments only.
Edit Environment	Available for every Environment.

The first, rank-0 Environment is the Workflow authoring slot. The production-flagged Environment remains last. Clicking New Environment inserts a non-production Environment immediately before Production. Learn more opens the Site Environment article in a new tab.

Add or edit an Environment

The Environment dialog contains these fields:

Field	Description
Environment name	Required display name. The dialog can suggest another generated name. When editing, the Console warns that name and casing changes can affect integrations that refer to the Environment by name.
Branch name	Specifies the version control branch that the Environment is mapped to. Visible only when Version control mode is Github.
Host name	Complete hostname used to route HTTP and MCP requests to the Environment. It must be unique within the Site and is stored in lowercase and usually ends with .flowgear.net. Whitelabelled hostname is offered on certain subscriptions.
Allowed origins	Optional newline-separated browser origins. Use * only when all browser origins are intentionally allowed.
Environment key	Read-only identifier shown when editing an existing Environment.

Click Confirm to apply the dialog changes to the page, then click Save changes to persist them.

For Flowgear-managed hostnames, the dialog recommends:

Non-production: {customPrefix}-{envName}-{tenantKey}.flowgear.net
Production:     {customPrefix}-{tenantKey}.flowgear.net

After entering a hostname, create a support ticket to request the DNS entry. DNS changes normally become active within a few minutes. Request a controlled update window if you need a custom .flowgear.net domain.

Enterprise subscriptions can use a custom Production domain and supply its TLS certificate to Flowgear. Other subscriptions use a custom Flowgear subdomain. Confirm the available hostname and certificate options with Support when requesting DNS changes.

Flowgear always permits supported Console browser origins in addition to values in Allowed origins. See Site Environment before using a wildcard or configuring a standalone browser App.

Version control

Version control mode selects the Workflow revision store:

Option	Behaviour
Basic	Stores Workflow revisions in Flowgear-managed storage. Environment branch identifiers are managed internally.
Github	Stores Workflow revisions in the configured GitHub repository. Each Environment uses the Branch name from its Environment settings.

When you select Github, Repository URL becomes available and is required. Use an HTTPS repository URL on github.com or api.github.com. Each user who performs GitHub-backed Workflow operations also needs a configured personal access token. See Setting up a Version Control Token.

Release Management

Release management mode determines where a Workflow revision is published when you save it:

Option	Behaviour
Disabled	Publishes Workflow changes to every Environment on each save.
Enabled	Publishes changes to the first Environment. Use Manage releases in the Workflow designer to promote a revision to subsequent Environments. In GitHub mode, promotion uses a Git commit action between Environment branches.

Release Management is a subscription feature and is separate from the selected version-control store. See Release Management for the Workflow promotion journey.