Runtime user connections

FEATURE AVAILABILITY

The runtime user connections feature is included in specific pricing plans for direct customers and is available by default for Embedded partners and their end customers. Refer to your pricing plan and contract to learn more.

Recipes perform actions based on the identity and permissions of the user who connects the application by default. Using Runtime user connections, users can use their own credentials when running a recipe, even if they didn't create the original application connection.

How do runtime user connections work?

The Runtime user connections feature allows users to authenticate themselves when a recipe runs, allowing the recipe to execute actions using their own credentials.

For example: We have a recipe that uses Workbot to create opportunities in Salesforce. Here's what the execution would look like with and without runtime user connections:

With runtime user connections	Without runtime user connections
User A invokes the recipe using the Workbot command Workbot prompts User A to use their own Salesforce credentials Workbot authenticates to Salesforce with User A's credentials Workbot creates opportunities credited to User A	User A invokes the recipe using the Workbot command Workbot authenticates to Salesforce with the default user in the recipe (User B) Workbot creates opportunities credited to User B

Connections persist after you create them. This means that users don't have to provide their credentials every time they run a recipe. Additionally, these connections can't be used in other recipes like normal connections.

What are parent connections?

Connections created at runtime link to a parent connection.

For example, when you run a recipe with a Salesforce connection and authenticate to Salesforce, it creates Connection B. This new connection links to the recipe's default Salesforce connection, Connection A, as its parent.

graph LR X(("Skill recipe <br/> with verified user <br/> access and a Salesforce <br/> connection is triggered")) --> Y{{"Runtime user <br/> access prompts the <br/> user to authenticate <br/> with existing credentials <br/> or create credentials"}} A[/"Recipe default connection <br/> or <strong> Parent connection </strong>"/] A -.User connection <br/> automatically links to <br/> the Parent connection.- Z("A child connection <br/> is created for the user") Y --> Z classDef default fill:#67eadd,stroke:#b3e0e1,stroke-width:2px,color:#000; classDef WorkatoBlue fill:#5159f6,stroke:#5159f6,stroke-width:2px,color:#fff; class Y WorkatoBlue

PARENT CONNECTIONS LIMITATION

Parent connections are not supported for recipe functions toggled with runtime user connections. You must create separate runtime user connections for these recipes. If you try to use a parent connection, it fails and may cause unexpected behavior. We recommend creating a specific runtime user connection.

Who can use runtime user connections?

While this feature is available to all plans and account types (including OEM), users need the following privileges to enable or disable the setting for recipes:

• Edit recipes
• View Runtime user connections
• Edit Runtime user connections

Where can I use runtime user connections?

The Runtime user connections feature is available in:

• Recipe functions
• Workbot recipes with a New command trigger
• Skill recipes

---

Enable and disable runtime user connections

Runtime user connections can be used in:

• Recipe functions
• Workbot command recipes
• Skill recipes

---

Manage runtime user connections

Manage runtime user connections in:

• Apps
• Workbot in Slack
• Workbot in Microsoft Teams
• Skill recipes

Manage all runtime user connections in-app

WHO CAN VIEW THIS PAGE?

Users must have the View Verified user access at runtime privilege to access this page.

Manage runtime user connections by going to Tools > Runtime user connections. This page lists all connections created at runtime.

Delete a connection

WHO CAN DELETE CONNECTIONS?

You must have the Delete connections privilege to delete connections.

Review the following information before you delete a connection:

• Deleting a parent connection causes recipes using the connection to stop. Child connections created at runtime aren't deleted.

• Deleting a child connection requires the user to re-authenticate themselves the next time the recipe runs. Successful re-authentication must occur before actions can be performed on their behalf.

Click the Delete link next to the connection to delete it.

Manage runtime user connections with Workbot in Slack

You can perform the following actions in Slack Workbot:

• View your own runtime user connections
• Disconnect your runtime user connections

View your runtime user connections

Workbot enables you to view your own runtime user connections in a DM (direct message) or in channels where Workbot is a member.

In a DM

Complete the following steps to view your own runtime user connections:

1

Open a DM with Workbot.

2

Enter connections.

3

Send help and then click the Personal accounts button.

View runtime user connections in a Workbot DM

In a channel

Complete the following steps view your runtime connections in a channel:

1

Go to a channel where Workbot is a member.

2

Enter @Workbot connections or @Workbot help to view your runtime user connections.

Disconnect your runtime user connections

You can disconnect your runtime user connections by going to your list of connections and clicking Disconnect:

Disconnect a runtime user connection

Manage runtime user connections with Workbot in Microsoft Teams

Workbot in Microsoft Teams enables you to:

• View personal connections
• Disconnect personal connections

View personal connections

View your personal connections by sending personal_connections in a DM to Workbot. Workbot lists your connections and their connection status.

Viewing your personal connections

Disconnect personal connections

Disconnect or delete your personal connections by selecting the connection in the picklist and clicking Disconnect or Delete.