Effective rights to Rename not available on all documents in folder

replied on April 22, 2019

Check the user's effective rights instead of the group's effective rights. The usual cause of something like this is a Deny setting from another group membership overriding the Allow.

0 0

View 6 previous replies

replied on April 22, 2019 • Show version history

Jason, good thought on checking the user rights. I did check the effective rights of the admin user (me) and it shows the rename right as allowed.

I did find that deleting the document from the folder and 'checking it out' again from it's original folder shows the rename rights.

User rights look exactly the same on both the one NOT allowing rename and the one that DOES allow rename.

04-22-19 rename in CIT 3.PNG (35.83 KB)

| Download

0 0

replied on April 22, 2019 • Show version history

Okay so in that case, this might not be a rights issue. If someone else has the document checked out, then you cannot make changes due to source control restrictions. It sounds like something is locking the document(s).

Find a document that won't let you rename it, then go into the admin console to the Activity section. Check under Checked Out Documents and/or Entry Locks to see if the document is in there and what account has the lock.

0 0

replied on April 22, 2019

Jason, I checked the check outs and locks and there is no lock on these documents.

0 0

replied on April 22, 2019

When you check to verify the permissions, are you checking the folder structure or the document itself? It is entirely possible to have full access to an entire folder structure and still have something denied on a specific document/folder.

0 0

replied on April 22, 2019

Is the volume locked? Volume rights originally only applied to content modification, but we have expanded the operations that a locked volume prevents.

1 0

replied on April 23, 2019

Jason, we are following the same triage path. I checked both document and folder rights and both are the same.

Brian, volumes do not appear to be locked.

0 0

replied on April 23, 2019

Sorry, I meant that your screenshot shows the right enabled but I was hoping you had a screenshot that shows the actual conflict/error.

0 0

replied on April 23, 2019

Hi Michelle,

In a similar vein as the above comments. If the user in question opens up the document, does it show to them as read-only? It would have a header bar in the document viewer in that scenario.

When you say "Some of these documents are not showing with the Rename effective right", do you mean the user is unable to perform the action and it's disabled or they get an error, or do you mean that if you look at the effective access rights for that user on some specific documents, it shows unchecked? If the later, you could select 'view detailed inheritance information' to get more information as to why the system thinks it's restricted.

1 0

replied on April 24, 2019

Justin, document is a PDF and shows in PDF viewer with no indication of read only.

Yes, my statement "Some of these documents are not showing with the Rename effective right", does refer to the fact that when you right click on the document the Rename action is disabled.

User does not get an error. What does happen, is that when the user wants to save a new version of the PDF, instead of asking if they want to create a new version, it automatically wants to save a new copy of the document with an (02) name. That's what led me to find the difference between those documents allowing the save as new version (those with rename action enabled) and those that would not allow save as new version (those with rename action disabled.)

If I look at the effective access rights for that user, on PDFs in that folder, the rename right is checked for that user on all documents while the rename action is disabled on some. See view detailed inheritance information attached.

04-24-19 rename in CIT 4.png (64.1 KB)

| Download

0 0

Question

Question

Effective rights to Rename not available on all documents in folder

Replies

Sign in to reply to this post.