Skip to content

Workspace settings

A Workspace is the tenant boundary for an application. Its Resource data, Files, Pages, Workflows, domains, brand settings, and users are isolated from other Workspaces.

System Administrators manage workspace settings from the workspace's System Admin area. Diagonal platform operators use the separate Control Panel for cross-workspace administration.

Domains

Every Workspace is available on its Diagonal workspace host and can have custom domains. The Domains settings page shows DNS status and lets you choose the primary custom domain.

  1. Add the domain exactly as it should appear in the browser.
  2. Apply the DNS records shown by Diagonal.
  3. Recheck DNS until the domain becomes active.
  4. Set an active custom domain as primary.

A Workspace can have several active domains but one designated primary custom domain. Pages, canonical links, and sitemap URLs use the primary domain, unless a Page is assigned to a specific active domain, in which case it serves on that domain instead. If the primary domain becomes inactive or is deleted, Diagonal updates the designation through the domain lifecycle; don't rely on an inactive domain as a fallback.

Brand Kit

The Brand Kit controls shared presentation used by workspace Pages and supported embedded experiences:

  • logos, favicon, and social sharing image;
  • light and dark color tokens;
  • typography and web fonts;
  • radius and shadow tokens;
  • design profile and theme preset;
  • SEO title and description defaults.

Save Brand Kit changes from the settings page. Pages that define their own values can override shared presentation, while Pages that use Brand Kit tokens receive the updated values.

Public brand assets should use Files intended for public delivery. Don't place private customer documents in logo, favicon, or social-image settings.

Email settings

Outbound emails enabled is a workspace-level switch. Turning it off prevents the workspace from sending outbound email even when email Workflows and provider configuration exist. Turning it on doesn't configure a sender or fix an invalid email integration by itself.

Use the switch when preparing or suspending a workspace without deleting its email Workflows.

Workspace values

Workspace Fields store shared application values such as name, default currency, sidebar presentation, homepage, email behavior, and custom configuration. Workflows, Pages, and Resolvers can read these values without hardcoding them.

Treat system Workspace Fields as platform settings. Custom fields are suitable for builder-owned configuration, but don't rename or repurpose a system key used by the runtime.

Child Workspaces

Some Workspaces are marked by Diagonal staff as parent Workspaces. Their System Administrators can create and manage white-labeled child Workspaces.

Creating a child Workspace creates an empty tenant, a team Resource named for the parent, and a blank homepage. It does not add a user automatically. From the child's detail page, add administrators and set an initial password so they can sign in immediately.

Only a Diagonal platform administrator or a System Administrator of the enabled parent Workspace can manage its children. Other Workspaces don't see these routes.

Import, export, and deletion

Platform operators can export a Workspace and import its definitions and Records through the Control Panel. Imports restore definitions before Records, then reconcile system Roles, Permissions, and indexes.

Permanent deletion coordinates PostgreSQL data, Mongo Resource data, Files, caches, and dependent module cleanup. It isn't an archive and can't be undone from the workspace UI.

Permanent deletion

Export anything that must be retained before a platform operator deletes a Workspace. Removing a Workspace row or domain is not a safe substitute for the coordinated deletion operation.

Control Panel versus System Admin

Surface Who uses it Scope
Workspace System Admin A permitted Resource identity One Workspace's Resources, Pages, Workflows, settings, domains, and Media Library.
Diagonal Control Panel A platform User with operator access Workspaces and platform Users, package library operations, impersonation, execution/email/conversation inspection, tokens, and AI evaluations.

The two surfaces use separate accounts and logins. A Workspace System Administrator isn't automatically a Control Panel user.