Roles & Permissions
B2B integrations act as trusted external systems within a single organization. They can initiate operations and read data, but execution control is reserved for facility staff (via the web app) and authorized devices.
What B2B integrations can do
Section titled “What B2B integrations can do”| Action | Details |
|---|---|
| Manage subjects | Create and retrieve subjects and their associated sample containers |
| Create procedures | Submit storage or retrieval procedures — these start as PENDING and must be progressed by facility staff before execution |
| Read procedures | List and retrieve procedures, including their current status and associated containers |
| Read facilities | List facilities and their storage solutions within the authorized organization |
| Read storage inventory | Inspect the current inventory of any storage solution within an authorized facility |
| Read organization | Retrieve details of the authorized organization |
What B2B integrations cannot do
Section titled “What B2B integrations cannot do”| Restriction | Who Can |
|---|---|
Advance a procedure beyond PENDING (accept retrieval, assign RFID tags for storage) | Facility staff via web app |
| Start or complete procedure execution | Cryogenic devices only |
| Access data outside their authorized organization | Not permitted for any integration type |
| Create or modify facilities, storage solutions, or containers | Facility staff via web app |
Permission errors
Section titled “Permission errors”When an operation is not permitted:
{ "error": { "code": "FORBIDDEN", "message": "Insufficient permissions to perform this operation" }}