From 541ea0141685f52a8f8a6bd84db4e914392a7b68 Mon Sep 17 00:00:00 2001 From: Rafael Farias Date: Thu, 26 Feb 2026 17:58:51 -0300 Subject: [PATCH] fix: grant manage permission to Manager on collection creation When a Manager without `access_all` creates a new collection, the CollectionUser record was saved with `manage=false`. This caused the ManagerHeaders guard to reject subsequent edit requests with "The current user isn't a manager for this collection". Set manage=true so the creating Manager can manage their own collection. Fixes #6871 --- src/api/core/organizations.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/api/core/organizations.rs b/src/api/core/organizations.rs index 4a5066ab..4b0ad683 100644 --- a/src/api/core/organizations.rs +++ b/src/api/core/organizations.rs @@ -521,7 +521,7 @@ async fn post_organization_collections( } if headers.membership.atype == MembershipType::Manager && !headers.membership.access_all { - CollectionUser::save(&headers.membership.user_uuid, &collection.uuid, false, false, false, &conn).await?; + CollectionUser::save(&headers.membership.user_uuid, &collection.uuid, false, false, true, &conn).await?; } Ok(Json(collection.to_json_details(&headers.membership.user_uuid, None, &conn).await))