Understanding plans and modules
Updated:
Plan decides what you may use; activation decides what you see.
Open Settings in FiattoIn this article
Under Settings → Subscription & licence (/dashboard/settings/abonnement) you see your plan, licence status and users, and manage payments via Stripe. Which modules are visible is set separately under Settings → Activate modules (/dashboard/settings/modules). Rule of thumb: the plan decides whether you may; activation decides whether you see it. Both pages are for admins.
Steps
- Open Settings → Subscription & licence. The License card shows plan, status, expiry date and number of users.
- Choose or change your plan under Subscription; payments run via Stripe. The tiers are Core, Pro and Complete — compare them beforehand on the public pricing page (
/prijzen). - Need more users than your plan includes? Add them one at a time under Extra users; no upgrade needed.
- Turn modules on or off under Settings → Activate modules, or all at once with Enable all in plan. Modules outside your plan show Not in your plan with an upgrade link.
- After a change: refresh the page — menu items appear or disappear accordingly.
Tips
- Documents read shows how many documents were read this month against what your plan includes. Above that you pay per document, afterwards on the next invoice — never a forced upgrade.
- Use of your modules shows, per module in your plan, when someone on your team last opened it, without names. That way you see which modules nobody uses.
- If you run several entities in one environment, Entities in this environment shows how many are active and which volume discount applies.
- On
/prijzen, the Calculator works out what a plan costs for your number of users and documents, and the Business case estimates what Fiatto returns per year. - Industry modules such as owners' associations, secondment, trip planning and readiness only switch on once you also enable the company setting under Settings → Data & compliance (Modules section).
- Module gating is a sales boundary, not a security boundary: sensitive actions stay behind roles, step-up and RLS. Turning a module off deletes nothing; data is kept.
- See also Settings hub.