Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

multitenancy: let the selected tenant's Owner manage its tenant-scoped settings (document numbering, tenant configuration, print templates)

Open
#7,877 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@ThuF is already working on this.

Since Oct 20, 2026.

  • #7973 by @ThuF — open

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
java

Research direction

Start with the role gates on DocumentNumberEndpoint, TenantConfigurationsEndpoint, and PrintEndpoint, then trace TenantConfigurationKeyPolicy and the application shell's Settings navigation. Check how the selected tenant is enforced in the existing endpoint and UI tests. Done means Owners can manage these settings for their selected tenant, instance-wide keys remain staff-only, and tests confirm cross-tenant writes and User access return 403.

Written by the indexing model from the issue text.

Description

enhancement

Problem

Under TOKEN_GROUPS, a tenant's own administrator is its Owner. Platform staff hold ADMINISTRATOR / OPERATOR. Several per-tenant settings are reachable only by staff:

Surface Gate
Document numbering (DocumentNumberEndpoint, /services/core/numbering) @RolesAllowed({"ADMINISTRATOR","OPERATOR"}) on the class
Tenant configuration (TenantConfigurationsEndpoint: languages, country, APP_BASE_URL, print-template choice) @RolesAllowed({"ADMINISTRATOR","OPERATOR"}) on the class
Print templates: read, edit, duplicate, delete (PrintEndpoint, /{entity}/templates/**) ADMINISTRATOR, OPERATOR

A concrete legal case: a Bulgarian tenant must clear or set to numeric the prefix of its sales-invoice series before its first invoice, because the VAT Act art. 114 requires a 10-digit Arabic-numeral number. Its Owner cannot open Document Numbering, so a member of staff has to do it for each customer.

Proposal

  • Let the selected tenant's Owner (ApplicationRoles.OWNER) read and write these tenant-scoped settings, in addition to ADMINISTRATOR/OPERATOR. The writes stay limited to the current tenant; everything here is already tenant-scoped.
  • Keep instance-wide keys (outside TenantConfigurationKeyPolicy's allow-list) staff-only.
  • Show these screens in the application shell's Settings for an Owner, next to Settings → Users.
  • ITs: an Owner of tenant A can change A's numbering, configuration and templates; an Owner of A gets 403 on B's; a User gets 403.
Dominant language
Java
Stars
278
Forks
97
Avg merge
18h 53m
Merged PRs (30d)
228

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from eclipse-dirigible/dirigible

All issues in eclipse-dirigible/dirigible

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.