Decision: Default Bundles for N-th Boo Deployments
Decision: Default Bundles for N-th Boo Deployments
Status: Decided (deferred implementation)
Channel: #e-boo-training
Participants: DK, Vishal Joshi
Context
When a customer creates a second Boo deployment in their org, should it get the same default bundles (content calendar, etc.) as the first one?
Decision
Certain bundles should be disabled on second/subsequent Boo installations. The default bundle set needs to be tailored for first Boo vs. subsequent ones.
Rationale
DK: "When customer creates a second Boo, bunch of things like content calendar etc might just frustrate them."
Status
Acknowledged and agreed upon. Deferred as "problems of tomorrow" — not blocking current work but logged as a design consideration for multi-deployment orgs.
Sources (1)
slack
Product Decision — Default Bundles for N-th Boo Deployments