If your team wants Taliho to open inside Procore, the Marketplace install is only the first step. A Procore Company Admin still needs to configure where the embedded app appears and make sure the right people can launch it.
What this setup needs to accomplish
At a high level, the Procore side of the rollout should do four things:
- Install or connect the Taliho embedded app in the correct Procore company.
- Create an App Configuration so Taliho can appear in the right Procore context.
- Apply that configuration to the company, selected projects, or all active and future projects.
- Verify users can open Taliho from Procore and finish the Taliho-side connection flow.
Know the difference between Procore setup and Taliho setup
The most common confusion is assuming the Marketplace install alone finishes the integration. It does not.
- Procore setup controls whether Taliho appears in Procore at all.
- Taliho setup controls which Taliho company, user, and project are connected after the app opens.
That means a Procore Company Admin usually handles the availability side first, then a Taliho admin or integration owner completes the connection inside Taliho.
Gather the right access before you begin
Before rollout, confirm you have:
- Procore Company Admin access for the company where Taliho will be installed.
- A Taliho company admin or integration owner available to complete the connection after launch.
- A short list of target projects if the app should not be available company-wide yet.
- Agreement on the display title users should see in Procore when they open Taliho.
Use App Configurations to control visibility
Procore manages embedded app visibility through App Configurations. If you are new to that concept, start with Procore's official guide to What are App Configurations?.
For most Taliho rollouts, the Company Admin will then choose one of these paths:
- project-level configuration for selected projects
- global projects configuration for all active and future projects
- company-level configuration if the embedded app should also be available from the company header and the app supports that option
Recommended rollout order
For a low-risk rollout, use this sequence:
- Install or connect Taliho in the target Procore company.
- Create the App Configuration and give it a clear title users will recognize.
- Apply the configuration to a pilot project or a controlled set of projects first.
- Launch Taliho from Procore and complete the Taliho sign-in or connection flow.
- Link a Taliho project to a Procore project where live Procore data will actually be used.
- Expand to more projects only after the embedded launch works cleanly.
What "success" looks like
You know the Procore-side setup is working when:
- Taliho appears in Procore's app-launch path for the intended users
- the app opens inside the Procore iframe instead of feeling like a dead link
- users can complete the Taliho connection flow without landing on an error page
- Taliho projects can be linked to the correct Procore projects when the workflow needs drawings, documents, tools, or fetched Procore items
Continue with the detailed guides
Use the deeper docs below for the actual hands-on steps:
- Install Taliho in Procore and Open It in the Embedded App
- Connect Procore to the Taliho Web App
- Troubleshoot Procore Integration in Taliho
If your goal is not installation but field access to live project content, continue with Share Procore Tool Data with Taliho.