nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Survey123 - Password protection

UdoKiefer

The possibility to set a passwort (identification) on an "open for public" survey.

With this function it would be possible to get input from a larger but defined group of participants, without open the query/ questionaire to the public or get a full account for every person. The passwort protection should only allow the access to the survey. For accessing the data, there ist still the need of an account.

A typical usecase would be an survey (arcgis online), which ist sent to the every empolyee of my companie. For exampel to get the information about their daily way to work (Adress, transportation (public, car, bike etc.), travel time, etc.). 95% of the employee don't work with GIS and have no Account. I just need the input for this specific case. Therefore it is not possible/ nessecary to create an accout for everybody. With a passwort protection the risk of an access form outside of the company will be minimized.

There are different reasons why the questions of the survey should not be open for public.
e.g. minimize risk of inputs from outside of the defined group, protect the questions of the survey

The workaround to create a passkey-field which only allows one specific number (field limitations max and min) is not safe, due to the possibility to look up the limitations with help of the developer console of the browser.

Find more posts tagged with

Content Management

Status: Open

Comments

DeonLengton

Hi Udo

You could create a survey link specific for each person in the organisation and then email each person their own link...

So perhaps pass in a unique UUID value and that same UUID field will have a unique index on it so that nobody can submit twice.

Not sure if that will work for you.

UdoKiefer

Hi @DeonLengton

thanks for your answer and idea.

never heard of the possibility to create a personal link in survey, is this a feature of survey-connect?

But I'm not sure if this will work out for me, due to it will limit the way of publishing the survey to email (or other individual ways of communication) and doesn't allow me to publish a permanent link . Additional the connection from an answer direclty to the person can make it trackabel and there is the need to know each indiviaual participant.

In my cases there is a need to publish the link public and protect it with a passwort, which also can be changed time to time.

EricaNova

I plan to store year-specific passwords in a csv in the media folder, grab the current year in a calculation, then check the user's entered password against the password listed in the csv for that year. The only thing that is missing is the 'dots' or 'asterisks' that hide a user's password as they enter it in the console.