> ## Documentation Index
> Fetch the complete documentation index at: https://support.essal.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# Resolve common app problems

> Check sign-in, permissions, saving, and connectivity before contacting support.

First identify which app, organization, and action are affected. A missing permission, interrupted connection, and service incident require different fixes.

| Symptom | What to check |
| - | - |
| Cannot sign in | App link, invited email, latest sign-in email, and account status. Follow [sign-in help](https://support.essal.cloud/getting-started/sign-in.md). |
| Missing page or button | Workspace, role, resource sharing, and modules enabled for that workspace. Ask its administrator. |
| Change does not appear | Look for a save confirmation or error, confirm the resource and workspace, then reopen it. Preserve unsaved text before refreshing. |
| Upload fails | Review the field’s displayed format and size requirements, connection, and permissions. Try a small permitted file without sensitive data. |
| Shared link is denied | Confirm the intended recipient, sign-in requirement, expiry or revocation, and resource permissions. |
| Access scan is denied | Check the displayed result, badge status, schedule, zone, and device synchronization. See [scan results](https://support.essal.cloud/access/check-in-devices/understanding-scan-results.md). |

Do not repeatedly submit an action that might create duplicate records or payments. Check for an existing result first.

For possible outages, check [service status](https://support.essal.cloud/introduction/status.md). For an unresolved issue, [send a support request](https://support.essal.cloud/introduction/contact.md). Do not clear browser storage on an offline Access device until pending scans are synchronized.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.