> 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/why-cant-i-see-a-page-or-button.md). # Why can't I see a page or button? A menu, button or record that isn't there for you. Almost always permissions, occasionally billing. Something a colleague can see isn't there for you, or a feature you used last week has gone. This is the most common thing studios ask us about, and it's almost never a bug. Work through these four in order. ## 1. Your permissions The usual answer. Each area of Schedulink has two switches on your permission set: **Read** lets you see it, **Write** lets you change it. With neither ticked, the area doesn't appear greyed out. **It isn't there at all.** So your app genuinely looks like a version of Schedulink that never had Templates, or Employees, or whatever is missing. Nothing tells you why, which is exactly why this gets reported as something broken. Whoever administers your studio can check in **Setup > Employees**: open your profile, see which permission set you have, then open that set in **Setup > User Permissions** and look at the area in question. Changes take effect immediately. No need to log out and back in, just refresh. Scheduling is the one exception. It isn't permission-controlled yet, so everyone can see it. ## 2. A new starter still on the Default set If it's someone who joined recently and can see very little, this is why. Everyone starts on the **Default** permission set, which gives read-only access to seven areas and nothing else. They can look at accounts, events, tasks and contacts, but they can't change anything and most of the app isn't there. That's not a mistake, it's just the starting point. Somebody has to assign them a fuller set. The step gets missed because the **Permissions** field only appears on an employee's profile after they've completed signup. Whoever set them up looked for it on day one, didn't find it, and never went back. See Employees. ## 3. Your subscription If **several people** suddenly can't change anything, this is the one. When a subscription lapses, editing is blocked across the app while viewing carries on working. So it looks like everyone's permissions were stripped at once, which is alarming and wrong. Check it under **Setup > Organization**, then Billing. ## 4. They never finished signing up If someone can't get in at all, rather than seeing a reduced version, that's a different problem. See My employee can't sign in. ## What this usually isn't **A record that vanished** is more often a filter than a permission. Filters persist between visits, so one set weeks ago and forgotten is the commonest reason something appears to be missing. Clear your filters first. See Working with lists. **An event that left your calendar** after you added a sub-event is behaving correctly. See Sub-events and your calendar. **A menu that moved** rather than disappeared. Templates used to sit under Setup and now has its own place in the top bar. ## Still missing If your permissions look right, your subscription is current and you've cleared your filters, get in touch. Tell us what you're expecting to see, where you'd expect to see it, and who it's affecting, and we'll take a look. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://schedulink.io/help-center/when-somethings-wrong/why-cant-i-see-a-page-or-button.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.