Sync Core Data in Glide

Overview

Sync Core Data ensures financial institutions always have accurate, real-time member information, reducing costly errors and manual reconciliation. It automatically reflects updates from your core system for select fields, whether from back-office actions or automated processes. Glide helps staff work efficiently with up-to-date member information, reducing errors, saving time, and ensuring every decision is based on accurate data.

• Note: this is only available for FIs using Fiserv XP2 currently. If interested in support for Symitar and Keystone in the future, please reach out to your DPM.

By keeping data in sync across systems, Core Data Sync helps your FI:

• Reduce manual reconciliation and data inconsistencies

• Improve staff confidence when reviewing or servicing memberships

• Maintain a clear audit trail of when and how member data changes

Syncs are field level, transparent, and protected by built in safeguards to prevent unnecessary load on your core.

Sync Core Data at a Glance

• Core System → Glide (automatic and manual syncs) → Staff and Member Dashboards with safeguards and audit trail

When Core Data Sync Runs

Core data can be synced in three ways, depending on how staff or members interact with Glide.

1) Automatic Sync on Dashboard Load

When a staff member opens a membership dashboard, Glide automatically checks whether a sync is needed.

• A sync runs if at least 1 minute has passed since the last sync

• Repeated page reloads within that window will not trigger additional core calls

• This ensures data stays fresh without impacting core performance

2) Manual Sync Core Data Button

Staff can manually trigger a sync at any time using the Sync Core Data option in the dashboard kebab menu.

• Triggers an immediate sync with the core

• Can be used even if a recent sync occurred

• Disabled while a sync is in progress

• Re enabled after completion, then subject to the 1 minute cooldown

Note: The Sync Core Data button only appears for memberships with an existing member number.

3) Member Login via Member Flow

When a known member logs in through the member flow, Glide automatically syncs core data.

• Sync runs even if a recent sync already occurred

• Ensures member initiated activity always reflects the latest core data

What Data Is Synced

Membership

• Membership status

If your core does not support dedicated membership statuses, such as XP2, Glide uses the primary individual’s status as the membership status.

Individual Member Information

The following individual level fields are synced from the core:

• First name

• Last name

• Phone number

• Email address

• Physical address

• Income

• Employer

• Occupation

Roles

Role changes made in the core are reflected in Glide after a sync.

• New roles added in the core appear in Glide

• Updates to the primary role are reflected

• Role removals are supported when enabled

All role changes are reflected in both the Glide UI and the activity trail.

Note: Role removal requires a production configuration flag to be enabled for your FI.

Shares

The following share level data is synced from the core:

• Share status

• Active balances

• Newly opened shares

Adding shares, closing shares, and removing shares are supported.

Activity Trail and Visibility

Every sync attempt, whether automatic or manual, is currently recorded in the activity trail, even if no data changes occur.
Note: This behavior will eventually be phased out so that activity trail entries appear only when changes are made.

Each log includes:

• Timestamp of the sync

• Fields that were updated, if applicable

This provides staff and auditors with clear visibility into when data was last refreshed and what changed.

Button Behavior and Safeguards

Sync Core Data Button

• Only visible for memberships with a member number

• Disabled while a sync is running

• Subject to cooldown rules after completion

Performance Protection

Core Data Sync includes built in protections to prevent excessive core calls:

• Dashboard reloads do not trigger repeated syncs within one minute

• Only one sync can run at a time per membership

• Manual syncs cannot be spammed

These safeguards ensure reliable performance for both Glide and your core system.

Error Handling and Notifications

If a sync fails due to a core timeout or error:

• The failure is logged

• The activity trail records the sync attempt

• Staff see a toast notification explaining the error

This ensures failures are visible and actionable without silently leaving data out of date.

Supported and Upcoming Sync Coverage

Currently Supported

Membership

• Membership status

Individual

• First name and last name

• Phone number, email, and address

• Income, employer, and occupation

• Roles, including new roles and primary updates

Shares

• Status

• Active balances

• Newly opened shares

In Progress (by Glide)

• Role removals

• Overdraft protection services

• Courtesy pay

• Debit cards

Availability will vary by core and configuration depending on your FI. Currently, we only support Fiserv XP2 clients. Please reach out to your DPM if you are interested in other fields or cores for sync support.

Why Core Data Sync Matters

Core Data Sync ensures Glide remains a reliable, real time extension of your core system. By combining automatic refreshes, staff controlled syncs, and a complete audit trail, your FI can operate with confidence knowing the data your teams rely on is accurate, current, and transparent.