Skip to content

Organisations (again) and various fixes - #2971

Merged
simonredfern merged 4 commits into
OpenBankProject:developfrom
simonredfern:develop
Nov 18, 2026
Merged

simonredfern merged 4 commits into
OpenBankProject:developfrom
simonredfern:develop

Conversation

@simonredfern

Copy link
Copy Markdown
Member

No description provided.

A fintech is usually a team, but a Consumer had one owner and a Dynamic
Entity record could only be shared with single Users. This adds
Organisations: groups of Users that can own Consumers and be given
access to records. They are separate from Customers and from Tenants.
Anyone logged in can create an Organisation under /my/organisations and
becomes its admin. Admins manage its members. An Organisation created
this way is always at SYS, so nobody can put one in a bank's space.
Staff with CanCreateOrganisationAtOneBank at a bank create Organisations
there and name their first admin. Staff read and suspend Organisations
with Roles held at the Organisation's bank_id.
A Consumer can belong to an Organisation. Its members then act for it,
and its creator no longer does on their own. The new /my/consumers
endpoints let owners read their Consumers, their usage, Scopes and API
Product Subscriptions without a Role. The API Product Subscription
endpoints use the same rule.
DELETE /banks/BANK_ID/entitlements/ENTITLEMENT_ID lets staff of one bank
remove a Role there with CanDeleteEntitlementAtOneBank.
A Dynamic Entity record with row-level access can now be shared with an
Organisation. Its members have access while they belong to it and it is
active. Row-level access can now be combined with community access, so
holders of the Get Role can read every record.
The test for duplicate error numbers now also checks messages written as
s"..." or in triple quotes. It used to skip 23 of them.
The Glossary, ResourceDocs and API_PRODUCT_SUBSCRIPTION_PLAN.md are
updated. New tests: OrganisationTest and DeleteEntitlementAtOneBankTest,
plus new scenarios in DynamicEntityRowLevelAccessTest and
DynamicEntityJoinQueryIntegrationTest.
Editing a chat message now checks that the message is in the room namein
the path. Before, a participant of one room could edit their own
messages in any other room by changing the room id. Editing a bank chat
message also checks that the room belongs to the bank in the path.
Either mismatch gets 404 and the message is left unchanged. This applies
to both PUT .../chat-rooms/CHAT_ROOM_ID/messages/CHAT_MESSAGE_ID
endpoints in v6.0.0.

v7.0.0 adds POST /my/accounts/account-routing-regex-query. It returns
only the caller's own accounts whose account routing matches the
pattern. A pattern that is not a valid regular expression gets 400
(OBP-30649) rather than a server error.

v7.0.0 no longer serves the v4.0.0 account routing regex query, and does
not list it in its ResourceDocs. It is still served at v4.0.0.
An endpoint listed in excludeEndpoints now gets 404 at v7.0.0, because
the bridge to v6.0.0 no longer passes such requests on.

UserReference now names the four user id columns added with
Organisations. This fixes UserReferenceAttributionPolicyTest, which
failed the develop build.

New tests: ChatMessageEditTest and MyAccountsByRoutingRegexTest.
@sonarqubecloud

Copy link
Copy Markdown

@simonredfern
simonredfern merged commit 6965530 into OpenBankProject:develop Nov 18, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant