Feature Planning
Choose the smallest feature set that matches the workspace plan and operating model.
Feature Planning
Use this page before enabling features or changing a workspace plan. The best first launch is usually the smallest useful feature set.
Plan Availability
| Plan | Feature availability |
|---|---|
| Free | playlists, galleries, links, forms, articles, documents |
| Starter | Free features plus ecommerce, customers, videos, community, events |
| Basic | Starter features plus canvas |
| Pro | Basic feature set with higher quotas |
| Enterprise | All tenant features, including live-streaming |
Feature Decisions
| Need | Start with | Add later when |
|---|---|---|
| publish updates or guides | articles or documents | editors need taxonomy or approval ownership |
| collect requests | forms | a team is assigned to monitor submissions |
| sell products | ecommerce | catalog, shipping, payments, and support owners are ready |
| manage customer accounts | customers | support owns verification and recovery decisions |
| open community spaces | customers and community | moderation ownership is ready |
| run events | events | calendar ownership and occurrence updates are assigned |
Dependencies
- Community depends on customer accounts.
- Plan-blocked feature intent may be saved, but it is not effective until the plan allows it.
- Disabling unused features keeps navigation and readiness checks focused.
Preserve intent, but launch with the smallest effective set. Add features after owners, content, support, and readiness checks exist.
Next Actions
- Prepare non-commerce areas in Content Operations.
- Prepare sales workflows in Commerce Operations.
- Check blockers in Launch Readiness.