AMP30
Multi-Tenant Rollout & Implementation Factory
Package template prompts, playbooks, automation policies, connector metadata, grants, module flags, seed packs, and acceptance scenarios into a customer launch packet. The assistant drafts the plan; humans approve the rollout.
Step 1
Choose pilot
Name the target tenant slug and inspect source template assets.
Step 2
Validate readiness
Check grants, module flags, demo packs, connector secret handling, and scenarios.
Step 3
Queue launch
Review onboarding and rollback steps before any copy or enablement work.
Assets
6
Role grants
62
Modules
7
Readiness
60
Gaps
2
Live Rollout Preview
Target New Customer Pilot · score 60/100 · BLOCKED · copyable assets 5 · secret metadata 0
Rollout factory score is 60/100 for New Customer Pilot from template tenant Demo Company. 6 template assets, 1 role grant gap, 1 module gap, and 0 seed gaps are ready for review. Packet creation does not create tenants, copy templates, run seeds, grant permissions, enable modules, or move connector secrets.
Template copy
CONNECTOR: REFERENCE_ONLY; ACCEPTANCE_SCENARIO: COPY_DRAFT; ACCEPTANCE_SCENARIO: COPY_DRAFT
Grant gaps
MEDIUM org.apihub:view
Module gaps
MEDIUM apihub
Rollback
Keep target tenant new-customer-pilot in pilot mode until onboarding review is approved.; Disable assistant module flags before inviting pilot users if validation fails.
Rollout Packets
No rollout packets yet.