> 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/when-somethings-wrong/my-employee-cant-sign-in.md).

# My employee can't sign in

Expired invites, password resets going to the wrong address, and new starters who can barely see anything.

Four situations, and they look similar from the outside. Work out which one you have before doing anything.

## They never received an invite

Adding someone to **Setup > Employees** doesn't invite them. It creates the record and nothing more.

The invite is a separate step: go back to the employee list, find their row, and click **Invite to Schedulink**. That's when the email goes out.

It's easy to miss, because you've just filled in their details and it feels finished.

## The invite link expired

Invite links don't last forever. Someone who was added weeks ago and only got round to it now will find the link doesn't work.

Open **Setup > Employees** and look at their row. If **Invite to Schedulink** is still clickable, they haven't completed signup. Click it again to send a fresh link.

If that button is greyed out, they're already in, and the problem is something else on this page.

## Password reset codes going to the wrong address

This one catches people badly.

**Your sign-in email and your profile email are two different things.** The one in My Profile is only used for notifications, and changing it doesn't change how you log in. Your sign-in address is separate, can't be edited by you, and is where password reset codes are sent.

So someone who updated their profile email months ago, then clicked Forgot Password, is waiting for a code at an address the system was never going to use.

Ask them to check the address they originally signed up with. If that mailbox is genuinely gone, get in touch and we'll change the sign-in address for them. Being able to do it yourself is on the way.

## They're in, but they can barely see anything

Not a sign-in problem. They've signed in successfully and are looking at a very reduced version of the app.

Everyone starts on the **Default** permission set, which gives read-only access to seven areas and nothing else. Until somebody assigns them a fuller set, that's all they get.

The **Permissions** field only appears on their profile after they've completed signup, which is why this step gets forgotten: the person setting them up looked for it on day one, didn't find it, and moved on.

Open **Setup > Employees**, open their profile, and set User Permissions. It applies immediately. See Permissions.

## Nobody can edit anything

If this is several people at once rather than one, it's billing rather than access. A lapsed subscription blocks editing across the app while viewing keeps working. See Why can't I see a page or button?


---

# 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/when-somethings-wrong/my-employee-cant-sign-in.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.
