At a larger company, giving people the right access is only half the job. The other half is showing it to an auditor, a security team, or a regional lead, with names and dates attached. Business adds the controls that make that part routine.
Included in Business
Business includes everything in Growth, plus:
- Multiple workspaces
- Advanced roles
- The audit log
- Priority support
- Guided onboarding
Pricing is custom. It depends on your size and requirements, so it is set with the sales team rather than listed.
Workspaces by region
Some organizations are really several: a subsidiary with its own admins, a region with its own hiring, a business unit with its own way of working. Multiple workspaces let each one run separately, with its own directory, role templates, grants, and careers page.
The record model is the same in every workspace. A grant means one tool, a scope, who granted it, and the role or request behind it, whether the person sits in Berlin or Boston. That consistency is what lets governance hold across teams and regions without a separate process for each.
Roles with finer lines
The standard roles cover most teams. Admins run the workspace. Managers see their own team. Staff see their own tasks and access. Contractors get a narrower, scoped view. Larger organizations often need finer lines than four roles can draw, and Business adds advanced roles for those cases. The roles and permissions guide explains how the standard roles are scoped.
Contractors deserve their own note. Each contractor has a record like an employee, plus an end date on every grant. When the date passes, the grant closes. Extensions need an approval and set a new date.
Evidence on the record
The audit log brings together what Folkbase writes down as work happens. Every grant, change, and revocation is recorded in plain language. Lifecycle transitions (onboarding, activation, offboarding, exit) are logged with who ran them, when, and why. Each grant keeps who granted it, when, and when it closed.
Most audit questions map to something that already exists:
| Question | Where the answer lives |
|---|---|
| Who has access to GitHub today? | The directory, filtered by tool, with the active grants behind it |
| Was access removed on the last day? | The offboarding run, with each grant stamped at the time it closed |
| Who approved this extra access? | The grant, with who granted it and the request that justifies it |
| When was access last reviewed? | The dated access review and each keep or remove decision |
| Why does this contractor still have Jira? | The grant's end date and any approved extension |
The answer to an audit question should already be on the record, with a name and a time.
Folkbase does not replace an auditor or a compliance program. It keeps the access records those programs ask for, so an audit starts from an export instead of weeks of chasing managers. The audit trail page shows what each entry contains.
Rollout and support
Setup for one team is a short session. Rolling out across several teams and regions takes more planning, and guided onboarding gives your admins help with it. A typical rollout covers:
- Deciding which workspaces you need and who administers each.
- Adding people and teams to each directory.
- Defining role templates for the roles you hire most.
- Installing the integrations each workspace uses.
- Running the first access review, so there is a baseline.
Priority support moves your questions ahead of the general queue once you are live. Nothing has to move at once. A single workspace or a single integration is a reasonable place to start.