Yes ! Confirm the issue !

And seeing "Survey participant summary" when the table does not exist is completely counterproductive and incomprehensible.

No way to allow register without create one particpant too …

The participant table is being created when you activate survey in closed mode.
You can also import participants from csv file before you activate survey.
If you want to import participants from csv file that has additional attributes, you can, but these attributes will be ignored -> this use case is something I can discuss with my team to see how we want to handle this.

@DenisChenu - No way to allow registering without creating one participant - also valid issue.

2 current issue (except the comprehensible part : "There is no participant table" somewhere)

• No way to manage Attributes (but even this one : it's great to allow edition without participant table)
• No way to have register survey without existing participant.

Idea

Capture d’écran du 2025-07-29 10-38-17.png (95,591 bytes)   

Capture d’écran du 2025-07-29 10-38-17.png (95,591 bytes)   

@tibor.pacalat

In general, one would want to configure additional participant attributes before activating the survey, in order to test settings such as branching logic based on those attributes or displaying them on the questionnaire screen etc. Testing should be done while the survey is not accessible from outside. Therefore, the current flow—where the participant table is only created upon activating the survey—is not ideal from a survey design perspective.

In general, one would want to configure additional participant attributes before activating the survey,

There are some other issue related to particpant_attribute

1. Allow updating attribute settings without token table
2. ATTRIBUTE_X always show as invalid if no token table , but settings is set

I have to report it…