Overview

The Adobe Sign for Facebook Workplace integration provides a simple interface designed to enable users to send agreements for signature and receive notifications as their agreements progress through the signature cycle.

The scope of this document is limited to the Adobe Sign functionality within the Workplace environment, and is not intended to be a comprehensive guide for Facebook Workplaces as a whole.


Prerequisites

Before installing the integration, contact your success manager and ensure your account is in the Facebook Workplace channel, or that the right settings have been applied to your account to ensure proper functionality.

The channel settings dictate how users are provisioned and notified, so this should be completed before users have access to the integration.

 

Supported Platforms:

  • Workplace web app on latest browser versions (Chrome 67+, Firefox 60+, Safari 11+)
  • Workplace chat app for desktop version 1.0.34 onwards (Win 7 and above, Mac 10.13 and above)
  • Workplace chat app for mobile (iOS v11.2.6+ and Android v7+)
    • Safari on iPad is not currently supported

Installing the integration

1. Log in to Facebook as a Workplace Admin

2. Click on the Integrations link in the left rail

3. Click Browse all integrations

1_click_integrations

4. Search for the Adobe Sign integration

5. Click the Adobe Sign tile

2_search_for_adobesign

 

The Adobe Sign integration summary opens.

6. Click the Add to Workplace button

3_the_aobe_sign_integrationsummary

 

The Install Adobe Sign overly displays.

7. Select the scope for the integration in terms of which Workplace groups should have access to the Adobe Sign solution:

  • All Groups - All groups in the Workplace have access to the Adobe Sign features
  • Select Groups - You can select the specific groups that should have access to the Adobe Sign features
    • Groups are added based on the group name in Facebook
    • Once you start typing, the interface suggests possible group matches that can be selected
    • Each group is displayed as a "tag" which can be individually deleted if need be

8. Click Install

4_click_install

 

The OAuth panel opens, asking for the login authentication to the Adobe Sign service

  • Make sure to use the login credentials for an Adobe Sign Account level administrator
  • Workplace users that invoke the Adobe Sign integration will have a new user created in the same Adobe Sign account as the admin that authenticates
    • New users created in this fashion have randomized passwords. If at any time the user tries to log in to Adobe Sign directly, they will first need to reset their password using the I forgot my password link
  • If you have multiple Adobe Sign accounts, and a user generates an error that their account can't be created, contact your Success Manager so they can evaluate if the user already exists in a different Adobe Sign account

9. After entering the email and password of the admin user, click Sign In

The OAuth scope details are presented.

  • The scopes involved in the Workplace integration are Account level, so individual users do not need to discretely authenticate. The Admin is authenticating for the entire Workplace tenant
  • The authentication token will persist through sixty days of inactivity. If the Abode Sign service is not used by any member of the Workplace for over sixty days, the token will be expired, and the Admin must re-authenticate to re-establish the trust relationship between the two applications
  • No data is lost if the OAuth token expires

10. Click the Allow Access button

5_allow_access

When the integrations is completed, the message Integration was installed successfully appears at the top of the panel

11. Close the panel

12. Click the Save button to complete the installation process

7_click_save

Change the Scope of the integration

1. Log in as a Workplaces Admin

2. Click on the Integrations link

3. Click on the Adobe Sign tile in the Installed Applications section

  • This opens the Settings for Adobe Sign overlay

4. Change the scope as needed:

  • It is permissible to switch between All groups and Specific Groups
  • Groups can be added or removed as needed
  • Existing agreements in Adobe Sign are still viable and in process. Decoupling the integration from various groups does not impact agreements "in-flight"

5. Click Save once the changes are complete

Uninstalling the integration

1. Log in as a Workplaces Admin

2. Click on the Integrations link

3. Click on the Adobe Sign tile in the Installed Applications section

  • This opens the Settings for Adobe Sign overlay

4. Click the Uninstall button in the lower left of the tile

  • Uninstalling removes access from all groups in all cases
  • Existing agreements in Adobe Sign are still viable and in process. Decoupling the integrations does not impact agreements "in-flight"

5. A challenge pops up to verify you want to uninstall the integration.  Click Uninstall

The application is uninstalled from Workplace.

8_click_uninstall

Things to know...

The Workplace Admin that establishes the OAuth link between Facebook and Adobe Sign defines the Adobe Sign account where new users are auto-provisioned.

When a user in Workplace attempts to access the Adobe Sign Bot, Adobe Sign checks to see if the user is valid:

  • If no user exists in the system, a new user is provisioned in the Adobe Sign account
  • If the account has no available licenses, an error is thrown
  • If the user exists in a different account, an error is thrown
  • If the user is in an Inactive state, an error is thrown

 

Once the OAuth connection is established, the token will tolerate being idle for 60 days. If no user uses the integration for sixty consecutive days, the token will expire.

 

The interface fields have limitations:

  • Maximum number of recipients is 25
  • Agreement names can be up to 255 characters
  • The Message field can contain up to 1000 characters

Known issues

  • IE 11 and Edge browsers are not supported (all operating systems)
  • Safari on the iPad is not supported

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy