> For the complete documentation index, see [llms.txt](https://schedulink.io/help-center/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://schedulink.io/help-center/set-up-your-studio/employees.md).

# Employees

Add your team, invite them, and give them access to the right parts of Schedulink.

An employee is anyone at your studio who works in Schedulink: photographers, coordinators, editors, front desk, admins.

Getting someone set up takes three steps, and the order matters because you can't assign access until they've accepted their invite.

## 1. Decide what they should see

Before inviting anyone, make sure a permission set exists for the kind of work they do. A photographer needs a very different view from an office manager.

If you haven't built these yet, start with Permissions.

## 2. Add and invite them

Go to **Setup > Employees**. If the person doesn't exist yet, add their details. Then send them an invite, either from their row in the list or from their own page.

They'll get an email with a link to create their account.

## Where everyone stands

The employee list shows a status against each person, so you can see at a glance who's actually in.

| Status         | What it means                                      |
| -------------- | -------------------------------------------------- |
| Not invited    | They exist in Schedulink but nothing has been sent |
| Invited        | The email has gone and they haven't signed up yet  |
| Invite expired | The link ran out before they used it. Send another |
| Active         | They've signed up and can use Schedulink           |

Their own page carries a banner telling you what to do next, and you can send or resend from either place.

Every invite sent, resent or accepted is recorded in their activity log, along with the email address it went to. So if an invite went to a typo and you corrected it, both addresses are on record.

{% hint style="warning" %}
**Anyone who isn't Active doesn't hear from you.** They can be assigned to jobs and they'll show on the schedule, but publishing sends them neither the email nor the text, because there's no account to send to.

Worth running your eye down this list before you publish a week.
{% endhint %}

## 3. Assign their permissions

You can't do this until they're Active. Open their profile in **Setup > Employees**, find the **User Permissions** field, choose the set you want, and save.

The change applies immediately. They don't need to log out and back in.

{% hint style="info" %}
This is the step most often missed. Adding someone and inviting them doesn't give them access on its own, so if a new starter says they can't see anything, check that a permission set was assigned.
{% endhint %}

## When someone leaves

Archive them rather than deleting. Archiving keeps the record of what they worked on and takes them out of the lists your team picks from, so nobody gets assigned to a job by mistake.

They're still there if you need them. Use the archived toggle on the filter bar to the left of the employee list to see archived people, which is what you'll do if a seasonal photographer comes back next autumn.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://schedulink.io/help-center/set-up-your-studio/employees.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
