What you can deliver
Connect the PSA you run
Five real adapters — HaloPSA, Autotask, Syncro, Atera and NinjaOne — not a generic webhook. Authenticate once, then choose the board or queue new tickets land in.
Field & company-site mapping
Match each SBCMSP customer to its PSA company so every ticket files under the right client. Finding title, severity, evidence and fix steps flow into the ticket's summary and detail fields.
Severity → priority mapping
Each finding's severity is translated to your PSA's native priority — Critical to P1 through Low to P4 — so the queue sorts itself the way your techs already triage.
Auto-create & auto-close
A ticket opens the moment a finding is detected and closes automatically once the next scan verifies the fix. Creation is idempotent and de-duplicated, so one finding never spawns a pile of tickets.
Slack & Teams alerts
Route the same events to Slack or Microsoft Teams alongside the PSA. Repeat alerts for the same finding are suppressed within a configurable window, so channels stay signal.
Least-privilege credentials
SBCMSP holds only a scoped key limited to filing and updating tickets — no standing admin rights in your PSA, and nothing it can use to reach further into your stack.