Workbot personal connections

By default, recipes perform actions based on the identity & permissions of the credentials used to connect the application.

A sales manager's credentials used in Salesforce connection

Using personal connections, Workbot allows individual users to authenticate themselves before carrying out actions on their behalf in other apps, e.g. asking sales reps to log in to Salesforce before dispatching Workbot to create the opportunity in Salesforce on their behalf.

This ensures that actions carried out by the recipe in the connected apps are done using the authenticated users' identity and permissions.

TIP

Personal connections persist, meaning that the user doesn't have to provide credentials every time they use the Workbot command

To enable personal connections, go to Recipe > Settings page and enable Verify user access at runtime. Currently, Workbot only supports personal connections to apps with OAuth2 connections, e.g. Salesforce, ServiceNow, Box.

When this feature is enabled, Workbot recipes will request individual users to authenticate (i.e. login) to the app, from Teams, before carrying out the app action(s).

Prompt to connect in Teams. Clicking Login will open a browser tab for you to authorize the connection

Authorization

Successfully connected

Personal connection is now registered for your Workbot for Teams account

Viewing personal connections

You can view your personal connections by sending 'personal_connections' in a DM to Workbot.

Viewing your personal connections

Disconnecting or deleting your personal connections

You can choose to disconnect or delete your personal connections by selecting the connection in the picklist and clicking Disconnect or Delete.