Accounts and API Audit
Accounts is the control plane for ASA connectivity in ASAPilot. It is where you finish setup, refresh metadata, choose access mode, and persist the app boundary used by Chat and Automations.
Connection statuses
- • Pending setup: Apple credentials are not verified yet.
- • Select apps: credentials are verified, but managed app scope has not been saved.
- • Connected: verified and has at least one selected app.
- • Paused: scope is retained, but the connection is excluded from default chat scope and new automations.
What each account view is for
Overview
Review connection health, sync freshness, discovered organizations, and metadata at a glance.
Apps
Inspect discovered app inventory per connection and compare it with the current managed app scope.
Config
Rename the connection, switch between read-only and managed mode, and save the exact app scope ASAPilot may use.
Audit
Inspect API request volume, failures, and endpoint-level logs when debugging Apple-side or auth-side issues.
Scope model
ASAPilot no longer saves organization-only scope. The saved boundary is the selected app list. Organization grouping is only a browsing aid inside the UI.
Canonical sources
Frequently asked questions
What does the Paused state change?
Paused preserves the saved scope but removes that connection from the default chat scope and new automations.
What boundary is actually saved for an account?
The durable boundary is the selected managed-app list, not an org-only placeholder.
Where do I inspect Apple API or auth issues?
Use the Audit view to inspect request volume, failures, and endpoint-level logs.