Skip to main content

Siteline + Foundation - Setup (Siteline)

One-time setup for the Siteline + Foundation integration via Siteline

Written by Bradley LaFave

Intended audience: technical user. This page covers the one-time Foundation-side setup required to connect Foundation to Siteline: requesting a dedicated Foundation user with the right access, whitelisting Siteline's static IPs if you run Foundation on-premise, and sharing your connection details. Day-to-day billing workflows are covered on the Usage page.

Siteline's integration with Foundation lets you set up projects for billing in Siteline and post your invoices back to Foundation. It also imports change orders into your Siteline schedule of values, and imports your vendor list for managing sub-tier lien waivers and compliance requirements.

This integration connects to your Foundation database directly. It works with both hosted and on-premise instances of Foundation, but there is one extra firewall step for on-premise installations of Foundation.

If you have questions at any point, reach out to [email protected] or your Siteline CSM.

Are you hosted or on-premise?

This determines which steps apply to you.

  • Hosted — your Foundation database is hosted by Foundation Software. Most customers are hosted.

  • On-premise — Foundation runs on a server your company controls.

If you're not sure, your IT team or Foundation support can confirm.

  1. Whitelist Siteline's static IPs and confirm port — On-premise instances only

    Skip this step if you're on hosted Foundation. Foundation Software's hosted database doesn't restrict connections by IP, so there's nothing to whitelist.

    If Foundation runs on your own server, ask your IT team to whitelist Siteline's static IPs:

    • 136.111.250.112

    • 34.123.68.248

    This allows Siteline's servers to communicate with the Foundation database hosted on your network. Siteline always connects from these two addresses and no others, so the rule can be scoped tightly rather than exposing the database more broadly.

    Exactly how this is configured depends on your network — your IT team will know whether it belongs on the perimeter firewall, a VPN appliance, or elsewhere.

    Also confirm which port Siteline should use to communicate with the Foundation database. Usually for on-premise instances, this is 4243.

  2. Request a dedicated Foundation user for Siteline

    Foundation's support team provisions database users — this generally can't be done by your own IT team, even on on-premise instances.

    File a support ticket with Foundation asking them to create a dedicated user for the Siteline integration, and to grant it the object-level permissions listed on the SQL Server Permissions page — that list is generated directly from Siteline's queries, so it is always current.

    Ask for every object on that page in one request. Partial grants tend to cause confusing failures rather than clean errors — a project imports with no schedule of values, or a pay app fails to sync — so a missed grant means another round-trip with Foundation support.

    Start this early. Foundation controls the access grant, and turnaround commonly takes several weeks. This is the step that most often determines your go-live date, so file the ticket before the rest of your Siteline onboarding is ready.

    A dedicated user is strongly recommended over reusing an existing login — it keeps the integration's access scoped and makes it easy to audit or revoke.

  3. Share connection details with Siteline

    Once the user is provisioned (and the IPs are whitelisted, if you're on-premise), share the following with your Siteline CSM through a secure channel such as a shared 1Password vault — not over plain email:

    • Hostnamesql.foundationsoft.com if hosted, or your network's external (WAN) address if on-premise. Confirm the exact value with your IT team.

    • Port9000 if hosted, usually 4243 if on-premise. Confirm the exact value with your IT team.

    • Database — the name of your Foundation database. On hosted instances this usually looks like CAS_<name>.

    • Username and Password — the dedicated user Foundation created.

    Siteline completes the connection on our side and runs a set of automated checks against your database. Your CSM will confirm once the integration is live, or tell you exactly which access grant is missing if a check fails.

Already using the Foundation integration?

If your company already connects Foundation to Siteline through our previous integration method, the Foundation user you have today is reused as-is — same credentials, same access. No new request to Foundation support is needed. Your CSM will coordinate the switch.

On-premise customers are the one exception: the previous method connected from a different set of addresses, so you'll need to complete the whitelisting step above before the switch.

Did this answer your question?