Thanks for elaborating @kristyb. I see how your flow works for a closed community. For open sign up however, I’m finding that with the two way sync, an access code from the sign in with code block immediately adds the user to Airtable. This is a no code work around to authenticate an email address, but the trick after this seems to be configuring a User Profile block to capture more user info and password so they can log in again.
If anyone sees issues with this on-boarding workflow, please let me know and thanks in advance!
I need to be able to delete from the source and reflect the deletion on softr.
When I tried to delete from Airtable, Sofrt would not delete the record but instead would re-add it to airtable.
Softr’s “2 way sync” does not correspond both ways when deleting users from Softr AND from Airtable. As I mentioned early last year, builders would have had more control over their users if it was a complete 2 way sync, where users would be deleted in Softr when deleted in our databases. It’s because Softr was never sufficiently designed for external users, even though it was positioned that way, unfortunately.
@artur I need to pause the auto sync then delete the user using API. Next I will update the user email on the airtable then resume the auto sync. So that I can update the user email without creating new one.