10
🗯️ Let's talk about Appwrite's permissions once more
Source: appwrite/appwrite#3612 · opened by @Meldiron
👋 hello("World") There are some limitations to the current permission system, and we would love to address them in future releases. Some of these problems can be solved by separating data into multiple collections (to have multiple permission control points), and some needs to be solved with the Appwrite Function (custom backend). With that said, we can all agree that both of these solutions can be annoying, and everyone would benefit from a more robust permission solution. 🧰 Permission Levels Refactor 🔥 As of right now, you either apply document-level or collection-level permissions. You can never apply both, which makes some use cases difficult (unless you write Appwrite Function for it). We did this because previously, we applied both permission levels at the same time, but developers found that hard to understand. 🧯 We came up with a solution to go back to using both while still keeping it dead simple to understand. Long story short: During the permissions…
No pledges yet. Be the first to back this.
Comments
Similar requests
Appwrite CLI working with Multiple Projects
2 votes · 0 comments
🚀 Feature: "Query" Database by permissions
2 votes · 0 comments
Let's talk about Appwrite's permissions
7 votes · 0 comments
feat: OAuth Provider Group-to-Appwrite Team Mapping
1 vote · 0 comments
Console translation
1 vote · 0 comments
No comments yet.