Ir para o conteúdo principal
DocumentMS
Solicitar uma demonstraçãoTeste gratuito
Português (Brasil)

Integration

Google Workspace document management integration

Google Workspace users sign in to DocumentMS with their existing account, and documents can be imported from Drive into a controlled folder. The imported copy becomes the record: versioned, permissioned and subject to the retention rule of its document type.

Solicitar uma demonstraçãoVer preços

What this connection does

Users sign in to DocumentMS with their Google Workspace account over OIDC, and documents can be imported from Google Drive into a controlled folder with metadata and a retention rule applied on arrival.

The imported copy becomes the record: versioned, permissioned and subject to the retention rule of its document type. That is the important distinction — this is not a sync that keeps two copies in step, it is a move from collaboration into control.

What you need on your side

Have these ready before you start; the configuration itself takes minutes.
  • A Google Workspace tenant and an administrator able to configure OAuth consent
  • A decision about which Drive content constitutes a record, made before the first import rather than after
  • Groups corresponding to the DocumentMS roles you intend to map

Setting it up

Test with one user and one document before rolling out. Connection events and permission changes appear in the audit trail.

  1. Step 1: Configure OAuth

    Create the OAuth client in Google Cloud console with the DocumentMS redirect URI and appropriate scopes.

  2. Step 2: Map groups to roles

    Map Workspace groups to DocumentMS roles so access follows directory membership.

  3. Step 3: Import selectively

    Import the identified records with record class and mandatory metadata applied. Do not bulk-import a whole Drive.

  4. Step 4: Revoke what you left behind

    Audit and revoke sharing links on the original Drive copies, or the record remains accessible outside the system you just moved it into.

Limits worth knowing before you rely on it

Stated up front rather than discovered later. Every integration has boundaries, and a directory that hides them just moves the discovery to a support ticket.
  • Native Google Docs, Sheets and Slides are converted on export; comments, suggestions and revision history do not travel intact — decide whether that history is evidential before importing
  • Import is a one-time move rather than a continuous sync, deliberately: two live copies of a record diverge, and a record that exists twice is not under control
  • Drive revision history is time-based and can be pruned by Google, so it should not be assumed to be a complete version series available for migration

Última revisão: 2026-09-01

Want to see this working?

We can set the connection up against a sandbox tenant on a demo call so you can see the behaviour rather than read about it.
Solicitar uma demonstraçãoTeste gratuito