[Subject]
Bug Report: User stuck in “Invited” status causing “Access Denied” error, resolved by temporarily changing permission to “Edit app”
[Overview]
In an AppSheet app, after adding a specific user to the Share list with “Use app” permission, their status remained stuck on “Invited,” and they encountered an “Access Denied” error when trying to log in. We ultimately resolved the issue by temporarily changing the user’s permission to “Edit app,” which seemed to normalize the system-side account synchronization. I am reporting this to request an investigation and potential fix for this status-sync freezing issue.
[Details of the Issue]
- App Status: Linked with Google Workspace, AppSheet Core license applied (not hitting the 10-user limit of the free plan), and fully Deployed.
- Error Encountered: The user was presented with an “Access Denied” screen upon login. The Audit Log also recorded an “App Access Denied” error.
- Ineffective Troubleshooting Steps: Clearing browser cache, accessing via Incognito mode, changing the Authentication provider to “Any provider,” disabling “Require domain authentication,” and removing/re-adding the user from the Share list.
[Suspected Trigger / Background]
Prior to adding the correct user address (e.g., user@tamsoft.dev), an access request and registration were mistakenly processed using their alias address (user@tamsoft.co.jp). This was later corrected to the .dev address. We highly suspect that the alias information on the Google Workspace side conflicted with the internal AppSheet ID linkage (SSO history) in the backend, causing the permission assignment process to freeze.
[Effective Workaround]
- On the app’s Share screen, change the affected user’s permission from “Use app” to “Edit app,” then Save.
- Have the user attempt to access the app again. (The login and sync succeeded normally at this point).
- Revert the permission from “Edit app” back to “Use app.” The user maintained normal access without further issues.
[Request for the Support Team]
It appears that changing the role to “Edit app” acted as a trigger to forcefully refresh and overwrite the backend permission data. We request that the engineering team investigate this issue where a user’s “Invited” status gets stuck—likely due to alias address history or SSO ID conflicts—and improve the backend synchronization process to prevent this in the future.