The shape of the setup
erp.io has exactly three things you have to create before anything else works: a user (you), an organisation (your company), and membership joining the two. Everything else — modules, permissions, billing, data — hangs off the organisation. If a screen anywhere in the suite refuses to load, the cause is almost always one of those three missing, and the troubleshooting page starts there for that reason.
Password, a magic link, or Google. Takes a minute. How
Name, timezone, currency, fiscal year. This is the tenancy boundary for everything you will ever put in. How
Email invitations with a role attached. People who accept become members and count as seats. How
Pick the applications you want in the rail. You can change this at any time. How
If you arrived from a campaign for one particular module — law.co, projectmanager.co, digitalmarketers.ai — the sign-up door at app.erp.io/sign-up/<module> creates the account and the organisation in one step and drops you straight into that module. You still get every live module on the menu; you just land where you registered.
What you get before you pay
A new organisation starts on a 30-day trial that grants every module. That is deliberate and slightly against our own interest: a trial that hides half the product is a trial of a different product, and the thing we are asking you to judge is whether the suite is worth having.
No card is taken to start. When the trial ends, the workspace does not silently degrade — it gates, visibly, on the home page, with the plan ladder in front of you. See Billing and plans for what the ladder costs and how seats are counted.
Which applications do you want?
Step 2 of 4 — you can change this later
Order matters in exactly one place
You can do most of this in any order, with one exception worth stating plainly: an account with no organisation cannot enter a module. The token that hands you from the shell into a module carries the organisation you are acting for, and a session with no current organisation is refused at the mint. This is the single most common cause of "I signed up and got thrown straight back out".
The normal sign-up flow cannot produce that state, because it creates the organisation for you. It shows up when an account is created by hand — an administrator adding someone by email, or a migration script — and the organisation membership is forgotten. See Organisations.
In this section
The four ways to sign in to app.erp.io — password, magic link, Google, and an invitation — and the one failure mode that looks like a bug and is not.
Your organisationAvailableThe organisation is the tenancy boundary for everything in erp.io. What to set when you create one, and what cannot be changed afterwards.
Invite your teamAvailableHow invitations work in erp.io, what a role grants, how seats are counted for billing, and why an invitation is the only supported way to add somebody.
Enable modulesAvailableTurning applications on for your organisation, narrowing them per person, and what the module rail shows when you do.
Your first weekAvailableA day-by-day plan for the first week in a new erp.io workspace: what to set up, what to leave alone, and what to check before you trust it.
What this does not do
SAML and OIDC against your own identity provider are on the Scale plan and are set up by us, not by you. Google sign-in is available to everyone.
You can belong to several organisations and switch between them, but the sign-up flow creates exactly one. Additional organisations are created from settings.
Bringing books, contacts or projects across is a migration, not a setting. See Migrate.
Questions
Can I try it without talking to anyone?
Yes. Sign-up is self-serve and no card is taken. Nothing in the trial requires a call.
What happens to my data if I stop after the trial?
The workspace gates rather than deletes. Contact [email protected] for an export while it is gated.
Can I change the organisation name later?
Yes, in Settings → Organisation. The name is display only — nothing keys off it.