> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ledgerup.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Permissions and approvals

> What Ari is allowed to do in your billing system, and who decides.

<AccordionGroup>
  <Accordion title="Can Ari change data in my billing system on its own?">
    Not unless you grant it. Ari is the AI agent inside LedgerUp, and its tools come in two kinds that behave differently by default:

    * **Read tools** (looking up an invoice, checking whether a customer has paid) are available by default.
    * **Action tools** (anything that writes, sends or changes a record) are **denied by default** and stay denied until someone grants them.

    Where an action tool has been granted, the normal pattern is that Ari proposes the change and a person approves it before anything is written.

    <Warning>
      Some workflows carry their own approval switch on top of that, subscription schedules, for example, have a **requires approval** setting that makes a person sign off on each invoice before it bills. Check that setting for any workflow you want a human in the loop on, rather than assuming every action pauses for approval.
    </Warning>
  </Accordion>

  <Accordion title="How do I control what Ari can do?">
    Permissions for Ari are set per tool and per connected integration, so you can allow it to update customer records while blocking it from creating products.

    They also apply at more than one level. A permission can be set for your whole company, for a specific Slack channel, or for an individual person, and **the most specific setting wins**. This is how teams give a collections channel a narrow set of tools while leaving a finance channel wider.

    Integrations work on the same principle: one that hasn't been permitted is denied rather than assumed.
  </Accordion>

  <Accordion title="Who on my team can change settings?">
    LedgerUp has four roles:

    | Role       | Access                                                               |
    | ---------- | -------------------------------------------------------------------- |
    | **Owner**  | Full access, including team management. One per company.             |
    | **Admin**  | Full access including team and settings management.                  |
    | **Editor** | Can create, edit and delete, but cannot manage the team or settings. |
    | **Viewer** | Read-only.                                                           |

    Settings, permissions, API access and team management are limited to owners and admins.
  </Accordion>

  <Accordion title="How does Ari sign in to a customer or vendor portal?">
    Credentials are stored in the vault under **Ari settings → Vault**, and Ari uses them only for the portal they belong to.

    <Tip>
      If Ari reports that it cannot submit an invoice to a portal, a missing vault entry is the first thing to check.
    </Tip>
  </Accordion>

  <Accordion title="Can I share an Ari conversation with a teammate?">
    Not from inside the platform today. Your conversations with Ari in the web app are private to you.

    For anything collaborative, work with Ari in your shared Slack channel instead, the thread is visible to everyone in the channel, so colleagues can read the reasoning and pick up where you left off.
  </Accordion>
</AccordionGroup>