Evaluating Appwrite Authentication: I have a few general questions

1. Linking accounts( ie, linking social providers, my github/google/username+email/xyz) is this supported, and if so are there any limitations for instance maybe can only link a user account with the same email from both social providers.

2. Migrating Auth0 -> Appwrite: is there any documentation on this process, is there any history of one of your Appwrite customers doign this migration. As well is this possible to transfer over social providers from Auth0 -> Appwrite without hiccup.

3. When taking a look at Github Social provider, I noticed that there was not a field to specify fine granular permissions on what our application has access to and was wondering if there is some documentation on this, specifically the permission available becuase we have a couple features where we are able to act on behalf of the user, the the access controll is very granular IE only to read public repos, and NOT private repos, ect...

Thanks for all the help.

I joined yesterday and was pointed to ask my many questions in here. Very open to collaborating and very pleased to see all the wonder work yall have been building.

Looking forward to a response!

Cheers,
Mark

1. Linking accounts( ie, linking social providers, my github/google/username+email/xyz) is this supported, and if so are there any limitations for instance maybe can only link a user account with the same email from both social providers.

Yes, in 1.4 we added Identities. It's not fully documented yet, but it allows a user to connect other (OAuth2) identities, regardless of email. A user would need to authenticate and then create an oauth2 session to create a new identity. There are some limitations with doing this on mobile, though.

2. Migrating Auth0 -> Appwrite: is there any documentation on this process, is there any history of one of your Appwrite customers doign this migration. As well is this possible to transfer over social providers from Auth0 -> Appwrite without hiccup.

No history of this, but we've seen migrating Firebase and GoTrue users. It would depend on if you can get the hashed password, and what the hash algorithm/params are. Depending on the algorithm, you would use the corresponding users API to create the user (e.g. https://appwrite.io/docs/references/cloud/server-nodejs/users#createArgon2User).

3. When taking a look at Github Social provider, I noticed that there was not a field to specify fine granular permissions on what our application has access to and was wondering if there is some documentation on this, specifically the permission available becuase we have a couple features where we are able to act on behalf of the user, the the access controll is very granular IE only to read public repos, and NOT private repos, ect...

When calling the Create OAuth2 session API you can pass additional scopes to request additional access. By default, it's only email

wonderful thank you for the speed response!

If your issue has been solved, you can mark this post as closed by adding "[SOLVED]" to the beginning of the title