Setting correct permissions for derived objects

Learn how to set permission for derived objects.

If you and other members of your team want to share derived objects (DOs), make sure that your views are configured to create shareable DOs and that the DOs are created with a mode that grants both read and write access to team members. To accomplish this, use either of the following alternatives:

Other users cannot overwrite and destroy a DO that you are still using, even if you use a CCASE_BLD_UMASK value that grants write access to group members. If your DO has been winked in to another view, and the corresponding makefile target is rebuilt in that view, clearmake first breaks the link to your DO, and then creates a file in that view for the build script to overwrite.

Permissions on DOs affect the extent to which they are shareable:

For information about fixing the permissions of DO versions, see the protect reference page.