> For the complete documentation index, see [llms.txt](https://docs.akenza.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akenza.io/device-management/managing-an-organization/general-settings/organization-properties.md).

# Organization Properties

Attach your own metadata to an organization as a JSON object, readable through the REST API.

**Organization properties** hold additional metadata about an organization as a free-form **JSON object**. The object is available through the [REST API](/reference/api-documentation.md), which makes it a useful place to keep information your own applications and integrations need to read alongside the organization.

Typical uses are recording identifiers from another system, such as a customer number in your ERP, or storing configuration that an integration of yours reads at runtime.

## Editing the object

Open **Organization properties** on the [General settings](/device-management/managing-an-organization/general-settings.md) page, edit the JSON in the editor, and select *Save*. The content must be a single valid JSON object, and an organization with nothing set shows an empty one:

```json
{}
```

{% hint style="warning" %}
The editor replaces the whole object, so an application writing here through the API and a person editing in the UI can overwrite each other. Read the current value before writing a new one, and keep keys that belong to other consumers intact.
{% endhint %}

{% hint style="info" %}
Organization properties describe the **organization**. For metadata on a single project or site, use [workspace properties](/device-management/managing-a-workspace/general-settings/workspace-properties.md); for metadata on individual devices, use [custom fields](/device-management/managing-a-workspace/custom-fields.md).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.akenza.io/device-management/managing-an-organization/general-settings/organization-properties.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.