---
title: "network.layout.changed@1 · OpenVibe.Services"
canonical: "https://openvibe.services/docs/contracts/network.layout.changed"
updated: null
---

# network.layout.changed@1 · OpenVibe.Services

HTML: [network.layout.changed@1 · OpenVibe.Services](https://openvibe.services/docs/contracts/network.layout.changed)

# NetworkLayoutChangedPayload `network.layout.changed@1`

Generated at 2026-11-13 06:25:48 UTC from [`openvibe-contracts v0.419.0`](https://github.com/OpenVibers/OpenVibe.Contracts/tree/v0.419.0) and [`openvibe-sdk v0.161.0`](https://github.com/OpenVibers/OpenVibe.SDK/tree/v0.161.0).

- Version: 1.0.0
- Owner: network
- Visibility: first-party
- Status: active
- Compatibility: backward
- Schema: [`https://openvibe.network/contracts/events/payloads/network.layout.changed.v1.json`](/docs/contracts/network.layout.changed.json)

network.layout.changed v1 (OpenVibe.Network server/layouts, written into network\_event\_outbox in the transaction that changes a stored layout). One event per change to one person's ui.layout@1: set active, saved, renamed, deleted, shared, unshared, published to the gallery, unpublished, copied from the gallery, or reset to the default. Envelope: subject { type: user, id } and the layout's revision, actor the person, visibility internal. The payload carries no account data and no layout contents, so an open page can announce a change and refetch with the person's own token.

## Fields

| Field | Type | Required | Description | Constraints |
| --- | --- | --- | --- | --- |
| `surface` | string | yes |  | - `pattern ^[a-z][a-z0-9_]*(\.[a-z0-9_]+)+$`<br>- `maxLength 80` |
| `device` | enum | yes |  | - `one of "phone", "tablet", "computer"` |
| `layout_id` | string | yes |  | - `pattern ^lay_[0-9A-HJKMNP-TV-Z]{26}$` |
| `change` | enum | yes |  | - `one of "active", "saved", "renamed", "deleted", "shared", "unshared", "published", "unpublished", "copied", "reset"` |
| `revision` | integer | yes |  | - `minimum 1` |
| `sharing` | enum |  |  | - `one of "private", "link", "gallery"` |

## Examples

From the contract's own test fixtures: valid ones validate, rejected ones must fail.

 Valid: activated

~~~~
{
  "surface": "bot.controls",
  "device": "phone",
  "layout_id": "lay_01JAB2C3D4E5F6G7H8J9K0MNPQ",
  "change": "active",
  "revision": 3,
  "sharing": "private"
}
~~~~

Valid: published

~~~~
{
  "surface": "bot.controls",
  "device": "computer",
  "layout_id": "lay_01JAB2C3D4E5F6G7H8J9K0MNPR",
  "change": "published",
  "revision": 7,
  "sharing": "gallery"
}
~~~~

Rejected: unknown-change

~~~~
{
  "surface": "bot.controls",
  "device": "phone",
  "layout_id": "lay_01JAB2C3D4E5F6G7H8J9K0MNPQ",
  "change": "applied",
  "revision": 3
}
~~~~

## Validate

~~~~
const contracts = require('openvibe-contracts');
contracts.validate('network.layout.changed@1', value);   // { valid, errors: [{ path, message }] }
~~~~