Skip to content

Instance Team

Every instance has a team of users and groups responsible for planning and executing the procedure. The instance team determines who can perform which actions during execution.

Instance team members are assigned one of five roles, listed from highest to lowest privilege:

RoleDescriptionKey permissions
HeadInstance owner and overall responsible partyFull control: edit all properties, manage team, control lifecycle status, execute steps, force-complete steps
Deputy HeadActs on behalf of the Head when neededNearly full control: manage team (except Head assignments), edit properties, control status, execute steps
EditorSupports planning and documentationEdit notes and comments, edit draft instance properties
ExecutorExecutes procedure stepsStart, complete, pause, resume, skip, and abort assigned steps; add step comments
ObserverMonitors progress (read-only)View all instance data, add comments
  1. Open the instance detail page.
  2. Click the Team tab.
  3. The team management panel shows all current team members.

Instance team members come from two sources:

When an instance is created from a published template version, all version team members are automatically added to the instance team. These members:

  • Are marked with a From Template source badge.
  • Cannot be fully removed from the team — only deactivated or reactivated.
  • Deactivating a template-sourced member prevents them from executing steps but preserves the audit trail.

Additional members can be added directly to the instance team. These members:

  • Are marked with an Instance source badge.
  • Can be fully added and removed as needed.
  • Are not constrained by the template version’s team roster.
  1. Click the Add Member button on the Team tab.
  2. A search dialog opens where you can search for users or groups by name.
  3. Select the member type (Person or Group).
  4. Select the desired role (Head, Deputy Head, Editor, Executor, or Observer).
  5. Click Add to add them to the instance team.

For template-sourced members, use the context menu (right-click or three-dot menu) to:

  • Deactivate — Prevents the member from performing actions. Shows a “Deactivated” status badge.
  • Reactivate — Restores the member to active status.

Deactivation records:

  • Who deactivated the member.
  • When the deactivation occurred.
  • If reactivated: who reactivated and when.

Instance-specific members can be fully removed:

  1. Right-click on the member row (or click the three-dot menu).
  2. Select Remove.
  3. Confirm the removal.

To change a member’s role:

  1. Open the member’s context menu.
  2. Select a new role from the available options.
  3. The role change takes effect immediately.

The team tab shows a data grid with the following columns:

ColumnDescription
NameUser display name or group name
TypePerson or Group icon
RoleCurrent team role (Head, Deputy Head, Editor, Executor, Observer)
SourceHow the member was added (From Template or Instance)
StatusActive or Deactivated
Added ByWho added this member
Added AtWhen the member was added

Team membership directly affects step execution authorization:

  • Steps configured with All Team Members responsibility can be executed by any active Executor on the team.
  • Steps configured with Specific Members responsibility can only be executed by the designated users or group members.
  • The Head and Deputy Head can always execute any step, regardless of responsibility settings.

The team tab receives real-time updates via SignalR. Changes made by other users (adding members, changing roles, deactivating) appear immediately.

ActionRequired role
Add team membersHead, Deputy Head
Remove instance-specific membersHead, Deputy Head
Deactivate template-sourced membersHead, Deputy Head
Reactivate template-sourced membersHead, Deputy Head
Assign Head roleHead only
Assign other rolesHead, Deputy Head