--- title: "Workspaces" slug: admin/workspaces url: https://projectri.com/docs/admin/workspaces section: admin audience: admin app_route: "/[slug]/admin/workspaces" permissions: [project.view, settings.manage] mobile: "/admin/workspaces" updated: 2026-09-08 source: Projectri documentation --- # Workspaces The containers projects live in, and what kind of place each one is — the type sets what a new project inherits and whether customers may be let in at all. ![Workspaces](https://projectri.com/docs-shots/admin-workspaces.png) ## What it is A workspace is the container projects sit in. Each one has a **type**, and the type is the whole point of this screen: until it existed, a support desk and a scrum team were the same object with a different name. There are seven types: **Agile development**, **Customer implementation**, **Product support**, **AMC support**, **Consulting**, **Internal operations** and **Client collaboration**. ## How to get there **Admin → Work → Workspaces**. The console needs the ADMIN role. Reading the list is `project.view`; creating, renaming, re-typing and deleting are all `settings.manage`. ## How to use it ### Create a workspace 1. Type a name in the **New** row, e.g. *AMC Desk*. 2. Pick a type. The sentence under the row describes the one you have selected. 3. Press **Create**. 4. The URL slug is derived from the name, and a collision is resolved by appending a number rather than refused — two workspaces called "Support" is a reasonable thing to want. ### Rename one 1. Press **Rename** on the row, edit in place, then **Save** (or press Enter). ### Change a type 1. Use the type picker on the row. The change saves immediately. 2. The row then redescribes itself: the project count, the view it opens on, and the badges it carries. ### Delete one 1. **Delete** is only enabled on a workspace with no projects. The tooltip on a disabled button says how many are in the way. 2. It asks for confirmation before deleting. ### Read a row Each row carries its project count, the layout its projects open on (*board*, *list*, *table*, *calendar* or *timeline*), and up to three badges: - **Support** — the ticket queue and SLAs belong to this kind of workspace. - **Billable** — hours logged against a new project here are billed by default. - **Internal only** — this workspace is *not* customer-facing. Only this one is badged, because most workspaces can be shown to a client and marking those would be a badge on nearly every row saying nothing. ## What it affects - **What the next project inherits.** The type sets the view a new project opens on and whether its hours are billable by default. Both are applied when the project is created and are then the project's own — editing either later is a project setting, not a workspace one. - **One hard line.** A workspace that is not customer-facing cannot have a customer granted access to its projects. That is a refusal, not a default — the reason the flag exists is the HR workspace that must never be one careless grant away from an external login. - **The support desk.** Whether tickets and SLAs are offered at all follows the type's *support* flag. - **Nothing existing is rewritten.** Changing the type re-labels the workspace and changes what the next project inherits. It does not migrate stages, move tickets, rewrite a board a team has been running for a year, or revoke a customer grant that is already live. ## On mobile The **Workspaces** screen in the app's Admin hub lists the same rows, grouped by kind rather than flat — a phone reading nine rows down a column benefits from the grouping a wide table gets for free from its type column. The same picker, the same badges, and the same note about what a type change does not do. It is deliberately not the workspace *switcher*: the switcher answers "where may I go", this answers "what exists here and how big is it". A member of one workspace may still need to know the organisation runs nine. ## Limits and gotchas > [!NOTE] > Switching a workspace to a type that is not customer-facing while customers > still hold access returns a warning rather than revoking anything: *"N customer > grants are still active on projects here. Changing the type does not revoke > them — remove them on the client's Portal access tab."* Silently revoking and > silently keeping are both wrong; the screen tells you which one happened. - **A workspace with projects in it cannot be deleted.** Cascading would take every project, task, worklog and invoice line with it — a destructive act disguised as tidying up a list. Move or delete the projects first. - Project stages are configured per company under Workflow, not per workspace type. The type does not carry its own stage list. - Workspaces are also created implicitly by the first project that needs one, so the list may contain rows nobody made here on purpose. - A workspace whose type is no longer in the catalogue still appears in the list; it is not hidden behind a data-migration detail. ## Related - [Admin console](/docs/admin/overview) — where this sits in the console. - [Projects](/docs/workspace/projects) — what a workspace contains. - [Switching workspaces](/docs/workspace/workspaces) — the member-facing switcher. - [Client portal](/docs/portal/overview) — the surface the customer-facing flag governs. ## Related - [Admin console](https://projectri.com/docs/admin/overview.md): The landing page of the admin console — the state of the whole company on one screen, and the map of every setting behind it. - [Projects](https://projectri.com/docs/workspace/projects.md): The project list and the project itself — its people, milestones and progress, its tasks as a table, board, timeline or roadmap, and its documents, boards and meetings. - [Your workspaces](https://projectri.com/docs/workspace/workspaces.md): Every workspace you belong to, which one you are in now, and how to switch between them or start one of your own. - [The client portal](https://projectri.com/docs/portal/overview.md): Your own view of the work your agency is doing for you — projects, requests, support tickets, quotes and invoices, in one place with your own login.