Team

Every template version has a team — a list of users and groups who participate in the template’s lifecycle. Team members defined at the template version level are automatically carried over to instances created from that version.

How template teams work

Template version teams serve two purposes:

1. Responsibility assignment — Steps can reference team members for responsibility settings (e.g., “only these specific members can execute this step”).
2. Instance team seeding — When an instance is created from a published version, the version’s team members are automatically added to the instance team.

Note

Team assignments are per-version, not per-template. Different versions of the same template can have different team compositions.

Accessing the team tab

1. Open a template version in the version editor.
2. Click the Team tab.
3. The team management panel displays all current team members.

Team member types

Team members can be:

• Individual users — Specific people from your tenant’s user directory.
• Groups — RAMP groups that contain multiple users. Adding a group adds all its members to the team.

Each member displays:

Field	Description
Name	User display name or group name
Type	Person icon for users, group icon for groups
Added By	Who added this member to the team
Added At	When the member was added

Adding team members

Adding individual members

1. Click the Add Member button on the Team tab.
2. A search dialog opens where you can search for users by name or email.
3. Select the desired user from the search results.
4. Click Add to add them to the version team.

Scaffold team (bulk operations)

For efficient team setup, use the Scaffold Team feature:

1. Click the Scaffold Team button (group add icon) on the Team tab.
2. Choose a mode:
   • Bulk add — Select multiple users and groups to add at once.
   • Copy from version — Copy the team roster from another version of the same template.
3. Configure your selections and click Apply.

Copy from another version

This is especially useful when creating a new version and wanting to start with the same team:

1. Open the Scaffold Team dialog.
2. Select Copy from version mode.
3. Choose the source version from the dropdown (shows all versions of the current template).
4. Click Copy to import all team members from that version.

The system reports how many members were added and how many were skipped (already on the team).

Removing team members

1. Right-click on a team member row, or click the three-dot menu icon on the row.
2. Select Remove from the context menu.
3. Confirm the removal in the dialog.

Caution

Removing a team member from a version may affect step responsibility assignments. If a removed member was designated as a responsible party for specific steps, those steps will need their responsibility reconfigured.

Team and step responsibility

Team members are the pool from which step responsibility is assigned. In the version editor, each step can be configured with:

• All Team Members — Any team member with the Executor role can execute the step.
• Specific Members — Only selected users or groups from the team can execute the step.

Only members currently on the version team are available for step-level responsibility assignment.

Locking on publish

When a template version is published:

• The team roster is locked along with all other version content.
• No further additions or removals are possible.
• The locked team is used as the basis for seeding the instance team when instances are created.

Real-time updates

The team tab updates in real-time via SignalR. When another user adds or removes a team member, the change appears immediately without refreshing the page.

Context menu

Right-clicking on a team member row opens a context menu with available actions. The three-dot menu on each row provides the same options. Available actions include:

• Remove — Remove the member from the version team (only on draft versions).

Relationship to instance teams

When an instance is created from a published version:

1. All version team members are copied to the instance team.
2. Instance team members are given roles (Head, Deputy Head, Editor, Executor, Observer).
3. Additional members can be added directly to the instance team.
4. Template-sourced members can be deactivated (but not fully removed) at the instance level.

See Instance Team for details on how instance teams work.

Related topics

Version Editor The workspace where team and steps come together

Steps & Variables Step responsibility and execution settings

Instance Team How template teams seed instance teams