[Yandex Cloud documentation](../../index.md) > [Yandex MetaData Hub](../index.md) > Schema Registry > Step-by-step guides > Namespace > Creating a namespace

# Creating a namespace



{% note info %}

This feature is at the [Preview](../../overview/concepts/launch-stages.md) stage.

{% endnote %}



{% list tabs group=instructions %}

- Management console {#console}

  1. In the [management console](https://console.yandex.cloud), select the [folder](../../resource-manager/concepts/resources-hierarchy.md#folder) you want to create a connection in.
  1. [Navigate](../../console/operations/select-service.md#select-service) to **Yandex MetaData Hub**.
  1. In the left-hand panel, select ![image](../../_assets/console-icons/layout-cells.svg) **Schema Registry**.
  1. Click **Create a namespace**.
  1. In the **Name** field, set a unique name for the namespace.
  1. Optionally, add a namespace description.
  1. Under **Compatibility parameters**:
      1. Set **Compatibility check level**:
          * `BACKWARD`: (Default) Consumers using the new schema can read data written by producers using the latest registered schema.
          * `BACKWARD_TRANSITIVE`: Consumers using the new schema can read data written by producers using all previously registered schemas.
          * `FORWARD`: Consumers using the latest registered schema can read data written by producers using the new schema.
          * `FORWARD_TRANSITIVE`: Consumers using all previously registered schemas can read data written by producers using the new schema.
          * `FULL`: New schema is forward and backward compatible with the latest registered schema.
          * `FULL_TRANSITIVE`: New schema is forward and backward compatible with all previously registered schemas.
          * `NONE`: Schema compatibility checks are disabled.
            For more information about schema compatibility types, see [this Confluent guide](https://docs.confluent.io/platform/current/schema-registry/fundamentals/schema-evolution.html#compatibility-types).
      1. Select a [compatibility policy](../concepts/compatibility-check-policy.md) for JSON schemas:
          * `optional-friendly`: Based on a [solution](#optional-parameters-compatibility-solution) using various content models for the producer and the consumer. It supports adding or removing optional parameters while maintaining full transitive compatibility.
          * `Confluent`: Follows the [Confluent Schema Registry](https://docs.confluent.io/platform/current/schema-registry/fundamentals/schema-evolution.html#compatibility-types) standards and ensures no full compatibility when adding and removing optional parameters.
      1. Select a compatibility policy for Protobuf schemas:
          * `Confluent`: Based on the [Confluent Schema Registry](https://docs.confluent.io/platform/current/schema-registry/fundamentals/schema-evolution.html#compatibility-types) standards.
          * `buf`: Based on the Buf v1 standards.
  1. Click **Create**.

{% endlist %}