Skip to main content

Central Customer: Org-Wide Event History

Ability to view critical organizational level events to provide insight into what updates were made by which store and when

R
Written by Richard Thorne

Overview

The customer profile in Customer Management has always included an Event History table showing what your store has done to that customer's record. With central customer enabled, that table gains a scope toggle: This store and Org-wide.

The Org-wide view shows the actions taken on the customer's organization profile at any location — who did it, at which store, and when. It appears only when central customer is enabled and the customer's store record is linked to an organization profile. Otherwise the Event History table behaves exactly as it does today.

Importantly, not every action is recorded here. The org-wide log is deliberately limited to the events other stores have a legitimate reason to know about, so it stays readable and useful rather than becoming a firehose of routine activity.

What Gets Logged (Org Events View)

  • Organization profile created, the first time the customer is established centrally.

  • Profile updated, when a check-in or profile edit at any store actually changes the customer's identity, contact, or address information.

  • Profile synced, when someone deliberately reconciles a store profile with the organization profile — including which fields changed and whether each value came from the store or the organization profile.

  • Documents uploaded or deleted, including the document type.

  • Notes added or deleted.

  • Warnings set or removed.

  • Customer banned or unbanned.

  • A store unlinked from the organization profile.

How to Read It

Select the scope you want. The table opens on This store by default; selecting Org-wide loads the organization-wide view.

Each entry shows the date, time, type, user, and a description of what happened, with the originating store named in the description so it's clear where the action took place.

Entries are listed newest first, and the view shows the most recent activity. If a customer has more history than can be displayed at once, the table states how many entries are being shown out of the total.

Nothing here can be edited. The org-wide history is a read-only audit record — it exists so any store can understand how a customer's organization profile came to look the way it does.

Did this answer your question?