Description

Currently a user cannot be a member of multiple organisations, nor is there really a concept of grouping them and allowing to work on a common content.

Describe the solution you'd like

1. Organisation management:

• Creating a new organisation: Allow users to sign up and create a new organisation instance with a unique organisation ID.
• Editing organisation information: Enable users to modify their organisation information such as name, description, or custom branding.

2. User management within an organisation:

• Inviting users: Allow the organisation admin to invite other users via email to join the organisation. Users should be able to accept or decline invitations
• User roles and permissions: Provide different levels of access and control within a organisation based on user roles.
• Removing users: Enable the organisation admin to remove users from the organisation.

3. Billing management:

• Assigning billing information to an organisation: Handle billing information per organisation.
• Subscription management: Allow the organisation admin to subscribe, upgrade, or downgrade their plan.
• Invoice generation and payment history: Generate invoices for each billing cycle and allow users to view their past payments.

4. organisation-specific configurations:

• Customizable settings: Allow organisation to set their settings like: preferred language, timezone, or other locale-specific settings.
• Feature toggling: Allow the organisation admin to enable or disable certain features based on their plan or needs.

5. Data isolation and security:

• Data separation: Ensure that each organisation's data is isolated from others
• Security measures: Implement necessary security controls to protect the organisation's data, such as access control policies.

Additional context

Refer to discussion #334 for a complete list of requirements.

Validations

• Follow our Code of Conduct.
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Subtasks

• Multi-tenancy / Allow user to create a new tenant on demand  #460
• Multi-tenancy / Allow user to switch tenant from menu in the header #461
• Multi-tenancy / Create a personal tenant for every new user #462
• Multi-tenancy / Allow user to edit organisation information #463
• Multi-tenancy / Allow tenant owners to invite new members #464
• Multi-tenancy / Allow users to accept tenant membership invitation #465
• Multi-tenancy / Provide different levels of access and control within a tenant based on user roles. #466
• Multi-tenancy / Enable the tenant admin to remove users from the tenant #467
• Multi-tenancy / Allow the tenant owner to subscribe, upgrade, or downgrade their subscription plan. #468
• Multi-tenancy / Allow tenant owners to edit billing information #469
• Multi-tenancy / Generate invoices for each billing cycle and allow users to view their past payments. #470
• Multi-tenancy / Add "introduction/features" documentation page for whole multi-tenancy feature #471
• Multi-tenancy / Modify CRUD module so that items created are bound to creator's tenant and cannot be seen by other tenants #527
• Multi-tenancy / Check and modify if needed notifications so they are dispatched only to tenant members #528
• Multi-tenancy / Add missing tenant notifications and check if all existing notifications require to modify #529
• Multi-tenancy / Add tenant removal form #540