What Are Workspaces?
Workspaces allow your organization to operate multiple independent GUIDEcx environments while using the same user login credentials.
Each workspace functions as its own separate GUIDEcx instance, with its own configuration, data, and settings. This makes it easy to support different teams, business units, testing environments, or customer experiences without requiring users to manage multiple accounts.
While users can belong to multiple workspaces, nearly everything else remains separate.
Each Workspace Has Its Own:
Templates
Projects
Customers
Branding and white labeling
Global settings
Custom fields
API access
Recipe Builder automations
Reports and dashboards
User permissions and license assignments
What Is Shared?
The only shared component between workspaces is user identity.
Users can be granted access to one workspace, multiple workspaces, or none at all. Access is managed independently within each workspace.
Common Workspace Use Cases
1. Sandbox Environment
Many organizations use a dedicated workspace as a sandbox for testing.
A sandbox workspace allows teams to:
Test integrations safely
Build and validate automation recipes
Experiment with new processes
Train administrators and team members
Because the workspace is separate from your production environment, you can test changes without impacting live customer data.
2. Separate Departments or Teams
Organizations often expand GUIDEcx beyond onboarding and implementation.
Examples include:
Customer Success
Support
Professional Services
Marketing
Operations
These teams may need their own templates, administrators, workflows, and reporting. Workspaces allow each department to maintain its own environment while still giving leadership visibility across multiple workspaces.
3. Supporting Multiple Languages
GUIDEcx's user interface is currently available in English. However, customer-facing communications can be customized using Custom Email Templates.
Organizations supporting multiple languages often create separate workspaces dedicated to specific regions or languages. This allows each workspace to maintain:
Language-specific email templates
Localized customer communications
Region-specific processes and workflows
Projects can then be managed from the workspace that best aligns with the customer's preferred language and experience.
Managing User Access
Although workspaces are independent environments, user access is managed by the GUIDEcx team. Please submit a ticket to request access to another workspace.
NOTE: Only Admins can chat in and request that users get access to workspaces. We'll need the following info:
User's email address
Desired user role in new workspace
Name of the new workspace
Creating a Workspace
If you're interested in adding Workspaces to your GUIDEcx account, contact your Customer Success Manager (CSM).
Your CSM can help determine whether Workspaces are a good fit for your organization and discuss available options.
Adding Users to a Workspace
Only users with an Admin license can add users to a workspace.
Open the workspace where you'd like to add users.
Navigate to Company Details.
Select the Users tab.
Add or manage workspace members as needed.
Switching Between Workspaces
If you have access to multiple workspaces:
Locate the workspace icons on the left side of the navigation menu.
Select the workspace you want to access.
GUIDEcx will immediately switch you into that environment.
Best Practices
Workspaces provide the most value when separate environments require unique configurations, processes, or customer experiences.
Consider creating a dedicated workspace when you need:
Different branding
Separate customer data
Distinct templates and workflows
Independent automation recipes
Testing or sandbox environments
Department-specific administration
If multiple teams can successfully operate within the same configuration and governance model, a single workspace may be sufficient.
Frequently Asked Questions
How much does a workspace cost?
Workspace availability and pricing vary. Contact your CSM to discuss your organization's needs and available options.
Does a new workspace inherit settings from an existing workspace?
No. New workspaces start as a blank environment and must be configured independently.
Can templates be moved between workspaces?
Yes. The GUIDEcx team can assist with a limited number of template transfers between workspaces.
If you need multiple templates moved, discuss your requirements with your CSM to determine the best approach.
Can automation recipes be shared between workspaces?
Yes. Depending on your use case, recipes can often be shared through the Recipe Community or migrated using professional services and Guide Hours.
Your CSM can help determine the best option.
If a user has a paid license in multiple workspaces, does that count as multiple paid licenses?
No. License counts are based on unique users. A user with paid access in multiple workspaces only consumes one paid license.
Who should have access to multiple workspaces?
Typically, administrators, executives, and operational leaders benefit most from access to multiple workspaces.
Most individual contributors only need access to the workspace where they perform their daily work.
Can users have different permissions in different workspaces?
Yes. A user can have different license types and permissions in each workspace.
For example, someone could be an Admin in one workspace and a Contributor in another.
Are projects, customers, and reports shared between workspaces?
No. Projects, customers, reports, templates, and settings remain completely separate between workspaces.
Only user identities can be shared across environments.
Can integrations be configured differently in each workspace?
Yes. Each workspace maintains its own integrations, API credentials, automation recipes, and related configurations.
Changes made in one workspace do not affect another workspace.