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

# Authentication and Access

### Sign in

Pulse Labs supports four sign-in methods:

* **Google** — Sign in with your Google account.
* **Microsoft** — Sign in with your Microsoft account.
* **Apple** — Sign in with your Apple ID.
* **Six-digit code** — Enter your email address, receive a six-digit code, and enter it to sign in. No password needed.

All methods use the same underlying account. You can switch between them freely as long as the email address matches.

### First-time setup

When you sign in for the first time:

1. **Enter your name** — Type your first and last name.
2. **Accept Terms** — Agree to the Terms of Use and acknowledge the Privacy Policy.
3. **Consent** — Agree to receive communications from Pulse Labs and its partners.

After onboarding, you'll see the workspace selection screen where you can join an existing workspace or create a new one.

### Enterprise SSO

Pulse Labs automatically integrates with your organization's Google or Microsoft SSO. Sign in with your corporate email through the Google or Microsoft option, and the platform will recognize your organization's domain for workspace discovery.

## Roles and permissions

Pulse Labs uses a two-tiered permission system to control access at the Workspace level and at the project level. The workspace is the top-level container that represents a team or organization, similar to a shared drive. The projects are the “functional” folders within the workspace where the research happens.

### Assign workspace roles

The platform automatically assigns the **Admin** role to the workspace creator. New users added to the workspace by the Admin default to the **Member** role.

| **Role** | **What You Can Do**                                                                                                                          |
| -------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| Admin    | Exercise full control: manage members, roles, workspace settings, and billing. View and manage everything in the workspace.                  |
| Member   | Create projects, invite new workspace members, and collaborate on projects they have access to. Cannot change workspace settings or billing. |

***

**Note:** Typically, the workspace creator or the account owner responsible for billing holds the Admin role. To ensure coverage, you can appoint more than one Admin as backup.

Here are the permissions for **workspace** roles at a glance.

| **Permission**               | **Admin** | **Member** |
| ---------------------------- | --------- | ---------- |
| Create projects              | ✅         | ✅          |
| Invite new workspace members | ✅         | ✅\*        |
| Remove workspace members     | ✅         | ❌          |
| Change member roles          | ✅         | ❌          |
| Edit workspace settings      | ✅         | ❌          |
| View/manage billing          | ✅         | ❌          |
| View member list             | ✅         | ✅          |

\* Configurable in workspace settings

### Assign project roles

Pulse Labs automatically assigns the project creator as the Manager. You manage roles at the project level; for example, you can serve as an Manager on one project while remaining a Viewer on another within the same workspace.

As a project Manager, you can:

* Invite others and assign them a role (Manager, Editor, or Viewer).
* Change any team member’s role at any time.

<table data-header-hidden><thead><tr><th width="119.59991455078125"></th><th></th></tr></thead><tbody><tr><td><strong>Role</strong></td><td><strong>What You Can Do</strong></td></tr><tr><td><strong>Manager</strong></td><td>Full control — In addition to all <strong>Editor</strong> permissions, can manage team members, invite and communicate with participants in-platform, change project settings, delete the project, and promote others to Admin.</td></tr><tr><td><strong>Editor</strong></td><td>Active research —  can create, modify, and run projects, review submissions, communicate with participants in-platform, and download data. Cannot manage workspace membership or delete the project.</td></tr><tr><td><strong>Viewer</strong></td><td>Read-only — can view project data, watch recordings, read transcripts, and survey responses. Cannot modify anything or communicate with participants.</td></tr></tbody></table>

**Editor is the recommended default for most team members**. It gives enough access for day-to-day research work without exposing administrative controls.

Here are the permissions for **project** roles at a glance.

<table data-header-hidden><thead><tr><th width="353.4000244140625">Permission</th><th>Manager</th><th>Editor</th><th>Viewer</th></tr></thead><tbody><tr><td><strong>Permission</strong></td><td><strong>Manager</strong></td><td><strong>Editor</strong></td><td><strong>Viewer</strong></td></tr><tr><td>View project content</td><td>✅</td><td>✅</td><td>✅</td></tr><tr><td>Create capture series</td><td>✅</td><td>✅</td><td>❌</td></tr><tr><td>Edit capture series</td><td>✅</td><td>✅</td><td>❌</td></tr><tr><td>Delete capture series</td><td>✅</td><td>✅</td><td>❌</td></tr><tr><td>Upload files/assets</td><td>✅</td><td>✅</td><td>❌</td></tr><tr><td>Approve/reject session data</td><td>✅</td><td>✅</td><td>❌</td></tr><tr><td>Download data</td><td>✅</td><td>✅</td><td>❌</td></tr><tr><td>Edit project settings</td><td>✅</td><td>✅</td><td>❌</td></tr><tr><td>Manage project access (share)</td><td>✅</td><td>✅</td><td>❌</td></tr><tr><td>Communicate with participants in-platform</td><td>✅</td><td>✅</td><td>❌</td></tr><tr><td>Archive project</td><td>✅</td><td>❌</td><td>❌</td></tr><tr><td>Delete project</td><td>✅</td><td>❌</td><td>❌</td></tr></tbody></table>

### Project visibility

Pulse Labs sets every new project to **Hidden** by default, ensuring only the project Manager and those directly invited can see it. This allows you to configure your study privately before sharing it with your team.

To grant access to others, open your project and select the **Share** icon to:

* **Find and invite** workspace members by name or email.
* **Assign specific roles** (Manager, Editor, Viewer) to each invitee.
* **Manage visibility** to determine if the project appears in the workspace directory for others to discover.

By keeping all research private until you explicitly share it, you maintain control over who accesses your data and their level of permission.

***


---

# 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://pulselabs.gitbook.io/pulse-labs/getting-started/authentication-and-access-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.