Add user, add or change details

Hi, need some help on this as I have not been able to find tutorials.

User A creates account for user B (A can also create C, D, E, F, etc. but in this case only B).
A and B can then add details for user B on the “user B details page” (of course, A can do this immediately, B after he or she has received an e-mail and created a password for his account).

My question:

  1. I have created the page from where A can create the account for B. When A clicks the “create user B” button, he should go to the “user B details page”. How do get the e-mail address of B showing on this page? How do I refer to the e-mail address for B that was just created by A?

  2. How do I succeed to get both A and B to add more details for user B on the “user B details page”? E.g. first name, last name, address, etc.
    So, A has the possibility to enter these details, and B will see this on the page. But if A doesn’t feel like adding details (or doesn’t have the info), B can enter them. A should then see this info whener he visits the “user B details page”.

This might be a bit harder than I thought. Any help is appreciated!

  1. Put something in the URL - i.e. the new User’s unique ID (it can be a query parameter, or a path… whichever makes the most sense in your case). Just make sure to use privacy rules and workflow permissions correctly here - as you don’t want anyone with the URL to be able to edit the User details. (you’ll need to add an ‘invited by’ field on the User datatype for this).

  2. The same answer applies here.

This might be a bit harder than I thought.

I don’t know exactly what you thought… but whatever it was, I’m pretty sure it’s a lot easier than that (as I’ve explained above).

(sure… you could do this with an additional ‘Invite’ datatype or something like that - but to keep it simple I’d just do what I outlined above).

Thanks, I will try this.

I succeeded in sending the ID from source to destination, (This is done by using a workflow on the source page, checking “Send more parameters to the page”, key: userid, = “Result of Step 1’s unique ID”)
On the destination page, the unique Id is shown in the URL.
So far, so good.

However I am struggling fetching the corresponding e-mail address as value on the destination page.
I have a text box where I want to see the e-mail address that corresponds with the userID in the URL. How do I do that?
I tried this: Do a search for: Users, (type=user), with constraint: e-mail=Get userid from page URL’s email.
This gives an error.

Edit also tried:
Get userid from page URL’s email.
This gives me no error but doesn’t return the e-mail adres in the destination page.
Even tried: Get email from page URL’s unique ID. This also gives no error but no result.

Just use: get data from URL ('Key=userid' 'Type=User')'s email

I tried that one:

Blockquote
Edit also tried:
Get userid from page URL’s email.
This gives me no error but doesn’t return the e-mail adres in the destination page.

Then you must be doing something wrong somewhere…

Without seeing your app I can only guess what…

But privacy rules would by my first guess.

Ok let me enlighten you then :slight_smile:
This is the setup. It is super simple, I havent made any privacy rules.
Source page:


Destination page (with the field I want to see the e-mail address of the user which userid is in the URL)

Preview step one

Result:

If you haven’t set any privacy rules, then the default privacy rules will be applied (which means you won’t be able to see the email address).

Unless you’ve deleted the default privacy rules?

@adamhholmes I just discovered privacy rules. There was one preset, that made only the logged in user view their info. This was the one which nagged me: I changed it and now I can see the e-mail adress on the destination page.
Thanks a lot!

As I suspected…

But you really don’t want to leave the User datatype with no privacy rules… especially doing what you’re doing here (or ever, really).

So make sure you set up appropriate privacy rules for your application… and also use conditions on your workflows.

Otherwise anyone who gets hold of the URL will be able to modify the data of that User.