Skip to main content
Provider connections are the standard way to enable organization-wide discovery. Depending on the provider and permissions granted, the connection can add applications, directory context, activity, delegated access, and relevant vendor signals from organizational mailboxes.

​
Google Workspace provider setup

Confirm that the Google service account exists, domain-wide delegation is enabled, and the Client ID and approved scopes match the setup guide.
  1. Open the Google Cloud service-account settings.
  2. Confirm domain-wide delegation is enabled.
  3. Open Google Admin Console → Security → Access and data control → API controls.
  4. Confirm the Porcia entry is present and authorized.
  5. Allow a short propagation period, then retry the provider verification.
Confirm that relevant vendor messages exist in organizational mailboxes and that the provider connection is active. Initial processing can take time for larger organizations. If the provider status shows an error, retry verification or contact support with the workspace and provider status.
Create or restore the approved service-account credential, confirm domain-wide delegation is still authorized, and complete the provider verification again. Do not email or commit service-account key files.

​
Microsoft Entra provider setup

Confirm that the Microsoft Entra connection is active and that the tenant has relevant vendor messages. Initial processing can take time for larger organizations. If the provider status shows an error, retry verification or contact support with the workspace and provider status.

​
Legacy forwarding fallback

If organization-wide provider access is unavailable and legacy forwarding is enabled for your workspace, forwarding requires a per-user rule and has no historical coverage.
Confirm the forwarding address and rule in your email provider, send a test vendor message, and wait for processing. Personal, internal, or unrelated messages may not produce an application signal.
Narrow the email-provider rule by sender domain or vendor-specific conditions. Test with one vendor before expanding the rule.

​
General discovery issues

Go to Settings → Integrations and review the connected provider status and latest synchronization information. Relevant mailbox signals follow the provider connection when they are available for the workspace.
Use the provider’s supported Sync Now control where it is available. Synchronization is asynchronous, and results may take time to appear in the Apps or Spend views.
Open the application in Assets → Apps, review the available spend fields, and correct the record if your role permits editing. Contact support if the same extraction issue repeats.
Review the source and vendor details on each record. If your workspace provides a merge or correction action, use it only after confirming the records represent the same application; otherwise contact support.

​
Getting help

If the issue persists, contact [email protected] with your workspace, provider type, connection status, approximate start time, and the safe error message shown in the product. Do not include credentials, access tokens, mailbox content, or private customer data.

Organization Integrations

Review provider connection methods and permissions