Password to protect node trees, etc

Most professional colourist often prefer not to share their project file or node trees or custom luts... it is also intellectual property, that we may not want to share with others for multiple reasons. However, there are some situations where we may want to share it but prevent a client from just copying those nodes, etc on to another project and so on.
It would be nice to see DR have some kind of password protection for node trees, luts, dctls, etc.

It would be nice to see DR have some kind of password protection for node trees, luts, dctls, etc.

PeterC would remember, but I think that idea was announced as a feature sometime around Resolve 15, but it just never made it into the released version. I think it was a way of locking a compound node so that nobody could open it up and figure out what it was and how it worked. I have no clue what the reason why it didn't come out was.

I had only one case when a client asked me for grading sources.
I think a third person cannot use my nodes, because nuances and understanding is a key. Of course, we have some know-how, but it requires a tuning for every project.

But, anyway, the idea is good, so +1.

This should be available everywhere. For example, I recently did a collaborative cloud project and the sound engineer unlocked one of my tracks in edit and moved some layout markers (blank adjustment clips) 57 frames to the right which caused our project to fail as it went over the time limit by 2 seconds and 9 frames. There should be a secure lock option where, I don't know, attempting to unlock it sends a message to the account which locked it to request permission to unlock. Or asks for a password or a pin or something.

This should be available everywhere. For example, I recently did a collaborative cloud project and the sound engineer unlocked one of my tracks in edit and moved some layout markers (blank adjustment clips) 57 frames to the right which caused our project to fail as it went over the time limit by 2 seconds and 9 frames. There should be a secure lock option where, I don't know, attempting to unlock it sends a message to the account which locked it to request permission to unlock. Or asks for a password or a pin or something.

That's a little complicated. Look at it this way: if you open up an Avid edit and make a stupid change, is there any failsafe to stop them? If you open up a Premiere edit and make a stupid change, is there any failsafe to stop them? If you open up an FCPX edit and make a stupid change, is there any failsafe to stop them? If you open up a Baselight session and make a stupid change, is there any failsafe to stop them?

The answer is no. As a guy who pays close attention to workflow, I tell our freelance people and co-workers, " don't F up. Don't make any changes unless you know exactly what you're doing. Ask first. When in doubt, make a copy of the timeline and make the change to the copy." So basically: this isn't a computer software problem -- this is a people problem. Get competent people and tell them not to change anything.

Note that it IS possible to lock tracks on the Edit page. We do that frequently when changes come in, and all the changes go on an upper track. That can stop people from inadvertently sliding the wrong tracks and causing chaos. As to color, you can lock one node at a time, but it's currently not possible to lock all nodes in the tree simultaneously.