Authenticated access
The application requires a signed-in account before a recruiter can view their workspace or analyses.
FORMA / SECURITYClear boundaries.
Clear boundaries.
Evidence stays in scope.
Recruiting documents deserve deliberate access boundaries. Forma. separates file storage, application records, and AI retrieval by user and analysis.
Understand the method01 / ACCESS MODEL
A boundary at every layer.
These controls describe the product's current implementation, from upload to answer.
Scoped file transfer
The server generates short-lived upload URLs and user/analysis-specific object keys for direct uploads to R2.
Row-level boundaries
Supabase row-level security and user-scoped queries restrict access to analysis and document records.
Analysis-scoped retrieval
Ask Forma. checks analysis ownership before retrieving document evidence for an answer.
02 / DOCUMENT PATH
Your source files follow a defined path.
The browser sends files directly to private object storage using server-issued upload URLs. The app stores processing state and indexed evidence separately.
01 / BROWSERChoose documentsPDF · DOCX · XML · TXT
02 / APIRequest upload URLsauthenticated, short-lived
03 / R2Store source filesuser + analysis object path
04 / DATAProcess and indexuser-owned analysis records
SECURITY / PRODUCT PRINCIPLE
Security begins with scope.
Source files, application records, and retrieved evidence each stay tied to the authenticated account and the active analysis. The controls above describe the boundaries built into Forma. today.
Start with a controlled analysis.
Create a role-specific workspace, upload the documents you choose, and inspect the evidence behind each result.
Start analysis