Configuration guides streamline the deployment of Box and your solution. We strongly encourage all partners to create configuration guides to provide our joint customers with the highest level of service and satisfaction.
When creating your deployment guide, please consider and answer the following questions:
Deployment
1. List types of resources required, activities, and time commitment from each for the following:
- Box Resources
- Partner Resources
- Customer Resources
2. What is the typical time required for an implementation?
- If time varies, what are the factors that can extend a timeline?
3. What are the technical prerequisites to getting the solution set up?
4. What is your implementation methodology?
- Is there a sample project plan with activities?
5. Does your integration have a global API key used across all Box customers?
- What API scopes are associated with that API key?
- How does the app handle rate throttling?
- If it is not a global key, what API scopes are required for the customer specific API key?
6. What functionalities can you perform in Box?
- For each piece of functionality, can you elaborate on the API calls used to accomplish this?
7. What kind of account is required in order to perform functions (Admin vs Co-Admin)?
- If main Admin, why?
- If Co-Admin, what specific permissions are required on the Box side to enable full functionality?
Limitations
1. What are the known limitations of your solution's Box integration?
2. Which of these limitations are on the roadmap for resolution? Can you provide rough ETAs?
3. Which limitations will not be resolved?
4. What is generally on the product roadmap?
5. What does your support process look like?
