Why would I get the enclosed warning when I have given myself permission to read and write?

Transparency, Consent, & Control (TCC) is what is responsible for controlling app access to other data including the Desktop, Documents, and Downloads folders.

tccutil is a command line utility to reset some or all of the control permissions.

tccutil reset All 

will reset all control and all apps would need to ask permission again. That might allow you to allow Bantivity to ask again. Maybe not.

lopezcalling wrote:

I have a file here. The app sends a message I can't do anything to the file because I don't have permission.

Then when I try Plan B of giving everyone permission, the OS warns me this action is undoable. Why is that? Couldn't I just go back change the permission back to the way they were before?

I have given myself permission to read and write. I have been looking through sort of similar questions and there some suggestions to "go to the drive". Don't quite understand what that means, but it sounds like I have to bypass this irritating warning and go somewhere deeper within the Mac OS. How and why?

"Plan B"...(?)

Old issue, new issue, what changed?

You really do not give any information to go on...

What app?

what are you trying to accomplish?

Is it added to the Full DIsk Access (if necessary)

Controlling app access to files in macOS

The current stable release of Ventura including bug fixes, security updates is macOS Ventura 13.5.2

Keep your Mac up to date - Apple Support

Keep your Mac up to date - Apple Support

Then when I try Plan B of giving everyone permission, the OS warns me this action is undoable. Why is that? Couldn't I just go back change the permission back to the way they were before?

Yes, with a lot of work. It doesn’t state you can’t change them later to get them back to what they were, it says you cannot undo what you did with the undo command. It’s not “undoable” which is not equivalent to “cannot be undone.” Since you have selected the enclosing folder (Documents?) to propagate permissions, it will propagate the “group everyone:deny delete” ACL to all files and folders. The children of Documents should not have that ACL.

Changing permissions most likely won’t fix the problem as I don’t think it is a POSIX or ACL issue. It looks like TCC isn’t processing that it has been approved. I’m not sure what to reset, maybe All.

Ok, I don't understand what you're telling me

Which part?