> 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/permissions.md).

# Permissions

Control what each person at your studio can see and change.

A permission set decides which parts of Schedulink someone can see and change. You build the sets once, then assign one to each employee.

**Setup > User Permissions**, then click Add.

Give it a name that describes the job rather than the person, like Photographer, Coordinator, Editor or Office Manager, and add a short description so whoever inherits your account knows what it was for.

## Read and Write are separate

Each area has two independent switches rather than a single level.

**Read** lets someone open the area and look at what's there. **Write** lets them add, edit and delete. Tick neither and the area disappears from their app entirely.

That last point is the one worth remembering. Someone with no Read on Templates doesn't see a greyed-out menu, they see no Templates menu at all, which is why a missing feature usually turns out to be a permission rather than a bug.

## What you can control

Eighteen areas, in four groups.

**Your day-to-day records**

| Area      | Read | Write |
| --------- | ---- | ----- |
| Accounts  | Yes  | Yes   |
| Events    | Yes  | Yes   |
| Tasks     | Yes  | Yes   |
| Contacts  | Yes  | Yes   |
| Employees | Yes  | Yes   |

**Templates**

| Area               | Read | Write |
| ------------------ | ---- | ----- |
| Event Templates    | Yes  | Yes   |
| Task Templates     | Yes  | Yes   |
| Email Templates    | Yes  | Yes   |
| Form Templates     | Yes  | Yes   |
| Account Templates  | Yes  | Yes   |
| Contact Templates  | Yes  | Yes   |
| Employee Templates | Yes  | Yes   |

**Studio settings**

| Area             | Read | Write |
| ---------------- | ---- | ----- |
| Preferences      | Yes  | Yes   |
| User Permissions | Yes  | Yes   |
| Organization     | Yes  | Yes   |
| Integrations     | Yes  | Yes   |

**Data**

| Area             | Read | Write |
| ---------------- | ---- | ----- |
| Reports          | Yes  | Yes   |
| Form Submissions | Yes  | No    |

There's no Reports menu in the app. This one controls whether someone can export data as CSV from your lists, so leave it off for anyone who shouldn't be taking your client list home.

Form Submissions is read-only by design, because a submission is a record of what a client sent you and shouldn't be editable after the fact.

Scheduling isn't on this list yet, so everyone with an account can currently see the Scheduling page. Permission control for it is coming.

## The set you start with

New studios get a default set with read access to Accounts, Events, Tasks, Contacts, Employees, Preferences and Task Templates.

It's an ordinary permission set, not something special, so edit it or ignore it as you prefer. Most studios build their own and leave the default for anyone whose role hasn't been decided yet.

## Changes apply immediately

Assign or change someone's permission set and it takes effect straight away. Nobody needs to log out and back in.

So if you're on the phone with someone who can't see a page, you can fix it while they're still on the call and ask them to refresh.

## Building sets that work

A few patterns that hold up across studios.

**Photographers** usually need Read on Events and Tasks, Write on Tasks so they can complete their work, and nothing else. Templates and settings are noise to them.

**Coordinators** need Write on Accounts, Events, Tasks and Contacts, Read on Templates so they can see how jobs are built without changing them, and Read on Form Submissions.

**Editors** often need very little: Read on Events, Write on Tasks.

**Office managers and owners** get Write on everything, including User Permissions and Organization.

Start tighter than you think you need. It's easier to grant access when someone asks than to explain why a photographer deleted an event template.

{% hint style="warning" %}
Be careful with Write on User Permissions. Someone with it can change their own access, and can also remove yours. Keep that one to the people who run the studio.
{% endhint %}

## When someone can't see something

Almost always a permission. Open **Setup > Employees**, check which set they have, then open that set and look at the area in question.

If their permissions look right, the other two causes are a lapsed subscription, which restricts editing across the board, and an expired invite link, which means they never fully joined.


---

# 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/permissions.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.
