Create a workspace

When to create a separate workspace

Create one workspace per project, team, or customer whose data and access should stay apart. Each workspace has its own stores, layers, styles, API keys, and service settings. A client key from one workspace can’t read another workspace’s data.

The workspace name is part of every service URL, for example /workspaces/tutorial-ui/wms. Choose a short, lowercase name that can stay the same for as long as clients use the service.

Create the project boundary

Sign in with a super_admin credential. Global workspace creation requires this role; workspace administrators operate within their assigned workspace.

1. Open the workspace list and choose New workspace.
2. Enter tutorial-ui as the Name and add a description.
3. Choose Create workspace.

↗

The console opens the new workspace. Its Publish your first dataset guide links to connecting or uploading data, publishing, previewing, and configuring client access.

↗

What belongs to a workspace

Stores, layers, coverages, styles, keys, claim mappings, and OGC service settings are scoped to the workspace. Changing a service title in one workspace does not change the other workspaces. See core concepts for how workspaces, stores, and publications relate.

The publishing guide can be hidden and restored without changing data. After publication, Review publishing guide reopens the steps.

Choose the next step

• Connect a PostGIS store when the data already lives in a database.
• Upload a file when managed imports are enabled.
• Configure workspace services for the clients you plan to use.

Delete with care

A workspace with dependent resources cannot be deleted as an empty resource. Review the dependency plan before confirming recursive deletion. Follow any asynchronous deletion operation to completion, and distinguish catalog removal from deleting source data. See referentially complete deletion.