Workspace administration · how to

Create, switch, and manage workspaces

Understand organization and workspace scope, then create, switch, or rename a workspace without cross-scope mistakes.

3 min readUpdated August 12, 2026
For
Owner, Admin, Member
Availability
Your current plan and entitlements
Product evidence
WRKZY · reviewed August 12, 2026
Editorial review
WRKZY Editorial
Before you begin
  • An active organization membership
  • A durable business, access, or data-boundary reason for a new workspace
  • Owner/Admin approval for workspace creation or configuration
  • A recognizable name, slug, timezone, currency, and initial owner

Organization and workspace are different scopes

An organization is the account-level membership boundary. A workspace is where customer records, channels, queues, settings, and day-to-day work are scoped. A person may belong to the organization but not every workspace. Always read the active workspace name and URL before changing configuration.

Scope and access

  1. 01
    AccountOrganization

    The customer account and ownership boundary.

  2. 02
    ScopeWorkspace

    The operating area where customer work and configuration live.

  3. 03
    GovernOwner

    Controls the organization, subscription, and highest-risk access.

  4. 04
    ConfigureAdministrator

    Configures members, channels, defaults, and operating controls.

  5. 05
    OperateMember

    Works customer queues, records outcomes, and escalates exceptions.

Organization membership makes a person eligible for account participation; workspace membership and role control their operating access inside one workspace.

Switch workspaces safely

Use the workspace switcher in the application header. After switching, confirm the URL contains the intended workspace slug and reopen the record or settings domain. Do not keep two tabs from different workspaces open while performing repetitive administration unless each tab's scope is unmistakable.

Create a workspace

Only an organization Owner or Admin can create a workspace, and the organization must have available workspace capacity in its current plan.

  1. Select your profile avatar in the top-right corner to open the account menu.
  2. Under Current workspace, choose Create workspace.
  3. Enter a distinct, durable workspace name based on the operating boundary—not a temporary project status.
  4. Select Create. WRKZY creates the workspace, makes you its Owner, switches to it, and opens its Workspace & members settings.
  5. Configure members, business defaults, channels, routing, privacy, and billing readiness before importing customer data.
  6. Run the launch-readiness checks with a controlled record.

You can also open Settings → Workspace & members, open More workspace actions beside the workspace name, and choose Create workspace. If Create workspace is not visible, verify your organization role and workspace capacity rather than looking under Members.

A new workspace is not automatically a copy of the current one's channels, members, templates, or policies.

Rename a workspace

  1. Open Settings → Workspace & members and select Rename beside the current workspace name.
  2. Enter the new name and select Save.
  3. WRKZY updates the workspace URL and redirects automatically.
  4. Update bookmarks, operating notes, contextual Help mappings, and any external documentation that used the old slug.
  5. Verify members and records still resolve in the renamed workspace.
WRKZY workspace administration and access settingsOpen full size
The Settings overview helps administrators confirm the active workspace before changing a shared configuration domain.

When to create another workspace

Create a separate workspace when access, data ownership, channels, reporting, or compliance boundaries truly differ. Do not create one merely to represent a team-inbox queue, sales stage, campaign, or temporary initiative; those have native structures inside a workspace.

Recovery

If you land in the wrong scope, stop before changing data. Record both slugs, switch to the intended workspace, and verify the action was not already saved elsewhere. If a rename broke a bookmark, use the workspace switcher to resolve the current slug. Do not create a replacement workspace to recover a naming or access issue.

Workspace scope check
  • Organization and workspace boundary understood
  • Active name and slug confirmed before changes
  • New workspace has a real access or data purpose
  • Rename redirect and bookmarks verified
  • Channels, members, privacy, and defaults reviewed before launch
Was this guide useful?

Choose an answer. No message text or personal information is collected.

Still need help?

Contact WRKZY support with the workspace name and a safe, redacted example.

Contact support about this guide