Make access settings for copied nests the same as for new nests#495

When I make a new nest, the SME organization is automatically added as an owner, which is useful for giving coworkers access and so the company’s projects aren’t solely tied to an individual’s account. When I copy a nest, that setting isn’t applied. From a user perspective, copying the nest is a form of making a new nest, so I always forget that I need to go in and add the organization on copied nests and expect people to have access who don’t. Making copied nest access settings be treated the same as new nest access settings would avoid the confusion.

Hi Erin, this is an intentional design- copying a nest doesn’t bring over any user/organization permissions. We have several reasons, but the largest is avoiding user confusion. If I’m copying nest X into Y with the same name, or subtly different name, AND my collaborators on X have access to Y, how will they be able to tell the X & Y apart? We have visions of bug reports flooding in like “why isn’t my nest updating when my teammates are screening it?”

So, we make our default behavior clumsy for your use case, but completely avoid any confusion for newer users.

I will point out, new in 1.55.0, restoring a backup will result in permissions being copied. The reasoning here is that restoring a backup typically means you are intentionally making an exact copy.

Perhaps we could have a toggle to enable this for vanilla copies as well.

I understand why you wouldn’t copy the same nest permissions from the copied nest, but to me that’s different than using the default new nest behavior. We always want the SME org to have access to all nests created by SME users, so there’s never an issue when an individual leaves or somehow loses access to their account. I can definitely see how similar naming could create confusion either way!