# change originator

<figure><img src="https://111806075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mg4otljWU9FsHKYhTsW%2Fuploads%2FJpcf8SIkVqONHvX03Kst%2Fimage.png?alt=media&#x26;token=a319d619-f99c-49c5-8674-e6aaeddf2094" alt=""><figcaption></figcaption></figure>

All incoming Messages have originator field that identifies an entity that submits Message. It could be a Device, Asset, Customer, Tenant, etc.

This node is used in cases when a submitted message should be processed as a message from another entity. For example, Device submits telemetry and telemetry should be copied into higher level Asset or to a Customer. In this case, Administrator should add this node before [save Timeseries](https://docs.tesenso.com/tesenso-iot-cloud/rule-engine/rule-engine/action-rule-nodes/save-timeseries) node.

The originator can be changed to:

* Originator’s Customer
* Originator’s Tenant
* Related Entity that is identified by Relations Query

In ‘Relations query’ configuration Administrator can select required **Direction** and **relation depth level**. Also set of **Relation filters** can be configured with required Relation type and Entity Types.

![](https://111806075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mg4otljWU9FsHKYhTsW%2Fuploads%2FxCwegbXjALAjeT57sDuo%2Fimage.png?alt=media\&token=255651b7-4bfb-4f74-8b9e-014bb1acc9ff)

If multiple Related Entities are found, ***only the first Entity is used*** as new originator, other entities are discarded.

**Failure** chain is used if no Related Entity / Customer / Tenant was found, otherwise - **Success** chain.

Outbound Message will have new originator Id.