Organisations

Every Receipt account belongs to an organisation — a shared workspace for a family, a small business, or an accounting team. All ledgers, members, and settings live inside the organisation.

Current shared clients support multi-organisation membership and organisation switching.

Member roles

Receipt uses role-based access control. Exact role names and permission bundles can vary by deployment policy and rollout stage, but commonly include:

Role type	Typical capability
Member / Viewer-level roles	Capture and view receipts within granted scope
Admin-level roles	Manage members, categories, and organisation settings
Owner	Full admin control, including billing and ownership actions

Each organisation has one Owner and one or more non-owner roles.

Inviting members

Current shared organisation APIs prove support for:

inviting a member by email,
updating member roles,
updating member permissions,
removing a member,
generating organisation invitation codes.

Use the members screen exposed by your current client to perform those actions.

Ledger-level access

Visibility and editing scope are governed by your organisation's configured permission model. In environments where per-ledger restriction is enabled, admins can limit visibility to selected members or role groups.

Removing a member

Use the members or organisation settings view exposed by your current client.

Removed members immediately lose access. Their historical entries remain in the organisation's ledgers.

Leaving an organisation

Current shared mobile and backend code also support leaving an organisation through the organisation settings flow, where allowed by the role and current ownership state.

Organisation settings

Admins and the Owner can configure:

Default currency — applied to new ledgers.
Category rules — merchant-to-category mappings shared across the org.
Audit and governance controls — visibility depends on deployment capabilities and plan permissions.