Integrations/setup
Integrations
Setup · Integrations · Guide

Customer setup steps for every connector

What each customer admin needs to do, what's gated, and what to fall back to. All connectors are read-only.

Buildpass

Live

Working via manual credentials. OAuth button hidden until BUILDPASS_OAUTH_CLIENT_ID is set.

Auth: OAuth2 client-credentials (per customer)

Open connector →

Customer steps

  1. Email Buildpass support and request an API client (clientId + clientSecret) for your builder. Buildpass issues these per customer — no self-serve.
  2. Find your builderId in your Buildpass URL (the bld_… value).
  3. In Alloovium → Integrations → Buildpass → Manual credentials, paste clientId, clientSecret, and builderId.
  4. Click 'Discover' to confirm the credentials see your builder + projects.
  5. Optionally narrow to specific projects, then 'Install connector'. Secrets land in AWS Secrets Manager; the next sweep indexes the docs.

If blocked

Buildpass API is gated. If a customer cannot get credentials, connect their SharePoint or Drive instead — most builders mirror docs there.

SharePoint

Live

Multi-tenant Entra app already registered. Customers consent into it.

Auth: Entra ID multi-tenant app (Microsoft Graph)

Open connector →

Customer steps

  1. An M365 global admin clicks 'Grant admin consent' in the SharePoint connect panel.
  2. Microsoft consent screen appears — admin approves the requested Graph scopes.
  3. Pick the SharePoint site and document library to index.
  4. Save → next sweep ingests.

Google Drive

Blocked

UI works but ingest will 403 — the shared service account only has docx-conversion scopes.

Auth: Service account + domain-wide delegation

Open connector →

Customer steps

  1. Workspace admin creates (or reuses) a Google Cloud service account and downloads its JSON key.
  2. Enable the Drive API for the service account's project.
  3. In Google Workspace Admin → Security → API controls → Domain-wide delegation, add the SA's client ID with scope https://www.googleapis.com/auth/drive.readonly.
  4. In Alloovium → Integrations → Drive, paste the SA JSON, optionally an impersonation email, pick folders to scope, and install.

If blocked

To unblock the shared SA: Workspace admin adds drive.readonly to the existing alloovium-docx-converter delegation entry. One-time, then no customer action required.

Procore

Off

PROCORE_ENABLED=false. Tile hidden / coming soon.

Auth: OAuth2 (custom app)

Customer steps

  1. Register a Procore custom app in your company account.
  2. Provide PROCORE_CLIENT_ID and PROCORE_CLIENT_SECRET to Alloovium ops.
  3. Once enabled, customer admin will OAuth-grant access in the Procore connect panel.

Always-on fallbacks

No connector setup required.

Manual upload
Drag-drop at /upload. No setup, no admin.
Email ingest
Each tenant gets {tenant}@ingest.alloovium.com — forward attachments and they're picked up automatically.

For technical/internal setup details (Entra app manifest, Buildpass scopes, Procore custom-app config) see docs/integrations/ in the repo.