> For the complete documentation index, see [llms.txt](https://documentation.carbonregistry.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.carbonregistry.com/documentation/carbonregistry.com/api/apps/creating-icr-apps/registering-an-icr-app/permissions.md).

# Permissions

The permissions for an app are configurable under the "Permissions" tab on an app's dashboard.

<figure><img src="/files/elDVeP74bofeWH5yNJMj" alt=""><figcaption></figcaption></figure>

Note: we will be adding permissions gradually.

## Organizations

* [`organization_info`](#organization_info) - "Read"
* [`organization_members`](#organization_members) - "Read"
* [`organization_warehouse`](#organization_warehouse) - "Read" / "Write"
* [`organization_inventory`](#organization_inventory) - "Read" / "Write" / "Request"&#x20;
* [`organization_projects`](#organization_projects) - "Read"

### organization\_info

* Read

The `organization_info` permission gives the holder access to organization specific data. It is a required permission for installations. It also allows the holder to read all retirements that the organization holds. Only "Read" is supported currently.

### organization\_members

* Read

The `organization_members` permission gives the holder access to metadata on all stakeholders of an organization. Most importantly the name and email. In future versions this will also include the kyc status of the stakeholder. Only "Read" is supported currently.

### organization\_warehouse

* Read
* Write

The organization\_warehouse permission gives the holder access to an organization's warehouse. The "Read" portion gives the holder access to the inventory of the warehouse and reservations made in the warehouse. The "Write" portion allows the holder to reserve credits from the warehouse and then also finish that reservation which moves the credit from the warehouse to some receiver, either as a retirement or the credits themselves.

### organization\_inventory

* Read
* Request
* Write

The organization\_inventory permission gives the holder access to an organization's inventory of carbon credits. The "Read" portion allows the holder to read all credits from the inventory of the organization and all requests made to that inventory. The "Request" portion allows the holder to request certain actions to be made. For example the holder of a "organization\_inventory:request" permission can request the transfer of credits from the inventory to some other address / organization.  The "Write" portion allows the holder to make specific credit actions on credits in the organization's inventory like `transfer` , `retire` and `transfer_retire`.For example the holder of a "organization\_inventory:request" permission can request the transfer of credits from the inventory to some other address / organization.&#x20;

### organization\_projects

* Read

Currently is not supported but will be.

## Users

* [examiner](#examiner) - "Read"

### examiner

* Read

The examiner permission gives the holder access to some superadmin / protected endpoints.


---

# 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:

```
GET https://documentation.carbonregistry.com/documentation/carbonregistry.com/api/apps/creating-icr-apps/registering-an-icr-app/permissions.md?ask=<question>
```

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.