xMatix
Sign in Request demo
xMatix
PRODUCTS
SalesField Sales & SFACRMRewardsClaimsInventoryProcurementWarehouse ManagementField ServiceServiceSupportTelephony & MessagingFinance & AccountingPayrollExpense ManagementCommercePortalsAnalytics & ReportingData StudioMobile AppSee all products →
PLATFORM
Platform overviewApp BuilderAutomationIntegrationsSecurity & GovernanceChange ManagementDevelopers
SENSE AI
Sense AI overviewSense AssistSense ControlSense VisionAI StudioTrust & governanceIn Claude & ChatGPTUse cases
SOLUTIONS
Auto DMSConsumer Goods DMSSales Force Automation (SFA) FMCG & DistributionManufacturing & Dealer NetworksAutomotive & DealershipsPharma & HealthcareConsumer DurablesAgri-InputsBuilding MaterialsService NetworksWarehousing & 3PLFinancial AccountingERP SoftwareIndia GST ComplianceUAE VAT & e-InvoicingSaudi ZATCA & VATAll solutions →
RESOURCES
Knowledge CenterDeveloper & CLIBlogGuidesWhat is xMatix?Company facts
COMPANY
AboutCareersPartnersEventsContactAuthorsLegal
Sign in Request demo
Home/Docs/Entity Reference/Follower — entity reference
REFERENCE · Last reviewed

Follower — entity reference

A follower is a colleague who watches a record so that they are emailed when it changes. Followers are added and removed from the Followers chip (the eye icon) in a record's header, which appears on record pages by default and offers only active resources linked to a user account. When someone else updates or deletes the record, xMatix emails each follower who has Notify On Change on and Muted off, together with every collaborator: the email lists each changed field with its old and new value and links to the record. The person who made the change, inactive users and users without an email address are never emailed, creating a record sends nothing, saves that touch only bookkeeping fields send nothing, and at most 100 people are emailed about one change. Removing a follower deletes the row. Following a record grants no access to it. A merge moves the duplicate's followers to the surviving record. The Follow and Unfollow actions do the same for the data API and need the user's id.

Fields

FieldLabelTypeRequiredWhat it does
MutedMutedBooleanYesWhen on, this follower receives no change emails while staying on the list. The record header has no mute switch, so it can only be set through the data API. Running the Follow action for someone already following turns it back off.
NotifyOnChangeNotify On ChangeBooleanYesWhether this follower is emailed when the record is updated or deleted. Set on for every follower added from the record header or by the Follow action. A follower with it off is still listed in the header but receives no change emails.
RecordIdRecordLookup → CaseYesThe record being followed. The column is shared by every entity that can be followed, so it is read together with the record's entity name and has no lookup of its own; the reference shows Case because that is where the follow actions are registered.
UserIdUserLookup → UserAccountYesThe user who follows the record and receives its change emails. When a follower is added from the record header it is taken from the chosen resource's linked user account, so the user must be active and have an email address to receive anything.

Actions

ActionLabelTypeWhat it does
CloneCloneServerAction (Clone)Create a copy of this record
EditInLineEditEditInlineEdit in page.
  • Case — looks up via CaseId