How to Lock Your Automations and Manage the Private/Public Permissions with Teams

In today's digital landscape, the ability to secure and manage permissions for your automations is crucial. Whether you're safeguarding sensitive processes or ensuring exclusive access, knowing how to lock your automations is a valuable skill.

The concept of privating or locking your automations is gaining popularity for various reasons. It provides a layer of control, allowing you to run processes exclusively from your computer without the prying eyes of team members.

Within your workspace and automation settings, the unlock or lock icon plays a pivotal role. By simply clicking on this icon and locking your automation, you ensure that only you have visibility and control over its execution.

When an automation is locked, it becomes invisible to other team members within the workspace. This means that when it runs, it does so exclusively from your desktop, mitigating the risk of unauthorized access.

Locking your automations not only adds a layer of security but also ensures that they run smoothly without any interruptions. This is particularly crucial for platforms like LinkedIn, where location changes can trigger account flags and affect automation performance.

Once your automation has served its purpose or needs to be shared with team members, simply unlocking it allows for seamless collaboration and visibility within the workspace.

Mastering the art of locking your automations and managing permissions with teams is a powerful tool in your digital arsenal. By understanding the intricacies of private-public settings, you can enhance security, streamline processes, and collaborate effectively within your team.

VIDEO TRANSCRIPT

Okay. So privating or locking your automations is a very popular feature for anything that maybe you're trying not to use a proxy for, um, or you're trying to verify that this only runs from your computer. You don't want any team members to see it, whatever the reason may be. Um, we're going to go over that feature and how that works today.

So inside of any workspace, and automation. We can hover over the automation and see this unlock or lock icon. If you've already used it, what this means is anybody else that you've invited to your workspace will not be able to see this automation if we lock it. So if I click this and then I lock this automation, which you may or may not see that pop up, if you've already dismissed it, uh, dismissed it, we will see this icon is now green.

Showing that it's locked and it's only displaying for us. Now, any of these other team members I have, when they log in and they go to the build workspace, they will not be able to see this automation. The other thing is, is when this automation is triggered to run from my desktop, it will only be allowed to run from my desktop.

If this automation is not locked and it's triggered to run, it can run from any team members computer. Um, even though it'll try to favor yours. When that's triggered, locking this makes it so that's not the case, which is really useful. Again, like I said, if you're trying not to use a proxy, because something like LinkedIn, if you're logging in from a new location, they might flag the account, which will make, which will affect your automation because it won't be able to perform the same steps that you recorded.

Then after we lock it, we can click the lock again, and that'll unlock our automation so that it shows for us and any other team members. Uh, in that workspace.