> 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.md).

# General Settings

Settings that apply to a whole organization.

The **General** page of an organization holds the settings that apply to the organization and, through it, to all of its workspaces.

Modifying the settings requires at least the **organization admin** role. Select *Save* to apply a change.

## Organization basics

<table><thead><tr><th width="220">Setting</th><th>What it does</th></tr></thead><tbody><tr><td><strong>Name</strong></td><td>The organization name, shown in the breadcrumb and in the organization switcher. Typically your company name.</td></tr><tr><td><strong>Description</strong></td><td>Optional free text, up to 500 characters. It appears under <em>About this Organization</em> on the organization home.</td></tr><tr><td><strong>Organization owner</strong></td><td>The single user who owns the organization. Only one user can hold this role, and only the owner can delete the organization or hand ownership to someone else.</td></tr></tbody></table>

{% hint style="warning" %}
Changing the **organization owner** transfers that role away from you immediately. Make sure the person taking it over is the right one, because only the new owner can transfer it back.
{% endhint %}

## Sections

<table><thead><tr><th width="250">Section</th><th>What it controls</th></tr></thead><tbody><tr><td><a href="/device-management/managing-an-organization/general-settings/white-labeling.md">White label settings</a></td><td>Present akenza under your own name, colors, and logo.</td></tr><tr><td><a href="/device-management/managing-an-organization/general-settings/genio-ai.md">Genio AI</a></td><td>Whether the AI assistant is available in this organization.</td></tr><tr><td><a href="/device-management/managing-an-organization/general-settings/organization-properties.md">Organization properties</a></td><td>A free-form JSON object of extra metadata, readable through the REST API.</td></tr><tr><td><a href="/device-management/managing-an-organization/general-settings/actions.md">Actions</a></td><td>Deleting the organization.</td></tr></tbody></table>

{% hint style="info" %}
[Billing & Subscription](/device-management/managing-an-organization/subscription.md), [API keys](/device-management/managing-an-organization/api-keys.md), [Audit Logs](/device-management/managing-an-organization/audit-logs.md), and [Users](/device-management/managing-an-organization/organization-users.md) are also organization-wide, but have their own pages in the settings group rather than living under General.
{% 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.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.
