ftwilliam.com - Managing Multiple Subscriptions

Whether it's the result of company acquisition or simply operational growth, large firms may encounter a situation where they are juggling multiple ftwilliam.com accounts and subscriptions. To improve ease of use and retain independence across these accounts, PensionPro can integrate with all of them simultaneously, relying on Locations to ensure that data is linked to and synced with the right place.

Article Contents

• Overview of FTW Subscription Management
• Enabling Multiple FTW API Keys
• Adding & Managing Multiple FTW API Keys
  • Adding a New FTW API Key
  • Editing an FTW Key's Preferences
  • Deleting an FTW API Key
• Managing Employee SSO
• Changes to Linking FTW Records
• Disabling Multiple FTW API Key Use

Overview of FTW Subscription Management

In the event that a firm is managing multiple ftwilliam.com subscriptions, the API key for each can be added to PensionPro. The firm can then assign Locations and handle Employee Single Sign-On for each FTW account. To get started, refer to the next section, Enabling Multiple API Keys.

The following changes are applied when multiple FTW API keys are in use:

• ftwilliam.com integration preferences are set on a per-account basis.
• PensionPro Locations are mapped to each ftwilliam.com account.
• PensionPro may ask for Location when linking Plans and Contacts.
• Multiple SSO usernames can be added for each Employee so they can easily navigate to each account.

Other items of note when using multiple ftwilliam.com accounts:

• Contacts are linked to a single FTW account based on their portal username. If in use, the Sign My 5500 option on PlanSponsorLink will direct the Contact to the corresponding account.
• Linked Clients (and associated records) will be unlinked from ftwilliam.com if they are assigned to a new Location which uses a different account.

Enabling Multiple FTW API Keys

Requires Security Rights: Maintenance

In order to get started with multiple ftwilliam.com API keys, the associated preference must be enabled:

1. Navigate to Maintenance > Preferences > Integrations > ftwilliam.com. The corresponding tab opens to the General view.
2. Select Edit at the top-right of the General FTW Settings grid. The corresponding window displays.
3. Select Multiple API Keys Enabled.
   • The integration preferences which are normally available in this window will no longer be accessible. Instead, these preferences will be managed per-key; see Adding & Managing Multiple FTW API Keys.
4. Select Save.

Once complete, the API Keys view will be available via the list on the left. Continue to the next section for adding any necessary keys.

Adding & Managing Multiple FTW API Keys

Requires Security Rights: Maintenance

When the Multiple API Keys option is enabled, the API Keys view is added to ftwilliam.com Preferences. The grid on this view displays the API key for each subscription alongside the Locations associated with that account.

Adding a New FTW API Key

To add a new API Key for use with the ftwilliam.com integration:

1. Select Add at the top-right of the FTW API Key Configurations grid. The corresponding window displays.
2. Enter the API Key from the new ftwilliam.com account.
3. Search for and select the Locations associated with this key.
4. Determine if this key is Primary.
5. Set any other ftwilliam.com Integration Preferences as desired.
6. Select Save. The new API key entry is added to the grid.

Editing an FTW Key's Preferences

The ftwilliam.com Integration Preferences that were previously available on the General view—such as enabling Divisions, Navigation Assistance, and other functions—are managed separately for each API key after the Multiple Keys option is enabled.

To view these preferences, hover over an API key entry in the grid and select Edit on the right. The Edit API Key window can be used to update the integration settings for this account. In addition, the associated Locations can be changed, and the key can be set as Primary if needed.

Reassigning Locations to a new key

Reassigning a Location to a different API key results in that Location being connected to a different ftwilliam.com account. Because of this, PensionPro must sever any existing links between the Location and the prior account. In this case, PensionPro will provide a warning indicating the number of records that will be affected.

Although all of the Location's records are unlinked after the change is saved, no items are deleted from the prior ftwilliam.com account.

Deleting an FTW API Key

To delete an API key, hover over its entry in the grid and select Delete on the right. The connection to the ftwilliam.com account will be removed.

Any Locations associated with the deleted key will be reverted to the primary account. This action will unlink all records under that Location; refer to the section Editing an FTW Key's Preferences.

Managing Employee SSO

Requires Security Rights: Add/Edit Employee

PensionPro requires an Employee's ftwilliam.com username to enable single sign-on functions like Navigation Assistance. This is typically entered on the General view of the user's Employee tab. However, when the Multiple API Keys option is enabled, FTW SSO settings are relocated to a new grid. To access these settings:

1. Open the user's Employee record in a new tab.
2. In the Views list on the left, select ftwilliam.com SSO Settings.

The grid on this view contains each of the Employee's ftwilliam.com usernames, and which Locations they apply to.

Use Add at the top-right of the grid to add a new SSO username, or hover over any entry to display the Edit and Delete options on the right-hand side. Deleting a username removes any associated functionality for the relevant Locations.

Changes to Linking FTW Records

There are some minor changes to the process of linking records to ftwilliam.com when multiple API keys are active. Most of these changes involve specifying Locations to identify which FTW account should be linked. Refer to the article ftwilliam.com - Creating and Linking Records from PensionPro for specific instructions.

Changes to linking a single Contact

Linking a single Contact to a portal user in ftwilliam.com still follows the steps outlined in Linking to an Existing ftwilliam.com 5500 Signer. However, when multiple API keys are in use, the Link Contact window also includes a Location field, which allows PensionPro to search for the portal user in the correct FTW account.

Changes to linking Plans and Contacts via Power Tools

When multiple API keys are in use, the ftwilliam.com Linking Power Tool still follows the processes found under Linking Multiple Records to ftwilliam.com Using Power Tools. However, Step 1 of the Power Tool will now ask for a Location; this applies to linking Plans as well as linking Contacts. The Location instructs PensionPro which FTW account to search, and limits the results that are returned in Step 2:

• Unlinked Plans must be assigned to the chosen Location.
• Unlinked Contacts must be a Plan Contact Role on at least one Plan assigned to the chosen Location.

Disabling Multiple FTW API Key Use

In the event that managing multiple ftwilliam.com subscriptions is no longer necessary, the additional functionality can be disabled and returned to its original state. To do so, clear the Multiple API Keys Enabled option in the General view of ftwilliam.com Integration Preferences. Once the change is saved, all Locations will be remapped to the primary API key.

When disabling this feature, PensionPro will indicate the number of records that will be affected by the change. Any records under non-primary Locations—including Clients, Plans, and Contacts—will be unlinked from ftwilliam.com upon completion. This action does not delete items from the unlinked ftwilliam.com accounts. The primary account is not impacted; these records will remain linked.

Additionally, Employee SSO preferences are removed when the feature is disabled. The only SSO username retained by PensionPro is the one connected to the primary FTW key.