Domain separation and Stream Connect

  • Release version: Australia
  • Updated March 12, 2026
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Domain Separation and Stream Connect

    Domain separation in Stream Connect allows for the organization of data, processes, and administrative tasks into distinct domains. This feature enables control over user access to data, ensuring that only authorized users can view or interact with specific information. It supports logical separation for multiple service provider (SP) customers within a single instance.

    Show full answer Show less

    Key Features

    • Standard Support: Includes all aspects of Basic support, with application properties being domain-aware.
    • Message Replication: Records related to message replication are domain separated, including tables for message replication, channel replication, and Kafka topic replication.
    • Topic Namespaces: Allows configuration of domain access to Kafka topics, ensuring users only see topics linked to their assigned namespaces.
    • Producers and Consumers: Stream Connect producers can only send data to visible topics, while consumers operate within domain-specific runtime data tables.
    • Schema Management: Tables for schemas and schema registries are also domain separated, facilitating organized management of Stream Connect schemas.

    Key Outcomes

    By leveraging domain separation in Stream Connect, ServiceNow customers can effectively manage access control and data visibility across multiple domains. This ensures that data integrity is maintained, and users can work within their designated domains without interference from other tenants. Customers can expect streamlined operations tailored to their specific needs while utilizing Kafka streams and schemas efficiently within their domain structures.

    Domain separation is supported for Stream Connect. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.

    Support level: Standard

    • Includes all aspects of Basic level support.
    • Application properties are domain-aware as needed.
    • Business logic: The service provider (SP) creates or modifies processes per customer. The use cases reflect proper use of the application by multiple SP customers in a single instance.
    • The instance owner must configure the minimum viable product (MVP) business logic and data parameters per tenant as expected for the specific application.

    Sample use case: An admin must be able to make comments required when a record closes for one tenant, but not for another.

    For more information on support levels, see Application support for domain separation.

    Message replication

    Records in the following Stream Connect Message Replication tables are domain separated.
    • Message Replications [sys_sc_message_replication]
    • Channel Replications [sys_sc_channel_replication]
    • Message Replication Statistics [sys_sc_channel_replication_metric]
    • Kafka Topic Replications [sys_kafka_topic_replication]

    The domain for a message replication record is specified in the record's sys_domain field.

    For channel replication and replication metrics records, the domain is determined by the domain_master attribute. The domain_master attribute uses a reference field's domain to determine the domain for the current record. A channel replication record gets its domain from the referenced message replication record. A replication metrics record gets its domain from the referenced channel replication record.

    A Kafka topic replication record has the same domain as its associated channel replication record because the Channel Replications table is a parent of the Kafka Topic Replications table.

    Topic namespaces

    You can use topic namespaces to configure which domains can access a Kafka topic on a domain-separated instance. In ServiceNow, Kafka topics are linked to a namespace. Namespaces can be linked to ServiceNow domains. When a namespace is assigned to a specific domain, all the topics created with that namespace are also assigned to the namespace's domain. Users can only see and interact with the topics they have access to, based on domain visibility and access control lists (ACLs).

    For more information, see Managing namespaces and topics in Hermes.

    Producers and consumers

    Stream Connect producers and consumers are also domain separated. For producers, you can produce data only to topics that are visible to the domain.

    For consumers, all the tables used to keep runtime data are domain separated. These tables include the following.
    • Kafka Streams [sys_kafka_stream]
    • Kafka Subscriptions [sys_kafka_subscription]
    • Kafka Subscription Partition Groups [sys_kafka_partition_group]
    • Kafka Consumer Statistics [sys_kafka_consumer_statistics]
    • Kafka Unprocessed Messages [sys_kafka_unprocessed_messages]

    Domain users can create domain-specific Kafka streams with the topics that are visible to the domain. When activating a Kafka stream, the subscription and partition groups are created within the same domain. At runtime, the domain of the partition group is set by the consumer thread so that all the data is imported to the correct domain. For more information on producers, consumers, and Kafka streams, see Using Stream Connect for Apache Kafka.

    Schema management

    Tables for schemas and schema registries are domain separated. These include the following.
    • Stream Connect Schemas [stream_connect_schema]
    • Standalone Stream Connect Schema [standalone_stream_connect_schema]
    • Confluent Stream Connect Schema [confluent_stream_connect_schema]
    • Stream Connect Schema Registry [stream_connect_schema_registry]
    • Confluent Stream Connect Schema [confluent_stream_connect_schema]
    • Standalone Stream Connect Schema [standalone_stream_connect_schema]