SigilbaseGoogle Workspace audit logs, sealed as they arrive.
Sigilbase will collect audit logs and configuration snapshots from Google Workspace into a chained, signed ledger: every collection receipted, every gap declared, and evidence your auditor verifies offline without an account.
Named connectors ship in waves, and Google Workspace is in the first. Until then, anything that can send JSON reaches Sigilbase through the events API today.
- Status. First wave.
- Collected by. A connector Sigilbase runs.
- Connects with. Service account with domain-wide delegation, narrowest Reports/Directory read scopes.
- Category. Identity, SSO and directory.
What can be ingested from Google Workspace
Each stream below becomes its own sequence in the ledger, with the record kept exactly as Google Workspace gives it and a hash of those bytes beside it. Snapshots are read on a cadence and the differences between them dated.
-
Event stream
Admin SDK Reports activities: admin, login, token, saml, groups, drive (opt-in), mobile, user accounts, access transparency (where licensed).
-
Snapshot
Users, 2SV enrolment, admin roles, OAuth app grants.
How it will be collected
When its connector ships, a connector Sigilbase runs will read Google Workspace on a schedule you set.
Stream and credential names follow the vendor's documentation as read in October 2026; the connector's build confirms them.
The evidence model
What every connector and receiver ships with, whatever the source:
- A receipt per collection: what was asked for, what arrived, the cursor before and after
- A declared gap for any interval nothing covers, never a blank
- A daily settlement once late records can no longer arrive
- The raw record, byte for byte, with its hash
- An evidence bundle anyone can verify offline
What you get
-
Sealed as it arrives
Every record is hashed and chained to the one before; every few minutes the chain is sealed into a signed checkpoint. A changed, deleted or reordered record fails verification at that exact point.
-
Continuity you can show
The receipts chain too, so an auditor sees not only the records but that nothing between them went uncollected, and where a gap was, that it was declared.
-
Verified without us
An export carries the open-source verifier. It runs offline, checks the chain, the receipts and the gaps, and needs no Sigilbase account. How the service is run.
Questions about Google Workspace
-
Does Sigilbase support Google Workspace?
Named connectors ship in waves, and Google Workspace is in the first. Until then, anything that can send JSON reaches Sigilbase through the events API today. Whatever arrives is written to a chained, signed ledger whose evidence anyone can verify offline with the open-source verifier, without a Sigilbase account.
-
What Google Workspace data can Sigilbase ingest?
Event stream: Admin SDK Reports activities: admin, login, token, saml, groups, drive (opt-in), mobile, user accounts, access transparency (where licensed). Snapshot: Users, 2SV enrolment, admin roles, OAuth app grants.
-
How will Google Workspace evidence be collected and verified?
When its connector ships, a connector Sigilbase runs will read Google Workspace on a schedule you set. Every collection will be receipted in the connection's own stream: what was asked for, what arrived, and the cursor before and after. An interval nothing covers will be declared as a gap, never left blank. Exports carry the standalone verifier, which checks the chain, the receipts and the gaps offline.
Start recording provable history
Chained, sealed, independently verifiable audit logs, from the first event. Free while Sigilbase is in beta.
Questions first? Write to hello@sigilbase.io.