Skip to content

Access

Who sees what, down to the field

Most tools stop at "can this person open the record". Formif goes further, because in this work a record often holds one client’s prices and another client’s address, and the wrong person reading the wrong row is a real problem.

The Formif company screen, listing branches with their logos
Branches, each with its own people and its own visibility.
Structure

Branches, teams, roles

A workspace holds companies — your head office and its branches. People belong to teams, teams carry roles, and a role is a set of permissions you assemble rather than one of three fixed tiers. Visibility rules then decide which branch can see which.

Field level

Two people, one form, different forms

Every field carries its own view and edit matrix. The same template can show a subcontractor the address and the photos while keeping the cost, the client and the margin to your own team — without maintaining two templates.

Hide a single dropdown option from a team without hiding the field
Read-only for one role, editable for another, invisible to a third
API and webhooks

Let another system in, narrowly

Storage, mail and spreadsheets connect through named integrations you switch on per workspace. For everything else there are API keys, and a key carries only the scopes you gave it — new endpoints stay unreachable until they are explicitly allowed, so growing the API never silently widens a key you issued last year. Webhooks are signed, and every delivery is logged.

The Formif integrations screen, listing connectable services
Connectors are switched on per workspace; keys and webhooks sit beside them.

Build your first form today

Start on the free plan and grow the plan as the team grows. No setup fee, no mandatory consultant.

No credit card required