[ADR] Organisations and Tenants

[piotrczyz]

Context

The driving factor was a need to centralize the BUK Clubs and move them from one of our apps to be available across all BCC services.

We've been talking about this concept for a long time, and we wanted to introduce it so that we can collectively understand what each term means.

Decision

Members have already implemented different types of organizations and we think it is a good idea to expand the org service and use it as a source.

Originally, we thought to use tenants that will bind data to organisation but after the investigation we decided to skip the tenant part as in most of the cases it would be 1-1 mapped to an organisation.

We distinguished two hierarchies:

1. Organisation hierarchy - Organisation
2. Geographic hierarchy - District

The Organisations will be used for memberships and data ownership while the Districts will be used for filtering.

Consequences

For some of our applications we will need to still use the tenant concept until we switched to the new concept.

Alternatives

Another alternative was to use tenants as a data scoped access. In BCC cases, we didn't see much benefit of using that and the term itself caused many confusions as we had different definition and understanding what "a tenant" means.

[github-actions]

Remember that ADRs are publicly available hence do not include any confidential information in the issue description!
To read more about ADR please refer to documentation.