Teams & Systems

Teams and systems are what make the rest of the app useful.

Without them, RectifAI can still record incidents. With them, RectifAI can route, notify, and report with much better context.

Teams

A team represents a responder group or ownership group.

Examples:

• Platform
• SRE
• Customer Engineering
• Core Services
• Payments

Teams can be associated with integration-specific configuration such as:

• Jira project defaults
• Slack user groups
• PagerDuty escalation policies
• JSM Operations responder teams

Systems

A system represents a service, domain, product area, or technical component your organization cares about during incidents.

Examples:

• API Gateway
• Worker Fleet
• Billing Service
• Authentication Platform

Systems can be mapped to teams and can also carry integration-specific routing details such as:

• PagerDuty service mappings
• JSM Operations team mappings

Why this mapping matters

When systems are attached to an incident, RectifAI can use those mappings to:

• identify likely owners
• determine whether to trigger paging
• determine whether to notify chat groups
• improve reporting on which systems and teams absorb the most incident load

Recommended setup pattern

For most teams:

1. Create teams first
2. Create systems second
3. Link systems to the teams that own them
4. Add paging/chat configuration to the relevant team or system records

Practical advice

• Keep system names stable and recognizable
• Avoid using generic names like Backend unless that is a real operational unit
• Prefer one team of clear ownership over many overlapping owners when possible
• Review mappings after each major re-org or service split