Workspace Settings allow administrators to define the foundational scheduling rules that GuideCX uses across projects. These settings establish a consistent framework for forecasting, timeline calculations, task scheduling, and project reporting.

Two key settings are available:

Properly configuring these settings is one of the most important steps when setting up GuideCX, as they directly influence project timelines, due dates, capacity planning, and forecasted completion dates.

Customer onboarding projects often involve multiple teams, customers, and stakeholders working across different regions and time zones. Without a shared scheduling standard, project dates can become confusing and difficult to manage.

Workspace Settings help ensure:

Think of these settings as the calendar rules that GuideCX uses when calculating project timelines.

Admin permissions are required to modify Workspace Settings. (Managers and below CANNOT edit workspace settings.)

The Workspace Timezone acts as the organizational standard timezone used throughout GuideCX.

Rather than relying on individual user locations, GuideCX uses a single workspace timezone to provide consistency in:

This ensures that everyone is working from the same scheduling framework regardless of where they are located.

Most organizations should select one of the following:

Avoid changing the workspace timezone frequently, especially after projects are already active, as it can create confusion when reviewing timelines and reports.

A company headquartered in Chicago with team members in California, New York, and Europe may choose Central Time (CT) as its workspace standard.

All project forecasting will then be calculated using Central Time regardless of where individual users are located.

Working Days define which days GuideCX considers available for project work.

These settings directly affect:

Days that are not designated as working days are skipped when GuideCX calculates future task and project dates.

Active Days:

Inactive Days:

This is the most common configuration for onboarding organizations.

Active Days:

Inactive Days:

Organizations that perform weekend implementations may choose this setup to accelerate project timelines.

Some organizations operate seven days per week.

Active Days:

This configuration allows forecasting calculations to utilize every calendar day.

When GuideCX calculates a timeline, it uses the configured working days to determine when work can occur.

Task Duration: 5 Days

Start Date: Thursday

Workweek: Monday–Friday

GuideCX Calculation:

Result: Task completes on Wednesday.

If Saturday is enabled as a working day, the same task would complete sooner because GuideCX includes Saturday in the calculation.

When Workspace Settings are updated, GuideCX applies changes differently depending on project status.

Newly created projects immediately use the updated configuration.

Examples:

Active projects are not instantly recalculated when settings are changed.

Instead, updates occur through:

This approach prevents large-scale timeline disruptions across active customer projects.

Before creating templates or launching projects:

This creates more accurate forecasts from day one.

Your workweek should reflect when work actually occurs.

For example:

✔ Enable Saturdays if implementation work routinely happens on Saturdays.

✖ Do not enable Saturdays simply to shorten projected timelines.

Accurate forecasting builds trust with customers and internal stakeholders.

When onboarding enterprise customers, remember that many customer teams work only Monday through Friday.

Even if your internal team works weekends, scheduling customer-dependent activities on weekends may create delays.

Changing timezone or workweek settings after hundreds of projects are running can introduce confusion and forecasting inconsistencies.

Whenever possible:

No. Working Days are configured at the workspace level and serve as the scheduling standard for all projects within that workspace.

No.

Existing projects are updated gradually through project activity, timeline changes, and scheduled forecasting processes rather than through an immediate system-wide recalculation.

Historical project data remains intact. However, future scheduling, forecasting, and date calculations will follow the updated workspace timezone.

In most cases, use the timezone that represents your implementation organization or primary operations team.

The goal is to create a single, consistent scheduling standard across all projects.

GuideCX will include Saturdays when calculating task durations, dependencies, milestone dates, and projected completion dates. This often results in shorter forecasted project timelines.

Not at the workspace level. The workspace workweek serves as the standard scheduling framework for all projects within that workspace.

To prevent large-scale disruptions, GuideCX does not force an instant recalculation of every active project. Instead, forecasting updates occur as projects progress and through scheduled system processing.

Workspace Settings establish the scheduling rules GuideCX uses across your organization. By configuring the correct timezone and workweek, you ensure that project timelines, task durations, dependencies, and forecasts remain accurate and consistent.

For best results, configure these settings before launching templates or creating projects, and ensure they accurately reflect how your onboarding teams operate in the real world.