I'm wondering if it's possible for a guest or anonymous user to create a document and attach an email address to it, so that the document can later be claimed by a registered user once they sign up.
I understand this might be doable by assigning permissions to the anonymous user, but the challenge comes when the user switches browsers or devices — at that point, it's not the same anonymous session anymore.
Is there a recommended pattern or best practice for handling this kind of flow in Appwrite?
Keeping a collection with only email field fulfilled. If anyone signs up check in that list Delete if match then create on the users collection with proper data
Recommended threads
- Streamlit UI and local DB
I want to use Appwrite for automation, like run watchdog service every morning 3 am. Anyone got suggestions, already explored github and documentation no luck. ...
- [SDK] [Postman] Can't post to Users usin...
when trying to post to users I'm getting missing scopes and at the same time I'm getting an authorised scope How do I generate an API and get around this issue
- Auth broken after update from 1.8.0 to 1...
So ive been having issues creating, deleting or updating users on my appwrite instance after i updated from 1.8.0 to version 1.9.0. When trying to create a user...