Sharing with partner organisations

Let another organisation on Faldaro see and use your form, without merging accounts and without either side seeing the other's submissions. Sharing is deliberately narrow: you share a definition, never data.

Two grains

Share a folder when a partner should work with everything in it, or a single form when a folder holds ten forms and only one is theirs. Both are found on the thing being shared — a folder's under its list of forms, a form's under its list of submissions, each as a Partner organizations row that says whom it is shared with — and both target a partner by their organisation's short name.

Where both apply, the stronger level wins. Folder sharing needs folder:share; form sharing needs form:share.

Access levels

There is no “manage” level. Cross-organisation editing is blocked in the database itself, so a level that promised it would be a promise the platform could not keep — it is refused when you try to grant it rather than accepted and quietly ignored.

What the partner sees

A recipient sees the folder shell and exactly the form shared with them — never its siblings. They can read the definition, because they must in order to render it, and that is the limit:

• They cannot edit it. Only the owner writes the definition.
• They cannot share it onward, or create public links for it.
• They never see your submissions, and you never see theirs.

Submissions stay with whoever made them

This is the asymmetry worth understanding before you share anything: definitions cross organisations, submitted data does not. A partner filing against your form owns those records; they are stored in their organisation, count against their allowances, and are invisible to you.

Two consequences follow. Their submissions trigger their integrations, resolved in their organisation — a form you shared fires their CRM, and your hook URL is never reachable from it. But payments resolve the other way, in the organisation that owns the form: you authored the price, so you are paid. Each rule follows from whose thing it actually is.

Digital delivery also works across a share, and a claim already issued survives the share being withdrawn.

Withdrawing a share

Remove the share and the partner immediately loses sight of the form. Submissions they already made remain entirely theirs — withdrawing your form does not reach into another organisation's records.

Not the same as child organisations

Sharing connects two independent organisations. If instead you run several entities that you administer — branches, subsidiaries, chapters — use child organisations, where a role on the parent grants its privileges throughout the subtree. See administration.