> For the complete documentation index, see [llms.txt](https://docs.cipp.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cipp.app/user-documentation/cipp/custom-data/schema-extensions/add.md).

# Add Schema Extension

Create a new schema extension and define the properties it contains. At least one property is required before the schema can be saved.

## Schema Details

| Field        | Description                                                                                                                                                                                                            |
| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Schema ID    | A short identifier for the schema, for example `cippUser`. Microsoft Graph generates and prepends a prefix after creation, so the final identifier is longer than the value entered.                                   |
| Description  | A description of what the schema is for. This is shown on the Schema Extensions table.                                                                                                                                 |
| Status       | The initial lifecycle state. In Development allows the schema to be deleted and reworked. Available makes the schema and its properties permanent.                                                                     |
| Target Types | The directory object types the schema applies to. Choose one or more of User, Group, Administrative Unit, Contact, Device, Event (User and Group Calendars), Message, Organization, or Post. At least one is required. |

## Properties

Use **Add Property** to add a row, and the remove icon to take one away before saving. Each property needs both a name and a type.

| Field         | Description                                                                                                                                                             |
| ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Property Name | The name of the property within the schema. Referenced elsewhere in CIPP as `<schemaId>.<propertyName>`.                                                                |
| Property Type | The type of value the property stores. Choose from Binary (256 bytes maximum), Boolean, DateTime (ISO 8601, UTC), Integer (32-bit), or String (256 characters maximum). |

{% hint style="danger" %}
Properties cannot be deleted once the schema is created, regardless of status. Removing a row here only works before you save.
{% endhint %}

{% hint style="info" %}
Schema extension properties are always single-valued. If you need to store a collection, use a multi-valued directory extension instead.
{% endhint %}

***

## Feature Requests / Ideas

We value your feedback and ideas. Please raise any [feature requests](https://github.com/CyberDrain/CIPP/issues/new?template=feature.yml) on GitHub.


---

# 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.cipp.app/user-documentation/cipp/custom-data/schema-extensions/add.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.