New to BotPM? Start with the User guide and FAQ for customer-facing answers. This hub adds deeper setup, integration, API, and operator material.
A product of Dritarr INC, Canada
Use these references when configuring autonomy policies, integrations, support workflows, and release readiness. They can be mirrored into your customer help center or shared with implementation teams during onboarding.
| Audience | Path (in repo) |
|---|---|
| Customer — autonomy | docs/BOTPM_AUTONOMY_MODES_CUSTOMER.md docs/BOTPM_AUTONOMY_MODES_ONE_PAGE.md |
| Customer — PM activity grid (128) | BotPM.ai product → PM activity grid (Assist / Operate / Lead + depth; synced from docs/PM_ACTIVITIES_AUTONOMY_MATRIX.md) |
| Customer — org admin policy | docs/BOTPM_ORG_ADMIN_POLICY_CUSTOMER.md |
| Integrator / API | docs/BOTPM_INTEGRATOR_API.md |
| Enablement index & RC checklist | docs/DOCUMENTATION_ENABLEMENT_RELEASE_READINESS.md |
| Support (first weeks) | docs/SUPPORT_FIRST_TWO_WEEKS_PLAYBOOK.md |
Operators: set NEXT_PUBLIC_SUPPORT_L1_CONTACT (and optional …_L2_…, …_ONCALL_…, NEXT_PUBLIC_RC_NOTES_URL) to show this train's escalation paths here and in the Help drawer—without a separate help-center publish step.
Stripe & billing (operators): docs/STRIPE_DEPLOYMENT_CHECKLIST.md (webhook URL, secrets, staging vs prod) and scripts/verify_stripe_env.py. In-app billing uses POST /organizations/{id}/billing/create-checkout-session and …/billing/portal when configured.
API reference snapshot: docs/contracts/openapi-v1.json (regenerate via scripts/export_openapi.py per docs/API_RC_CONTRACT_FREEZE.md).
Use this section to confirm release evidence, rollout checks, support readiness, and operational runbooks before a customer-facing launch or major tenant rollout.
| Topic | Path (in repo) |
|---|---|
| Staging → RC → UAT → prod | docs/STAGING_UAT_GOLIVE_RELEASE_READINESS.md |
| Testing / RC definition | docs/TESTING_RELEASE_READINESS.md |
| RC sign-off + migration drill logs | docs/RC_SIGNOFF_LOG.md docs/MIGRATION_DRILL_LOG.md |
| UAT evidence | docs/UAT_SIGNOFF_LOG.md |
| Performance sign-off (staging) | docs/PERFORMANCE_RELEASE_READINESS.md · docs/PERFORMANCE_SIGNOFF_LOG.md · scripts/performance_release_gate.py |
| RC automation entrypoint | scripts/rc_release_gate.py |
| Deployment + rollback | docs/deployment-runbook.md |
| Security review + go/no-go inputs | docs/SECURITY_REVIEW_CHECKLIST.md |
| Manual UAT / smoke scripts | docs/smoke-manual.md · docs/beta-test-script.md |
| Staging dry-run | docs/deployment-dry-run.md |
| Pilot — known limitations (one page) | docs/PILOT_KNOWN_LIMITATIONS.md |
Pilot support: confirm the configured support contacts and share known limitations through your help center, onboarding email, or customer wiki.
Autonomy levels control what bots can do directly versus what needs approval. Browse the full PM activity grid (128 rows).
| Level | Behavior | Approval Path |
|---|---|---|
| ASSIST | Insights and recommendations only. | No direct execution. |
| OPERATE | Executes approved low-risk actions. | Policy-driven checks before execution. |
| LEAD | Generates strategic proposals. | Human approval required. |
Use organization settings to upload custom templates, define PMO overrides, and set default autonomy.