Partner Playbook – Platform Adoption¶

This document guides partners on adopting ConnectSoft platforms (Identity, Audit, Config, Bot) for customers. It is written for partners integrating platforms and ConnectSoft team members supporting partners.

Platform adoption enables partners to leverage ConnectSoft's ready-made platforms instead of building custom solutions. This playbook provides step-by-step guidance for successful platform adoption.

Tip

Use platforms instead of building custom solutions. Platforms are production-ready, well-tested, and integrate seamlessly with Factory-generated services.

Note

ConnectSoft is expanding from 4 to 100+ platforms across 12 categories. While currently focusing on Identity, Audit, Config, and Bot platforms, many more platforms are coming. See: Platform Categories Overview and Platforms Roadmap for the expansion plan.

Platform Use Cases¶

Platform	Typical Customer Scenario	Partner Role
Identity Platform	Customer needs multi-tenant authentication, user management, RBAC	Integrate Identity Platform, configure OAuth2/OIDC, set up user management
Audit Platform	Customer needs audit logging for compliance (SOC2, GDPR)	Integrate Audit Platform, configure audit events, set up retention policies
Config Platform	Customer needs feature flags, tenant configuration, A/B testing	Integrate Config Platform, configure feature flags, set up tenant settings
Bot Platform	Customer needs conversational interface, customer support bot	Integrate Bot Platform, configure channels, set up bot workflows

Discovery and Scoping¶

Discovery Questions¶

Identity Platform: - [ ] Do you need user authentication? - [ ] Do you need multi-tenant user management? - [ ] Do you need RBAC? - [ ] Do you need external IdP federation? - [ ] How many users do you expect?

Audit Platform: - [ ] Do you have compliance requirements (SOC2, GDPR, HIPAA)? - [ ] Do you need audit trails for user actions? - [ ] Do you need audit logging for system events? - [ ] How long do you need to retain audit logs? - [ ] Do you need SIEM integration?

Config Platform: - [ ] Do you need feature flags? - [ ] Do you need tenant-level configuration? - [ ] Do you need A/B testing capabilities? - [ ] Do you need configuration versioning? - [ ] How many configuration keys do you expect?

Bot Platform: - [ ] Do you need conversational interfaces? - [ ] What channels do you need (Slack, Teams, web chat)? - [ ] What use cases do you have for bots? - [ ] Do you need AI-powered responses? - [ ] Do you need bot analytics?

See: Platform Adoption Checklist for detailed checklist.

Implementation Steps¶

Step 1: Platform Provisioning¶

Activities: - Provision platform tenant(s) - Configure tenant settings - Set up authentication and access - Configure initial settings

Checklist: - [ ] Platform tenant provisioned - [ ] Tenant settings configured - [ ] Access credentials obtained - [ ] Initial configuration completed

See: Getting Started with Platforms for platform setup.

Step 2: Service Integration¶

Activities: - Integrate services with platforms - Configure API clients - Set up authentication flows - Test integration

Checklist: - [ ] Platform APIs integrated - [ ] Authentication configured - [ ] API clients tested - [ ] Integration validated

See: Integration Overview for integration patterns.

Step 3: Configuration and Customization¶

Activities: - Configure platform settings - Set up feature flags (Config Platform) - Configure audit events (Audit Platform) - Customize platform behavior

Checklist: - [ ] Platform settings configured - [ ] Feature flags set up - [ ] Audit events configured - [ ] Customization completed

Step 4: Testing and Validation¶

Activities: - Test platform integration - Validate functionality - Test error handling - Performance testing

Checklist: - [ ] Integration tests passing - [ ] Functionality validated - [ ] Error handling tested - [ ] Performance acceptable

See: Testing Strategy for testing guidance.

Step 5: Deployment and Handover¶

Activities: - Deploy to production - Set up monitoring - Customer training - Documentation delivery

Checklist: - [ ] Production deployment completed - [ ] Monitoring configured - [ ] Customer trained - [ ] Documentation delivered

Testing and Handover¶

Testing Requirements¶

Integration Testing: - [ ] Platform APIs work correctly - [ ] Authentication flows work - [ ] Error handling works - [ ] Performance is acceptable

End-to-End Testing: - [ ] Complete user flows work - [ ] Platform integration works end-to-end - [ ] Error scenarios handled - [ ] Customer acceptance testing passed

Handover Requirements¶

Documentation: - [ ] Platform integration guide - [ ] API documentation - [ ] Configuration guide - [ ] Troubleshooting guide

Training: - [ ] Customer team trained - [ ] Support contacts provided - [ ] Documentation reviewed - [ ] Questions answered