> ## Documentation Index
> Fetch the complete documentation index at: https://developer.box.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Plan your integration
> Assess whether your use case fits Box, then choose the application type that matches how your app runs.
export const Link = ({href, children, className, ...props}) => {
const localizedHref = localizeLink(href);
return
{children}
;
};
## Assess your use case
Content-centric processes perform best on Box. Ask yourself:
* Is content always involved in the process?
* Does the process involve:
* moving content from one place to another,
* collecting e-signatures,
* generating documents,
* automating multi-step review, approval, or routing workflows,
* answering questions about content or extracting metadata with AI,
* building purpose-built agents or custom AI extractions,
* publishing governed knowledge portals for teams or departments,
* classifying, protecting, or monitoring sensitive content for threats,
* or applying retention schedules, legal holds, or other compliance controls?
* Can the workflow abide by waterfall permissions?
* Does the process involve administrative tasks that may be automated?
If you answered **yes** to these questions, you most likely have a strong use case for Box.
Many teams also build on Box for **AI-first** workflows: agents that work across authorized content, curated knowledge shared at org scale, and documents generated from templates.
Common solutions include:
| Use case | Example Box products |
| -------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Agentic file system | Box MCP server and the Box AI API so agents search, reason over, and act on files a user can access; Box Agent Skills for building integrations with coding assistants; webhooks and events to trigger downstream automation. |
| Company Brain | Box Hubs as governed knowledge portals, Box AI Ask for permissions-aware answers across hub content, Box AI Studio for purpose-built agents, and metadata for structured context. |
| Team and department knowledge portals (Hubs) | Box Hubs API to create and populate portals programmatically, Box AI for natural-language search within a hub, and Box Embed to surface hubs in internal apps — see the sales RFP answer bank tutorial. |
| Template-based document generation | Box Doc Gen to merge structured data into Word templates and output PDFs; often paired with Box Sign for approval and signature — see the offer letter automation tutorial. |
| Marketing asset management | Box Hubs for curated libraries, metadata and search for discovery, and UI Elements for browse and preview experiences. |
| Secure document vaults | Box Shield for classification and threat detection, Box Governance for retention and legal holds, plus classifications on files and folders. |
| Content classification | Classifications to label files and folders by sensitivity, Box AI to suggest or auto-apply labels at scale, and Box Shield to enforce classification-based access policies and detect threats. |
| Wealth management portals | Custom Platform Apps with UI Elements or Box Embed, Box Sign for client agreements, and metadata for client or account context. |
| Automatic folder creation based on user provisioning | folders, users, and groups APIs, plus webhooks to react to user lifecycle events |
| Adding relevant metadata using AI | Box AI to extract or suggest metadata, Box AI Studio for custom agents. |
| Claim reviews with built-in approval and rejection flows | Box Relay for review workflows, Box Sign for approvals and signatures, and Box Doc Gen to generate claim or decision letters. |
| Event monitoring for security and auditing | events and webhooks for real-time activity, Box Shield alerts, and Box Governance reporting for retention and hold activity. |
Product availability depends on your Box plan and enterprise entitlements. Not every product is included on the free developer plan. See select the right plan for paid tiers and add-on products.
Still not sure if you have a good use case? Reach out to your Box account team or our sales team at [`sales@box.com`](mailto:sales@box.com).
## Choose an application type
Box applications support different capabilities and authentication options.
### Platform App
Platform Apps cover most use cases. They let you present Box functionality in a custom interface, including UI Elements for browsing, searching, and previewing content.
When you create a Platform App, you select an app type:
* **User** — for user-facing apps (OAuth 2.0)
* **Server** — for backend services using Client Credentials Grant or JWT
Platform Apps are a good fit when you need to access your own files and others' files, upload and download content, and optionally list the app in Box Integrations.
### Web App Integrations
Web App Integrations let third-party applications work inside the Box user experience. Users can edit, share, or modify Box content with your app, and you can surface the integration in Recommended Web Integrations in Box Preview.
## Publish your app
Box Integrations is where Box users discover apps that work with Box. Listing your app is an effective way to reach new users, especially for apps meant for other enterprises.
To publish, make sure your app is production-ready and uses OAuth 2.0. Submit it for approval in the Developer Console:
1. Select **Apps**.
2. Select **Submit for Approval**.
3. Fill out the form and select **Submit**.
Approved apps can appear in featured, most popular, or recently added sections.
For the submission checklist, required assets, and partner review process, see Box Integrations.
Non-OAuth integrations cannot use that listing flow as-is; the guide describes using an OAuth listing as a marketing redirect when needed.
Questions about publishing: [`integrate@box.com`](mailto:integrate@box.com).
## Next steps
* Submit your app to Box Integrations — review the full listing checklist, required assets, and partner review process
* Reach users inside Box with Web App Integrations
* Explore tutorials to build a working integration end to end