Login issues
Issue: 403 Forbidden error when accessing Visualcare
Symptoms: A 403 Forbidden error appears when trying to open Visualcare. Cause: Visualcare blocks access from international IP addresses for security reasons. If you’re connecting from outside Australia, your request is rejected before the login screen loads. Fix:- Connect to a VPN set to an Australian server
- Once the VPN is active, navigate to Visualcare as normal
International IP addresses are not permitted to access Visualcare directly. A VPN connected to an Australian server is the only supported workaround for overseas access.
Issue: SSO login loop after Microsoft sign-in
Symptoms: After entering Microsoft credentials, the user is stuck in a login loop or receives an error. Cause: When Single Sign-On (SSO) is enabled for a user, the system expects the SSO login flow. A mismatch between the user’s SSO configuration and their Visualcare account can prevent the login from completing. Fix:- Disable SSO for the affected user in Users → select the user → disable SSO
- Ask the user to sign in with their standard Visualcare username and password
- Once the user has signed in successfully, re-enable SSO for the user
Issue: Worker unable to log in to the vWorker app
Symptoms: A worker reports being unable to log in to the vWorker app. Cause: This is most commonly caused by an incorrect username or password, or a worker profile that hasn’t been set up correctly. Fix:- Ask the worker to confirm they’re using the correct username and password
- If the password is incorrect, go to the Worker Profile, locate the active worker account, and use the Reset Password option
- If the password is correct but login still fails, review the worker’s profile to confirm it’s set up correctly and linked to an active user account
- If the issue persists after checking credentials and profile setup, ask the worker to uninstall and reinstall the vWorker app, then attempt login again
- If the worker is still unable to log in, raise a ticket with the Visualcare helpdesk at support@visualcare.com.au
Issue: Clearing browser cookies and cache
Several fixes on this page ask you to clear your browser’s cookies and cache. Each browser does this differently - use the official guide for yours:Access and permissions
Issue: Suspend button not visible in Users
Symptoms: A user navigates to the Users section but the Suspend button (used to deactivate a user account) doesn’t appear. Cause: The Suspend button is controlled by a User Group Security permission. If the user’s assigned User Group doesn’t have permission to view other user groups, the button is hidden. Fix:- Go to User Group Security
- Select the User Group assigned to the affected user
- Expand the Settings section
- Set User Groups permission to Show
- Click Save
This permission change needs to be made by someone in your organisation with User Group Security access. The Visualcare helpdesk is unable to modify user permissions on your behalf.
Issue: User unable to view documents
Symptoms: A user navigates to the Documents screen but expected documents don’t appear. Cause: This is usually caused by active filters hiding document categories, or User Group permissions restricting access to one or more Worker Document Categories. Fix - clear filters:- Go to the Documents screen
- In the top-right corner, click Reset Filter to clear any active filters
- Check whether the documents now appear
- Go to Maintenance → Document Categories
- Select Worker Documents
- Review the User Group Permissions section and confirm the correct User Groups have access
- Click Save
Issue: User unable to view worker pay rates
Symptoms: A user cannot see worker pay rates while rostering or in the Timesheets section. Cause: The user’s User Group does not have the pay rate permission enabled. Fix:- Go to Settings → User Group Security
- Select the User Group assigned to the affected user
- Click the Workers tab
- Set Worker Finance Tab and Pay Rate in Rosters and Timesheets to Show
- Scroll down and click Save
- Ask the user to refresh and confirm the pay rate field now appears
Issue: Users cannot see the Incidents tab
Symptoms: The Incidents tab does not appear for a user. Cause: One or more of three User Group Security permissions is missing. Fix:- Go to User Group Security and select the user’s User Group (if you’re unsure which group the user is in, go to Users, select the user, and note their User Group)
- Check all three of these permissions:
- Home → KPI Incidents is set to Show
- Clients → Ability to View Incidents is set to Yes
- Worker → Worker Incidents is set to Show
- Click Save
Issue: User unable to create a contact
Symptoms: A user cannot create a contact. Cause: The Contacts to Show permission is missing from the user’s User Group. Fix:- Go to User Group Security
- Select the relevant User Group
- Click Maintenance to expand the permissions
- Enable Contacts to Show
- Click Save
Running into issues?
If your issue isn’t listed here, contact the Visualcare helpdesk at support@visualcare.com.au.Related articles
Logging in
How to log in to Visualcare, including SSO and standard login options
Resetting your password
Steps to reset a forgotten or expired password
User group security
Configuring permissions for user groups in Visualcare
User access control
Managing user accounts and access levels
vWorker app login
How workers log in to the vWorker app
vWorker app access
Managing worker access to the vWorker app
