> For the complete documentation index, see [llms.txt](https://docs.pulselabs.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pulselabs.ai/getting-started/workspace-management.md).

# Workspaces

### What Is a workspace?

A workspace is your team's shared home on Pulse Labs. It's where your projects live, where you invite collaborators, and where you control who has access to your research. It's the top-level container for everything your team does.

Most teams only need one workspace. Larger organizations might use separate workspaces for different departments, client engagements, or long-running research projects.

### Creating a workspace

As creator of the workspace, you are automatically assigned as the Manager. When you create a workspace, you'll set three things:

* **Name** — A short, descriptive name for your team or organization
* **Privacy level** — Controls who can discover and join
* **Icon or avatar** — Easily identifies your workspace (optional)

### Privacy levels

<table data-header-hidden><thead><tr><th width="125"></th><th width="263.800048828125"></th><th></th></tr></thead><tbody><tr><td><strong>Level</strong></td><td><strong>Who Can Find It</strong></td><td><strong>How They Join</strong></td></tr><tr><td>Open</td><td>Anyone with a matching email domain</td><td>Select <strong>Join</strong> to access workspace instantly. </td></tr><tr><td>Closed</td><td>Anyone with a matching email domain</td><td>Select <strong>Request access</strong> to send a request to Admin. Access granted upon approval.</td></tr><tr><td>Hidden</td><td>Nobody — invisible in directories</td><td>N/A. Only invited members can join.</td></tr></tbody></table>

**Open** works well for cross-functional teams where you want broad engagement. **Closed** gives you a review step before people join. **Hidden** is for confidential work where even the existence of the workspace should be private.

As an admin, you can change the privacy level at any time.

### Workspace identity

You can add an icon or avatar to your workspace for quick visual recognition in the sidebar and directory. This is optional but helpful when team members belong to multiple workspaces.

### Navigating workspaces

After signing in, you'll see your workspaces organized into two groups:

* **Your Workspaces** — Workspaces you created or have joined/been invited to.
* **Company Workspaces** — Workspaces created by colleagues at your organization, with indicators showing whether you can join directly or need to request access.

Switch between workspaces at any time by selecting the workspace icon in the header.

### Managing members

Workspace managers can:

* **Invite members** by email or from the organization directory.
* **View the member list** with roles and join dates.
* **Remove members** who no longer need access.
* **Promote members** to Manager role.

Workspace membership controls who can be added to projects. You can only invite someone to a project if they're already a workspace member (or you invite them to the workspace at the same time).

### How workspaces relate to projects

* A workspace contains multiple projects.
* Each project has its own team and permissions (Manager, Editor, Viewer).
* New projects are hidden by default — workspace members can't see them until the creator shares them.
* Workspace settings (like the member list) are inherited by projects, but each project controls its own access independently.

### When to create a new workspace

Create a separate workspace when you need:

* **Different teams** — A client services team and an internal research team that shouldn't see each other's work.
* **Different access boundaries** — One group that's open to the whole company and another that's invite-only.
* **Client separation** — Dedicated spaces for different clients with no cross-visibility.

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.pulselabs.ai/getting-started/workspace-management.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.