Box

Overview
How to connect
Automated checks
Useful links

DSALTA connects to Box using read-only API access to collect compliance evidence automatically. Data feeds into your Data Library modules.

DSALTA only reads. Every request this integration makes is an HTTP GET against Box’s user endpoints. DSALTA has no code path that creates, modifies, or deletes anything in your Box environment.

DSALTA collects this integration’s data when you connect it — you can refresh it at any time with Sync from integrations on the Integrations page. The compliance checks below re-run once a day at 02:00 America/New_York.

What DSALTA reads

DSALTA reads the Box user roster — names, emails, roles and active status, which appears on your Access page.It calls these Box endpoints:

/2.0/users
/2.0/users/me

Permissions the checks require: manage_managed_usersEvery request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Box environment.

Troubleshooting

Integration shows Disconnected

There is no Reconnect button. Open Integrations → Connected, click Manage on the Box card, and check the Status tab — it shows either Connected and working properly or Connection issues detected. To restore a broken connection you must Disconnect and connect again, which permanently deletes the data and tests collected from Box. This usually happens when API tokens expire.

Data is not syncing

Verify the connected account still holds the permissions this integration requires. Then open Integrations in the DSALTA sidebar, stay on the Connected tab, and click Sync from integrations at the top right. That button refreshes every connected integration at once — there is no per-integration sync control.

DSALTA requests these scopes: manage_managed_users.Before you begin

Authorize as a Box admin or co-admin with user-management rights. DSALTA builds the Access page from Box’s enterprise user list, and Box requires that “the application and the authenticated user need to have the permission to look up users in the entire enterprise”. If you authorize with an ordinary Box account the connection still succeeds — it just returns that one user.

Open the integration

In the DSALTA sidebar, go to Integrations, find Box, and click Connect.

Authorize access

A secure Box window opens. Sign in if prompted and approve the request. DSALTA does not ask you to choose which resources to monitor — the connection covers everything the credential you authorize can read.

DSALTA's Link Box Account panel stating that a pop-up will open, with a Connect button

Once connected, Box appears on the Connected tab and the checks below begin reporting after the first sync.

Each check below re-runs once a day, at 02:00 America/New_York, while this integration is connected. Click any check for step-by-step remediation guidance.

Check	Severity	What it verifies
User access to Critical System should be valid	Info	Checks that everyone with Box access is an active employee on the People page.
Offboarded users should not have active access	High	Checks that offboarded employees no longer have active Box access.

Topic	Link
Setup	Box API — List enterprise users (GET /2.0/users)
General	Box website
DSALTA	Connection error messages

Getting Connected

Identity Providers

Cloud Infrastructure

Code Repositories

Security & Monitoring

Databases

SaaS & Productivity

What DSALTA reads

Troubleshooting

​What DSALTA reads

​Troubleshooting

What DSALTA reads

Troubleshooting