Overview

Use this article to create a Fieldguide connection in Drata and link that connection to a connected audit in Audit Hub.

This setup flow applies to the new first-party Fieldguide integration in Audit Hub.

Before you begin

Before you start, make sure that:

your auditor has invited you to Fieldguide so you can access the correct engagement there.
you can sign in to Fieldguide and generate an API token to use in Drata.
you have access to Settings > Connections in Drata.

Treat your API token like a credential. Store and share it securely.

Step 1: Generate your Fieldguide API token

After your auditor invites you to Fieldguide, sign in to Fieldguide and generate your API token.

When you create the token in Fieldguide, make sure it includes all required scopes for the Drata integration:

engagements:read
engagements:write
comments:write
comments:read
companies:read
engagements.files:write
engagements.files:read
files:read
requests.files:write
requests.files:read
requests:write
requests:read
users:read
webhooks:write
webhooks:read

You will paste this token into Drata when you create the Fieldguide connection.

Step 2: Create the Fieldguide connection in Drata

In Drata, go to Settings > Connections and create a new Fieldguide connection.

When you create the connection:

enter the connection details.
paste your Fieldguide API token.
save and test the connection.

If you work with multiple auditors or audit firms that use Fieldguide, create a separate Fieldguide connection for each one. This makes it easier to choose the correct connection later when you create connected audits.

When naming the connection, use the auditor or audit firm name as the alias so it is easy to identify later.

After the connection is created, Drata shows a connection health status such as Connected, Disconnected, or Error.

Step 3: Create a connected audit

Go to Compliance > Audits > Create audit. On the Audit type step, select Connected audit tool. This option appears only if at least one audit-tool connection already exists in your workspace.

Then:

select the Fieldguide connection you want to use.
choose the connection by the alias or name you created for that auditor or audit firm.
wait for the Fieldguide engagement list to load.
select the Fieldguide engagement you want to link to the audit.

If no Fieldguide connection exists yet, you must create one in Settings > Connections before you can create a connected audit.

Step 4: Finish audit setup

After you select the Fieldguide engagement, continue through the rest of the audit setup flow.

For connected audits:

the standard Assign auditors step is skipped.
assigned auditors are synced from the linked Fieldguide engagement when the audit is created.
the audit period is pulled from Fieldguide and becomes read-only in Drata for that connected audit.

On the review step, you should see the connected audit tool and the selected Fieldguide engagement before you create the audit.

Step 5: Confirm that the audit is connected

After the audit is created:

the audit shows Fieldguide as the connected audit tool.
the audit header shows the linked engagement and connection health.
requests from the linked Fieldguide engagement begin appearing in Audit Hub.

Troubleshooting

I do not see Connected audit tool in the audit wizard

Make sure a Fieldguide connection already exists in Settings > Connections. If no audit-tool connection is configured, the connected audit option is unavailable in the wizard.

My Fieldguide connection shows Disconnected or Error

Re-test the connection and update the Fieldguide token if needed. Connected audits surface the connection health so you know when sync may be interrupted.