Instruction

Creating a User Group

To create a read-only account, you first need to create a read-only user group. You can do this as follows:

  1. In the environment, switch to configuration mode (you can activate this mode under the grey bar at the top right with your username in it).
  2. Click on System > User Groups in the top-left menu.
  3. Click Add Group at the bottom of the page.
  4. Enter "Read Only" (or another suitable description for this type of account) as the group name and description.
  5. For the newly created user group, click the block with the gear icon to assign permissions.
  6. In the Unassigned tab, add the permissions that the read-only user should have.
  7. To give this user access only to the roster and reservation pages, assign the following rights.
  8. Note: Some actions are part of the right to view these pages (see the note in this guide for more explanation), so make sure the read-only account can only perform the desired actions.
  9. Once the permissions are selected, click Assign to this group at the bottom of the page.

Permissions for access to the roster and reservation pages

  • entity_booking_read
  • entity_booking_read_all
  • menu_booking
  • menu_booking_roster

Creating a User

Next, you create a new user and assign them to the read-only user group. You can do this as follows:

  1. In the environment, make sure you are still in configuration mode (you can find this under the grey bar at the top right with your username).
  2. Click on System > Users in the top-left menu.
  3. Click Add admin in the top-right corner.
  4. Fill in the desired information for the new user.
  5. Under User parent, select the user who will manage this read-only account.
  6. Under Groups, select the read-only user group you just created.

Some actions are part of the permission to view a page.
For example, comments in the blocks below the roster can be edited with the permission to view the schedule. To prevent this action, a separate roster can be created for the read-only user without any blocks underneath.

Another example is that the reservation page allows a user to mark a reservation as paid. To prevent this action, the permission to view the reservation page should not be granted to the read-only account.

Therefore, carefully check that the read-only user can only perform the intended actions.