Skip to main content
You decide what Ari can reach. This page covers the systems he connects to, what each connection lets him see and do, and how to manage access over time.

​
Connected systems

Ari queries your systems live at request time. He doesn’t cache data or rely on periodic syncs, so answers reflect what’s true right now.
Live queries are the trade-off for accuracy: first answers typically take a few seconds while Ari fetches current data. If an invoice was paid five minutes ago, he knows.
Need something not listed here? The Enterprise tier supports additional integrations beyond this list. Reach out at [email protected] and tell us about your stack.

​
Connecting a system

1

Open the control panel

Message Ari privately: @Ari settings. He sends you a link to the LedgerUp control panel; log in with your LedgerUp credentials.
2

Authorize the integration

Go to Integrations, choose the system, and authorize access through that system’s own login. You choose the account and confirm the permissions being granted.
3

Verify it works

Back in Slack, ask a question only that system can answer: @Ari how many customers do I have in Stripe?
Start with your billing system (Stripe or Chargebee), then add CRM, accounting, and document integrations as your workflows need them.

​
Access is scoped

  • Write actions are approval-gated everywhere. Connecting a system grants Ari read and write access, but every write still passes through your approval.
  • Contracts are permission-scoped. Documents are stored encrypted, and team members can only view contracts for customers they have access to.
  • Payment data stays in Stripe. Ari never sees raw card numbers; payment methods are tokenized in line with PCI requirements.
  • Approver permissions. Team members with finance or admin permissions can approve actions; this is configured in your workspace settings.

​
Managing and removing access

Access is managed in the same Integrations page of the LedgerUp control panel: reconnect an expired authorization, switch accounts, or disconnect a system entirely. Disconnecting removes Ari’s ability to read or act in that system immediately.
If Ari can’t answer a question you expect him to handle, check here first: the relevant integration may not be connected, or its authorization may have expired. See Troubleshooting.