Connect a document source
Import drawings and specs from SharePoint, ACC, Procore or Egnyte instead of uploading them by hand.
If your drawings already live somewhere your team maintains, connect that source and import from it. It removes the step where somebody downloads a set, renames it, and uploads a version that is a week old by the time it is reviewed.
Available sources
| Source | What it imports |
|---|---|
| SharePoint / OneDrive | Drawings, specs, standards |
| Autodesk Construction Cloud | Drawings, from ACC and BIM 360 Docs |
| Procore | Drawings from the Drawings tool, plus RFI write-back |
| Egnyte | Drawings, specs, standards |
Egnyte is in development. It needs your firm's Egnyte subdomain at connect time, and that step is not finished yet.
Connecting
Connections are made once per organisation, not per user or per project, from Integrations in your account area. Once connected, everyone in the organisation can import from it into any project.
This usually means the connection has to be made by somebody who can approve it. SharePoint and ACC in particular are commonly locked down so that a tenant administrator must consent on the organisation's behalf.
If a source shows as not yet available rather than offering a Connect button, that provider is not configured on this deployment. It is not something you can fix from your side.
What Bimiq asks for
Read access, and nothing more than it needs.
| Source | Scopes requested |
|---|---|
| SharePoint | Files.Read.All, Sites.Read.All, User.Read, offline_access |
| ACC | data:read, account:read |
There is exactly one write in the whole integration surface: pushing an RFI you have approved back to Procore. Nothing else writes to a connected source, and nothing writes without your confirmation.
Importing
From any module that takes documents, use Import from, pick the connected source, browse to the file and import it. The document lands in the project as though you had uploaded it, with the type set by the module you imported from.
Importing from Documents rather than from a module means you choose the type yourself. Get this right, because it decides which engine reads the file. See Document types.
How your credentials are held
Tokens are encrypted with AES-256-GCM and decrypted server-side only, at the moment a call is made. They are scoped to your organisation and are never shared across firms.
If a connection fails
- The Connect button is missing. The provider is not configured on this deployment.
- Consent was refused. Your tenant requires an administrator to approve the application. Ask them to complete the connection.
- A folder is empty when you browse it. The connected account may not have access to that site or project. Bimiq can only see what the account that authorised it can see.
- A previously working connection stops. The grant may have been revoked or expired at the source. Disconnect and reconnect from Integrations.
These connectors have not yet been exercised against a wide range of live customer tenants. If a connection behaves oddly, it is worth telling us rather than assuming it is your configuration. Contact details are on the contact page.