A scope is a permission you grant to your Sellsy Oauth2 application. The connector asks for 16 of them, and each one unlocks a precise part of the synchronization: a missing scope does not break the connection, it silently takes the matching data out of reach.
| Scope | What it unlocks |
|---|---|
companies.read, companies.write |
Customers and suppliers, as Splash ThirdParty |
contacts.read, contacts.write |
Contacts and their addresses, as Splash Address |
items.read, items.write |
The catalog, as Splash Product |
invoices.read, invoices.write |
Invoices, their rows and their status |
orders.read, orders.write |
Orders, read to link them to the invoices |
taxes.read |
Vat rates, to apply the right one on each row |
payments.read, payments.write |
Payments recorded on the invoices |
scopes.read |
Lets the connector check its own permissions |
webhooks.read, webhooks.write |
Lets the connector install the webhooks that push your Sellsy changes to Splash |
The connector configuration page carries an Api access scopes panel. It lists what the connector requires, and above all what is missing on your application. An empty list means you are good.
[!TIP] Granting a scope on your Sellsy application is not enough on its own: the token already issued does not gain it. Click connect again so Sellsy issues a new one.
[!NOTE] The connector never asks for more than the table above — no access to your emails, your agenda or your staff.