livekit/livekit · error

update own metadata not allowed

Error message

update own metadata not allowed

What it means

Sentinel error returned when a participant attempts to update their own metadata without the updateOwnMetadata permission grant. The caller rejects the change with a RequestResponse of NOT_ALLOWED and the message 'does not have permission to update own metadata'.

Source

Thrown at pkg/rtc/signalling/errors.go:26

//
// Unless required by applicable law or agreed to in writing, software
// distributed under the License is distributed on an "AS IS" BASIS,
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
// See the License for the specific language governing permissions and
// limitations under the License.

package signalling

import (
	"errors"
)

var (
	ErrInvalidMessageType          = errors.New("invalid message type")
	ErrNameExceedsLimits           = errors.New("name length exceeds limits")
	ErrMetadataExceedsLimits       = errors.New("metadata size exceeds limits")
	ErrAttributesExceedsLimits     = errors.New("attributes size exceeds limits")
	ErrUpdateOwnMetadataNotAllowed = errors.New("update own metadata not allowed")
)

View on GitHub (pinned to ee45c3f0b1)

Solutions

1. Grant the canUpdateOwnMetadata permission in the participant's access token
2. Have a privileged actor (server-side API or admin) perform the metadata update instead
3. Check the permission grant before attempting self-metadata updates

When it happens

Trigger: Thrown at pkg/rtc/signalling/errors.go:26 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of livekit/livekit@ee45c3f0b1 (2026-09-02). Data as JSON: /api/errors/1266e8c31bf7daa2. Report an issue: GitHub.