Keep the signed contract exactly where your content already lives
Connect CLMS 360 to Box so contract documents, versions, and permissions stay in your existing content library — no duplicate copies, no separate access rules to manage.
Contracts live with the rest of your content, not beside it
Once Box and CLMS 360 are linked, contract files, versions, and permissions follow the same structure and access rules as everything else in your Box account.
No duplicate document copies
Contract documents live in Box as the single source of truth — CLMS 360 references the file instead of storing a separate copy.
Version history stays intact
Every redline and revision is a Box version, so the full drafting history is preserved without exporting side copies.
Permissions inherited automatically
Box folder and file permissions carry over to the contract record, so access control doesn't need to be set up twice.
Signed contracts file back automatically
Once a contract is fully executed, the completed document is stored back to the matching Box folder without manual upload.
Retention and legal hold compliance
Contract documents follow the same Box retention policies and legal holds already governing the rest of your files.
Admin-controlled folder mapping
Choose exactly which Box folders sync to which contract types, without engineering involvement.
Setup
Live in three steps
Connect once with OAuth, choose your folder mapping, and the sync runs in the background from then on.
Sync setup diagram
Authorize → Map folders → Sync, as a Box flow · 1000×625px · SVG/PNG
Connect your Box account
An admin authorizes the connection through Box's OAuth consent screen using your existing enterprise account. No API keys to generate or store.
Map folders and contract types
Match CLMS 360 contract types to Box folders, and choose whether documents are referenced in place or copied on execution.
Turn on sync
New and existing contracts start syncing immediately, with permissions and retention policies applied from day one.
Field mapping
What syncs, and which way
A sample of the default field mapping — every field is editable during setup.
Box field
CLMS 360 field
Direction
Status
Box file
contract.document
CLMS → Box
Live
Folder path
contract.folder_path
CLMS → Box
Live
File version
contract.revision_id
Box → CLMS
Live
Access permissions
contract.access_level
Box → CLMS
Live
Retention policy
contract.retention_policy
Box → CLMS
Live
Executed document
contract.signature_event
CLMS → Box
Live
Common questions
Box integration, answered
Does CLMS 360 store its own copy of the document, or reference the Box file?＋
By default, CLMS 360 references the file in place in Box. You can optionally configure a copy-on-execution rule for completed contracts if your process requires it.
Do Box permissions carry over automatically?＋
Yes. Folder and file-level permissions set in Box are inherited by the linked contract record, so access control only needs to be managed in one place.
Does this support Box Governance and legal holds?＋
Yes. Contract documents follow existing Box Governance retention schedules and legal holds without any separate configuration in CLMS 360.
Does this require a Box developer app or custom scripting?＋
No. The integration uses Box's standard OAuth 2.0 and platform APIs. No custom Box application or scripting is required for standard folder sync.
Can we control which folders sync, and how?＋
Yes. Every folder mapping is configured individually by contract type, and can be changed at any time by a CLMS 360 admin.
Ready to take control of your contracts?
Join enterprise legal, procurement, and sales teams running their entire contract lifecycle on CLMS 360.
