Jobsite Access & Safety integration
Brivo COI compliance integration
Suspend Brivo Access users when their employer's insurance lapses, and reinstate them the moment a renewal is verified. Pikorua Security maps each vendor to its Brivo groups, verifies certificates and endorsements against your rules, and suspends or reinstates the company's users through the Brivo API, with an event subscription logging any entry attempts while a hold is in place.
Brivo, Westlake Tower, Austin
Group Clearview Window Cleaning LLC
Access suspended: COI deficient
GL 2245-8810-06 expired 10/15/2026. 6 users suspended at Westlake Tower.
- Access points
- Roof door R1, Loading dock gate D2
- Users
- 6 suspended
- COI status (custom field)
- Suspended: GL expired
- Entry attempts
- 2 denied, 07:12 AM
- Group schedule
- Weekdays 6:00 AM to 6:00 PM
Written by Pikorua Security Oct 16, 2026, 06:00 AM ET
- Setup time
- 45 minutes
- Connection
- Brivo API + OAuth 2.0 + event subscriptions
- Fields synced
- 6 fields, 4 trigger events
- Included on
- Enterprise
Sync fields
What Pikorua Security reads from and writes to Brivo.
| Field | Direction | What happens |
|---|---|---|
| Sites and access points | Brivo to Pikorua Security | Read to map each project or property to the doors, gates and elevators that matter. |
| Groups | Brivo to Pikorua Security | Vendor groups matched to Pikorua Security vendors. Group schedules are left untouched. |
| Users | Brivo to Pikorua Security | Users in each group, read to size a hold before it happens. |
| User suspension | Pikorua Security to Brivo | Users in a held vendor's groups are suspended. Brivo keeps their credentials, so reinstatement needs no reissue. |
| Custom field: COI status | Pikorua Security to Brivo | Optional user custom field showing why a user is suspended, for whoever answers the intercom. |
| Access events | Brivo to Pikorua Security | An event subscription on held groups, so Pikorua Security records attempted entries during a hold. |
Trigger events
When the certificate changes, Brivo changes with it.
- Hold
Policy expires or is cancelled
Then: Users in the vendor's Brivo groups are suspended, and their credentials stop working at every access point on that site.
- Hold
Deficiency on a rule you set to gate
Then: Same suspension with the rule recorded; the property manager or superintendent is notified with the user count.
- Warn
Coverage expiring in 15 days
Then: No change in Brivo. The vendor's site contact and broker are notified.
- Release
Renewal verified
Then: Suspended users reinstated, the custom field cleared, and the event subscription for that group ended.
Setup
Live in 45 minutes.
5 steps, done by your Brivo administrator and a Pikorua Security Admin together. Nothing to install on your servers.
Brivo API + OAuth 2.0 + event subscriptions- 1
Authorize the application
A Brivo Access administrator approves Pikorua Security's OAuth 2.0 authorization from Pikorua Security's Integrations screen.
- 2
Confirm the scope
Pikorua Security's calls carry its Brivo developer API key alongside your OAuth token and are limited to sites, access points, groups and users.
- 3
Map groups to vendors
Match each vendor group to a Pikorua Security vendor, per site.
- 4
Approve the event subscription
A Brivo super admin approves the event subscription Pikorua Security uses to log entry attempts by suspended users.
- 5
Pick gating rules and preview
Choose which failures suspend users and review the list of users who would be suspended today.
Suspension, not deletion
Brivo Access, the cloud access control platform from Brivo of Bethesda, Maryland, models access with users, credentials, groups, sites and access points, plus schedules for when a group may enter. For compliance holds the safest lever is user suspension: the user and credentials stay in place and simply stop working until reinstated. Pikorua Security suspends only users in the groups mapped to the held vendor, then reinstates the same users when the renewal clears.
That matters for property managers as much as builders. A janitorial vendor at a Class A office tower, an elevator service contractor with machine room access, a landscaper with a gate fob: each is a vendor whose certificate can lapse mid-contract, and each has credentials in Brivo.
Logged on both sides
The connector authenticates with OAuth 2.0 plus the API key Brivo requires, refreshes tokens automatically and records every suspension and reinstatement in Pikorua Security's audit log with the rule that caused it. Brivo's own audit history shows the same change, so security and risk teams read one story.
The event subscription lets Pikorua Security record when a suspended user tried a door. That report settles vendor disputes and occasionally matters in a claim, when the question is whether an uninsured company was on site.
More jobsite access & safety connectors
Teams that connect this usually connect these too.
FAQ
Brivo connector questions.
Pikorua Security is compliance software. It verifies certificates and endorsements against your contract requirements; it does not sell insurance or give legal advice.
Does suspension delete credentials?
Can different properties have different rules?
What Brivo permissions does Pikorua Security need?
14-day free production trial
Connect Brivo during your 14-day trial.
Upload your current certificates, authorize Brivo, and see which vendors would be on hold today before you switch a single rule on.