This article is machine translated from english
Why is the registration process important?
A well-designed registration process is key to creating a smooth experience for new users. Keeping the form short, simple, and clear helps boost user satisfaction and reduces drop-offs.
Before you start building your registration form, ask yourself:
What demographic data do I need to collect from all users?
What information is only relevant for certain participants or projects?
How to set up the registration process?
Create a smooth onboarding experience by customizing your platform’s registration steps.
The registration flow consists of four steps:
User fills in the sign-up form
User verifies their email address, then logs in successfully
User answers demographic questions (optional or required)
User selects follow preferences (optional, if enabled)
Registration Flow
Step 1: Sign-up form
Add a custom message via Settings > Registration > Email and password step
Step 2: Email verification
By default users will be prompted to verify their email address when registering on the platform.
ℹ️ If you want to disable email verification on your platform, contact support via the chat bubble at the bottom right of your screen
Step 3: Demographic questions
After email verification, users can be shown demographic questions. These can be set as optional or required, depending on your needs.
Step 4: Follow preferences (optional)
If enabled, users can select topics and areas they want to receive updates about, you can add these via:
Settings > Tags (topics)
Settings > Areas (locations)
When users select preferences they will receive email notifications when a project is published/updated that has been tagged with one of their preferences.
ℹ️ Users can update their follow preferences or unsubscribe anytime via Account Settings > Notifications or Activity > Following.
How to customize your registration questions?
Add, remove, or adjust the questions asked during user registration.
Default fields:
Gender
Year of birth: used for age group insights on dashboards
Place of residence: linked to geographic areas (Areas tab in the Platform Settings), useful for access control and representation analysis
You can:
Disable any default field (toggle off).
Make any field required (click Edit, enable “required”).
Add your own custom fields:
You can add these types of questions:
Multiple choice (single or multiple selection)
Yes/No (checkbox)
Short/long text
Numeric
Date
Examples:
Which topics are you interested in? (multi-select)
How many people live in your household? (numeric)
⚠️ For the representativeness dashboard only single select questions can be used.
What is demographic data?
Why it matters:
Access Control: Control participation based on user traits
Group Segmentation: Sort users into smart or standard groups
Data Consistency: Only registration fields appear across all dashboards and reports
Community Representation: Representativeness and demographic-based analytics
Important notes:
Only default registration fields can be used in AI analysis
Only single-choice questions show up in demographic graphs
"Year of birth" cannot currently be used for grouping survey answers by age
Where is this data used?
Reports: Add demographic widgets
Participation projects: View demographic participation per project.
AI analysis and Auto-insights: Segment insights based on default demographic fields.
Grouping survey answers:
What are project level demographic questions?
How it works:
By default, new projects inherit platform-level registration questions
Project managers can:
Choose which questions apply to their project
Mark them required or optional
To modify this, go to the phase settings and check the Phase access and user data section.
⚠️ Project managers can select registration questions that are not enabled on the platform level, however, the questions need to be created by a platform admin in the registration section of the platform settings. After this, a project manager can ask this as a specific question for their project.
To learn more about access rights specifically, read our article: Understanding Access Rights