Sorry for the added post, I do not know what “In GWS Admin Settings” means.
You have to go to admin.google.com and login with an admin account, so that you can disable the problematic setting. This applies for the account (Workspace domain) of the app creator and every Workspace domain used by the users to access your app.
1 Like
I was called by another customer who is accessing the app that is under my own account using his Workspace accounts. I failed to detect the error since it was working for me, but not for my client. I had to login to his workspace and do the same change. Double luck, I have a super admin account on that workspace as well 
It works both ways for Workspace users and workspace app creators, not only logged in users.
- If you have an app that is part of a Workspace, the app cannot have users with another domain, either consumer or Workspace. This will cause the app to fail for everyone even for the own Workspace users.
- If you have an app on a normal gmail account, no Workspace user will be able to access it. You’ll have to go each user Workspace domain and change this setting.
1 Like
Thank you for the reply. This is just baffling to me. I log in through Microsoft and have never had a Workspace account (that I am aware of, anyway.)
1 Like
it turned off the secutiry core thing and still my app is broken
Wait a few minutes.
2 Likes
If the app is part of a Workspace domain it will fail when you login with an account outside this domain, like in your case a Microsoft account.
sorry for my anxiety. you’re right! haha
1 Like
Someone else must be sorry for our anxiety ..
1 Like
Thank you for trying to help. So, if I’m the app creator and I don’t have a Workspace account (and it appears I can’t create one based on the admin.google.com link,) how am I supposed to fix the issue and give my clients the ability to log into the apps I created for them? Everything was working great for months. I just don’t understand. Am I supposed to log into Microsoft to work this out?
1 Like
This is outside of your hand. The solution is to contact each of your workspace clients (once per domain), and ask the workspace admin to implement this change in his own Workspace.
For example, you have created an app using your own non-Workspace account, and your customers are logging in using their user@customdomain.com which is a Google Workspace domain. You should then contact your customer and tell him to ask the admin of his customdomain.com workspace to modify this Appsheet security settings.
You have other users under another Workspace domain accessing your app, then you should contact them as well.
1 Like
A quick update here - this update has been partially rolled back, which should resolve most of these blocked user issues - a fix is being worked on before the rollout continues. Please let us know though if you’re still having issues right now with blocked users.
2 Likes
There’s hope Thank you!
I had acted already, so I can only confirm that turning OFF Appsheet Core Security restored access.
3 Likes
One of my client is working under MS auth only (office365 digital workplace).
Will this one be impacted by a setting on which he can’t have any control since he is not using GWS?
Thanks in advance for your consideration
@Aurelien if your Workspace org has the setting turned OFF (when it’s available to you), there should not be anything else preventing a non-Workspace user from accessing apps shared with them.
1 Like
Thank you for the quick response @peterdykstra .
t’s not a client in the sense of “I share an app to them”, but rather “I help them to implement their own AppSheet platform internally”.
From what I understood, they may encounter a situation by the time they get back to office. (Timezone UTC+1 here, almost midnight).
Sorry, I’m just having a hard time understanding this issue. Are you saying I need to contact each of the IT departments of each company (because they use their own domain name) that I created an AppSheet app for and have them adjust the Workspace setting on their end?
Yes, you need to contact each of those who are using Workspace accounts to login to your app. This is the remedy. But wait because the change has been rolled back (partially), and as per @peterdykstra 's advise, this is supposed to solve the issue. You might want to test it.
1 Like
Thank you for the reply. I hope this gets resolved. The clients have no idea that I’m using AppSheet to create their apps. If they find out, there’s zero reason they can’t build the apps themselves.
1 Like
I think they know; it is too visible, and I think you’re underestimating your value.
1 Like