EliEliOriginal post
Web Developer
Hi, I'm evaluating appwrite for a project and through reading the documentation (I haven't coded/tested anything yet, just trying to have a grasp of the basic framework for now against supabase), it reads to me as though anyone having an "update" permission is also granted to change the permission itself on a document.
A concrete example, a row is set by some server side function to be "owned" by team A by which I mean any member of team A can update said row's columns (name, description, etc) but it appears to me that "permission" is just another column which reads to me that then any of these users in team A, can set the permission values to whatever it wants? Do I understand this correctly?
Summary
The user is evaluating Appwrite and unsure about permission changes. They are concerned that users with the "update" permission can also change the permission itself on a document. It seems like any member of Team A can update columns and also change permission values.
Solution: The permission change is tied to the update permission. This means users with the update permission can also modify the permission settings for a document.