This page covers the security controls you configure and can see inside Folkbase: who can see what, why each piece of access exists, and how it ends. It does not describe hosting or infrastructure. For those questions, and for security questionnaires, write to the team directly.
Scope by workspace and role
Each workspace is its own boundary. Records, grants, tasks, and settings belong to one workspace and do not appear in another. Companies on Business can run multiple workspaces and keep each one separate.
Inside a workspace, least privilege starts with the four workspace roles. Admins manage the workspace. Managers see their own team. Staff see their own tasks and access. Contractors get a narrower, scoped view. The details are in roles and permissions.
Role templates apply the same idea to the tools a person can open. A template lists the grants a job needs, so a new hire starts with that set and nothing more. Anything outside it becomes a request that a manager or admin has to approve.
Grants that carry a reason
A grant is one person's access to one tool. Each grant stores:
- The tool and the scope of access
- Who granted it, and when
- The role template or approved request that justifies it
- Its current state: pending, active, suspended, or revoked
Access is easiest to defend when every grant carries its own reason.
The justification is part of the grant, not a note kept somewhere else. When someone asks why a person can open GitHub, the answer is on the record: the template that included it, or the request someone approved.
Access that ends on time
Offboarding starts with a last day. When that day comes, every open grant closes in a single action, and each grant keeps the time it closed. With an integration connected, revoking a grant in Folkbase closes the account in the tool itself. The record is then archived with its history intact, so it still answers questions after the person has left. Offboarding walks through a full exit run.
Contractor access follows the same rule, with the date set up front. Every contractor grant carries an end date. When the date passes, the grant closes. Extending it takes an approval and sets a new date, so no contractor grant is open-ended.
Every change on record
Lifecycle transitions are logged as they happen. Onboarding, activation, offboarding, and exit each record who ran the step, when, and why. Grants keep their own history: who granted them, when they opened, and when they closed.
Access reviews add a periodic check on top of that. A review snapshots every active grant into a dated list. Reviewers keep or remove each one, and every decision is recorded on the person's record. The question of who has access to what then has an answer with a timestamp, and the audit trail reads in plain language rather than raw events.
Access reviews and offboarding come with Growth, and Business adds the audit log.
Security questionnaires
If your security or procurement team sends a questionnaire, email support@folkbase.app with the document and your deadline. We answer for the product as it works today, and we say plainly when something is not available. For any control described on this page, we can point to where it lives in the product and what it records.