Skip to main content
Each row names the systems supported for one source, how that source connects, how often its data refreshes, and whether the connection can write. You grant permissions in the source tool itself, usually on its own consent screen, which lists the access being requested before you approve it. That screen is the record of what was granted. Some systems grant access in one broad permission rather than object by object, and a few connect with a key and have no consent screen at all — see Permissions requested. Method and refresh are stated where they hold for every customer. For the remaining sources they depend on which system you run and how it exposes its data, and are agreed with you before the connection is made. Those cells read set per connection rather than carrying a figure that would not hold. See Refresh for what each method delivers.

​
Sources

Billing is the only required source. What each source turns on, and what stays unavailable without it, is on Connect your tools.

​
Refresh

A source connects by the highest method available to it. The method determines refresh. Every screen states the freshness of the source behind it. A weekly export is never presented as a live figure. Where a row reads set per connection, no single method applies to every customer running that source. The method and its refresh are agreed and stated before the connection is made, and appear on the screens that depend on it. No interval is published here that would not hold for the system you run.

​
Permissions requested

Beacon reads only the objects its figures are built from. What you approve can be wider than that, because some systems grant access in one broad permission rather than object by object, and some connect with a key or a local agent and have no consent screen at all. QuickBooks is one of these. It has one accounting permission, and approving it gives access to your whole accounting file — there is no narrower option to choose. Beacon’s restraint is in what it reads: invoices and credit notes, what customers still owe, the customer records those invoices belong to, your chart of accounts, journal entries and monthly account balances. It does not read suppliers, employees, bank accounts, attachments or full ledger exports. Where a system has a consent screen, it lists the access being requested before you approve it, and the granted access can be inspected there at any time. Billing, accounting and banking connections stay read-only whether or not the system allows writes. This is a choice about systems of record, not a limit of the connection.

​
What Beacon writes

Today Beacon writes nothing back to any source, including your CRM. The Connections page says so on your CRM: Writes nothing back yet. The CRM is the only source the connection lets Beacon write to, and any writing there is limited to a small set of Beacon’s own prefixed fields on your records — added, never edited over your own fields, and removable as one set. Every other connection in this catalogue is read-only. The full write limits are on Boundaries.