Please help us help you and fill where relevant:
Your LimeSurvey version: 5.0.7+210628
LimeSurvey Cloud
Survey theme/template: fruity
==================
Hey there,

We want to use a participant list where every participant has an individual username (string) and password (string) column in the csv file.
It's a survey with 15 different languages with different filters where the invitation information is sent via letter and not via E-Mail. It's not very handy that the participants have to enter the long access url via hand. That's why we want to use short usernames + passwords. The invitation letter first guides the participants to a separate landing page (with a short domain like xyz.org where they can choose their language. The language will redirect them to their LimeSurvey language version where they should enter their username and password.

But is it even possible to use participant lists without the need to access the survey via the access tokens that are generated by Limesurvey?

We want to have a validation - that the participant can only give answers when the combination of the username and password matches one of the participants.
I'm not sure if this is even possible or if there is a workaround for this. Do you have a hint for that?

Is there a way we can deactivate the first add "access token" screen somehow?

Thank you.

Hi,
so you seem to create your "landing page" by yourself.

So, I should do it like this:
Generate the participant table and export it.

The landing page should be able to

• let the respondent enter his username and password (token)
• let the respondent select his preferred language (if you do not want to set the default language of each user in the participants table)
• check if username and password are valid
• create the link to LimeSurvey with the token
• redirect to limesurvey with this link.

Now the user doesn't see any screen where he has to enter some credentials.

Joffm

Limesurvey has no user management for surveys, only the token system. However, given your description, I can see certain work arounds.

First of all: You do not need the token generated by Limesurvey, you can create your own participant table with your own "tokens" and upload them via CSV.

You also do not need to use the survey link that includes the token already. If the survey is using tokens and is closed, but the link does not contain the token, the user is asked to type in the token to have access to the survey.

Now, you want to add another level to that, you want basically two tokens (one being the user name, the other being a password).

You could think about using the token as a password that the respondent will type in when accessing the survey and then as a custom attribute you could include a password for this "user" (token). You then check if the password that the respondent types in matches the custom attribute and if not you do not let them continue (e.g. screen them out via a zero quota).

Joffm's suggestion is probably cleaner, but requires more "outside" programming.

Hey there

Thank you both for your time and hints.
The mentioned workarounds seem be practical.
Will test them out.

Thank you!