Tools and Enterprise Integrations

Compound Leverage uses approved tools and integrations to complete Managed Team work and deliver finished artifacts. Customers are not required to adopt a new toolset.

Working through existing channels

Customers can assign work in meetings, by email, or through the optional Customer Portal. Deliverables may be provided through Compound Leverage systems or placed into a customer’s existing systems when authorized.

Integration options

Depending on the assignment and approved access, the Managed Team may use document repositories, enterprise applications, APIs, files, search, databases, and other tools. Integration is selected to support the requested work, not to require a customer-operated AI deployment.

Access and oversight

The THINK Strategist coordinates execution and quality review. Tools must operate within approved permissions, customer instructions, and applicable data-handling arrangements. Customer approval is required for consequential actions and commitments.

See Customer Access and Data Controls and Work Execution Layer.

Integration categories

Category	Example work	Access requirement
Document and file systems	Read sources and deliver reports	Approved folders, files, and identities
Repositories	Inspect, modify, or propose code changes	Authorized repository and change scope
Enterprise applications	Research, update, or analyze approved records	Application permissions and customer policy
APIs and MCP tools	Execute named capabilities	Provider availability and policy approval
Research sources	Collect supporting evidence	Approved sources and use constraints

Integration selection

Task need → Named capability → Approved provider → Authorized operation → Reviewed result

The THINK Harness documents capability mappings such as github_read and notion_read; these are examples of resolution, not a guarantee that each integration is active for every customer.

Troubleshooting

Problem	Check
Access denied	Identity, authorization, tenant, and resource scope
Data missing	Source availability and customer permission
Connector unavailable	Approved alternative or change in delivery plan
Write action requested	Whether modification is within the assignment
Production action requested	Explicit customer change authorization