Audit and manage who accesses each Box from the BrainBox API
How to generate, from your systems, a report of who accesses each Box, and how to grant, change or remove access through the API.
Lesson 5 of 5 · 1:19
What it covers
Compliance needs to know who sees what. With the API, a system walks every Box and builds the report: each person, their role and pending invitations. And with the same endpoints you grant, change or remove access for workspace members, for example when someone joins or leaves a project.
Frequently asked questions
›How do I see who has access to a Box through the API?
With GET /boxes/{id}/acl: it returns the users with their role and the pending invitations.
›Can I give access to any email through the API?
Only to people who are already workspace members. Workspace invitations are done in the app.
›Does the API send emails when granting access?
Only if you ask for it with notify. By default it doesn't notify.
Transcript
0:00The report
Audit asks Andrés for a report of who has access to each contracts folder. Building it by hand is slow and goes stale. The API builds it in seconds.
0:13The code
The report is a loop. For each Box, you ask for its access list. And with the same endpoints you grant, change or remove access, without sending emails if you don't want to. Each Box returns its users, their role and pending invitations. One detail: through the API you only manage people who are already in the workspace.
0:37In Celtara Hub
In the Hub, Generate audit: it walks every Box in the workspace. And there's the report: each Box, each person, their role and status. Ready for the audit, and always up to date.
0:51Recap
To recap: with the access list you know who sees each Box and with what role, through the API you grant, change or remove access, always for workspace members, and without emails unless you ask. Andrés delivered his report in a minute. With BrainBox, you know who sees what, always.