Folkbase connects to eight tools. An admin installs each integration once for the workspace, and from then on a person's access to that tool is a grant on their record. When that grant is revoked in Folkbase, the account in the tool closes with it.
The catalog
These are the tools Folkbase supports today:
- Slack and Microsoft Teams for messaging.
- Google Workspace for email, calendar, and documents.
- Notion for shared docs and wikis.
- GitHub and Jira for engineering and project work.
- Okta for identity.
- BambooHR for HR records.
Each integration stands on its own. A team can start with the directory and one tool, then add the others as they come up. Integrations are included in the Growth and Business plans.
Installing for the workspace
Integrations are installed at the workspace level, and installing one is an admin action. Admins already run the workspace's members, access, and settings, so the person who connects a tool is also the person accountable for who can open it.
Once a tool is installed, Folkbase can grant it. An admin can add it to a role template, so everyone in that role is meant to have it with the same scope. People whose role does not include it can request access, and a manager or admin approves the request. Either way, the result is the same kind of entry on the person's record.
Access lives on the record
After installation, a person's access to the tool is a grant, not a row in a spreadsheet or a line in a ticket. Each grant records:
- The tool.
- The scope of access.
- Who granted it.
- The role or request that justifies it.
- Its state: pending, active, suspended, or revoked.
Because every grant names the role or request behind it, the question of why someone has GitHub has an answer on their record, readable without asking IT. The full model is described on the grants page.
Grants follow the record through the lifecycle. Starting onboarding queues the role's grants as pending, and activating the person opens them, so accounts are ready on the start date. When someone is promoted or transfers, their access changes in the same motion as their role. For example, if Maya Okonkwo moves from Product Designer to Design Lead, the change shows up as grants on record FB-2481 rather than as a request someone has to remember.
Revoking closes the account
Revoke a grant in Folkbase and the account closes in the tool.
That is the point of installing an integration. Without one, removing access means a list of tools and a person working through them one login at a time. With one, the decision is made once, in Folkbase, and nobody has to sign in to the tool to finish the job.
This matters most on a last day. Offboarding closes every grant in one run, each stamped with the time it closed, and the record is archived with its history intact. Contractor grants carry an end date, and when that date passes, the grant closes. The offboarding page covers the full exit.
Each grant keeps who granted it, when, and when it closed. Whether a person could open a given tool on a given day becomes a lookup on their record, not an investigation across admin consoles.