Global permissions apply to the whole survey installation. If you want to set permissions only for a specific survey you can use the Survey permissions settings.
To set global permissions for a user just click the lock symbol.
The system use CRUD (Create, read, update and delete) like the Survey permission setttings. Checking the first input checks all the CRUD permission for that row. To fine-tune permission we strongly recommend to extend the view using the arrow button on top of the checkbox column.
You can now add or remove the following permissions.
These permissions only apply for a single survey. If you want to set permissions for the whole system you can use the global permissions.
Please note: An existing user account is required to set permissions for a single survey. If the account doesn't exist you have to create it first and then change the survey permissions. You don't have to apply any global rights to the user, it is just necessary that the user account itself exists.
To change the survey permissions you have to select Survey permissions from the Survey properties menu.
In the next step you select the user you want to change the survey rights and click Add user.
After you click Set survey permissions the survey permissions matrix for the survey and user will be shown.
In this matrix you can set the rights for the different features and parts. You simply click a checkbox if you want to add or remove this right. If you click a checkbox in the first column all rights for this line will be selected/removed.
In the other columns you can choose whether a user can do a single actions from this feature/part.
After you finished editing the survey permissions click Save or Save and close in the upper right corner.
In this part of the article we'll provide a few ideas which use cases may exist and how and which rights would be a good choice.
To be moved somewhere else once better defined:
There are several classes of possible people who access a LimeSurvey installation. But only one set of people is actually termed a user in the code and documentation. So lets understand what these classes of people are so we can better understand the terminology of the program.
|Primary user account||Those people who create login user accounts to allow others to create, edit, activate and/or view surveys and their results. Often can be given access to edit the templates, labelsets and other key features independent of any particular survey stored.|
|Survey Administrator||A person with a login account that is given some management access to a particular survey. Each survey can have its own set of users with specific rights to manipulate the survey. These rights can be as broad as to activate a survey and possibly edit its question base. They can be as minimum as simply able to review the results to date.|
|Participant||Those people who simply respond or participate in taking a survey. They may or may not have token access. They do not need a login account to the administrative interface and thus are not termed users.|