Organisations

Nothing to switch on

A project with no organisations behaves exactly as it did before, and rows written before you created the first one stay shared across the project.

Two kinds of people

An organisation has members, who run it, and users of its own. A member is someone signed in to your project who holds a membership in the organisation, with a role you defined. One login can hold memberships in several organisations and move between them. An organisation's own users belong to that one organisation, and the same email address can exist separately in two of them.

Your team keeps the Fóir console. An organisation's members sign in to your application.

Limits per organisation

You can cap records, media storage, active users and emails per month for an organisation, and a cap covers everything nested beneath it. Sender name and reply-to address can be set per organisation, and apps are installed per organisation with their own credentials.

Self-service sign-up

If you switch it on, a signed-in user can found their own organisation and becomes its first member with the role you chose. The mutation that does it appears in your API only while the setting is on.

Three shapes

One project with organisations suits a product whose tenants share a schema. A project for each client suits clients who share nothing. A plain project needs neither, and the first two combine.