Administration

Organizations And Grid Permissions

Share the right grids with the right people.

The public homepage is /. The workspace is /app; sign-in and registration are /login and /signup.

A user identity can belong to multiple tenants. Registration asks for an Organization Name and creates that tenant with the new user as its owner. The next screen asks for the first grid name; no grid or equipment is created automatically. Unfinished setup resumes on the next visit. Existing saved workspaces are preserved. The tenant creator retains ownership. Tenant administrators can rename the tenant, invite/remove members and manage grid permissions. Removing a member does not delete tenant equipment or other records.

Use Tenants in the workspace header to switch tenants or create another one. Open Tenant Settings → Members And Grid Access to create an invitation or change access. Invitations are email-bound, single-use links valid for seven days. Share the generated link yourself; no email is sent automatically. A recipient signs in or registers with the invited email, then accepts the link. Their existing tenants remain available. Public registration opens after the installation's first-administrator setup is complete.

Grid Access

LevelBehavior
HiddenGrid, equipment, drawings, feeds and associated activities are excluded from responses and streams.
View OnlyObserve the grid and permitted video feeds. No edits or controls.
EditChange grid equipment, layout, wires, drawings, local templates and variables. Use approved service controls and grid automation targets.
Grid AdministratorEdit access plus grid naming/removal and grid access grants for existing tenant members, limited to that administrator's grids.
Tenant Administrator / OwnerAll grids and tenant-wide configuration, integrations, sources, credentials and membership.

New members receive no grid access unless explicitly granted. Tenant administrators have all-grid access. Grid administrators cannot promote tenant administrators, invite users into the tenant, alter the owner, or grant access outside their own grids. Membership/access changes revoke the affected user's sessions, including active console and activity connections. That user signs in again to receive the new permissions.

Active checks, agent assignments, reusable scripts, integrations and credentials are tenant-administrator configuration. Grid editors can configure manual/pushed observations and use existing approved service targets; they cannot redirect checks to arbitrary systems or edit shared integration credentials. Interactive consoles require edit access to a grid containing their playback placement. Video feeds can be viewed with view-only access. New source assignments are managed by tenant administrators; grid editors can reuse sources already exposed in their visible grids.

Custom Equipment Scope

The custom equipment editor includes Global Equipment · Available In All Tenant Grids. It applies to the reusable template, not a shared live device instance. Each placed device remains independent and belongs to one grid.

  • Checked: every grid in that tenant can use the template. Only tenant administrators can create/edit global templates.
  • Unchecked: the template appears only in its owning grid. Grid editors can create and edit local templates.
  • A grid-only template cannot be placed in another grid, including through API requests/imports. A global template cannot be narrowed to one grid while devices based on it remain in other grids.

Built-in equipment templates are available in every tenant. Custom templates, equipment and configuration never become global across tenants.

Agents, Collectors and Panel Execution

Every tenant has independent agent, telemetry and automation-event credentials. In Tenant Settings → Machine Credentials, generate a credential and copy it once. The database stores only its hash. Rotating a credential invalidates the previous credential of that type.

Configure the agent's server using the displayed tenant URL:

https://your-panel.example/t/TENANT_ID

The agent appends its endpoint to that URL. For pushed telemetry, post to /t/TENANT_ID/api/telemetry; for custom events use /t/TENANT_ID/api/automation-events, with the matching bearer credential. Site collector enrollment generates a tenant-specific server URL automatically. Keep your local agents and collectors on a supported version.

Use a site collector inside your network for private checks and device access. Hosted execution is a service capability managed by Sysavia; contact support if you need it enabled. Grid administrator access does not grant access to the hosting infrastructure.

Use System Connections for your organization’s equipment credentials, or configure credential references on your own collector. Being an organization administrator does not grant Sysavia staff access.

Sysavia handles the hosted panel and its streaming endpoints. Use the organization-specific URL shown in your downloaded collector profile.