Skip to main content
Your workspace is the central hub for your entire team — every flow, monitor, integration, and setting lives here. Whether you’re onboarding a new engineer or rotating an API key, all workspace-level configuration is accessible from Settings → Workspace.

Workspace Settings

From Settings → Workspace, you can configure the foundational properties that apply across all flows and monitors in your workspace.
  • Workspace name — the display name shown across the dashboard and in notification messages.
  • Workspace slug — a URL-safe identifier used in your workspace’s unique TYAN URL. Changing the slug updates all shared links.
  • Default production URL — the base URL prepended to relative paths in all your flows. Set this once and every flow inherits it automatically.
  • API key management — view active keys, rotate a key to issue a replacement, or revoke a key to invalidate it immediately.

Team Members

Invite your team so everyone has the right level of access to flows, monitors, and reports.

Invite a team member

1

Open the Members panel

Navigate to Settings → Workspace → Members.
2

Enter the email address

Type the invitee’s work email address into the Invite by email field.
3

Assign a role

Choose the appropriate role from the dropdown (see the roles table below).
4

Send the invite

Click Send Invite. The invitee receives an email with a link to join your workspace. The invitation expires after 72 hours.

Roles and capabilities

RoleCapabilities
OwnerFull access, billing management, delete workspace
AdminManage flows, monitors, and integrations; invite and remove members
EditorCreate and edit flows, trigger manual runs
ViewerView run results and reports only
Only the workspace Owner can change billing settings or delete the workspace. Transfer ownership in Settings → Workspace → Danger Zone before removing the current Owner.

Remove a team member

Navigate to Settings → Workspace → Members, locate the member’s row, and click Remove. Removed members lose access immediately. Any flows or monitors they created remain in the workspace.

API Keys

API keys are workspace-scoped — a single key grants full API access to everything in that workspace, including triggering runs, reading results, and managing monitors programmatically. To create a new key, go to Settings → Workspace → API Keys → Create Key. Give the key a descriptive label (for example, ci-pipeline-prod) so you can identify it later.
Never commit API keys to source control. Store them in environment variables or a secrets manager such as AWS Secrets Manager, HashiCorp Vault, or your CI provider’s secret store. Rotate any key you suspect has been exposed.
Each key is displayed once at creation time. Copy it immediately — TYAN does not show the full key again after you close the dialog. If you lose a key, revoke it and create a replacement.