Thank @Tolu , is there a reason that resources cannot be checked out and/or whether a symbol is not considered as an exception? As we use 2D/3D hybrid symbols extensively in our studio, we find that there are often conflicts between users working from different locations and remotely. I find the check-out feature to be extremely beneficial to the workflow of project sharing by reducing conflicts, but, this seems to be ineffective if you have to discard a certain amount of work done within a resource.
Right now, we avoid this by clicking into the 2D component, select all, check out. Then returning and clicking into the 3D component, select all, and checking out. It's not a streamlined process.
Basically, I'm curious how the hierarchy of checking out is based in concept. If there is something that can be conflicted-- a symbol-- that has contents that can be checked out and edited, why not make the entire object able to be checked out to reduce the opportunity for error and streamline the workflow of the program? Rather than requiring users to have a transparent process alongside the program's workflow.