🚀 Feature: about read only prefs

[zdanl]

🔖 Feature description

as mentioned before, userPrefs 🌈 is a great feature for extensibility 🧬 of fields, like verified ✔️ , but is user-writeable. leaving it not very useful to render internal purposes with solidity.

i am suggesting, once more, userPrefsRo / userPrefsReadOnly / userPrefsVault. visible in the web console, editable in the web console, but only to Administrators, yet extended to the browser.

could we discuss, therefore, adding this functionality? or could one provide "the life of a user field" from MariaDB to Appwrite Web Console, for quick hacks turning full features?

Best,
d

🎤 Pitch

i realize there may be other ways like harnessing database docs to accomplish what we would like to do, but -- if we want to mess with standard appwrite, even in the format of leaving it as a useful pull request and not just bending it to our needs -- how would i, for example, add a "role" field? is there an example of how to integrate this with teams, in a secure way?

but disregarding "role", our application requires a full banking KYC for "verified" users. meaning, our "verified" is different from just the email confirmation "verified" field, and we would like to use it that way.

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

[stnguyen90]

@zdanl, thanks for creating this issue! 🙏🏼 As you pointed out, we recommend creating a custom collection for this type of data.

Related issue: #4805

how would i, for example, add a "role" field?

This would be a little complicated as there would be multiple places where this would need to be modified. At the very least, the users collection would need to be modified. Then, various places where the user document is used would need to be updated.

[rafagazani]

Subscribing here, would also like to see this feature