Engage Studio uses Workspaces and Policy-Based Permissions (PBP) to manage access and governance. This ensures that your teams can collaborate securely, with clear separation between brands, regions, or business units.
A Workspace is a secure container for your marketing assets. Everything you build in Engage Studio belongs to a specific workspace.
- Isolation: Separate assets by brand or region (e.g., "Japan Marketing" vs. "US Marketing").
- Governance: Control which Email Domains, Custom Web Subdomains, and Audience Segments are available to each team.
- Security: Prevent accidental access to sensitive data or unauthorized sending.
Each Workspace contains:
- Campaigns: The journeys and activations.
- Landing Pages: Static campaign destinations created in this workspace.
- Templates: Email designs and content.
- Senders: Verified sender profiles authorized for use in this workspace.
- Workspace Settings: Configuration of available Email Domains, Custom Web Subdomains, and Parent Segments.
- Navigate to Engage Studio > Workspaces.
- Click Create Workspace.
- Enter a unique Name and optional Description.
- Click Save.

Once created, an Admin must assign resources to the Workspace:
- Email Domains: Select which verified sending domains (configured by IT) can be used.
- Custom Web Subdomains: Select which registered, Active Landing Page custom subdomains are available to this workspace. Marketers can select only the subdomains assigned to their workspace. When a subdomain is assigned to multiple workspaces, coordinate the URL slugs used by each workspace because a slug must be unique across landing pages using that subdomain.
- Parent Segments: Select which CDP segments are visible for targeting within this workspace.
Policy-Based Permissions (PBP) allow you to define granular access controls. Instead of simple "Admin" or "User" roles, you create Policies that define exactly what a user can do.
Landing Pages and Landing Page custom subdomains do not have dedicated permission entries in the policy screens. Access is derived from these existing groups:
| Permission group | How it affects Landing Pages |
|---|---|
| Workspace Configuration Permissions | Control workspace administration and assignment of available resources, including custom subdomains. |
| Workspace Feature Permissions | The existing EngageCampaign View, Edit, and Launch permissions control viewing pages and uploads, managing drafts and uploads, and publishing or unpublishing pages. |
| Domain Permissions | The existing EngageDomain view and edit permissions control web-domain status and operations. EngageDomain covers both Email Domain and Web Domain. |
A user must have access to the target workspace and the appropriate permissions in these groups. Landing Page operations follow the user’s existing Campaign permissions, while web-domain operations use the account-scoped Engage Domain permission.
Permissions are managed in the Control Panel, not inside Engage Studio itself.
- Go to Control Panel > Policies.
- Create a new Policy or edit an existing one.
- Scroll to the Engage Studio section.
- Configurations: Who can manage Workspaces, Domains, and Parent Segments? (Usually Admins).
- Features: Who can build campaigns and templates? (Marketers, Designers).
- Domains: Who can view and manage email and web domains? (IT/Admins).
| Role | Recommended Permissions |
|---|---|
| Marketing Manager | Edit Campaigns/Templates, Launch Campaigns. Access to specific Workspaces. |
| Content Designer | Edit Templates. View Campaigns. No Launch access. |
| Analyst | View Campaigns and Reports. No Edit access. |
| IT Admin | Full Access to Configurations and Domains. |
Q. Can I share an Email Domain across multiple Workspaces? Yes. A verified domain (e.g., marketing.example.com) can be assigned to multiple workspaces.
Q. Can I move a campaign to another Workspace? No. Resources are bound to the workspace where they were created.
Q. Who "owns" the campaign launch? Campaigns run under the permissions of the user who activates them, but the resources used (Senders, Segments) are scoped by the Workspace.


