Metadata Schema-Error: - Unable to edit properties Insufficient permissions

[dineshd48807150]

Hi Team,

when i am applying metadata schema to some assets folder and when i am editing the asset properties and while saving i am unable to save it as it is throwing error i.e., --  "Unable to edit properties Insufficient permissions"

i am admin user and having all permissions but still getting this kind of error.

Can anyone provide some suggestions on this..,

Thanks in Advance.

[Umesh_Sondhi]

Hi dineshd48807150 ,

Please go and check the rules of your respective field in the metadata schema is enabled or disabled. For reference, please check

Create, add, and manage metadata schemas

If this could help you .

Thanks

[hamidk92094312 · Accepted solution]

If you are connected to the instance as an admin then you should have access to the /conf directory. You may want to double check that you have Create, Modify, and Delete permissions on the /conf folder. This can be checked via user/group admin console:
http://host:port/useradmin

[10024]

Thanks!

[zxcvzxcvzxcvxx]

where is the /conf folder located? I tried using the http://host:port/useramin but get an error. 

[10024]

Hi @dineshd48807150,

Were you able to resolve this issue? I am encountering this now. Upon checking, I already have the admin access.

Thanks in advance.

[sumi271]

Hi,

I was trying to edit multiple assets, but when i select Append Mode for multiple asset its giving error pop up saying "Unable to edit properties."

any suggestions, what's the root cause of the issue?

Thanks

[Abie]

Hi @sumi271 

Did you manage the find the solution for this problem? I am facing exactly the same problem.

"Unable to edit properties."

Thanks,

Abhey

[PremV]

I am also facing the issue of being unable to edit the asset metadata, Can someone provide a solution for this?

Thank you!

[WesleyGrant]

For me the issue was the metadata I was trying to save was using an unregistered namespace (like [ns:title = "my title"] where 'ns' was not registered as a namespace in the system. You can confirm this by going to CRXDE and trying to save the metadata field directly to the asset's metadata node.  If this is your problem you will see a long error that starts with something like: "Could not save changes. Received 403 (Forbidden) for saving changes in workspace crx.default. OakName0001: Invalid namespace prefix([, ....."

Fix it with the following:

https://experienceleague.adobe.com/en/docs/experience-cloud-kcs/kbarticles/ka-20396

[testUserMe]

Enabling Disable Edit for the field