Builder

You define capabilities, package them as solutions and publish them — on the platform, or in your own account for the account's tenants.

The builder builds: defines capabilities, versions them, publishes them and packages them as solutions. You can work on the platform or inside an account; a capability you publish in an account is visible only to that account's tenants.

The builder archetype carries only what is needed to build and stops there: read, write and publish for capability, solution, application and metadata, and read and write for workspace. Member management, writing configuration or deleting (purge) are not yours. Opening and installing a capability in a tenant is the tenant administrator's job too.

Publishing and being installable are not the same thing. A version whose dependencies have not been declared can be published but cannot be installed in a tenant; before you publish, declare what the version needs (or, if it needs nothing, declare that).

Start here

  1. Read a capability's path end to end: draft, publish, solution and being opened in a tenant.
  2. In Capability Studio, create a new capability draft with its key, name and business purpose.
  3. In Account Studio, declare a version's dependencies and publish the draft to the account's tenants.
  4. In Solution Studio, bring published capability versions together in a solution.
  5. On the Change impact screen, see what a version change would touch in a tenant.

Getting started

Concepts

My account and security

Studio

Applications and data

Platform governance

Account governance

Tenant design

Audit

When things go wrong

Troubleshooting

Reference