Why the HR system is the right source of truth for a business card
Most digital business card platforms treat your employee roster as a file. You export a CSV from BambooHR, map the columns, upload it, and the data is accurate until the next person is hired, promoted, or resigns — usually within the same week. From there the roster drifts quietly, and nobody notices until someone spots a live card for a person who left in March.
BambooHR already holds the answer to every question a business card asks. It knows who works here, what their title is, which department they sit in, what their work email is, and — the part that matters most — the exact date they stopped working here. Reading that directly removes the export step, and with it the drift.
There is a security argument too, and it is usually the one that gets the project approved. A digital business card is a public URL carrying a name, a job title, a company, a direct phone number, and an email address. Left live after termination it is a working asset for social engineering, and unlike a deactivated email account, nobody gets an alert when it is used.
What the hourly sync actually does
Every scheduled run reads your current BambooHR roster and compares it to what QRBold already holds, then acts only on the differences.
- New employees. Appear in the roster as eligible. Whether they receive a card depends on the provisioning rule you set — being in the roster is not the same as getting a card.
- Changed attributes. A promotion, a department move, or a new mobile number updates the card behind the existing QR code. The printed code never changes.
- Terminations. Trigger the deprovision action you configured — suspend, delete, or keep — without anyone remembering to do it.
- Re-hires. A returning employee is matched back to their existing record rather than duplicated, so scan history is preserved.
- Plan re-check. The Enterprise capability is verified on every run, not just at connect time, so the integration state always reflects your current plan.
Reading the roster is not the same as handing out cards
This distinction is deliberate and worth being explicit about, because it is the difference between an integration you can pilot safely and one you cannot. The BambooHR connector fills a roster and does nothing else. It never creates a card on its own.
Card creation is governed separately by the provisioning rule, and it runs the same way for every connected system. That means you can connect BambooHR to a 900-person company, look at the full roster, and still have provisioned exactly zero cards until you choose a rule and confirm the preview. A phased rollout — Sales first, then Customer Success — is a normal configuration rather than a workaround.
What QRBold can and cannot see
The connection is read-only and scoped. QRBold requests the fields needed to build a business card and to know whether someone is currently employed. It does not request compensation, performance, time-off, or benefits data, and it has no write path back into BambooHR at all — nothing QRBold does can alter an employee record.
The credential is handled accordingly. BambooHR issues a refresh token per customer, which stays valid until revoked and therefore represents the whole grant. QRBold encrypts it at rest with AES-256-GCM, never returns it from any endpoint, and never writes it to a log. If the deployment has no encryption key configured, the connector reports itself unavailable rather than storing the token in the clear.
Revoking access is done from your side and takes effect immediately: remove the authorisation in BambooHR and the next scheduled read fails closed.