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.
Prerequisite
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 0: Auditor sets up the engagement in Fieldguide
Before you can connect Drata to Fieldguide, your audit firm must complete this step on their end:
The auditor adds your organization as a customer/company in Fieldguide.
The auditor creates the audit (engagement) in Fieldguide for this specific engagement.
Confirm with your auditor that both of these are done before starting Step 1.
Step 1: Generate your Fieldguide API token
After your auditor invites you to Fieldguide, sign in to your Fieldguide instance and navigate to My Profile > API Tokens > Create API Token.
Select the checkboxes for all of the required scopes below, then click Generate Token:
engagements:readengagements:writecomments:writecomments:readcompanies:readengagements.files:writeengagements.files:readfiles:readrequests.files:writerequests.files:readrequests:writerequests:readusers:readwebhooks:writewebhooks:read
You will paste this token into Drata whenyou create the Fieldguide connection.
Step 2: Create the Fieldguide connection in Drata
In Drata, go to Settings > Connections and create a new Fieldguide connection.
Complete the following fields:
Audit Firm Name — enter a name that identifies this audit firm's connection. When naming the connection, use the auditor or audit firm name as the alias so it is easy to identify later.
Auditor Domain — enter your audit firm's domain.
API Key — paste the API token you generated in Step 1.
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.
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 and select External Audit as the audit type.
Under Conduct Audit, select Connected Audit Tool.
Scroll down to the Configure connected audit tool section and select the desired drop down.
Tool: choose the Fieldguide connection you created.
Audit firm name (This name may change depending on the firm name): Select the specific audit/engagement your auditor already created and named in Fieldguide. Wait for this list to load if it doesn't appear immediately.
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.
I do not see requests in the connected audit yet
Confirm that you selected the correct Fieldguide engagement and that requests already exist in that engagement.