Skip to content
Connection Guide

Connect Swimlane Without Breaking the Audit Trail

Use this guide to connect Swimlane or confirm the export-based path that fits your environment. Aurora keeps source, timestamps, ownership, and collection history attached so the first run becomes reusable proof instead of one-off setup work.

Connector Summary
Connection typeDirect connection
CategoryIncident management
Checklist4 steps
Want help with rollout?
We'll confirm what can be automated, what stays export-based, and how to keep the first evidence record clean.

First-Run Checklist

Use this sequence to connect Swimlane and make sure the first collection lands cleanly.

  1. 1
    Create a dedicated Swimlane user with read access to the applications Aurora must inventory.
  2. 2
    Store base_url, username, and password securely and validate the documented /api/user/login flow before rollout.
  3. 3
    Confirm GET /api/app exposes the target applications and field metadata in the tenant.
  4. 4
    Keep record, logging, export, and write-capable surfaces out of this baseline.

Credentials and Secrets

The keys, secrets, or tokens Aurora uses to authenticate and collect proof.

password

Recommended Access

Aurora only asks for the minimum read access needed for collection and checks.

Access requirements depend on the collection mode and scope you choose.