Workato docs Return to Workato
Edit this page
GitHub (opens new window)
  • Introduction
  • Getting started
  • Product Updates (opens new window)
  • Building recipes

  • Running recipes

  • Troubleshooting

  • Data types and formulas

  • Tools
  • Files and attachments

  • Batch processing

  • Teams and collaboration
  • People Task by Workato
  • Recipe lifecycle management
  • On-prem connectivity
  • Key features
  • Workbot for Slack
  • Workbot for MS Teams
  • Workbot for Workplace
  • API Platform
  • Connectors

  • Universal connectors
  • Community connectors
  • Connector SDK
  • Custom OAuth profiles
  • Workato API
  • Security
  • Training & Certification
  • Contact us

# Verified user access at runtime

By default, recipes perform actions based on the identity and permissions of the user who connects the application. It is also common for these to be integration users, created in the application instances for the sole purpose of connecting to Workato. However, when a user commands a bot to perform an action, the user would probably want the bot to carry out actions on the users' behalf, rather than the integration user (which is the default behavior).

Connection credentials A sales manager's credentials used in Salesforce connection

By enabling Verified user access at runtime, Workbot allows individual users to authenticate themselves at runtime. This creates personal connections that can be used to carry out recipe actions on behalf of individual users, rather than the default one used in the recipe. For example, when a sales rep requests a bot to show open opportunities in Salesforce, Workbot authenticates the user at runtime, so that the Salesforce opportunities retrieved belong to the sales rep, not the integration user in Salesforce.

TIP

These personal connections persist, meaning that the user doesn't have to authenticate every time they use the Workbot command

# Prerequisites

# OAuth 2.0

Verified user access at runtime only works with applications that connect using OAuth 2.0 (e.g. Salesforce, ServiceNow, Google Sheets). For applications that support multiple authentication methods (e.g. ServiceNow), OAuth 2.0 must be used.

# Workbot command trigger must be used

To leverage Verified user access at runtime, Workbot commands must be used as the recipe trigger.

# Enabling verified user access at runtime

To enable verified user access at runtime, go to Recipe > Settings page and enable Verified user access at runtime.

recipe-setting Select Verified user access at runtime in the recipe settings

personal-connection-flow-1 Prompt to connect in Workplace. Clicking Login will open a browser tab for you to authorize the connection

personal-connection-flow-2 Authorization

personal-connection-flow-3 Successfully connected

personal-connection-flow-4 Personal connection is now registered

# Viewing personal connections

Users can view their personal connections by sending 'personal connections' in a DM to Workbot.

Personal connections - DM 'personal_connections' Scroll through the carousel to view multiple personal connections

# Disconnecting or deleting personal connections

Users can choose to disconnect or delete their personal connections by sending a 'personal connections' DM to Workbot and clicking Disconnect or Delete.

← Workbot actions Dashboard →

Didn’t find what you are looking for?
Search our resource library View getting started guides, tutorials, training videos, webinars and FAQ Ask our community View questions and answers from other users and Workato experts. File a support ticket File a support ticket for critical issues that require a higher level of support.
Privacy Terms (844) 469-6752 Workato 2021