Tenant management, anyone working on the Tenant module?

[umerhassan-av]

I've been digging into multi-tenancy in citrineos-core. The data layer and WS routing are solid, but there's no way to create or manage a tenant without writing SQL by hand. I'd like to help close that gap and wanted to check direction first.

What I found:

• packages/core/src/modules/Tenant/ is scaffolded but empty.
• ITenantRepository only has createTenant() — no list/update/delete.
• Operator UI has no Tenants page; useTenantId() is single-value only.

Before I write anything: is that placeholder intentional, is anyone already on this?

[thanaParis]

GraphQL is what we use, generally done in the hasura console.

We don't put CRUD endpoints on citrine's REST API anymore, graphql is used for API access to data.

[umerhassan-av]

Yeah, GraphQL-only is fine, that doesn't really change. I understand that

My actual goal is the UI. Right now managing tenants is all manual hasura console or custom REST API, and there's no way for an admin to see tenants or link charging stations to them from the Operator UI.

I'd like to add a Tenants section that works the same way Locations does today, and set a station's tenant from the station form instead of hasura console.

If this isn't a priority for you that's completely fine, but I'm happy to do it.

[thanaParis]

it isn't a priority for us but I'd be down to merge such a feature, as long as it's properly configurable
most operator-ui sessions are single-tenant scoped, not tenant-of-tenants, so an embedded tenants section would serve no purpose
however, it would be a good feature for tenant-of-tenants!