xMatix
Sign in Request demo
xMatix
PRODUCTS
SalesField SalesCRMRewardsClaimsInventoryProcurementWarehouse 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
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 subscription marking a user as watching a record, created by the Follow server action and retired by Unfollow, both of which soft-delete rather than remove rows. Like Collaborator it is polymorphic - Record plus Related Entity Name, no foreign key - and the actions are registered on Case only in first-party metadata. Notify On Change and Muted express an intention to be notified, and following an already-followed record un-mutes it instead of duplicating the row, but no first-party business rule or notification service reads either flag, so following a record currently produces no messages on its own. Record merge re-points followers onto the surviving record.

Fields

FieldLabelTypeRequiredWhat it does
MutedMutedBooleanYesFollowing a record that is already followed clears this back to false instead of creating a second row, which is how a mute is undone. Nothing reads the flag, so muting currently suppresses nothing.
NotifyOnChangeNotify On ChangeBooleanYesSet true on every row the follow action creates and never changed afterwards. No first-party business rule or notification service reads it, so it records an intention to be notified rather than driving any message.
RecordIdRecordLookup → CaseYesThe record being watched, stored as a bare identifier with no foreign key behind it. It is only meaningful together with the related entity name, since identifiers from different entities share this one column.
UserIdUserLookup → UserAccountYes

Actions

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