How authentication works
The integration uses Box OAuth 2.0. The user authorizes Edict IQ in Box, and the connection is handled through the Edict IQ integration layer. Access tokens remain bounded by the authorized Box user and application scopes.
Box integration
Connect Box as a read-only document source for governed evidence workflows in Edict IQ. Access remains limited by the connected user's Box permissions.
Open your Edict IQ workspace, go to Settings > Integrations and choose Box. Edict IQ starts the Box OAuth authorization flow for your account.
Confirm the read-only access shown by Box. The connection remains subject to the permissions of the Box user who authorizes it.
Return to the integrations area in your Edict IQ workspace and complete the Box connection. Credentials and provider tokens are never displayed in the workspace UI.
Approved Box content can then be referenced in governed evidence workflows, while review state, ownership and audit activity remain managed in Edict IQ.
The Box application is configured for read-only content access. Administrative, Box Sign, Box AI and write permissions are not requested.
Read files and foldersNo write accessNo administrative accessNo Box Sign or Box AI accessThe integration uses Box OAuth 2.0. The user authorizes Edict IQ in Box, and the connection is handled through the Edict IQ integration layer. Access tokens remain bounded by the authorized Box user and application scopes.
To stop access, remove or disable the Edict IQ connection in your Edict IQ workspace, or revoke the application's access from Box. Revoked authorization can no longer be used for Box API access.
Contact Edict IQ Support at support@edictiq.com.