Step 1
Create the organization
Create an account, sign in, and create the organization that should own repositories, members, billing, policies, reports, and MCP tokens.
Quick Start
Turn GitHub alerts into SLA-tracked remediation work.
Follow this sequence to connect repositories, create accountable queues, escalate overdue work, export evidence, and enable MCP where appropriate.
Step 2
Connect GitHub
Install the InstaSLA GitHub App, choose repositories, and run the first sync. Confirm each repository shows a last sync status before relying on reports.
Step 3
Configure SLA rules
Start with critical in 3 days, high in 7 days, medium in 30 days, and low in 90 days, then adjust for customer commitments or internal policy.
Step 4
Assign owners
Add repository, path, team, or manual owner mappings so remediation work has an accountable person or team before escalation starts.
Step 5
Review fix campaigns
Use campaigns to group repeated package or advisory work across repositories. Review owner, severity, earliest due date, and completion percentage.
Step 6
Set email escalation
Create email escalation policies for due-soon and overdue work. Use delivery logs to confirm whether reminders were sent, suppressed, or failed.
Step 7
Export evidence
Export alert evidence or compliance reports for the date range and organization scope that match the audit or customer request.
Step 8
Create MCP tokens
Create scoped MCP tokens only for compatible clients that need them. Use narrow scopes, token names, expiration, and audit logs.