Please help us help you and fill where relevant:
Your LimeSurvey version: 5.3.23+220705
Own server or LimeSurvey hosting: Own
Survey theme/template: Fruity Theme ( fruity)
==================
Problem: Having any amount of participants (loaded via a .csv file) in a survey I must assign a specific amount to each of the Users (Interviewers) that will be filling the surveys for them, but no Interviewer must see the participants asigned to the other.

I have tried already: 
      - Sharing participants in the Central Participants Database, however, when any given Interviewer enters the Survey all participants are visible and not just those shared.
      - Importing / Exporting participants to and form the Survey to the Central Participants Database.

Notes: Users have hierarchy of permissions, from top to bottom are Administrator, Supervisor and Interviewer. The problem is at the Interviewer level.
 

You talk about a CATI survey.
And as you mention "participants" it is a closed survey.

Now, how do the interviewers start an interview?

​​​​​​Do they click a link?
Do they enter the token manually?

Joffm 

Preferably, Interviewers should start the interview for every participant directly from the Participants Table inside the Survey Panel (avoiding the need to input the generated token).

In said list, only participants assinged to each Interviewer should be visible. 

For example:

User John (Interviewer) should only see 10/50 participants, User Max (Interviewer) should see other 10/50 participants and so on.

User Dave (Supervisor) should see 20/50 participants (those of John and Max).

User Bob (Administrator) should see 50/50 participants.

I don't think it is possible what you are trying to do.

Users/participants are assigned to surveys, not to "interviewers".

Integrated solution
Token table with response persistence to OFF and Allow multiple responses to ON . You give one token Interviewer, he use save with password if needed

Plugin solution
Can use TokenUsersListAndManage and/or responseListAndManage
with responseListAndManage : Interviewer have one token, Supervisor are Group manager (group are set using attribute in plugin setting), Administrator are LimeSurvey admin with response read+update permission

External solution
QueXS is near done for this : quexs.acspri.org.au/
Work with or without complete Phone system.

Managed by Limesurey Partner www.acspri.org.au/limesurvey if you need support.
 

If we do CAPI or CATI interviews, or data entry, we create our own tokens, e.g.:
01001
01002
01003
...
02001
02002
...

And give the respective links or codes to the interviewer or data entry staff.

holch wrote:

And give the respective links or codes to the interviewer or data entry staff.
 

Yes ! Great solution too !
,
And if you want to separate add a rando value at start (randomvalue1)0001, (randomvalue1)0002, (randomvalue1)0003 …
and (randomvalue2)0001, (randomvalue2)0002, (randomvalue2)0003
etc

With interviewers I am generally not worried about any random element in the token for two reasons:

- It makes it more complicated and therefore increases the risk of error
- Interviewers are intrinsically motivated to only fill surveys with THEIR specific code, because if they use the code of another interviewer, they won't get paid for their work.

I already created MS-excel file ( ) with data from user, phone number and link to click (with CTRL+Click).
But we need the attribute data of each user (Survey by categorie, with a lot of hidden/shown dependant from attributes)

But really ;: after testing QueXS for this : it's a great tool for CATI survey !

But really ;: after testing QueXS for this : it's a great tool for CATI survey !

I never really got it to run, but also haven't put too much effort into it either. Should give it another try to see how it works.

Which LS version does it run with now? Still LS3?

It work with LimeSurey API, then not totally related to LimeSurey version.

You have some video here : www.youtube.com/playlist?list=PLi-vaZcHN...TzF0m-w9FWbUfC2Ma0Nu

Ahhh, great. So now it works with the API. Last time i really looked into it a little further it was still fixed to one Limesurvey branch. Makes a lot more sense using the API.