@Chr1sG I understand the limitations. As @Oshyan pointed out, I guess the options we are suggesting (either having conditional control over fields and/or multiple layouts) would be half measures from a permission-perspective but they would also have other useful benefits. So they can be suggested as possible workarounds (along with separate dedicated database as @mdubakov indicated) each with their own limitations, so creators can choose based on their needs. For example, in many cases, hiding or locking fields is not so much a matter of security but convenience/user experience.
cannibalflea
71
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Permissions - entities vs views | 36 | 1909 | December 7, 2022 | |
| Nov 16, 2023 / 🔒 Entity permissions (experimental) | 60 | 2167 | June 18, 2024 | |
| Feature Request: Share Space but restrict entity views | 53 | 718 | March 29, 2025 | |
| Q3 2025 Roadmap | 77 | 1417 | September 15, 2025 | |
| July 25, 2024 / Entity access explained, markdown import, hidden Fields section | 17 | 374 | November 6, 2025 |