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

# Workspaces and roles

A workspace groups the documents, source files, companies and deal activity your team works on. Always check the workspace name before creating, importing or sharing information.

## Switch or create a workspace

Use the workspace selector at the top of the app to switch among workspaces you can access. **Workspace → All workspaces** opens workspace management. Eligible accounts can use **Create workspace** to create a team workspace. A personal workspace is separate from a team workspace.

If a workspace is missing, verify your signed-in email address and ask its administrator to check membership or a pending invitation. Switching workspace does not copy content from another workspace.

## Manage members

Administrators can open **Workspace → Members, invitations & settings**. Select the workspace and use its **Members** controls to invite someone, change a role or remove access. Review pending invitations as well as active members.

| Role   | Intended use                                                                                                                                  |
| ------ | --------------------------------------------------------------------------------------------------------------------------------------------- |
| Admin  | Manage workspace membership and settings, with access to the workspace's working tools.                                                       |
| Member | Work on the workspace's content and enabled features.                                                                                         |
| Viewer | Read documents according to their configured folder access and the pipeline boards granted to them; editing and Analyst tools are restricted. |

When inviting a viewer, choose the intended document access: **No documents** or **Every document in the workspace**. Use **Folder Access** to grant selected folders when that is the intended scope. Review existing viewers too: a viewer can have all-document access, so the role alone does not mean selected folders only. Grant pipeline boards separately. **Folder Access** for Deliverables and **Board Access** for pipelines serve different purposes; neither should be assumed to grant access to all Source Files.

An invitation may be delivered by email or created as a link where offered. A link created for an email address must be accepted while signed in with that address. Check its expiry and do not post invitation links publicly.

Administrators also have a separate **Downloads on/off** control for viewers. Turning downloads off restricts attachment and export actions, but someone allowed to read a document can still take screenshots or retype it.

## Configure the workspace

Workspace management includes the name, description, logo and default landing page. Choose a landing page the intended members can use; restricted viewers may be directed to their allowed content instead.

The **Workspace** settings page also links to:

* **Analyst channels** for enabled messaging channels.
* **Sent messages** for delivery records.
* **Document queue** for generated-document jobs.
* **API & MCP access**, when enabled and visible to your role.

## Separate personal connections from shared content

Google, Microsoft and other connections under **Integrations** belong to the signed-in account. Information copied from them into a workspace document or activity entry becomes workspace content. Review the destination before capturing communications. See [Integrations](https://docs.corpdev.ai/corpdev.ai-docs/connect-email-files-and-meetings) and [Sharing](https://docs.corpdev.ai/corpdev.ai-docs/sharing-and-data-handling).

Removing a member or revoking a link does not retrieve files they already downloaded or information already sent by email. Consider those copies when planning access changes.