Reference · built on requestOperator by FibricSafety, security & compliance

Contractor Credentials

Checks contractor insurance, training, and certification end dates against site access and proposes an access hold or a renewal request.

Request accessPricing ↗

About

Contractor Credentials is an operator job for the paperwork that has to be current before a contractor badges in. It reads the register you keep of each contractor's insurance, training, and certification end dates, whether that is a Smartsheet, a Google Sheet, a SharePoint list, or an Airtable base, and the completed agreements in Docusign. It reads the access side too: contractor users and their groups in Brivo, time-limited group links in Kisi, and cardholder competencies with an expiry in Gallagher Command Centre.

Where an end date falls before a scheduled visit, or has already passed while the credential is still active, it proposes an access hold and a renewal request to the contractor's contact. You approve each one. Nothing is suspended, and nothing is sent, until you do.

This is a reference listing. It documents what Fibric would read from Contractor Credentials and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Contractor registers with insurance, training, and certification end dates: rows in Smartsheet, Google Sheets, a SharePoint list, or Airtable
  • Completed and expiring agreements in Docusign: status through listStatusChanges and Connect events such as completed and voided
  • Contractor users, groups, and suspended state in Brivo; group links with valid_from and valid_until in Kisi
  • Cardholder competencies in Gallagher Command Centre, each with expiry, enabled, and a status such as Expiring
  • Access events for contractor credentials, so a lapsed contractor who badged in today rises to the top of the list
  • Scheduled visits or work windows, where a sheet or work order names the dates a contractor is expected on site

Proposed actions

  • Target capability: propose suspending a contractor's user in Brivo, or removing them from an access group, until the document is renewed
  • Target capability: propose a renewal request by email through SendGrid, or a Microsoft Teams note to the host, naming the document and end date
  • Target capability: propose a weekly list of contractors whose documents end before their next scheduled visit, with the access each one still holds
  • Target capability: propose reinstating access once a new end date is entered in the register, for the same approver

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Hold a badge before the insurance lapses

    A Smartsheet row shows liability cover ending Friday and a Brivo user still active. The operator proposes a suspend on that user and an email through SendGrid to the contractor's contact.

    With Smartsheet, Brivo Access, Twilio SendGrid

  • Let Gallagher competencies drive the request

    Competencies with status Expiring in Gallagher Command Centre become one renewal request each, sent to the contractor and copied to the host in Microsoft Teams.

    With Gallagher Command Centre, Microsoft Teams

  • Time-box a Kisi group link to the paperwork

    For contractors on Kisi group links, the operator proposes setting valid_until to the earliest document end date in your Google Sheet, so access ends when the cover does.

    With Kisi, Google Sheets

  • Close the loop from Docusign

    When a renewed agreement completes in Docusign, the operator proposes updating the Airtable row and reinstating the Brivo access it earlier proposed holding.

    With Docusign eSignature, Airtable, Brivo Access

Requirements

  • A register of contractor documents and end dates in Smartsheet, Google Sheets, SharePoint, or Airtable, with one row per contractor and document
  • One access control connector holding contractor credentials: Brivo, Kisi, or Gallagher Command Centre
  • One messaging connector for renewal requests: SendGrid for email, or Microsoft Teams
  • A mapping from register row to access user, set once in the operator's configuration, since the two systems rarely share an id
Authentication
Reads registers and access records through the connectors you bind, each with its own service account or API key, and writes holds and requests through them; it keeps no credentials of its own.

Limits

  • No contractor prequalification platform is in the catalog. Fibric links yours on request; until then, end dates come from the register you keep
  • It reads end dates as entered. A renewed policy not yet typed into the register still reads as lapsed until someone updates the row
  • It checks dates, not documents. Whether a certificate is genuine or the cover adequate stays with the person who files it
  • Access holds go only through platforms whose API exposes a suspend or group change; on others it proposes a task for an administrator

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Contractor Credentials ↗

Questions and answers

Who approves a hold on a contractor?
Every hold and every request. You see the contractor, the document, its end date, the access they hold, and the message text. You can approve as written, change the text, or dismiss it. Reinstating access after renewal is its own proposal.
What is on the record for each contractor?
A receipt per contractor: the register row read, the end date, the access found, the hold or request proposed, who approved it, what changed in the access platform, and how to reverse it.
Does it suspend anyone on its own?
No. A suspend or group removal is written only after a person approves it, through the access connector, once. It never deletes users or credentials, and it never sends a message that was not approved.
Ask about Contractor Credentials

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy