Admins look for locking in the Directory first, so it's there too, as well as on Compliance › Locked accounts and the account page's banner:
Each person's row menu in Directory › Accounts ends with Lock this account…, or Unlock… when the account is locked. They use the same dialogs, with the reason required. Groups get neither.
A locked account shows a Locked badge beside its address in the list.
Both depend on the same permissions as the Compliance page (sysAccountLockGet, and …Create/…Destroy for the actions).
The list code in DynamicList changed only in three small places. Everything else is in features/lock/useDirectoryLocks.tsx.
Checked in Chrome against a local server: lock from the menu, badge appears, unlock from the menu, badge goes. Typecheck, lint and 408 tests pass.
Admins look for locking in the Directory first, so it's there too, as well as on Compliance › Locked accounts and the account page's banner:
- Each person's row menu in Directory › Accounts ends with **Lock this account…**, or **Unlock…** when the account is locked. They use the same dialogs, with the reason required. Groups get neither.
- A locked account shows a **Locked** badge beside its address in the list.
- Both depend on the same permissions as the Compliance page (`sysAccountLockGet`, and `…Create`/`…Destroy` for the actions).
The list code in `DynamicList` changed only in three small places. Everything else is in `features/lock/useDirectoryLocks.tsx`.
Checked in Chrome against a local server: lock from the menu, badge appears, unlock from the menu, badge goes. Typecheck, lint and 408 tests pass.
Each person's row menu offers Lock this account… or Unlock…, with the
same dialogs as Compliance › Locked accounts, and a locked account shows
a Locked badge beside its address. The account page's banner stays, so
locking is in all three places admins look (audit-hold-lock spec, AL-1).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Admins look for locking in the Directory first, so it's there too, as well as on Compliance › Locked accounts and the account page's banner:
sysAccountLockGet, and…Create/…Destroyfor the actions).The list code in
DynamicListchanged only in three small places. Everything else is infeatures/lock/useDirectoryLocks.tsx.Checked in Chrome against a local server: lock from the menu, badge appears, unlock from the menu, badge goes. Typecheck, lint and 408 tests pass.