Strange App Visibility Issue in SeaTable Cloud - Role-Based Permissions Unexpectedly Reset?

[Soonimproveduser]

Hi everyone,

I’m experiencing a peculiar issue with SeaTable that I’m hoping someone might have encountered before or can offer some insight into.

I’m using SeaTable via the cloud service, and I’ve built an app within a base. The app contains multiple pages. Access to these pages is controlled via role-based permissions, ensuring that only specific roles can view certain pages. This setup has been working flawlessly for months.

However, a colleague recently reported that she can no longer see the entire app, despite her role settings being correct (as far as we can tell). Upon investigation (as an admin), I discovered that the page permissions for several pages within the app had been inexplicably changed to “Nobody.” I definitely did not make this change manually, especially not across multiple pages, and haven’t touched the app configuration in months since it was running smoothly.

This sudden change in permissions is perplexing. Has anyone else experienced a similar issue where role-based permissions seem to reset themselves or change without any manual intervention, especially when using the cloud version of SeaTable?

I’m trying to understand what might have caused this and how to prevent it from happening again.

Some additional information, we are using the SeaTable cloud service.

Any advice or suggestions would be greatly appreciated!

Thanks in advance

[rdb]

In what way is this issue different from what you posted here?

I am not aware of any other reports of unintentional permission modifications.

[Soonimproveduser]

Different issue, in the same base, but two different Apps.

[rdb]

Sorry for asking again, but in what way is this issue - the permissions were modified to “Nobody” - different from the other one?

[Soonimproveduser]

Nevermind.