Confusing experience deleting files in remote project

[emesare]

When deleting a file in a project with no permissions the behavior is odd:

1. It deletes the file on disk
2. It removes the file from the project?
3. It says that I have no permission to delete the file

Screen.Recording.2026-02-10.at.1.06.43.PM.mov

We should be checking if the user has permissions to delete the file before making any destructive changes to the project as it exists locally.

Additionally, all the logs should be scoped to some actual name rather than the default log, makes it difficult to ascertain what system is having problems (is it project support in general, or collaboration).

[fuzyll]

I'm not sure I agree about checking permissions first. Enterprise is built around the idea that you make local changes, then synchronize them with the server. Git doesn't prevent you from deleting something in a local repository just because you don't have push access to that branch, either.

That said, I can see a few sharp edges here that we might need to address in some fashion:

1. What if you want to remove the downloaded file, but not the file from the project? You can do this by opening the file location on disk and deleting that way, but that might not be obvious to a new user.
2. What if you did this accidentally, while offline, and you want to undo it before going back online? I'm pretty sure the file deletion will be pending and I don't know that there is a way to see and 'cancel' that.
3. In this case, it looks like you intended to do the deletion, but couldn't because of the error. Does this mean we're now out-of-sync forever? Or are we just carrying around and "rebasing" a project file deletion that we can't actually apply?

Not entirely sure, at this moment, what the full set of changes are we should make here. But, I agree the user experience could be better. I also agree we should specialize the logging. Thanks for the issue.