Skip to main content
TYAN is built for teams. Whether you’re a CTO overseeing delivery, a QA lead maintaining a regression suite, or an engineer building flows for a new feature, everyone works from the same workspace — with the same real-time view of what’s passing, what’s failing, and what needs attention.

​
Workspaces

A workspace is the shared environment that groups all of your team’s flows, journeys, monitors, and integration settings under one roof. Every resource you create lives in the workspace, and every team member you invite can access it according to their role. To invite someone, go to Settings → Workspace → Members and enter their email address. They’ll receive an invitation link and can join immediately. You can invite as many team members as your plan allows.

​
Roles and Permissions

Each team member is assigned a role that controls what they can see and do inside the workspace.
The Owner has full, unrestricted access to the workspace. This includes managing billing, modifying the workspace name and settings, and permanently deleting the workspace. There is one Owner per workspace, and ownership can be transferred to another member.
Admins can do everything an Editor can, plus manage integrations (Slack, CI/CD, webhooks), invite or remove team members, and configure workspace-level notification settings. Assign this role to leads and senior engineers who need operational control without billing access.
Editors can create, edit, and delete flows and journeys, run flows manually, and configure monitors. This is the right role for engineers and QA team members who are actively building and maintaining the test suite.
Viewers have read-only access. They can browse flows, view run histories, and open reports, but cannot make changes or trigger runs. This role is ideal for stakeholders, product managers, and clients who need visibility into application health without the ability to modify anything.

​
Sharing Flows with External Stakeholders

Not every stakeholder needs a workspace account. For one-off visibility — sharing an acceptance test result with a client, for example — open any completed run and click Share Report. TYAN generates a read-only link that anyone can open in a browser, no login required. The link shows the full run detail: steps, results, timestamps, and failure screenshots. Shared links expire based on your workspace retention settings. You can also revoke a link at any time from the run detail page.

​
Notifications and Alert Subscriptions

Team members can subscribe to alerts for specific flows, journeys, or the entire workspace. To configure your personal alert preferences, go to Settings → Notifications and choose which events trigger an alert and through which channel — email or Slack. For workspace-wide alert routing (for example, sending all production monitor failures to a dedicated Slack channel), Admins can configure shared notification rules under Settings → Integrations.
Workspace membership, roles, and global notification rules are all managed in Settings → Workspace. Individual members can update their own notification preferences independently without affecting the team’s shared settings.

Workspace Settings

Manage team members, roles, workspace name, and data retention settings in one place.

Notifications

Configure personal and workspace-wide alert rules for flow failures, monitor results, and run completions.