Several Procore instances
Understand how Procore instances connect to LaunchPad Safety, and set up a company that runs several instances, with one Safety program or a Safety officer for each.
Larger contractors often run more than one Procore instance. How they divide them is up to them: by region, department, division or location (for example one instance for California and one for Texas). Each instance is separate in Procore, with its own projects, Directory and Admin tool. LaunchPad Safety follows the same lines: every rule below is about Procore instances, whatever your company calls them.
How connections work
- LaunchPad Safety connects to Procore one instance at a time. On the Connect Procore page, each instance is listed by its Procore company name.
- One LaunchPad Safety account can connect several instances. Repeat Connect Procore for each one. They all show under Your Procore connections.
- Each instance can belong to only one LaunchPad Safety account. Once it's connected, no other LaunchPad Safety account can connect it, even if the person trying belongs to both. They see Connected to another LaunchPad Safety account.
- To connect an instance, all three must be true:
- LaunchPad Safety is installed in that instance. That needs Admin rights in that instance. See Install LaunchPad Safety in your Procore company.
- You verify with Procore that you belong to that instance. See Connect your Procore company.
- It isn't already connected to another LaunchPad Safety account.
Option 1: one LaunchPad Safety account for every instance
Best when the company runs one safety program across its instances.
- Connect each instance (for example California and Texas) to the same LaunchPad Safety account.
- Everyone shares one safety library, one set of company rules, one safety manual, one team list and one bill.
- To give each instance its own Safety officer: as the Administrator, open Settings and turn on Limit people to their Procore projects. Then everyone except the Administrator sees only the projects whose Procore Directory lists them. Put the California Safety officer in the Directory of the California instance's projects and the Texas Safety officer in the Texas ones. Each sees only their own jobs. See Your Procore project team, and limiting people to their projects.
- The Administrator sees every project in every connected instance.
- Count the seats: everyone, across every instance, uses a seat on the one account. See Plans, prices and users.
Option 2: a separate LaunchPad Safety account for each instance
Best when each instance runs its own program: its own rules, manual, library and Safety officer, or its own budget.
- Sign up one LaunchPad Safety account per instance (for example "Ruiz Petroleum California" and "Ruiz Petroleum Texas"), each with its own Administrator and its own subscription.
- Connect each instance to its own account.
- Each account has its own library, company rules, manual, team, Safety Scores and bill. Nothing is shared between them.
- People who work in more than one instance (a corporate Safety director, for example) keep one sign-in: each account's Administrator invites them, and they switch between the accounts. See Work for more than one company.
Day to day with several instances
- One choice for the Dashboard and Safety Scores. With more than one instance connected, Procore instance at the top of both pages offers All instances or one instance. Change it on either page and the other follows. It's remembered on this computer.
- Dashboard. One instance shows only its jobs, and Safety Scores and Closures by role count only the work on them. All instances combines everything and adds an Instance column to the job table. See The Dashboard and its PDF.
- Safety Scores. One instance scores only its projects. A Superintendent or Project Manager who works in two instances shows under each with only that instance's projects, and once under All instances with all of them. See Safety Scores.
- Reports follow the choice. The Dashboard PDF, the Safety Scores company report, each person's PDF and the CSV cover the instance you chose and name it; the CSV has a Procore instance column.
- Who sees which jobs. With Limit people to their Procore projects on, each person sees the jobs whose Procore Directory lists them, in whichever instance they are. Someone on the California Directory only sees California jobs; someone on both sees both. See Your Procore project team, and limiting people to their projects.
- One setting stays company-wide: Count Procore-started safety work from on the Dashboard applies to every instance.
Plan it before you install
Connections are first come, first served, one instance at a time. - Decide which LaunchPad Safety account each instance belongs to before anyone installs LaunchPad Safety in it. - If you're not ready to connect an instance yet, don't install the app in it.
Moving an instance to another account
- If the connection has no LaunchPad Safety records yet, its account's Administrator can remove it: under Your Procore connections, click Remove this connection. Then connect the instance to the other account.
- If it has inspections, observations or other records, LaunchPad Safety keeps the connection for that account's logs and reports, and you can't remove it yourself. Call (888) 207-2330 or email support@launch-pad-core.com.
- Records already in Procore stay in Procore either way.
Good to know
- Not sure which option fits? Start with option 1. It's one bill and one program, and Limit people to their Procore projects gives each instance's people their own view.
- Talk to us about an Enterprise plan for many instances or many seats: support@launch-pad-core.com.
