# tenant attributes
Node finds Tenant of the Message Originator entity and adds Tenant Attributes or Latest Telemetry value into Message Metadata.
Administrator can configure the mapping between original attribute name and Metadata attribute name.
There is **Latest Telemetry** checkbox in the Node configuration. If this checkbox selected, Node will fetch Latest telemetry for configured keys. Otherwise, Node will fetch server scope attributes.
Outbound Message Metadata will contain configured attributes if they exist. To access fetched attributes in other nodes you can use this template ‘`metadata.tempo`’
Following Message Originator types are allowed: **Tenant**, **Customer**, **User**, **Asset**, **Device**, **Alarm**, **Rule Chain**.
If unsupported Originator type found, an error is thrown.
**Failure** chain is used if Originator does not have assigned Tenant Entity, otherwise - **Success** chain.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.tesenso.com/tesenso-iot-cloud/rule-engine/rule-engine/enrichment-rule-nodes/tenant-attributes.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.