Capability Studio
The list of capabilities the platform owns, and a form for opening a new capability draft. A capability's journey to the tenants starts here.
What's on this screen
- Defined capabilities, on the left: every capability the platform owns, with its key, name and latest version. Choose one to open it on the right: its canonical address (
inlorus://capability/platform/<key>), a link to the capability page, and each version with its status; the address keeps the choice (?open=). - A draft version has a Publish button next to it, and a version that hasn't declared its dependencies yet has a Declare no dependencies button. Declared ones show "dependencies declared".
- New capability draft, on the right when no capability is chosen: the form that creates a new capability and its first version as a draft.
What a version carries — its entities, EntityViews, applications, roles, configuration, onboarding journey and help — is set on the capability page, in its Contents section. Publishing a version from this list checks and locks those contents the same way.
Creating a new draft
- Enter a Key. It must be unique within the platform; the canonical address is derived from this key and can't be changed later.
- Fill in Name, Category (foundation, business, governance, integration, analytics, experience, operational), Business purpose and Version purpose. Description is optional.
- Press Create draft. If it succeeds, the resulting canonical address is shown and the capability is added to the list. Clear only empties the form.
Then press Declare no dependencies and Publish next to the new version in the list. The published version can be selected in Solution Studio and appears on the tenants' Capabilities screen.
If the save is rejected, the error code and reason appear above the form. The most common reason is DUPLICATE_CANONICAL_ADDRESS: a capability with the same key already exists.
Who can do what
| Task | Permission key needed (in the platform scope) |
|---|---|
| See the list | capability.read |
| Create a draft, declare dependencies | capability.write |
| Publish the draft | capability.publish |
Tip If you can see the list but not the form, only capability.write is missing; the screen says so in place of the form. The platform administrator grants the key. Permission is checked again the moment you press the button; you can't save with a permission that was taken away after the page opened.
Keep in mind A draft version isn't served anywhere: it can't be selected in Solution Studio and doesn't appear on the tenants' Capabilities screen. A version whose dependencies haven't been declared can be published but can't be installed in a tenant; the install stops with NO_DEPENDENCY_SET. This screen only allows declaring "no dependencies"; there is no field for entering a real dependency.