# Workspaces

Workspaces divide an organisation into separate operating areas, each with its own maps, sites, team, and campaigns.

A workspace is one operating area. It owns its own maps, sites, team members,
and campaigns, and none of them are visible from any other workspace.

This page covers workspaces from the organisation's point of view — when to
create one, and how they are configured. For what you actually do inside one,
see [Workspaces](/docs/workspaces).

## When to create a second workspace

Create a new workspace when a group of people plan and deliver independently of
another group. Some examples:

* A political party with a workspace per electorate. Each candidate's team sees
  their own volunteers and their own hoardings, while head office keeps one
  plan and one invoice.
* A real estate agency with a workspace per office. Each office manages its own
  signboards and its own patch.
* A distribution business with a workspace per depot.

Stay in one workspace when the same people plan the same area, even if you run
many campaigns. Campaigns already separate one distribution from the next.

> **Workspaces don't share data**
>
> Maps, sites, and team members belong to a single workspace. Splitting an area
> in two later means rebuilding its maps, so it's worth deciding early. Only
> [capabilities](/docs/organisations#capabilities) are shared, because they are
> defined at the organisation level.

## Creating a workspace

Use the workspace switcher in the sidebar and choose **Create workspace**. You
provide the same details as your first one: name, URL slug, industry, country,
and base address.

Your plan sets how many you can have — one on Starter and Pro, five on
Business, unlimited on Enterprise. Prenso blocks creation past the limit rather
than billing you for the overage.

## Workspace settings

Organisation owners and admins can open **Settings** inside any workspace to
change:

* **Name, URL, and logo.** Changing the URL changes every link into the
  workspace, so existing bookmarks stop working.
* **Industry.** Switches the wording used for fixed signage between hoardings,
  signboards, and sites. Nothing about the records themselves changes.
* **Base address.** Where the map opens when you start a new one.
* **Public sign-up.** Lets people request to join your delivery team from a
  public link. See [Team](/docs/workspaces/team#public-sign-up).

Deleting a workspace is restricted to the organisation owner and removes every
map, site, campaign, and team member in it.

## Geographic scope

A workspace can optionally be restricted to a set of boundaries — an electorate,
a council area, a group of suburbs. When a scope is set, everything the
workspace touches is confined to it: map creation, address searches, and the
data on screen.

This is worth setting when you run one workspace per area and want to make it
impossible to plan into someone else's patch by accident. Left unrestricted, a
workspace can draw a map anywhere in its country.

The scope applies inside the workspace. The
[organisation map](/docs/organisations/map) looks across every workspace and is
never cut to any one of their scopes.

## Next steps

- [Users and roles](/docs/organisations/users) — Decide who reaches which workspace.

- [Working in a workspace](/docs/workspaces) — Maps, sites, campaigns, and team.