> For the complete documentation index, see [llms.txt](https://docs.energyweb.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.energyweb.org/launchpad/generic-and-energy-services/green-proofs-as-a-service/green-proofs-as-a-service-quickstart-guide/issuance-certificate-creation.md).

# Issuance/Certificate Creation

For starters, there are 20 fields available to be used. There are some which are predetermined, and predefined and some which are user-generated. So let's dive into each of them:

1. Name the certificate: Naming your certificate is the first process. The name is a "text" field which will stay the same on the platform for all certificates (Editing your registries is on our current roadmap)

<figure><img src="/files/2fSdasD85Ugc1abAkLjz" alt=""><figcaption></figcaption></figure>

2. The ID number: this is a predefined field, which the system provides for each creation (issuance) of a certificate to give it a unique identifier.
3. Date of issuance: the last predefined field, it is given by the system to asses the date that the issuance occurred. It is very useful to see which certificates have been issued more recently or not.&#x20;
4. There are 17 more fields which you can create, with the following types: string/text/number/date/email/upload file.&#x20;

Each of the 20 fields has an extra box for description.

You can also define if the field in the end will be "required" or not by triggering the boolean value.

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

Also, there are 4 values that can be part of the "Table". Which means that they will be shown front and centre on the table. The rest will be displayed only on the unit.&#x20;

<figure><img src="/files/01Wyo7mvqGH99ZpsXYcM" alt=""><figcaption></figcaption></figure>


---

# 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.energyweb.org/launchpad/generic-and-energy-services/green-proofs-as-a-service/green-proofs-as-a-service-quickstart-guide/issuance-certificate-creation.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.