Summary
Troubleshooting in Safety App helps you resolve the common errors and access problems that keep people from signing in or using the workspace. This article walks through the checks to run first, from confirming account status and role to clearing browser issues and network blocks, and explains what to gather before contacting support.
Introduction
Most problems people report in Safety App fall into a few predictable categories: they cannot sign in, they can sign in but cannot see something they expect, or a page fails to load correctly. Working through these issues in order lets you separate an account or permissions problem from a browser or network problem before it goes any further.
This article is written for everyday users who hit a snag, and for the administrators who help them. It focuses on the first-line checks anyone can perform and shows when to escalate an issue to your account manager or support team.
Key Concepts
- Access problem: any situation where a person cannot sign in to Safety App or cannot reach content they expect to see, usually tied to account status, role, or a network block.
- Active status: the indicator of whether a user can currently sign in; a deactivated account blocks sign-in even when the password is correct.
- Role: the assigned set of permissions that decides what a user can see and do, so a missing feature is often a role issue rather than an error.
- Pending invitation: an account that has been invited but not yet set up, which prevents sign-in until the person completes their account.
- Browser or cache issue: a local problem where stale cached data or a browser extension causes pages to load incorrectly, often confirmed by testing in incognito mode.
- Network block: a corporate VPN, proxy, or firewall that prevents Safety App from loading, often confirmed by testing on a different connection.
Steps to Follow
Confirming the sign-in problem
Start by pinning down exactly what happens when the person tries to sign in. Note whether they see an error message, a blank page, or simply cannot get past the login screen, and whether the problem affects one person or several. A single affected user usually points to an account issue, while many affected users at once points to a network or workspace-wide issue.
Checking account status and invitation
If someone cannot sign in, an administrator should confirm the account is set up and active in the users area. A deactivated account blocks sign-in while preserving the person's history, so reactivate it if access is still needed. If the person was recently added, check whether their invitation is still pending; until they accept the invitation and finish setting up their account, they will not be able to sign in.
Verifying the assigned role
When a user can sign in but cannot see a feature, report, or area they expect, treat it as a permissions question before treating it as an error. Open the user's entry, review the assigned Role, and confirm it grants the access the person actually needs. Changing the role adjusts their permissions, so review the choice carefully before saving.
Caption: The Users list lets you search and filter by Role, Status, and Department to review what a person can see and do.
Ruling out browser and cache issues
If a page loads incorrectly or behaves unexpectedly, have the person try again in an incognito or private window. If it works there, the cause is almost always cached data or a browser extension. Clearing the browser cache and disabling extensions usually resolves it. Testing in a second browser is another quick way to confirm the problem is local rather than in Safety App itself.
Checking the network and connection
If the app will not load at all, have the person try a different network, such as switching from office wifi to mobile data. If it works on the other connection, a corporate VPN, proxy, or firewall is likely blocking Safety App. In that case, your organization's IT team may need to allow access.
Gathering details for support
If the issue survives these checks, collect the information support needs so it can be diagnosed quickly. Note the URL the person is trying to reach, how many users are affected, whether it works on mobile data, and whether it works in incognito mode. Record the browser name and version and the operating system, and capture any red errors shown in the browser console. Sharing these details up front avoids a round trip and speeds up resolution.
Escalating to support
When you have run the checks above and the problem persists, contact your account manager or the support team with the details you gathered. Explain what you have already tried, since that lets support skip the first-line checks and focus on the underlying cause.
Conclusion
Working through Safety App issues in a set order, confirming the symptom, then account status, role, browser, and network, resolves most access problems without help and gives support a clear starting point for the ones that remain. Gathering the key details before you escalate keeps the whole process fast and predictable.