User Authentications Tab

Enabling user authentication allows individual users in your Smart Flows project to authenticate via the connector. As an Administrator, this is advantageous because it allows you to trace user actions based on who completed the actions instead of seeing all actions as if they were taken by the user who created the connector. By default, individual user authentication is not enabled, so a Smart Flows administrator must enable it.

User Authentication Parameters

Parameter	Description
Enable user authentications for this connector	Checked(ON): Users with authentication-enabled connectors can initiate flow executions. The execution of steps associated with the authentication-enabled connector will be carried out using the individual user's authentication credentials. Unchecked(OFF): All data transactions will be carried out under the identity of the service users authenticated during connector setup. This matches the functionality of Smart Flows before the implementation of individual user authentications.
In non-interactive mode	Non-interactive flow executions skip all user input and are triggered through the flows/executions/start endpoint of the Experlogix Smart Flows API, seeUsing the APIfor more information. Flows that run in a non-interactive mode as a background process cannot ask a user to authenticate in the rare case that the user’s authentication token has expired.
Fallback to connector user	The flow will run via impersonation using the identity of the user who originally created the connector.
Fallback to connector user and generate a warning on the flow execution	The flow will run via impersonation using the identity of the user who originally created the connector and generate a warning in the Flow Execution Panel.
Pause flows and wait for the user to authenticate	The flow waits with the status "Authentication needed,” until the user completes authentication via the authentication-enabled connector.
End flow with error	The flow ends with an error message.

Enable User Authentication

Administrators must manually enable user authentication for their connectors using the process below. Please ensure your connector supports user authentication before proceeding.

Connectors Supporting User Authentication

The following connectors support individual user authentication. However, Administrators must enable the feature in their application. Please refer to Managing Users for more details. For users who have the User authentication enabled and trigger a flow containing any of the specific flow steps described below, they will need to authenticate the first time they execute such a flow. If the refresh token expires, users will need to authenticate again.

When running a flow with user authentication, the system creates a document in Connectors with the owner not being the connector user but the user who did the user authentication.

Salesforce
- Retrieve Data (Salesforce)
- Store In Salesforce
- Email (Salesforce)
SharePoint
- Store in Microsoft SharePoint
- Supported Connections
  - SharePoint Online (OAuth)
  - SharePoint Server (OAuth)

User Authentications are disabled for SharePoint Server (Username/Password).

DocuSign
- Send to DocuSign

In the Control Panel, select Connectors.

In the Connectors Listview, select an authentication-enabled connector.

In the left-hand navigation, select the User authentications tab.

Next to Enable user authentications for this connector, select the checkbox.

Under in non-interactive mode, when no user authentication is available during the flow execution, select an option.

Select to display parameter options

Parameter	Description
Enable user authentications for this connector	Checked(ON): any authentication-enabled connector users can start flow execution. The user’s individual authentication will be used to execute the steps related to the authentication enabled connector. Unchecked(OFF): the connector behaves like in previous Smart Flows versions, meaning that all data transactions will be carried out under the identity of the service users authenticated during connector setup.
In non-interactive mode	Non-interactive flow executions skip all user input and are triggered through the flows/executions/start endpoint of the Experlogix Smart Flows API. Flows that run in a non-interactive mode as a background process cannot ask a user to authenticate in the rare case that the user’s authentication token has expired.
Fallback to connector user	The flow will run via impersonation using the identity of the user who originally created the connector.
Fallback to connector user and generate a warning on the flow execution	The flow will run via impersonation using the identity of the user who originally created the connector and generates a warning in the Flow Execution Panel.
Pause flows and wait for the user to authenticate	The flow waits with the status "Authentication needed,” until the user completes authentication via the authentication-enabled connector.
End flow with error	The flow ends with an error message.

In the bottom right, select the Save changes button.

Your connector is now enabled to support user authentications.