Settings And Ownership

Forge separates settings by ownership. Select the correct workspace and project before changing a resource.

Account Settings

Account settings belong to the signed-in person. They include profile information, password, MFA, recovery codes and personal sessions. Account settings do not grant access to a workspace or project.

Workspace Settings

Workspace settings apply to one tenant workspace. Depending on your returned permissions, they include:

• workspace name and membership;
• invitations and workspace roles;
• workspace GitHub connections;
• workspace DNS provider connections;
• workspace security policy;
• billing and usage when enabled.

A person can belong to multiple workspaces. The workspace selector changes the active authorization and resource boundary; it does not merge projects from different workspaces.

Project Settings

Project settings apply to one application boundary. They include project membership, project-owned domains, email resources and project defaults. Services and databases in another project are not visible through these settings.

Service Settings

Service settings apply to one application or data service. They include source or image configuration, runtime commands, variables, domains, deployments, logs and supported backup settings.

Variable management and variable reveal are separate permissions. A role allowed to replace a secret may still be unable to read its current value.

Platform Settings

Forge Cloud platform settings are controlled by Forge operators on a separate hostname and identity realm. Tenant accounts cannot use that console, and customers do not need to configure Forge’s control-plane domains, provider credentials, system email route, software updates or infrastructure recovery.

Platform configuration never replaces workspace or project authorization. Contact Forge support when a platform dependency prevents a customer action.