> For the complete documentation index, see [llms.txt](https://docs.flashback.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flashback.tech/flashgate-platform/organization/organization-profile.md).

# Organization Profile

The **Organization Profile** is where admins maintain core company information used across the platform.

## What you can edit

Typical editable fields include:

* organization name,
* legal or billing identity details,
* operational metadata used for administration,
* organization-wide settings exposed in the platform.

## Who can edit

Only high-privilege roles should edit profile settings (typically **ADMINISTRATOR** or **OWNER**).

## Best practices

* Keep organization metadata up to date to reduce billing and compliance issues.
* Restrict profile-edit permissions to a small admin group.
* Review settings after ownership or finance changes.

## API mapping

* `GET /organization/{orgId}`
* `PUT /organization/{orgId}`

See: [Organization Management API](/support-reference/platform-api-reference/organization.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.flashback.tech/flashgate-platform/organization/organization-profile.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.