Remove a Required Role From a Service
Remove one staff role requirement from a service so Antylogic no longer expects that role in the planned coverage for the service.
In this article
Use this guide when a location manager needs to remove a role from a service coverage plan, for example when Soho lunch service no longer needs one of its seeded required roles.
The row is removed inside the service editor. The change is only persisted when the operator saves the service.
Before you start
- You are signed in to Harbor Demo Group with Harbor Soho selected.
- Your user can manage service calendar events for the location with `service:manage`.
- The target calendar event is a service, such as Soho lunch service.
- The service has at least one required role row to remove, such as floor, kitchen or bar in the demo data.
Instructions
- 1.
Open the service
Open Soho lunch service in the service calendar editor and confirm that the form is editable.
- 2.
Open Required roles
Select the `Required roles` tab and review the role requirements currently attached to the service.
- 3.
Remove the row
Reveal the row action for the role that is no longer required, then choose `Remove`. The row disappears from the form immediately.
- 4.
Save the service
Choose `Save` to persist the service without the removed role requirement. For a recurring service, choose the required update scope in the recurrence prompt before applying the change.
Validations and limits
- The removed role no longer appears in the `Required roles` list before saving.
- Removing the row without saving does not persist the change.
- Remaining requirements still need a staff role and positive whole-number minimum and recommended counts.
- This action applies only to service events.
- The visible editor workflow persists the removal through the service bundle save, not through the direct delete endpoint.
Expected result
The saved service coverage plan no longer requires the removed staff role.