The possibilities to set the page permissions in SeaTable like this make no sense:
Somebody who is not allowed to see the page can edit it?
No, it doesn’t make sense. Agreed. But no one forces you to configure the page like that.
What is the point you try to make?
Note: When posting screenshots, please set your UI language to English so everyone can otherstand.
Correct, I didn´t get forced to do it that way.
However, this is a total unnecessary source for failure, which could be prevented by design.
When you delete a table/column that is used in an automation, the automation stands to break. When you delete an email account, your buttons / automations may not send emails anymore. When you modify a view that is the basis for a common dataset, you may cause a data leak.
All these things can be avoided by actively managing dependencies.
This is a topic for the future development. But the topic is all but bottomless. Your case is - IMHO - a rather trivial case as it has no grave consequences.
Finally, you can post these feature requests in https://ideas.seatable.io
