> ## Documentation Index
> Fetch the complete documentation index at: https://docs.worksynk.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Workspaces and people

> Workspace roles, project roles, and how the two combine to decide what someone sees.

A **workspace** is your company. Projects, clients, members, and settings all
belong to one, and nothing crosses between workspaces.

## Workspace roles

Set under **Settings → Members**.

| Role       | Can do                                                                           |
| ---------- | -------------------------------------------------------------------------------- |
| **Owner**  | Everything, including billing, deleting the workspace, and enabling paid modules |
| **Admin**  | Manage members, projects, and most settings — but not billing                    |
| **Member** | Work on the projects they're added to                                            |

## Project roles

Workspace role is only half the picture. Someone is also given a role **per
project**, which is what actually decides whether they see a project at all.

| Project role           | Typically                                  |
| ---------------------- | ------------------------------------------ |
| **Owner**              | Accountable for delivery; gets escalations |
| **Manager**            | Runs the day-to-day, assigns work          |
| **Account manager**    | Client-facing; gets escalations            |
| **Member / Developer** | Does the work                              |
| **Viewer**             | Read-only                                  |

<Note>
  Workspace owners and admins can see every project. Everyone else sees only
  the projects they're a member of — which is also what limits what reports,
  search, and connected AI tools can surface for them.
</Note>

You can define your own project roles under **Settings → Roles** if these
don't match how your team works.

## Inviting people

**Settings → Members → Invite.** They receive an email; the invitation
carries the workspace role you picked. Add them to projects afterwards, or
invite them straight onto a project from the project's own members tab.

### Clients and external people

Clients don't need a full seat. Depending on the modules you have on, you can
share a read-only **client portal** link, or invite someone as an external
member limited to specific projects. See [Clients](/clients).

## Workspace settings worth setting early

<AccordionGroup>
  <Accordion title="Timezone">
    **Settings → General.** Business-hours calculations — including SLA
    deadlines — are interpreted in this zone, so set it before configuring
    SLAs. It's suggested from your browser but isn't saved until you confirm.
  </Accordion>

  <Accordion title="Workspace address">
    The link your team uses to jump straight to this workspace.
  </Accordion>

  <Accordion title="Statuses and types">
    **Settings → Statuses / Types.** Rename, recolor, and reorder the built-in
    task statuses, or add your own. See [Tasks](/tasks).
  </Accordion>

  <Accordion title="Discoverability">
    Optionally let people signing up with a teammate's email domain find and
    request to join, instead of waiting for an invitation.
  </Accordion>
</AccordionGroup>