Skip to main content
Zygo uses a multi-tenant architecture where every resource — flows, credentials, tickets, dashboards, and data — is scoped to a tenant. Users are invited to tenants and assigned roles that control what they can see and do.

Key Concepts

Users

A user account represents a single person. One user can belong to multiple tenants with different roles in each.

Tenants

A tenant is an isolated workspace. All resources live within a tenant, and data is never shared between tenants.

Roles

Roles control what a user can do within a tenant. Roles are hierarchical — higher roles inherit all permissions from lower ones.

Superadmins

Superadmins are platform-level administrators who can access any tenant and manage all users.

Role Hierarchy

Every tenant member is assigned one or more roles. Roles are cumulative and hierarchical:
RolePermissions
UserMinimal access. Can view and submit web forms only.
ViewerRead-only access to all tenant resources — flows, runs, tickets, dashboards, credentials (masked), data tables, and logs.
EditorEverything a Viewer can do, plus create, edit, delete, and run flows, manage credentials, records, tickets, and dashboards.
AdminEverything an Editor can do, plus manage tenant members, assign roles, and configure tenant settings.
A user with the Editor role automatically has all Viewer permissions. You don’t need to assign both.

What’s Next?

Managing Users

Invite users, update profiles, and deactivate accounts

Managing Tenants

Create tenants, configure settings, and manage membership

Roles & Permissions

Understand the role hierarchy and permission model

API Authentication

Authenticate API requests with tokens