Skip to content
New AI Custom Form BuilderDescribe the intake form. It ships branded and end-to-end encrypted.AI Custom Form Builder is here See it build
Engineering

Personal Actions Workflows: Automation for non-admin users

We’re excited to announce that Personal Actions Workflows are now available in the SendSafely web portal.

Brian Holyfield · 2 min read

We’re excited to announce that Personal Actions Workflows are now available in the SendSafely web portal. Personal workflows let individual non-admin users configure automations triggered by their own SendSafely activity, such as received packages or completed transfers.

These user-specific automations are great for developers testing new workflows, or non-admin service accounts running production workflows with a narrow scope, such as a operating on a single Dropzone or Workspace. The key differences between personal and enterprise workflows are outlined below:

Personal Workflows

Enterprise Workflows

Can be created by a non-admin user, such as service accounts or developer test accounts Can only be created by Admins
Are only triggered by events related to the user/owner, cannot run on events by other users Can be triggered by events related to any or all users in the organization
Workflow Identity (ownership) cannot be changed Workflow Identity can be changed to any other Admin account

####

Accessing Personal Workflows

Users authorized to create Personal Workflows will see a “SendSafely Actions” option in their profile dropdown menu.

Menu option

This link leads to the Workflow Listing page, showing only their own Personal Workflows and an option to create new workflows by clicking the “New Personal Workflow” button. A user can have up to 5 personal workflows at a time.

Workflow Listing

The same workflow editor used for Enterprise Workflows is used for editing Personal Workflows. All existing triggers, events, and actions are supported, with two key differences:

  1. Workflow Identity
    Personal workflows are automatically tied to the user’s account — this cannot be changed in the workflow settings.

  2. Default Event Filter
    A non-editable, default filter (“Package Owner ID”) ensures personal workflows only execute for items owned by that user.

Event Filter-1

####

Admin Impersonation Support

Admins can impersonate users, including service accounts from the Registered Users section of the Enterprise console to view, create, and edit Personal Workflows on their behalf.

Impersonation-1

####

Getting Started

Personal Workflows are available to all Enterprise plan customers and are an opt-in feature. We recommend managing the users or no-login service accounts who are authorized to to create Personal Workflows via SendSafely Security Groups. Please contact the SendSafely support team for more information.

Enterprise Security Group

Personal Workflows are available on SendSafely Enterprise plans. For more information, contact success@sendsafely.com.


SendSafely: Integrated File Transfer for the Apps you Love

If you are looking for a secure way to send or receive files with anyone, or simply need a better way to transfer large files, our platform might be right for you.

Request a Demo

Frequently asked questions

Can non-admin users create SendSafely Actions workflows?

Yes, through Personal Workflows. Authorized non-admin users, such as developers or service accounts, can create automations triggered by their own SendSafely activity, like received packages or completed transfers. Personal Workflows are an opt-in feature on Enterprise plans. See SendSafely Actions.

What is the difference between personal and enterprise workflows in SendSafely?

Personal workflows can be created by non-admin users, run only on events related to that user, and have a fixed workflow identity. Enterprise workflows can only be created by Admins, can trigger on events from any or all users in the organization, and their identity can be changed to another Admin account.

How many personal workflows can a SendSafely user have?

A user can have up to 5 personal workflows at a time. Authorized users see a SendSafely Actions option in their profile dropdown, which opens a list of their own workflows and a “New Personal Workflow” button.

How are personal workflows limited to the user's own data?

Each personal workflow is tied to the user’s account as its workflow identity, which can’t be changed. A non-editable default filter, “Package Owner ID,” ensures the workflow only runs for items owned by that user.

Can admins manage personal workflows on behalf of other users?

Yes. Admins can impersonate users, including service accounts, from the Registered Users section of the Enterprise Console to view, create, and edit Personal Workflows for them. SendSafely recommends controlling who can create Personal Workflows through Security Groups.