Studio
Defining capabilities, packaging them as solutions, publishing them and opening them in a tenant.
The studios are where things are built in inlorus. A capability is a unit that makes a business outcome possible; it is defined in the studio, versioned, published, and only then can it be opened in a tenant. A solution is a package of published capability versions.
This section has the guides to Capability Studio, the capability page, Solution Studio, Account Studio, Journey Designer and the Roles screen, as well as the Capabilities screen on the tenant side. A capability can be built on the platform or in an account: a capability the account publishes is visible only to that account's tenants.
To follow a capability end to end, first read the concept article “Capability, solution and activation”. Remember that publishing and opening are separate permissions: the builder publishes, the tenant administrator opens and installs.
Articles in Studio
- Screen guideCapability StudioThe list of capabilities the platform owns, and a form for opening a new capability draft. A capability's journey to the tenants starts here.
- Screen guideCapabilityThe page of a single platform capability: its canonical address in the header, the outcomes of the served version and the publish bar, and the Contents of its latest version — what the package carries, what each item pulls in, and the lock recorded at publish.
- Screen guideSolution StudioThe screen where you bring published capability versions together to create a solution on behalf of the platform. You also see listed solutions here.
- Screen guideAccount StudioThe screen where an Account defines and publishes its own capabilities. A capability published from here is visible only to that Account's tenants.
- Screen guideJourney DesignerThe screen where you set up and publish the start journeys that welcome new people, based on how the person arrived and which persona cell they fall into.
- Screen guideRolesThe screen where you create a role at the platform or at an account, and change which permission keys a platform role carries. Before you save a change to a role's keys, it shows who will gain and lose what.
- Screen guideCapabilitiesThe screen where you turn on and install the published capabilities your tenant can see. This is the last step on the way a capability defined and published in the studios reaches the tenant.
- How-toCreate and publish a capability on the platformIn Capability Studio you open a capability's first version as a draft, declare its dependencies and publish it; the capability lands on the tenants' Capabilities screen.
- How-toPut content into a capabilityA capability version is a package: on the capability page, its Contents section references what the package delivers — entities, EntityViews, applications, roles, configuration, an onboarding journey, help — and publishing locks all of it at its current revision.
- How-toDesign an application at the platformAn application a package delivers is more than its catalogue row: at the platform you give it a runtime — workspaces, navigation and a default workspace — and A_EntityViews, publish the runtime, and a capability version that carries the application carries all of it.
- How-toDesign a workflow at the platformA workflow at the platform runs on a platform entity in every tenant that reads it — until the tenant publishes its own — and a package carries it. You give it states, transitions with their permission, required fields, guards and effects, and publish it.
- How-toDefine an actionAn action is something the product does to a record — set fields, create a related record, start or move its workflow, record a notice — defined once, and run from a record or from a workflow effect through the same checked path.
- How-toAdd a validation rule or computed fieldA validation rule is a condition every record of an entity must meet, checked by every record write; a computed field is a field whose value is calculated. Both are designed on the entity's page in the Metadata Designer and belong to whoever owns the entity.
- How-toPublish reference data from the platformReference data is the lists others point at — countries, industries, course levels. It is published once, at the platform, on a reference entity's page in the Metadata Designer; every tenant reads it, and no tenant can change it.
- How-toAdd sample data to a packageSample data is a small, realistic set of records — a few programmes, sessions, clients and engagements, linked — that a tenant gets when it installs the package. It is stored with the capability version, never in a tenant, and checked against the model before it is locked.
- How-toPublish a capability to your account's tenantsIn Account Studio you open a capability draft, declare the version's dependencies and publish the draft; the capability is visible only to the account's tenants.
- How-toRequest and install a capability in a tenantOn the Capabilities screen you request a capability published by the platform or your account with Request install, and install it with Install.
- How-toSee the impact before changing a role's keysOn the Roles screen you edit a role's keys, see who will be affected with “What will change?”, and only then apply.