Revoking a staff member's access
When a staff member leaves or changes role, their access has to stop cleanly — but their history must not disappear. Offboarding in Ustawi removes what a person can do going forward while preserving the full record of what they did, so accountability outlives the account.
The offboarding checklist
- 1Deactivate the accountRemove the staff member's ability to sign in, so no further action can be taken under their identity.
- 2Remove roles and branch scopeWithdraw the capabilities and branch scope they held, so nothing lingers if the account is ever reactivated in a different capacity.
- 3Revoke trusted devicesFor a field agent, remove device trust so a previously approved phone can no longer authenticate.
- 4Reassign live workMove ongoing loans or caseloads to another officer so servicing and collections continue uninterrupted.
History is preserved, not deleted
Revoking access is not the same as erasing the person from the record. Every action they took stays attributed to them in the audit log — approvals, disbursements, edits — exactly as it happened. This is deliberate: an audit or investigation months later must still be able to see who did what, even for staff who have since left.
The moment you deactivate the account, forward access stops. The backward record remains, which is precisely what a departing staff member's activity should look like in a controlled system.