Which Digs users can use the Procore integration?

TLDR;

If you are part of the company’s Digs Workspace, you can use the Procore integration.

However, while you must be part of the Workspace to gain access, that access is NOT 100% by default.

If you’re unsure whether a user should have access, the simplest path is:

• Confirm they are part of the correct Digs Workspace

• Confirm they are invited to the relevant project

Once those two boxes are checked, the integration will work as expected.

Workspace membership is required

The Procore integration is designed for core team members. To connect projects, transfer files, or manage project pairing, you must be a user inside the company’s Digs Workspace.

Access to Procore data does not infer Access to Digs, this would be poor behavior for many security reasons as the Homeowner starts to become more involved.

This restriction ensures that only trusted, internal team members can:

• Connect Procore projects/ Create Digs Projects

  Copy files from Procore

  Link or unlink projects

  Manage long-term project continuity

A user cannot use the Integration if they are:

• Part of a different company’s Digs Workspace

  Only invited as a Collaborator on a single project

  Not part of the Workspace at all

This is intentional and protects your company’s data.
if you have scenarios which need different rights we, we would love to talk to you and understand more.

Digs Project Visibility rules still apply

Even within a Workspace, users can only see and interact with projects they’ve been invited to.

For security reasons:

• Admins are automatically invited to all projects and can see everything.

• Workspace Members must be invited to individual projects to access them.

How this shows up in Procore

Here’s what that looks like in practice:

• Admins will see all connected projects and can use the integration without restriction.

• Workspace Members may open the Digs app and see fewer projects than expected.

• A user may load a connected Procore project and receive a message advising that they need to be invited to that project inside Digs.

This does not mean the integration is broken. It simply means the user does not yet have project-level access.

Why it works this way

The Procore integration allows access and transfer of sensitive project data. Digs workspace membership ensures that only trusted internal team members can connect systems and move files between them. It’s just how we roll. Better safe than sorry, and changes can be easily made to allow users.

For small, close-knit teams, it’s common to have multiple Admins to keep processes smooth. Admins have access to all projects, no invitation needed.

As teams grow, inviting users to specific projects becomes more important for maintaining clean security boundaries.