Litify Inbox Mass Deployment Scenarios

Setting up Litify Inbox for multiple end users is a standard procedure performed by you local IT Admin and/or Litify System Admin. 

The following options are available for mass deployment of Litify Inbox.

Please remember that Litify Inbox is not a standalone application. It is either installed in MS Outlook environments (such as Desktop, Web, or Mobile implementations) as an add-in, or in the Chrome browser as an extension.

Litify Inbox Deployment Scenarios for MS Exchange/Office 365 Mail Accounts

Deployment Scenario

Required Admin Actions

Required User Actions

Admin deploys the add-in and activates users’ sync

(This scenario requires minimum user action. Recommended for Firms with 20+ users.)

  1. Set up an Impersonating Service Account in MS Exchange.

  2. Mass deploy the add-in to all users in MS Exchange or Office 365 Admin Center.

  3. Mass activate users’ sync with the Impersonating Service Account.
  • Litify Inbox sync will be activated when users first log into the add-in by connecting the add-in to Litify.
  • Open the add-in and connect to Litify.

Admin deploys add-in only

(Admin only deploys the add-in, users connect their add-ins both to Litify and Office 365/MS Exchange mailboxes.)

  1. Mass deploy the add-in to all users in MS Exchange or Office 365 account.

  2. In this case Litify Inbox sync is activated by end users.
  1. Open the add-in and connect to Litify.

  2. Connect the add-in to MS Exchange / Office 365 account.

Admin activates users’ sync only

(In this scenario users install the add-in themselves and Admin helps to mass activate their sync.)

  1. Set up Impersonation Service Account in MS Exchange / Office 365.

  2. Set up mailbox access in the Litify Inbox Admin Panel.
  1. Install the add-in (refer to How to Install Litify Inbox add-in from a manifest URL).

  2. Open the add-in and connect to Litify

Users install the add-in and activate the sync.

(In this scenario no actions needed from Admin. Applicable to Firms with <20 users.)

  • No actions are required.
  1. Install the add-in.

  2. Open the add-in and connect to Litify.

  3. Connect the add-in to MS Exchange / Office 365 account.

 

There are additional actions that Admins will need to perform for each deployment scenario:

  • Ensure that Litify Inbox IP addresses are not blocked by either Litify or the Firm’s Firewall.
  • The Invisible Suite managed package is installed into the Litify organization.

For more information please refer to the Litify Inbox Admin Guide.

Litify Inbox Deployment Scenarios for Chrome Extension

Deployment Scenario

Required Admin Actions

Required User Actions

Admin installs the extension and activates users’ sync

(This scenario requires minimum user action. Recommended for Firms with 20+ users.)

  1. Mass install the Chrome extension to end users.

  2. Configure a service Gmail account and mass sign-in to Litify on behalf of the users.
  • Log in to the corporate Gmail / Google Workspace (G Suite) account in Chrome Browser.

Admin installs extension only
(only via Windows Active Directory)

(Admin only deploys the add-in, users connect their Gmail extensions both to Litify and Gmail.)

  • Mass install Chrome Extension.
  1. Log in to the corporate Gmail / Google Workspace (G Suite) account in Chrome Browser.

  2. Sign in to the Chrome Extension.

Admin activates users’ sync only

(In this scenario users install the extension themselves and Admin helps to mass activate their sync.)

  • Configure a Service Gmail account and mass sign in to Litify on behalf of the users.
  1. Install the Chrome extension.

  2. Log in to the corporate Gmail/Google Workspace (G Suite) account in Chrome Browser.

 

There are additional actions that Admins will need to perform for each deployment scenario:

  • Ensure that Litify Inbox IP addresses are not blocked by either Litify or the Firm’s Firewall.
  • The Invisible Suite managed package is installed into the Litify organization.

For more information please refer to the Litify Inbox Admin Guide.

Related Articles

Was this article helpful?
0 out of 0 found this helpful