> For the complete documentation index, see [llms.txt](https://schedulink.gitbook.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.gitbook.io/help-center/setup-and-configuration/user-permissions.md).

# User Permissions

Onboarding a team member has three steps, and order matters. Define what they can access first, then invite them, then assign their permissions.

***

### Step 1: Define user permissions

Do this before inviting anyone.

1. Go to **Setup > User Permissions**
2. Click **Add**
3. Give it a clear name — e.g., "Admin," "Photographer," "Manager"
4. Add a short description of what the role is for
5. Set access for each module:

| Level | What they can do              |
| ----- | ----------------------------- |
| Read  | View data, but not change it  |
| Write | View, add, and edit data      |
| None  | Cannot see this module at all |

***

### Step 2: Invite the employee

1. Go to **Setup > Employees**
2. Make sure the employee record exists — add their details if not
3. Find the person in the list and click **Invite to ScheduLink**

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

Once they sign up, the **Invite to ScheduLink** button will go gray. That confirms they're in the system.

***

### Step 3: Assign their permissions

You can't do this until the employee has accepted the invite and signed up.

1. Once the invite button is disabled, open their profile in **Setup > Employees**
2. Find the **User Permissions** field
3. Select the role you created in Step 1
4. Save

They now have access based on the rules you defined.