Troubleshoot Sign-In Errors

Type: Troubleshooting Module: Sign-In (bonus) Template: v0.5

At a glance

This article resolves the six sign-in errors that generate the most support tickets: the "not associated with a restaurant location" message, the "permission denied" message, the CFA Wi-Fi authentication block, the Google-versus-Create-an-Account mismatch, the archived-team-member lockout, and the Operator account-already-exists error. Each section starts with the exact symptom, walks through causes in order of likelihood, and ends with the recovery path.

Before you start

If you are still figuring out how to sign in for the first time, read Sign In to OneClick first; that article covers the first-time paths. For background on why these errors happen (the midnight sync, the 3-month archive rule, the two-permission-check pattern), see Understand OneClick Sign-In.

The pencil-icon refresh described below requires a Shift Leader or higher at the relevant store. If the affected team member is the only person at the store, they will need a leader to step in or a Support ticket to unblock them.

"Sorry, this email address is not yet associated with a restaurant location"

The full message is: Sorry, this email address is not yet associated with a restaurant location. Ensure you login with your email as listed in HotSchedules. If your email is correct, then your account will be automatically linked soon, after which you may log in as normal.

Three possible causes, in order of likelihood.

Cause 1: Wrong email

The most common cause. The email on the sign-in attempt does not match the email on the HotSchedules record.

How to check: ask your leader to confirm the email on your HotSchedules record, or log into HotSchedules directly. Compare that email character-for-character to what you are typing into OneClick.

How to fix: sign in again using the exact HotSchedules email. If your HotSchedules email is Google-based, tap Google Sign-in. If not, tap Create an Account.

Cause 2: New hire, midnight sync has not run

OneClick syncs with HotSchedules at midnight each night. A team member added to HotSchedules today cannot sign in to OneClick until the next midnight sync completes.

How to check: ask your leader when you were added to HotSchedules. If the answer is "today" or "this shift," the sync is the cause.

How to fix: two options. Wait until tomorrow; the midnight sync runs automatically. Or contact OneClick Support to force a manual sync cycle (1 to 15 minutes).

Cause 3: Server miscommunication, record is stale

The least common cause, and the only one that requires another person's help. Your HotSchedules record exists and the email is right, but the OneClick server has a stale version of your record.

How to fix: a Shift Leader or higher at your store refreshes your record.

1. They sign in to their own OneClick account.
2. They open your team-member profile.
3. They tap the pencil icon next to your email.
4. A confirmation pop-up appears showing your email. They tap OK.
5. You sign in again.

The record refresh propagates in 1 to 15 minutes.

"Sorry, you don't have permission to access this location"

The full message is: Sorry, you don't have permission to access this location. Select another from the list below.

Two possible causes.

Cause 1: Recent store move, sync has not caught up

You were recently moved from Store A to Store B in HotSchedules. The OneClick server still has you associated with the old store.

How to fix: a Shift Leader or higher at the new store runs the same pencil-icon refresh as Cause 3 above.

1. They sign in to their own OneClick account at the new store.
2. They open your profile.
3. They tap the pencil icon next to your email.
4. They tap OK on the confirmation pop-up.
5. You sign in again.

Cause 2: Marked archived or terminated

Either the 3-month no-shifts archive rule has applied (OneClick automatically archives anyone not scheduled for 3 months), or a leader has unchecked Team Member on your profile.

How to fix: a Manager or higher opens your profile and confirms the Team Member checkbox is checked. If it was unchecked, re-checking it restores your access immediately. If the archive rule caused the lockout, schedule the team member for an upcoming shift and the next sync cycle will automatically reactivate them.

For details on the archive rule and termination grace period, see Understand OneClick Sign-In and Understand Permission Levels.

Sign-in times out or loops on CFA Wi-Fi

CFA Wi-Fi occasionally blocks the sign-in authentication flow. The issue is sporadic: it can work one day and block the next. Only the initial authentication is affected; ongoing app usage on CFA Wi-Fi is fine.

How to fix:

1. Switch your device to a phone hotspot or another network.
2. Complete sign-in.
3. Switch back to CFA Wi-Fi for normal use.

If you cannot switch networks, contact OneClick Support and include the error code or screen that appears during the block.

Google sign-in prompts for a password, or Create-an-Account rejects the email

This is the Google-versus-Create-an-Account mismatch. It happens when the wrong first-time path was chosen for the email type.

How to check: open HotSchedules and look at the email on your record. If the domain is gmail.com or a Google-managed workspace domain, your sign-in path is Google. Otherwise, it is Create an Account.

How to fix: back out of the current sign-in attempt and start over on the correct path.

• Google-based email: tap Google Sign-in on the login screen and authenticate through Google.
• Non-Google email: tap Create an Account and set a OneClick-specific password.

If the error persists after choosing the correct path, the HotSchedules email may be typed wrong on your record. Ask your leader to verify.

Team member disappeared from OneClick after no scheduled shifts

OneClick automatically moves team members to Archived status when they have not been scheduled in HotSchedules for 3 months. Archived team members cannot sign in and do not appear in the active team-member list.

This is normal behavior, not a bug. Archived team members are not deleted; their data is preserved.

How to fix:

1. Schedule the team member for an upcoming shift in HotSchedules.
2. Wait for the next sync cycle (1 to 15 minutes, or the next midnight sync, whichever comes first).
3. The team member reactivates automatically and can sign in again.

If the team member needs access without being regularly scheduled (for example, a leader covering across stores), apply the Long-Term Employee tag instead. Contact OneClick Support with the store number and the team member's name to apply the tag.

Operator account-already-exists error

When an Operator tries to Create an Account and the system returns that an account already exists with this email, the cause is almost always that the Operator is tied to two OneClick stores and has already set up credentials at the first store.

How to fix: do not create a second account. Instead:

1. Sign in with the credentials from your first store.
2. Tap the profile icon at the bottom left.
3. Tap Switch Account.
4. Choose the second store from the list.

If the second store does not appear in the Switch Account list, your two stores may have different HotSchedules emails. Contact OneClick Support to link the accounts manually. For details on multi-store mechanics, see Understand OneClick Sign-In.

When to escalate

If none of the above resolves the sign-in problem, contact OneClick Support with five pieces of information. Most escalations stall because one of these is missing.

1. The exact error message (a screenshot is ideal).
2. The team member's name and HotSchedules email.
3. The store number.
4. The device type (iPad, iPhone, Android, web browser).
5. Whether the store has already tried the pencil-icon refresh.

Video

Video placeholder.

Related articles

• Sign In to OneClick
• Understand OneClick Sign-In
• Download the OneClick App
• Understand the Service Account
• Understand Permission Levels
• Request a Permission Change

Still stuck?

Contact OneClick Support from the Chat menu, or email support@oneclickapp.com.