LimeSurvey version: 6.15.4
LimeSurvey Cloud
Survey theme/template: fruity
==================
When creating a new survey in LimeSurvey and setting a participant list with an access code for each participant, entering an access code is not required. Instead, without access codes, it is possible to proceed to questions after activating the survey in closed-access mode. Does anyone know of a similar problem and how to address this issue? 
Regarding another survey created (likely) in a previous version of LimeSurvey Cloud, entering the access codes is required to proceed to the questions. I might miss some relevant information to be conveyed. Thank you for your experiences.

When creating a new survey in LimeSurvey and setting a participant list with an access code for each participant, entering an access code is not required. Instead, without access codes, it is possible to proceed to questions after activating the survey in closed-access mode.

This should definitely not happen. Is the survey active?

So you are saying, in the same installation (LS6.15.4) you have two surveys that behave totally different?

The one created in LS 6.15.4 is allowing to access a survey in closed mode without a token, while the survey that was created in a previous version requires a token in closed mode (as it should)?

Can you provide a little example LSS that shows the issue, with all the settings you did?

Dear holch,

Thank you for your immediate response.
I will send the .lss file. Does it also work?

The one created in LS 6.15.4 is allowing to access a survey in closed mode without a token, while the survey that was created in a previous version requires a token in closed mode (as it should)?
-> Yes. I might have lost any relevant settings, but I cannot find for now.

I appreciate your time.

Best,
Kenji

I just had a chance to test your LSS and then created my own survey and tested.

Seems like when activating, there is no screen to set a survey as closed anymore. Might be a bug. Please report the bug.

Thank you for checking the LSS file.
I will report this issue.