Find the right plan for your team.
Answer three questions and compare the options that fit your organization.
1 to 20 people21 to 100 peopleMore than 100
ContinueLayout protectedCopy editableBrand governance
Scale creation without losing the brand system.
Designers define templates, components, responsive behavior and editing boundaries in Studio. Other teams update approved content, follow the right review path and publish without rebuilding the design.
Spring campaign / Product finder Approved template
Brand system
SC
Approved componentsStorycardsEnterprise system
- Product header 12
- Answer cards 08
- Form fields 14
- Action buttons 06
Editing rules
Content teamCampaign editors
Text and labelsEditable
ImagesEditable
Brand stylesLocked
Responsive layoutLocked
InteractionsLocked
PublishingApproval requiredBrand manager or admin
Governance starts in the design system, not at the end of review.
Storycards separates system design from day-to-day content work. Designers decide what is reusable, what stays protected and which fields another team can change.
Everyone works in the same product. Content teams do not need a new design handoff for every update, and designers do not need to inspect the same brand decisions again and again.
Clear ownership
Give each team the control its job requires.
Governance works when the design team can protect the system and operating teams can still complete their work without a queue of manual design requests.
Designers own the system
Define the visual language, responsive behavior, components and reusable templates in Studio.
Teams edit approved content
Expose the fields each team should update while brand-critical layout and behavior stay protected.
Admins control access and publishing
Set roles, organize teams and products, and keep review and publishing rights with the right people.
Governance controls
Control the parts that should stay consistent.
Build the rules into the workspace so teams see what they can use, what they can edit and who can approve the finished product.
Approved templates
Turn a proven product into a governed starting point for a department, brand, market or recurring campaign.
Reusable component library
Give teams access to the same approved cards, interactions, controls and responsive patterns.
Protected editing
Lock layout, styling and behavior while keeping selected text, media and data fields editable.
Roles and permissions
Control who can create, edit, review, publish and access data across the organization.
Review and publishing controls
Keep draft work separate from live products and reserve approval and publishing for authorized roles.
Central product management
Manage templates, active products, ownership and access from one organization-level workspace.
From system to live product
A governance model that keeps work moving.
Set the system once, then let each team move through a clear creation and publishing path.
- 01
Define
Designers build the visual system, components and responsive behavior.
- 02
Package
Save approved structures as templates and choose which fields remain editable.
- 03
Assign
Give each team the right template, product access and publishing role.
- 04
Create
Teams adapt content for a specific campaign, audience or market inside the approved boundaries.
- 05
Review and publish
The right owner reviews the product and controls when it goes live.
Organization-wide consistency
One operating model across teams, brands and markets.
Across teams
Marketing, product, digital, HR and data teams work from the same governed foundation.
Across brands
Maintain a distinct system, template library and access model for each brand or business unit.
Across markets
Reuse an approved structure while local teams adapt the content and variations they are allowed to change.
Across products
Keep active experiences, ownership and publishing status visible in one product library.
Build your brand system into the way teams create.
Plan the templates, permissions and publishing model your organization needs.