# Team & roles

> What someone may do, and who they are. Two different things.

Source: https://docs.usejot.co/docs/team

Jot keeps apart two things most tools squash into one field. A QA engineer can
be an admin. A founder can be a plain member.

## Role — what you may do

| Role       | Can                                                        |
| ---------- | ---------------------------------------------------------- |
| **Owner**  | Everything, including billing and deleting the workspace   |
| **Admin**  | Invite and remove people, create projects, change settings |
| **Member** | Comment, reply, triage, resolve                            |

A workspace always keeps at least one owner; the last one can't be demoted.

## Job label — who you are

**Founder** · **Product manager** · **Designer** · **Developer** ·
**QA engineer** · **Marketing** · **Support** · **Client** · **Stakeholder** ·
**Other**

The label sits next to someone's name on every Jot they file, so a developer can
tell a QA engineer's reproducible report from a stakeholder's opinion at a
glance. It changes nothing about what they are allowed to do.

## Inviting people

**Settings → Team**: enter an email, pick a role and a label, send. The
invitation link is tied to that address and expires after 14 days — it can't be
forwarded to someone else.

Reviewers are free and unlimited on every plan, including Free.

## Who can leave Jots

Each project picks one, in **Project → Settings → Who can leave Jots**:

* **Members only** (default) — reviewers sign in inside the widget with a
  6-digit code. The people who can sign in are exactly your workspace members;
  there is no second list to keep.
* **Anyone on the page** — no account needed. Visitors can leave their name and
  email if they want to hear back, and only ever see their own pins.

Turn on **Internal-only mode** to keep the widget for your team alone, even on a
public page. See [the widget reference](/docs/widget#internal-only).