Running the self-hosted community edition. I enabled all the new metadata stuff but when I tried to add an additional URI to a credential that was shared with a group I got the following:
{ “code”: 400, “body”: { “metadata_key_type”: { “isMetadataKeyTypeSharedOnSharedItem”: “A resource of type personal cannot be shared with other users or a group.” } } }
When I remove the share and only myself as owner, I am able to modify the records.
It’s confusing because I don’t have an option to create a “shared folder” or anything except folders in “My Workspace”
Hello @synertekcs, welcome to the forum in order for us to reproduce the issues in the same context, we would need more information. Since some of them might be considered sensitive, can you please email us at support@passbolt.com:
The full output of the status report
sudo su -s /bin/bash -c “/usr/share/php/passbolt/bin/status-report” www-data
If you are on a RPM distribution please replace www-data with nginx
If you are on Docker, please run docker compose -f docker-compose-ce.yaml exec -ti passbolt su -s /bin/bash -c “source /etc/environment && /usr/share/php/passbolt/bin/status-report” www-data instead.
The server logs that should be located in /var/log/passbolt/error.log or in the docker logs if you are using Docker.
Screenshots of all the settings regarding Metadata
Having the exact same issue. Self-hosted docker CE.
Web:
{
"code": 400,
"body": {
"metadata_key_type": {
"isMetadataKeyTypeSharedOnSharedItem": "A resource of type personal cannot be shared with other users or a group."
}
}
}
Docker:
2025-08-29 09:49:54 error: [App\Error\Exception\ValidationException] Could not validate resource data. in /usr/share/php/passbolt/src/Service/Resources/ResourcesUpdateService.php on line 270
Help me fix this and we will use Passbolt in our organization.
After that, have you tried modifying the resource itself (any field) and saving it?
My setup is a bit different though - I’m running a manual install (current Passbolt version from git) on Archlinux with postgresql as RDBMS. Only v2 resources are allowed.
Got the same issue. The way i encountered the problem:
Created folder “Devices” in “My workspace”
Created Group “L3-1”
Added new password “Pass1” in “Devices”
Shared “Devices” with Group “L3-1”
Changed something in “Pass1“
Pressed Save
Got an error:
{
"code": 400,
"body": {
"metadata_key_type": {
"isMetadataKeyTypeSharedOnSharedItem": "A resource of type personal cannot be shared with other users or groups."
}
}
}
By “changed something” I mean I’ve tested one by one: name, URI, username, password, icon and color.
When I create a new password “Pass2” in “Devices” after sharing this folder and try to modify the “Pass2” I’m getting the same error. So there is no difference in order of creating/sharing
The way to avoid is mentioned by OP and works in my environment (removing share and editing)
Hi folks.
My colleagues have identified and reproduced the issue.
This issue occurs when a resource is shared with a group where the user is the only member. In certain cases, the resource is considered personal, which is true from a cryptographic perspective but incorrect from the permission system’s point of view. We need to update the resource update service so that it encrypts with the user’s personal key only if the resource is shared exclusively with that user from a permissions standpoint.
The task is PB-46065 and it’s been added to the next sprint.
cheers
Gareth
in order for us to reproduce the issues in the same context, we would need more information. Since some of them might be considered sensitive, can you please email us at 
