How to delete a TPV staff credential
Remove a staff member's TPV credential from the selected location so it no longer appears in TPV settings or works as a TPV access credential.
In this article
Use this when a PIN, card, or selector credential should stop granting TPV access for the selected location. The staff member stays in staff management; only the TPV credential is removed.
Deletion is location-scoped and permanent. Antylogic checks TPV management permission and confirms that the selected credential belongs to the current location before deleting it.
Before you start
- Harbor Demo Group and Harbor Soho, or another valid organisation and location, are selected in the app context.
- At least one staff TPV credential is visible on the Staff credentials tab.
- The operator has `tpv:manage` permission for the location.
- For documentation captures or training runs, use a disposable credential rather than a seeded demo credential.
Instructions
- 1.
Open Staff credentials
Go to TPV settings and open the Staff credentials tab. Use the table to identify the credential by visible label, staff member, credential type and status.
- 2.
Choose Delete
Open the row actions for the target credential and choose Delete. This action is shown only to operators with TPV management permission.
- 3.
Review the confirmation
The app opens the generic Delete resource confirmation modal. Review the credential name, choose Cancel to keep it, or continue only if the credential should be permanently removed.
- 4.
Confirm deletion
Choose Delete in the modal. The app sends a no-payload delete request for the selected credential id, refreshes the staff credentials list, and shows the success feedback when the change is applied.
Validations and limits
- The Delete row action requires `tpv:manage`. View-only users do not get a delete entry point from the table.
- The selected credential must belong to the current location. Credentials from another location are treated as not found.
- The backend route is `DELETE /api/app/{orgId}/{locationId}/staff-tpv-credentials/{id}` and accepts no request body.
- A successful delete returns `204 No Content`, refreshes the staff credentials list, and removes the deleted credential detail from cache.
- Deletion is physical, not a soft delete. The implementation does not block active credentials, last credentials for a staff member, or credentials with previous use.
- Deleting the TPV credential does not delete the staff member.
- Known permission mismatch: the UI surface may be reachable with `tpv:view`, while the credentials list endpoint requires `tpv:manage`, `staff:manage`, or `staff:view`.
Expected result
The credential is removed from `staff_tpv_credentials`, no longer appears in the Staff credentials table, and can no longer be resolved for TPV access. The staff member remains available.