---
title: "Workspaces & Projects"
canonical: https://trickest.com/docs/key-concepts/workspaces-and-projects
description: "Organize workflows in spaces and projects, and distinguish space views from vault-wide navigation."
---

# Workspaces & Projects

## Workspaces

A **space** groups related workflows, projects, runs, and variables. The platform also calls a space a **workspace**, particularly in settings and developer tools. Use one for a client, a team, or a process that needs its own access assignments.

Open a space under **Your spaces** in the sidebar. Its **Overview** shows projects and workflows; **Workflows**, **Runs**, and **Variables** show that space's content. The header identifies the space you are viewing.

The **Vault** section provides shared destinations, such as the Library, and broader views where your permissions allow them. Opening a space does not turn every platform page into a view of that space. Check the page header and filters when working across clients.

### Playground Workspace

Use your Playground workspace for experiments and copies from the Library. A copy is still a real workflow: running it uses fleet capacity and can contact the targets configured in its nodes.

### Common patterns

- A space per client, with access granted to that client's delivery team.
- A space for a recurring process, with projects for its workflow groups.
- A Playground space for testing changes before copying them into shared work.

## Projects

A **project** groups workflows inside one space. Workflows can also live directly in the space, without a project.

For example, a `Client A` space might contain `External discovery` and `Application testing` projects. Both use the space's access rules; a project is an organizational folder, not a separate permission boundary or execution environment.

## How it relates

| Item | Scope and purpose |
|---|---|
| Vault | The organization context for shared settings, members, and platform access. |
| Space / workspace | Groups work and carries space access assignments. |
| Project | An optional workflow folder within a space. |
| Workflow | A graph stored in a space, optionally inside a project. |
| Run | An execution record belonging to a workflow. |

A space does not create dedicated compute. Runs use the fleet you select. Likewise, personal secrets and space variables have different scopes; see [Managing Variables](/docs/using-the-app/workflow-and-executions/managing-variables).

## Next Steps

- [Copy or move workflows](/docs/using-the-app/workflow-and-executions/copying-workflows) between spaces and projects.
- [Assign space access](/docs/using-the-app/users-access-management/teams-and-roles) to users and teams.
- [Understand roles](/docs/key-concepts/roles-and-permissions) before using spaces to restrict access.

---
_Markdown source of https://trickest.com/docs/key-concepts/workspaces-and-projects._