RowSync
Connections and object mappings
Tenants
Creating a new tenant + its first admin is the only way a new tenant comes into existence — no public signup.
| Name | Region | Created |
|---|
+ New tenant
+ Invite a tenant's first admin
They'll get an email with a one-click activation link — no password ever set.
Region · Created
Admins
| Role | Status | Created |
|---|
Target databases
Connections
You're logged in as the super-admin — this account manages tenants only and isn't itself a member of any tenant, so it can't register target databases or Salesforce connections. Create a tenant and its first admin above, then log out and log back in as that admin to continue setup.
Connection
Browse and manage your connections here — pick which one to configure sync objects for on the "Sync objects" page.
None yet — connect one below.
1. Salesforce connection
One org can sync into more than one target database. Pick "Existing SF org" to add another database to an org you've already connected, instead of reconnecting it.
Have you installed the RowSync package in this Salesforce org before?
Install it once for this org — one click, matching whichever org type you picked above — then come back and continue.
Click, log in, Allow — no Connected App setup in your org required.
Uses your own Connected App with a certificate instead of the login flow. No RowSync package needed for this path.
Reuses that org's stored credentials — no login round-trip needed, and its shared Apex integration is already deployed.
This only labels the connection — it does not create or pick a database. Choose the actual target database and schema in step 3, to the right.
2. Target database
Where synced Salesforce tables actually live. Connection strings are encrypted at rest and never shown again after saving.
Manage target databases
Need to provision a brand-new database and role instead of pasting an existing connection string? Use the Provision Database wizard.
3. Database & schema
Sync objects
No connections yet — add one on the Connection page first.
Configuring — eligible fields.
New tables always go in this connection's own schema.
Tables in sync
Objects
Set each Salesforce object up on its own. Open one to choose its fields, copy its existing records and turn on sync.
| Salesforce object | Lightfield object | Status | |
|---|---|---|---|
| Loading… | |||
Changes made in Lightfield
For every object on this connection. Changes made in Salesforce always reach Lightfield within seconds.
Faster, optional: on Lightfield plans with Workflows (Pro), a Workflow that notifies RowSync brings Lightfield changes within seconds, and this check becomes a backup.
Webhook health: —
x-lightfield-secret = Lightfield object
Which Lightfield object receives these records.
Fields
Fields that already exist on the Lightfield object are matched and ticked for you. Ones marked new must be created in Lightfield: "Check fields" lists them, with a request to paste into Lightfield's agent.
Record Type (optional)
A Lightfield single-select field that receives the Salesforce Record Type's name. Only needed when a picklist's allowed values depend on the Record Type (e.g. Opportunity Stage).
Record Type values
A suggested Lightfield value is pre-filled by matching labels; change any row before saving. A row left empty fails when that value comes back from Lightfield to Salesforce.
| Record Type | Field | Salesforce value | Lightfield value |
|---|
Copy existing records optional
A one-time copy of the records already in Salesforce. Records RowSync copied can be removed again.
| Earlier copies | Records | Started | Last error |
|---|
Two-way sync
Activity
Sync history and any Postgres → Salesforce rows that need attention, per connection.
No connections yet — add one on the Connection page first.
Rows that ran out of automatic retries. Retrying re-queues the original change exactly as captured — nothing is re-derived.
| Object | Operation | Salesforce Id | Attempts | Last error | Failed |
|---|
Needs attention
Rows that ran out of automatic retries. Retrying re-queues the original change exactly as captured — nothing is re-derived.
| Object | Operation | Salesforce Id | Lightfield Id | Attempts | Last error | Failed |
|---|
Recent sync history
| Object | Salesforce Id | Lightfield Id | Operation | Direction | Status | Detail | When |
|---|
Record Status
Row counts on each side for every actively-synced object — a mismatch means the two systems have drifted, even if every sync attempt reported success.
No connections yet — add one on the Connection page first.
| Object | Table | Postgres rows | Salesforce rows | Status |
|---|
Sync Maps
Every connected Salesforce org, on its own tab — the sync-target connections under it (each labeled by its actual target database and schema, not just its own name), and the tables currently syncing under each one.
No Salesforce orgs connected yet — add one on the Connection page first.
Provision Database
Generates the exact least-privilege Postgres script a DBA needs to run for a new RowSync target database — RowSync never touches an elevated database credential itself; a DBA always runs the script under their own authority, then this page verifies the result and registers it.
New or existing database?
This database will be created by the script.
Role & schema
Does another application (not RowSync) already have its own Postgres role that will need to read the tables RowSync syncs into this database? Name it here as a reminder for yourself — RowSync can't grant it access until the connection itself exists (a later step), but this carries the name forward so you don't have to remember it. Leave blank if none, or add one later from a connection's Details panel.
Run this script as your DBA
Hand this to whoever administers this Postgres server — it's safe to re-run if something partially fails.
Connection details for this role
Save this alongside the script — it's the connection RowSync will use once registered.
Registering…
Field Rules
Every field across your synced objects that carries a Record Type, restricted-picklist, dependent-picklist, or Global Value Set requirement — the same things Sync objects badges per-field, all in one place, so a requirement that could derail a sync is visible before it does.
No connections yet — add one on the Connection page first.
Tutorials
Short videos of the main things you do in RowSync, recorded on a sample workspace (none of it is real data).
Team
Everyone with access to this tenant. Invited teammates get an emailed activation link — no password is ever set by anyone but them. Members can configure and activate object syncs but can't manage connections or the team.
| Role | Status |
|---|