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

# Connecting SASBOSS to Neo

> Get Neo whitelisted by Access4, make a SASBOSS login for Neo, and save it in Neo

You connect SASBOSS once at the MSP level. One connection covers every client enterprise under your Access4 partner account.

## 1. Ask Access4 to whitelist Neo

The SASBOSS API answers only IP addresses Access4 has whitelisted. Email Access4 TAC at [tac@access4.com.au](mailto:tac@access4.com.au) and ask them to whitelist these three addresses for API access to your partner account:

```
74.235.25.90
52.5.41.248
44.196.4.206
```

Ask for all three: different Neo services use different addresses (see [IP Whitelisting](https://docs.neoagent.io/integrations/ip-whitelisting.md)). Until Access4 confirms, Neo cannot reach SASBOSS, and saving the connection fails with a message that says so.

## 2. Make a SASBOSS login for Neo

Make a login in SASBOSS for Neo, so you can change or remove Neo's access without touching a person's login. Its role decides what Neo can do, whatever Neo's own settings say:

* **reseller-admin** covers onboarding, offboarding and number changes.
* **reseller-superadmin** is needed only if Neo should release quarantined numbers.
* A call recording link is given only to an enterprise-admin or group-admin login, so Neo can list recordings but not play them with a reseller login.

## 3. Add the login in Neo

**1. Open Integrations**

In the Neo Dashboard, open **Integrations** and find the SASBOSS card, under Phone & VoIP.

**2. Save the login**

Choose your region (Australia and New Zealand, or United Kingdom), enter the login's user name and password, then click **Save settings**. Neo signs in to SASBOSS before saving, so a wrong password or a missing whitelist is rejected straight away with what to fix.

## 4. Turn SASBOSS on per agent

Open the agent, go to the Integrations section, and pick an access profile for the SASBOSS block, or set each area yourself:

| Area | Access levels you can pick | Notes |
| - | - | - |
| **Customers & Sites** | Disabled, Read Only, Read / Write | Enterprises, their groups (sites) and group settings. Read Only is enough for onboarding. |
| **Phone Numbers** | Disabled, Read Only, Read / Write | Your numbers, allocating them to a site and taking them back, porting. Turn on for onboarding and offboarding. |
| **Users & Services** | Disabled, Read Only, Read / Write | Users' extensions, Teams calling, hunt groups and SIP trunks. Turn on for onboarding and offboarding. |
| **Call Routing** | Disabled, Read Only, Read / Write | Forwarding, schedules, call rejection, BroadWorks Anywhere. |
| **Devices** | Disabled, Read Only, Read / Write | Desk phones on a user's service, your device inventory. |
| **SMS & Fax** | Disabled, Read Only, Read / Write | SMS gateway and eFax. A sent message reaches people outside your team. |
| **Call Records** | Disabled, Read Only | Call records, call centre statistics, call recordings. |
| **Billing** | Disabled, Read Only, Read / Write | Balances, invoices, payments and charges. |
| **Reseller Account** | Disabled, Read Only, Read / Write | New SASBOSS logins and domains. It has no reads, so Read Only allows nothing. |

See [SASBOSS API](https://docs.neoagent.io/agents/tools/communication/sasboss-api.md) for the profiles and the safety controls.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.