BambooHR
What Paperbeam reads from BambooHR, the read-only access it asks for and why, filters, and the beats it feeds.
People
Read-only API key
New hires and work anniversaries, with titles and teams.
What we read
- Hires, work anniversaries and promotions
Only the reporting window of each edition is read. Paperbeam stores derived facts and short excerpts, not copies of your BambooHR data, and keeps raw evidence only for your retention period.
Access we ask for, and why
| Scope | Why |
|---|---|
API key (read: employees) | Read names, titles, departments and hire dates. Never compensation. |
All access is read-only. You can revoke it from BambooHR at any time, or disconnect the source in Paperbeam.
Connect BambooHR
- Go to Sources and choose BambooHR.
- Create a api key. BambooHR → your avatar → API keys → Add new key. Open BambooHR settings.
- Fill in Subdomain and API key, then click Test connection. Paperbeam makes one read-only call and shows the account it reached, or exactly what went wrong.
- Click Connect. The credential is encrypted before it is stored and never shown again. Use Sync now on the source’s page to see what it collects from the last 24 hours, and set filters there.
You need the admin or owner role in Paperbeam, and enough permission in BambooHR to grant read access to the data listed above.
Filters
Set on the source’s page at Sources›BambooHR. Filtered-out data is never collected.
| Filter | Effect |
|---|---|
| Work anniversaries | Celebrate whole-year anniversaries as well as new hires. |
| Departments | Only people in these departments. Leave empty for everyone. |
To keep specific people, channels or topics out of the paper across all sources, use exclusion rules and the never-mention list in House style.
Beats
BambooHR is a source for:
Stories land in whichever of your sections fits them best.