Tenants V2

The earlier platform screen for maintaining tenants: a list of every tenant, a create form that records a tenant and provisions its database, and an edit form for its name, status, members and password policy, with the newer Platform SysAdmin covering the same ground. Nothing posts. Add Member adds the user to the tenant you are signed into, not the one you are editing, and Delete never succeeds, so add users to a specific tenant from Platform SysAdmin.

Overview

Tenants V2 is the earlier platform screen for maintaining tenants: a list of every tenant with its catalogue and member counts, a create form, and an edit form that changes the tenant’s name and status, adds members, and sets a per-tenant password policy. It is a ROOT-ADMIN applet that works on the shared platform database rather than on any one tenant. The newer Platform SysAdmin applet covers the same ground with more tabs and a different authorisation model; this applet is still registered and installable.

The application’s own title bar says Tenant Applet; the registry name, and the title of this page, is Tenants V2.

Where it fits

Direction	What	Why
Sibling	Platform SysAdmin — Tenant menu	The newer console for the same tenants. It is authorised by sysadmin rank; this applet is authorised by platform permissions assigned to your login.
Downstream	Tenant Admin Applet	Administers one tenant from inside it once the tenant exists.

Screens and menus

The menu has one working entry, Tenant Listing, plus the shared Settings and Personalization groups.

Screen	What it shows / does
Tenant Listing	Tenant Name, Tenant Code, No. of Catalogs, No. of Members, Status, Owner, Creation Date, Modified Date. The counts and the owner are looked up separately for each row, so a long list fills in gradually.
Create	Tenant Name, Tenant Code (both required), Status, Tenant Type, Subscription — only name, code and status are sent.
Edit → Details	Name, Code, No. of Catalogs, Members, Subscription, Status, audit columns; a red Delete button.
Edit → Applet Catalog	Search box and a Create button over the tenant’s catalogues.
Edit → Members	Search box and a Create button that opens Add Member.
Edit → RDS	Empty tab — the template has no content.
Edit → Password Policy	Policy Start Date, Policy End Date, Max Password Age, Min Password Length — all required.
Settings	Default Selection, Field Settings, Webhook, Feature Visibility, Permission Set / User / Team / Role Permission (shared components).

Configuration

Before you can use it

Platform permissions, not sysadmin rank. Unlike Platform SysAdmin, this applet checks the permissions assigned to your login: the listing needs MST_API_TNT_MGT_TENANT_READ and Create needs MST_API_TNT_MGT_TENANT_CREATE. A platform system administrator who holds neither is refused by this applet and accepted by Platform SysAdmin — the two authorisation models side by side.
The applet must be installed for your login through a catalogue.

Applet settings

None. Field Settings shows eight slide-toggles, but they are not connected to anything and there is no save — the same placeholder as in Platform SysAdmin. Nothing in this applet changes its behaviour based on a setting.

Settings in other applets that control this applet

None found.

Feature visibility / permissions

This applet defines no feature-visibility codes of its own. What varies by user is whether the platform accepts the call, per the permissions above.

Fields

Create

Field	Meaning	Required	Notes
Tenant Name	Display name	Yes	The screen lets you type letters, digits, space, hyphen and underscore, but only letters, digits and underscore are accepted on save — a name with a space or hyphen passes the screen and is rejected when you save.
Tenant Code	Database and login identifier	Yes	Same backend rule, and refused when a tenant with that code already exists. Lower-cased, it becomes the name of the new database and of its database user. Changing the code later on the Edit tab does not rename either — the database keeps the name it was given here.
Status	ACTIVE / INACTIVE	–	The form starts blank, and a blank status is saved as `ACTIVE`, so a tenant created without touching this box is live at once.
Tenant Type, Subscription	–	–	Shown on the form but not saved — only name, code and status are sent.

Edit → Details

Name, Code and Status are editable and saved; No. of Catalogs, Members, Subscription and the audit columns are display-only.

Edit → Password Policy

Field	Meaning	Required	Notes
Policy Start Date, Policy End Date	Validity window of the policy	Yes	Stored with the policy, but no sign-in check reads either date: the policy applies from the moment it is saved and keeps applying after the end date.
Max Password Age	How long a password lasts	Yes	Typed as a duration, such as `90 days`. This is the field that bites: a sign-in made for this tenant is refused once the user last changed their password longer ago than this — Duration of when password was last changed until now has exceeded configured expiry duration. A tenant with no policy saved is held to 720 hours (30 days).

Because all four are required, SAVE on the Details tab is disabled until a policy is filled in, even when you only wanted to rename the tenant.

Add Member

Field	Meaning	Required	Notes
Email	E-mail of an existing platform user	Yes	Verified in two steps: does the user exist on the platform at all, then does the user already have a profile in the tenant. Messages: “The user doesn’t exist in the root”, “User does’t exist in tenant”, “User email ‘…’ is valid”.
Rank	Rank in the tenant	Yes	Must be chosen, but it is never sent: the add call carries only the e-mail, and every new member joins as `MEMBER`, whatever you picked.

Lifecycle and effects

Action	What happens
Create	After the permission check, the platform records the new tenant, provisions its database, links you as OWNER, queues the default configuration for the new tenant, and writes an audit-trail entry — the only tenant-creation path that leaves one.
Edit → SAVE	Updates code, name and status only. In the same click the Password Policy is saved: updated if this tenant already has one, otherwise created.
Edit → Delete	Cannot succeed. The applet identifies the tenant one way and the platform expects it identified another, so the request always answers tenant code does not exist — and the applet does not surface that failure, so nothing visible happens.
Add Member	Adds the user to the tenant you are signed into, not the tenant you are editing. The call is authorised by your being an owner or admin of that signed-in tenant.

No stock or journal effect; nothing is posted.

Related applets

Platform SysAdmin — the newer console; use it to add a user to a specific tenant, which works there.
Tenant Admin Applet — a tenant’s own administration once it exists.
Developer SysAdmin Applet — the applet registry that the Applet Catalog tab draws from.

Troubleshooting

Symptom	Cause	Fix
Create fails after several minutes, and the tenant then appears in the list as ACTIVE	The tenant record is written first; the database provisioning that follows failed, and nothing removes the record.	Do not retry — each retry leaves another tenant record. Report it to platform engineering.
“Only alphanumerics and underscore allowed in tenant code/name !”	The screen lets you type characters the platform rejects on save, and the rule applies to the name as well as the code.	Remove spaces and hyphens from both.
“Users’ email is not verified !”	Your own e-mail address must be confirmed before you can create a tenant.	Confirm your e-mail first.
The listing is empty or not authorised although you are a platform system administrator	This applet needs the `MST_API_TNT_MGT_TENANT_READ` permission on your login, which sysadmin rank does not grant.	Have the permissions assigned, or use Platform SysAdmin.
A member added here appears in the wrong tenant	The add-member call is scoped by the operator’s session tenant, not the edited tenant.	Add users to a tenant from Platform SysAdmin → Tenant → Users → Add.
Delete does nothing visible	The applet and the platform disagree on how the tenant is identified (see Lifecycle).	Tenant delete does not work in either platform applet.
SAVE stays disabled on the Details tab	The four Password Policy fields are required for the whole form.	Fill in the policy tab first.