Supporting collections of files via your Internal tools

nima supports submitting collections of related files as a single moderation case this is particularly useful when multiple pieces of content are part of a single entity (e g , a photo album, a multi image post, or a document with attachments) overview content collections allow you to submit multiple related files as a single moderation case maintain context between related content items apply moderation decisions to the collection as a whole view and evaluate all files within the collection context in the moderation console common use cases photo albums or galleries multi image social media posts documents with attachments chat conversations with multiple media files carousel posts with multiple slides api structure when submitting a collection, your payload includes main content the parent content node containing collection level details child contents an array of individual files within the collection example request { "priority" "severe", "channel" "automated detection", "reason for request" "violent reason for request", "customerspecific" {}, "content" { "content id" "mainimg {{$randompassword}}", "title" "preview content", "body" "lorem ipsum is simply dummy text of the printing and typesetting industry lorem ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book ", "url" "https //www shutterstock com/shutterstock/photos/1051839905/display 1500/stock photo horror scary photo of a killer in white shirt with blood splatter and posing with black gun on dark 1051839905 jpg", "token" "", "type" { "id" "img", "name" "image" }, "status" "published", "customerspecific" { "contenttype" "portals review", "summary" "the video features a man's torso with a focus on his chest and pubic area, along with the title \\"fetish 2025,\\" which is suggestive and could be interpreted as sexual in nature ", "probs" "{\\"phishing\\" 0 28}", "detectedby" "internal tool" } }, "child contents" \[ { "content id" "childimg {{$randompassword}}", "title" "preview content", "body" "lorem ipsum is simply dummy text of the printing and typesetting industry lorem ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book ", "url" "https //www shutterstock com/shutterstock/photos/1051839905/display 1500/stock photo horror scary photo of a killer in white shirt with blood splatter and posing with black gun on dark 1051839905 jpg", "token" "", "type" { "id" "img", "name" "image" }, "status" "published", "customerspecific" { "summary" "the video features a man's torso with a focus on his chest and pubic area, along with the title \\"fetish 2025,\\" which is suggestive and could be interpreted as sexual in nature ", "probs" "{\\"csam\\" 0 8}", "detectedby" "internal tool" } } ], "reporter" { "id" "123", "name" "reporter james", "lang" "en", "phonenumber" "070 123456", "emailaddress" "reporter\@tremau net", "customerspecific" {} }, "reportee" { "id" "321", "name" "reportee john", "lang" "en", "phonenumber" "070 564123", "emailaddress" "reportee\@tremau net", "customerspecific" {} }, "label" \[ "policy" ], "location" { "city" "stockholm", "postalcode" "111 57", "region" "stockholm", "countrycode" "al", "ipaddress" "192 168 0 1", "customerspecific" {} } } understanding the structure main content node the content node contains collection level details collection metadata title, description, and overall summary of the collection collection url link to the parent collection or album custom attributes collection specific attributes in the customerspecific node example "content" { "content id" "mainimg 12345", "title" "preview content", "body" "collection description", "url" "https //example com/collection/12345", "type" { "id" "img" }, "customerspecific" { "contenttype" "portals review", "summary" "ai generated summary of the collection" } } child contents array the child contents array contains individual files within the collection each child content includes individual file details each file's specific metadata detection results ai detection provider signals for each file file specific attributes custom attributes unique to each file example "child contents" \[ { "content id" "childimg 67890", "title" "individual image", "url" "https //example com/image1 jpg", "type" { "id" "img" }, "customerspecific" { "probs" "{\\"csam\\" 0 8}", "detectedby" "internal tool" } } ] detection and rule processing each individual file in the collection is evaluated against your configured rules individual evaluation each file in child contents is processed independently signal detection ai detection providers analyze each file and return signals rule matching signals are matched against your configured rules in priority order policy application matching rules trigger the appropriate policies note rules are processed in priority order you can configure rule priority by dragging and dropping in the rules configuration interface viewing collections in the moderation console files are displayed in the moderation console within the context of their collection, allowing moderators to view all files in the collection together navigate between individual files make informed decisions based on the full collection context apply actions to individual files or the entire collection