chore: add some routes and descriptions

Signed-off-by: IAmTomahawkx <iamtomahawkx@gmail.com>
This commit is contained in:
IAmTomahawkx
2026-06-28 19:38:16 -07:00
parent db6cd1a014
commit 7cebf6e35b
19 changed files with 67 additions and 3 deletions

View File

@@ -0,0 +1,2 @@
// this one is sort of just an idea. hold off on it for now.
// Allow the mod to add an action to a case (same as the audit log actions), in case it got missed by the automated system.

View File

@@ -0,0 +1,4 @@
// add a collaborator (this concept does not replace case ownership,
// but will allow it to show up in both the owner and any collaborators personalized open case list)
// users without sensitive permissions may only be added as collaborators to sensitive cases by administrators/moderation leads
// users who do not have administrator/moderation lead perms may only add a collaborator to a case they own or are also a collaborator on.

View File

@@ -0,0 +1,5 @@
// assign reports or other cases to the specified case by ULID
// this should take an array of {type: report | case, id: ULID}
// recursion of cases should be allowed
// reports are allowed to be assigned to multiple cases
// if a report comes from a queue that is marked as sensitive, this case should also be marked sensitive.

View File

@@ -0,0 +1,3 @@
// Assign a new owner to a case.
// Only administrators/moderation leads should be allowed to assign a case that does not belong to them.
// only administrators/moderation leads may assign someone a sensitive case if the assignee does not have sensitive permissions.

View File

@@ -0,0 +1,3 @@
// see add_collaborator
// The same rules apply, but collaborators may not remove other collaborators unless they are an admin/moderation lead.
// Owners may assign whoever (observing sensitive case rules).

View File

@@ -0,0 +1,2 @@
// mark a case as sensitive or not.
// cases with reports that contain