> For the complete documentation index, see [llms.txt](https://docs.pyck.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pyck.cloud/graphql-api/inputs/registertenantinput.md).

# RegisterTenantInput

Audience: Programmer

**Services:** [management](https://docs.pyck.cloud/graphql-api/services/management.md)

## Fields

| Name             | Type                                                                 | Default | Description                                                                                                                                                                                                                                                                                                                                                    |
| ---------------- | -------------------------------------------------------------------- | ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `name`           | String!                                                              |         |                                                                                                                                                                                                                                                                                                                                                                |
| `adminUsername`  | String!                                                              |         |                                                                                                                                                                                                                                                                                                                                                                |
| `adminEmail`     | String!                                                              |         |                                                                                                                                                                                                                                                                                                                                                                |
| `adminFirstName` | String!                                                              |         |                                                                                                                                                                                                                                                                                                                                                                |
| `adminLastName`  | String!                                                              |         |                                                                                                                                                                                                                                                                                                                                                                |
| `adminPassword`  | [Password](https://docs.pyck.cloud/graphql-api/scalars/password.md)! |         | <p>Password of the tenant's first admin. Hashed exactly as sent (no<br>normalization, no trimming); the admin logs in with the same bytes.<br>Must be in Unicode NFC (composed) form, the form keyboards send: a<br>decomposed password (e.g. "o" + U+0308) is refused, since the login<br>would not send those bytes. Control characters are refused too.</p> |
| `data`           | [Map](https://docs.pyck.cloud/graphql-api/scalars/map.md)            |         | <p>Optional metadata for the tenant.<br>Synced to Zitadel org metadata and tenant.data.<br>The UI template keys (remoteWebUITemplate / remoteMobileUITemplate) require<br>ROLE\_SYSTEM and are validated as in setTenantUITemplate.</p>                                                                                                                        |
| `expiresAt`      | [Time](https://docs.pyck.cloud/graphql-api/scalars/time.md)          |         | <p>Optional expiry timestamp. Written directly to<br>tenant.expires\_at; the periodic tenant-expiry-check workflow<br>soft-deletes the tenant once the timestamp is in the past.</p>                                                                                                                                                                           |


---

# 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.pyck.cloud/graphql-api/inputs/registertenantinput.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.
