Extensions

Extension Studio belongs to your organisation. Owners can create private extensions and appoint member authors. No separate provider account or commercial tier is required. Marketplace shows versions that their providers have chosen to publish after independent review.

Studio records extension metadata and organisation approvals. It does not install code, connect an external service account or activate an extension on your Edges. The permission and runtime fields describe the provider’s requested behaviour; saving them is not evidence that the integration runs or has been verified.

Create a private version

Open Extension Studio in the intended organisation. Choose a new extension or an existing extension for another version. Import a JSON manifest or paste it into Manifest JSON, then choose Validate and save private version. The API validates the fields and stores an immutable version and its digest: SHA-256 over the manifest’s RFC 8785 canonical JSON, written sha256:<hex>. Corrections need a new version number. The version starts private.

The manifest contains its ID, name, numeric version, summary, kind, purposes, provider, maintainer, runtime binding, requested permissions, requirements and an optional HTTPS documentation URL. Do not include credentials, licensed content, private source records or personal information. URLs are stored, never fetched; package archives and executable files are not accepted.

An extension belongs to the organisation. Its version retains the original author when members join, leave or become owners. Owners appoint existing members under Extension authors; ordinary members can read their organisation’s metadata. Removing a member also removes their author grant.

Saved versions show their review or publication state separately from organisation approval. Runtime activation unavailable remains visible beside the page title. Expand a version to inspect its manifest, digest and recorded scope.

Record an organisation decision

Open a saved version and expand Organisation approval. Set the permitted Edges, operations and data scope, then choose Record approval. The recorded scope belongs to that exact version and carries its own digest in the same form, taken over the recorded edges, operations and data scope. A new version starts without approval; changing the scope appends another decision. Withdraw approval records a negative decision without deleting history.

These are decisions for your own organisation’s extensions. They do not change Edge configuration. Marketplace adoption of another provider’s version is not available in this release.

Offer a version publicly

Before choosing Submit version for review, confirm that the entire manifest may be made public and contains no credentials or private evidence. Submission shares the selected version with platform reviewers. Other private versions and your organisation’s approval settings remain private.

An independent staff reviewer records a version decision and the basis for public provider admission. Someone who belongs to, authored for or submitted for that provider organisation cannot perform its independent review. Once both gates are satisfied, the provider’s owner can publish the reviewed version to Marketplace. A submission or approved review alone does not publish it.

Withdrawing publication removes it from public discovery. A withdrawn review, suspended provider admission or closed organisation also makes it unavailable. Neither a marketplace review nor a public listing proves runtime compatibility.

Hand ownership to a partner

Prepare the partner’s private extensions in its own organisation using your own sign-in. Invite its representatives from Team when you are ready for feedback. Use member access and a separate author grant for collaborators who should edit. When a representative is ready to administer the organisation, make them an owner from Team. At least one owner must always remain.

Before removing the initial owner, inspect the removal impact shown by Team and replace any credentials or Edges that will be revoked. Removal ends their access; it preserves organisation-owned extension versions and their original authorship. The partner keeps a Common Measure collaborator only by keeping them as a member.