Frequently asked questions

No, and it would be a bad idea. You start from one clear need — collecting requests, tracking files — then switch on a module when it answers a real problem. Modules you have not enabled do not clutter your workspace.

Separate tools each keep their own copy of the data, and you are the link — through exports, copy-paste or a connector to maintain. Here the modules read the same base: a form response becomes a task then an invoice line with no re-keying.

Not for everyday use: forms, tasks, documents and automations are configured in the interface. An API and webhooks exist for teams that want to go further, but they remain optional.

A first published form with usable responses fits in one working session. The rest comes gradually: you add an automation when a step starts repeating, not before.

The free plan works without a card and without a time limit. It lets you actually collect data rather than watch a demo — the best way to find out whether the tool fits how you work.

The one matching what costs you time today. In most cases that is Forms, because collection sits upstream of nearly everything else — but if your problem is tracking files, start there.

Yes, with per-person permissions. Partitioned spaces — groups, client portal, shared access — let you open part of the account to a colleague, a client or a contractor without giving them the rest.

In Europe, within the European Union, in line with GDPR. This is worth checking before choosing a tool rather than after: changing hosting midstream costs far more than it appears.

It stays yours and can be exported. The GDPR module also extracts what the account holds about a given person, which serves both to answer an access request and to prepare a departure.

It provides tools — consent capture and history, exporting one person's data, an activity log, encryption of sensitive fields. It makes nobody compliant on its own: compliance also depends on what you collect and how you work.

Yes, through fine-grained permissions and organisation-wide policies: mandatory two-factor authentication, IP restrictions, session duration, export control. That last point is often the forgotten link.

Yes, and it matters for field work: forms filled on site, photos attached to a job, the client signing on the technician's device. Recording on the spot always beats writing it up in the evening.

Yes, through the API, webhooks and HTTP automations, in both directions: your system can query the platform, and the platform can notify your system when an event occurs.

No. AI modules are enabled if you want them, with tokens tracked separately so usage stays legible. Actions the agent proposes are shown before they run: nothing happens in your workspace without approval.