A User Structure defines the fields collected when users register or manage their account in PalDock. Separate structures exist for Affiliate partners and Advertisers.
- Used in registration forms and user management.
- Can include global fields (Name, Email) as well as any custom fields.
- Admins can customize fields to fit their tenant’s needs.
It is not attached to anything
Unlike a form structure, a user structure is not connected to an offer or an integration. The registration form and the account page use it directly, so a change takes effect the moment you save it, for people who registered long ago as well as for new ones.
Some fields belong to the person, not to you
Global fields such as first name, last name and email are tied to the user’s account, which spans every workspace they have access to.
- When the user changes one of these, it changes in every workspace at once.
- An admin cannot change them on the user’s behalf.
That is deliberate. The same person should not be called two different things in two workspaces. If you need a value that behaves differently, make a local field instead, and accept that it will not be linked to the account. See Local, Global and Custom fields.
What to collect
A registration form is where partners decide whether to bother. Every field you add is a reason to stop.
- Ask for what you need to pay them and to know who they are.
- Anything you only need later, such as billing details or a tax number, can be collected when it becomes relevant rather than at sign-up.
- Validation, Modify and AutoComplete work here exactly as they do in a lead form, so a company number can be checked against a registry during registration.
👉 For details about field types, validation, Modify, and translations, see the other pages in this section.
