inbuxa/inbuxa-server
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 23 Wiki Activity
355 Commits 9 Branches 27 Tags
3217aae4e8ae19d4627b4b4a01f6a1babbdc4800
Commit Graph
3 Commits
Author SHA1 Message Date
jcoffey-dev 3217aae4e8 LegalHold/get takes coveringAccount 
Only the active holds covering one account, live or deleted and kept,
through any route: for the console's Held badge (LH-14).
 2026-09-27 19:33:07 -07:00
jcoffey-dev 538ae107d7 Legal holds, step 6: what each hold keeps 
inbuxa:LegalHold/get answers accountsCovered, itemsHeld and sizeHeld
when asked: the accounts a hold reaches now (deleted ones it keeps
included) and the archived items it keeps, with their size. Worked out
in one pass over accounts and archive, only for requests that name them.
Held items stay out of the user's quota, as all archived copies do
(LH-9).
 2026-09-27 19:33:07 -07:00
jcoffey-dev 5d2e35b2dc Legal holds, step 1: the hold itself 
inbuxa:LegalHold get/set places a hold on accounts, groups, domains,
tenants or the whole server, with an optional date range. A hold's range
and scope can only widen, a released hold is read-only, and none is ever
deleted. Placing, changing and releasing each need a reason and are
audited (LH-1, LH-3, LH-10, AU-12).

Permissions 669-672 (see, place, widen or release, export held data)
go to server administrators only; the tenant ceiling always strips them,
as it does Impersonate (LH-13). Schema: Compliance > Legal Holds.

What a hold keeps comes next, through the undelete hooks.

Also moves the lock expiry helpers below the lock module's imports.
 2026-09-27 19:33:06 -07:00