I’m new to Adalo, but not to Databases. I have built an app that has account users with login accounts. I am able to use an intermediate ‘People’ Table to successfully create new users who can share data with an account ‘owner’. So I have an account, I can invite someone else to share my data (a helper if you like) Helpers are user accounts who are link to my data. So far so good…
the problem comes when an invitee already has an account in my app. I cannot ‘create the user’ because they already exist… So I need to link an existing user to my data… (I’ve created User Owners and User Helpers fields within Users and withing the data… As the app owner I can add the user to my data easily, but I obviously dont want all the users to surface when trying to create a link. zapier doesnt have a search finction so that’s a non starter, Has anyone found a way of users within an app, to invite other users to share their app data? It seem to me to be a fairly big ommision?
A work around would be to check if an email address existing in the user table, but I cant seem to find any conditional data rules… i’m probably missing something.
you’ve created People table as a junction table, which has 2 relationships with Users
each record in People represent a “link” between an Owner and Helper?
If yes, then:
I can see that there should be 2 ways to add a new record to People table:
→ case A: Helper User record doesn’t exist
→ case B: Helper User record exists.
Then you can do something like: on a screen add an input and a list. Make list a list of Users, filtered by User → Email is equal to Other Components → Input.
Make this list conditionally visible: if Other Components → Input is not equal to empty. Otherwise it will show all users to you.
Then add a button, make it conditionally visible, so that Users → Count, where User → Email is equal to Other Components → Input, is equal to 0. The idea here is to show this button only when the number (count) of users with the email == email in the input is 0 (meaning there is no such user).
As a result:
→ when logged-in user enters the email of a nonexistent user, button is visible. On this button you can add the invitation flow (create user etc.)
→ when logged-in user enters the email of an existing user, the list entry is displayed. Then you can add an action to this list to add Current User to needed People relationship.
Hi Victor, Thanks for your reply. I have been away for a few days hence my slow reply to you.
The very last point is the point of pain… and this might solve the problem. I’m coming from environments where user accounts are only ever managed by users themselves, and they might get invitations to join another site, indeed might have a dashboard of many such memberships, and the app manages invited users centrally. I will circle back if this is the answer with kudos and thanks :-). Best wishes, Chris.