topic Re: Loyalty Settings Locked? in Restaurant Operations

Loyalty Settings Locked?

JesseQ — Tue, 15 Aug 2023 23:17:07 GMT

I'm trying to change the settings of our loyalty program, specifically the fraud alert setting, but its not allowing me to change anything. The button are greyed out and aren't doing anything when I try to click them. What do I need to do to change these settings

Re: Loyalty Settings Locked?

rcmck — Tue, 15 Aug 2023 23:35:19 GMT

Are you the account owner? Check that you have permissions 4.13 Customer credits and reports enabled.

Re: Loyalty Settings Locked?

JesseQ — Wed, 16 Aug 2023 00:06:37 GMT

Yes I am, and do have the permission enabled

Re: Loyalty Settings Locked?

rcmck — Wed, 16 Aug 2023 00:17:59 GMT

Possible to share a screenshot of what you are seeing?

Re: Loyalty Settings Locked?

au79teahouse — Wed, 16 Aug 2023 00:22:12 GMT

Try to clear your browser cache and cookies, and then login with account that has the permission to configure loyalty program.

Re: Loyalty Settings Locked?

JesseQ — Wed, 16 Aug 2023 19:43:30 GMT

Re: Loyalty Settings Locked?

rcmck — Wed, 16 Aug 2023 21:12:56 GMT

Have you tried the suggestion of clearing browser cookies and cache yet? Also noticed a setup checklist on your screen, its not for loyalty is it?

Re: Loyalty Settings Locked?

JesseQ — Wed, 16 Aug 2023 21:40:15 GMT

Tried that. Didn't work

Re: Loyalty Settings Locked?

JesseQ — Wed, 16 Aug 2023 21:41:05 GMT

Yes that didn't seem to work. And the set up checklist is there for our xtrachef account we didn't set up yet

Re: Loyalty Settings Locked?

rcmck — Wed, 16 Aug 2023 21:49:36 GMT

Ok, maybe @Rob can take a look at this, seems like a deeper issue than we can troubleshoot.

Re: Loyalty Settings Locked?

JesseQ — Thu, 17 Aug 2023 02:02:30 GMT

Was just able to figure this out. There was another owner account set up when we started. When we went in through there, i was able to adjust settings. Thanks for the help

Re: Loyalty Settings Locked?

rcmck — Thu, 17 Aug 2023 02:12:08 GMT

Ahh, so it was a permissions problem after all, glad you got it straightened out!