CT-Ops

Engineering Teams

Global CT-Ops settings for team ownership, DSUM membership, and incident ownership scopes.

The Engineering Teams settings page controls the teams that own incidents and daily stand-ups. Open it from Settings -> Engineering Teams at /settings/engineering-teams.

These settings directly affect DSUM: users only see DSUMs for teams where they are members, and DSUM calendar events use team membership as the participant list.

Access and scope

Only instance_admin and super_admin users can open the page or change team membership. Non-admin users are redirected to the dashboard.

Teams and memberships are instance-scoped. A team name must be unique inside the instance.

Create team

Use Create team when a new operational team needs its own incident ownership and DSUM board.

Field or control	Default	Validation	What it does
Name	Empty	Required, up to 80 characters; unique per instance	Team name shown in incidents, DSUM, calendar event titles, and ownership controls.
Description	Empty	Optional, up to 500 characters	Operator-facing context for what the team owns.
Members	None selected	Selected users must belong to the current instance	Initial team members. Members can see and edit the team’s DSUM when they also have write access.
Create team	Enabled after required fields validate	Requires administrator access	Creates the team, inserts selected memberships, writes an audit event, and refreshes incidents, DSUM, and the Engineering Teams page.

The member list contains active users in the current instance.

Existing team cards

Each existing team appears as a card with the team name, optional description, member checkboxes, and Save members.

Control	What it does
Member checkbox	Adds or removes the user from the team when the card is saved.
Save members	Replaces the team’s membership with the selected users. The backend accepts up to 100 member IDs for the update.

Removing a user from a team removes that user’s access to the team’s DSUM page and removes them from future DSUM calendar participant syncs. Existing DSUM items, actions, and comments remain in history.

DSUM effects

DSUM area	Effect
DSUM index	Shows only teams where the current user is a member.
Team DSUM page	Rejects direct access when the current user is not a member of the team.
Engineer list	Shows active users who are members of the selected DSUM team.
Action assignee fields	Lists active users in the instance, not only team members. Operators can assign helper engineers outside the team, but the DSUM page itself still requires team membership to open.
Calendar event participants	Uses the current team member list when the DSUM schedule is created or updated.

Use team membership deliberately. Adding a user gives them access to the team’s stand-up board; removing a user can make their assigned DSUM actions visible only to remaining team members unless the user is added back.