The console side of inbuxa-server's legal holds (phase 3):
Place a hold: people, groups, domains, tenants or the whole server, an optional UTC date range, a case name, a reference and a reason.
Widen a hold: the dialog refuses anything that would take something out.
Release a hold: type the case name and give a reason.
What each hold shows: what it covers and what it keeps now (accounts, deleted items, size). Released holds stay listed.
Held notice: a person's account page shows the holds covering them, only to those who may see holds.
Typecheck, lint and 412 tests pass. Checked in Chrome against a local server.
The console side of inbuxa-server's legal holds (phase 3):
- **Place a hold:** people, groups, domains, tenants or the whole server, an optional UTC date range, a case name, a reference and a reason.
- **Widen a hold:** the dialog refuses anything that would take something out.
- **Release a hold:** type the case name and give a reason.
- **What each hold shows:** what it covers and what it keeps now (accounts, deleted items, size). Released holds stay listed.
- **Held notice:** a person's account page shows the holds covering them, only to those who may see holds.
Typecheck, lint and 412 tests pass. Checked in Chrome against a local server.
Place a legal hold on people, groups, domains, tenants or the whole
server, optionally for a date range; widen it (the dialog refuses
anything that would take something out); release it by typing the case
name and giving a reason. Each hold shows what it covers and what it
keeps now: accounts, deleted items and their size. Released holds stay
listed. A person's account page says which holds cover it, to those who
may see holds only (audit-hold-lock spec, LH-1 to LH-14).
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.
The console side of inbuxa-server's legal holds (phase 3):
Typecheck, lint and 412 tests pass. Checked in Chrome against a local server.