Sharing Across a Workspace
Products, Writing Styles, and ICPs can be shared across your workspace so all team members use the same configuration.
What Sharing Means
In Valley's Studio, each component (Product, Writing Style, ICP) can be toggled between Personal and Shared:
Personal: Only visible to you. Other workspace members can't see or use it.
Shared: Visible to all workspace members. Everyone can select it when creating campaigns.
How to Share
Go to Studio > Products (or Writing Styles or ICPs)
Select the component you want to share
Find the sharing toggle
Switch from Personal to Shared
Save
The component now appears in every team member's Studio when they're creating or editing campaigns.
Why Share
Consistency: All team members send messages from the same playbook. Unified brand voice across all outreach.
One source of truth: Instead of 10 different Writing Styles, everyone uses the one that actually works.
Faster onboarding: New team members inherit proven components instead of building from scratch.
Cleaner data: When everyone uses the same Product or Writing Style, performance data tells you what's truly resonating vs. what's noise from different configurations.
Best Practice: Share Your Winners
After 2-4 weeks of running campaigns, identify which Product and Writing Style drove the highest reply rates. Share those across the team and retire personal variants.
The Booking Link Caveat
When you share a Product, the booking link in that Product is YOUR booking link. If reps use the shared Product as-is, meetings book on your calendar, not theirs.
What Reps Should Do
See the shared Product the admin placed in Studio
Duplicate it
Replace the booking link with their own personal scheduling link
Rename it: "PRODUCT NAME - (Rep Name)"
Save their personal copy
Use their personal copy (not the shared one) when creating campaigns
This ensures every rep's campaigns use the correct booking link while still inheriting the admin's proven product definition and messaging angles.
When NOT to Share
Different ICPs by rep: If rep A targets CFOs and rep B targets VPs of Sales, let each define their own ICP.
Experimental components: Keep new Writing Styles personal while testing. Share only after validating they work.
Niche angles: If a Product is specific to one vertical or one rep's territory, keep it personal.
Sharing is additive, not restrictive. Team members can always create and use personal components alongside shared ones.