--- title: "Sync a Supabase alarm asset register with Salesforce" description: "Build a multisite alarm and access-control asset register with clear identity, service history and authorized access." canonical: https://www.stacksync.com/blog/multi-site-alarm-and-access-control-service-connect-a-supabase-asset-register-with-salesforce last_modified: 2026-09-18 --- # Multi-Site Alarm and Access-Control Service: Connect a Supabase Asset Register With Salesforce > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md Build a multisite alarm and access-control asset register with clear identity, service history and authorized access. Author Ruben Burdin · Founder & CEO Published September 18, 2026 Read time 5 min read DATA ENGINEERING ## The operating decision A Supabase asset register can keep alarm and access-control equipment context aligned with Salesforce while supporting a field or customer application. Model site, functional location, installed device and service event separately. Two-way sync maintains approved record changes; the application still needs its own authorization rules. Limit what users can see and edit by their actual site and role, and keep security-sensitive access details outside broad customer or sales views. Explore the complete [fire, life-safety and security integrators integration and automation hub](https://www.stacksync.com/industry/construction/fire-life-safety-security-integrators) for the systems and processes around this guide. ![Summary card: Sync a Supabase alarm asset register with Salesforce](https://www.stacksync.com/images/blog-highlights/icp-multi-site-alarm-and-access-control-service-connect-a-supabase-asset-register-with-salesforce.webp) ## What this looks like in fire, life-safety and security integrators An integrator services several office buildings for a facilities group. A field app needs device identifiers and service history, while Salesforce needs customer-facing status. Some users cover the whole portfolio and others only one building. A replaced reader should retain its predecessor history without exposing restricted system details to every account contact. The register needs an accurate business model and tested access boundaries, not merely a copied Salesforce asset table. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Site | Service administration | Maintain a stable location key and approved customer relationship. | | Functional position | Asset administrator | Describe where equipment operates independently of the current device. | | Installed device | Service team | Record identity and replacement history through a reviewed update path. | | User-to-site access | Application administrator | Authorize access explicitly rather than inferring it from CRM associations. | ![Record ownership diagram: Site, Functional position, Installed device](https://www.stacksync.com/images/blog-diagrams/icp-multi-site-alarm-and-access-control-service-connect-a-supabase-asset-register-with-salesforce.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Separate position and device Create distinct references for a door, panel location or other functional position and the equipment installed there. A replacement changes the device relationship while the position remains. This prevents service history from becoming ambiguous when equipment labels are reused. 2. 02 Choose the CRM context to share Select the asset and service fields Salesforce users need for customer conversations. Keep restricted configuration, credentials and other sensitive operational details outside that broad summary. A successful sync should not expose every field simply because it exists in the source register. 3. 03 Define permitted field edits Allow field personnel to submit verified identifier corrections or service evidence through the application's reviewed process. Decide which edits can become approved changes and which need asset-administrator review. Preserve the original value and evidence when resolving a disputed device identity. 4. 04 Implement access independently Use Supabase grants and row policies for the actual user-to-site relationships. Keep the integration connection separate from client credentials and test cross-customer access explicitly. Authentication alone does not establish that a person may view every site associated with the same CRM company. 5. 05 Reconcile replacements and delayed events Test a device replacement, an offline service submission and a reassigned customer relationship. Confirm that late evidence attaches to the device active at the time of the visit, not automatically to the current replacement. Verify the selected Salesforce object's supported change-detection and write behavior. 6. 06 Review exported documents as well as database rows An asset register may link to service reports or supporting files that contain information beyond the summary fields. Apply the same project and role boundaries to those resources and test their direct access paths. Hiding a document link in the application does not establish authorization. The product owner should know which evidence may be shared with a customer and which remains restricted to authorized service or administrative personnel. ![6-step operating sequence: Sync a Supabase alarm asset register with Salesforce](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-multi-site-alarm-and-access-control-service-connect-a-supabase-asset-register-with-salesforce.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### Service note arrives after device replacement Attach it to the correct historical device and visit rather than the latest asset automatically. ### User moves to another property group Update explicit memberships and verify the access change under the application's session policy. ### Two assets share a handwritten label Use reviewed identifiers and location evidence to resolve the ambiguity. ## What to verify before expanding - Current equipment and previous devices remain distinct. - A customer user cannot read unrelated sites. - Restricted operational fields stay out of the sales summary. - Late service evidence attaches to the correct historical device. ## Connect this process to the rest of your operation [Explore Stacksync two-way sync](https://www.stacksync.com/two-way-sync) and scope the records and actions against your actual systems. [Book a demo](https://www.stacksync.com/book-a-demo) with a real site example and the exception your team handles most often, for example service note arrives after device replacement. - [Salesforce–NetSuite for Fire and Security Integrators](https://www.stacksync.com/use-case/salesforce-netsuite-fire-security-integrators) - [HubSpot–Acumatica for Inspection and Monitoring Contracts](https://www.stacksync.com/use-case/hubspot-acumatica-fire-security-contracts) - [Fire and Security Integrators: Align Salesforce Installed Equipment With NetSuite Customer and Service Records](https://www.stacksync.com/blog/fire-and-security-integrators-align-salesforce-installed-equipment-with-netsuite-customer-and-service-records) - [New Security Installations: Route Customer Acceptance Before Activating Recurring Billing](https://www.stacksync.com/blog/new-security-installations-route-customer-acceptance-before-activating-recurring-billing) - [Fire-System Inspection Follow-Ups: Route Deficiency Records to Approved Remedial Work](https://www.stacksync.com/blog/fire-system-inspection-follow-ups-route-deficiency-records-to-approved-remedial-work) - [Two-Way Sync Production-Readiness Checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) - [Remove Duplicate HubSpot Contacts Fast with Stacksync](https://www.stacksync.com/blog/remove-duplicate-hubspot-contacts-fast-stacksync) The shared architecture guide covers record matching, ownership, and recovery across systems. ## Technical references - [Stacksync Supabase connection setup](https://docs.stacksync.com/two-way-sync/connectors/postgres/authorize-postgres/supabase) - [Supabase row level security](https://supabase.com/docs/guides/database/postgres/row-level-security) - [Stacksync Salesforce connector requirements](https://docs.stacksync.com/two-way-sync/connectors/salesforce) FAQ ## Frequently asked questions Does a Salesforce contact association grant portal access? No. A CRM relationship is not an authorization decision. The application must maintain and enforce approved user-to-site access. Can this store access credentials for technicians? That requires a separately designed credential-management process. This register focuses on asset identity and service evidence, not distributing sensitive access information through broad sync fields. Which records should the pilot include? Use a multisite customer, a replaced device and a service event submitted late. Test those alongside users with different site permissions to validate both identity and access. About the author Ruben Burdin Founder & CEO Ruben Burdin is the Founder and CEO of Stacksync, the first real-time and two-way sync for enterprise data at scale. Ruben is a Y Combinator alumni with a strong background in software engineering and business. [All posts by Ruben Burdin](https://www.stacksync.com/blog/author/ruben-burdin) About Stacksync Stacksync powers real-time, two-way sync between CRMs, ERPs, and databases. Engineers sync data at scale and automate workflows, not dirty API plumbing. Stacksync ## Explore these integrations and topics - [integration Salesforce and Supabase integration](https://www.stacksync.com/integrations/salesforce-and-supabase) - [connector Supabase integrations](https://www.stacksync.com/connectors/supabase) - [connector Salesforce integrations](https://www.stacksync.com/connectors/salesforce) - [platform Two-way sync](https://www.stacksync.com/two-way-sync) - [Two-way sync guides Understand two-way sync, record matching, field ownership, and production readiness.](https://www.stacksync.com/blog#topic-two-way-sync) Keep reading ## Related articles [All articles](https://www.stacksync.com/blog) [Data engineering Fire and Security Integrators: Align Salesforce Installed Equipment With NetSuite Customer and Service Records 5 min read read](https://www.stacksync.com/blog/fire-and-security-integrators-align-salesforce-installed-equipment-with-netsuite-customer-and-service-records) [Data engineering Salesforce–NetSuite Integration: Mapping and Setup 8 min read read](https://www.stacksync.com/blog/the-complete-guide-to-salesforce-netsuite-integration-achieving-true-bi-directional-sync) [App tips Fire and Security Handoff Exceptions: Missing Device IDs, Conflicting Site Records, and Unapproved Remediation 5 min read read](https://www.stacksync.com/blog/fire-and-security-handoff-exceptions-missing-device-ids-conflicting-site-records-and-unapproved-remediation) ## You just read how it should work. See it run on your own data. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)