Overview

Sprinklr Advocacy allows organizations to synchronize user attributes through Secure File Transfer Protocol (SFTP). Traditionally, SFTP updates were applied only to users already present in the Advocacy platform. This enhancement extends the functionality by allowing administrators to pre-provision users before they sign in to Advocacy.

With this feature enabled, user records can be created automatically through SFTP and stored in a Screener Pending state. Screener responses and custom field values from the SFTP file are saved and applied when the user logs in for the first time. This capability helps organizations reduce onboarding friction and ensure that user profile data is pre-populated.

Supported SFTP File Requirements

The SFTP integration requires a specific file structure.

• File Format: The uploaded file must be XLSX. Other formats such as CSV or XLS are not supported.

• File Name: The file name must always be: CommunityUserSync.xlsx. The file name cannot be changed.

• Mandatory Column: The file must contain the following column: email. This column is used to match users in Advocacy and cannot be renamed.

• Additional Columns: Additional columns represent Screener questions and Custom fields. Example:

How the Feature Works

During each scheduled SFTP job:

1. The system reads the uploaded file CommunityUserSync.xlsx.

2. Each row is processed using the email column as the unique identifier.

The system evaluates each email and performs one of the following actions.

Scenario 1 — User Already Exists in Advocacy

If the user already exists in the platform:

• Screener answers are updated

• Custom fields are updated

• Normal SFTP sync behavior applies

Scenario 2 — User Does Not Exist in Advocacy

If the user does not exist and the feature is enabled:

• A new user record is created

• The user is placed in the state: Screener Pending

The system stores:

• Email

• Screener answers

• Custom field values

At this stage:

• The user cannot log in

• The user cannot share content

• The user is not included in segmentation targeting

The record is stored until the user logs in for the first time.

Admin Configuration

Administrators can configure this behavior in SFTP User Sync Settings.

• Setting Name

  Action for Users Not Yet on Advocacy

• Available Options

When Create User as Screener Pending is selected, SFTP can create placeholder users.

Behavior Before First Login

Before the user logs in:

• SFTP continues updating screener answers

• Custom fields continue syncing

• User status remains Screener Pending

During this phase, SFTP acts as the source of truth for user attributes.

Behavior During First Login

When the user signs in using the same email address:

1. The platform identifies the existing Screener Pending user record

2. Screener questions appear pre-filled

3. The user reviews and submits the screener

After submission:

• The user moves into the standard approval workflow

• Segmentation rules begin applying

• The user gains full Advocacy access

Important Authentication Requirement

This feature should only be enabled when the Advocacy site uses Single Sign-On (SSO). If the platform allows Email/Password signup, enabling this feature may prevent users from registering because the account already exists.

SFTP Data Rules

The following rules apply to the SFTP file.

• Case Sensitivity

  Field values must match exactly. Example: USA is different from usa.

• Multi-Select Values

  Multi-select screener answers must be separated using commas. Example: USA,Canada,Mexico

• Duplicate Rows

If the file contains multiple rows for the same email:

• user@company.com,USA

• user@company.com,Canada

The system applies last-row-wins logic. The final value in the file is used.

Audit Logging

The system records the following events:

• User email

• Subsequent SFTP updates

• First login timestamp

These logs help administrators track how user records were created and updated.

Expected Outcome

With this feature enabled, organizations can:

• Prepare user profiles before onboarding

• Pre-populate screener questions

• Reduce user onboarding effort

• Manage user attributes centrally through SFTP