> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/products/registry/registry/developer-zone/building-a-registry/concepts/registry-and-register-metadata/g2pintakeformdefinition.md).

# G2PIntakeFormDefinition

g2p\_intake\_form\_definitions - the principal metadata information on creation of intake forms on registers

Defines **intake forms** — structured input channels for creating new records in a **REGISTER** or **PROGRAM\_REGISTER**.

An intake form groups sections (via G2PIntakeFormUITab and G2PIntakeFormUITabSection) into a workflow exposed through portal UIs or the ingestion pipeline.

***

### Attributes

| Attribute                               | Description                                                         |
| --------------------------------------- | ------------------------------------------------------------------- |
| **form\_id**                            | Primary key.                                                        |
| **register\_id**                        | Target register. References `g2p_register_definitions.register_id`. |
| **form\_mnemonic**                      | Unique short name for API routing and configuration lookup.         |
| **form\_description**                   | Human-readable description of purpose and channel.                  |
| **number\_of\_verifications**           | Independent verifications required before approval.                 |
| **used\_only\_in\_ingestion\_pipeline** | When `TRUE`, form is pipeline-only and not shown in portal UIs.     |

***

### Intake workflow

When a user submits an intake form:

1. The platform creates intake submission records and **change requests per section**.
2. The **primary section** (G2PRegisterSection) is processed first.
3. Required verifications must complete before approval.
4. On approval, change requests are applied to the register.

***

### Related metadata

| Table                             | Document                                                                                                                                           |
| --------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| `g2p_intake_form_ui_tabs`         | G2PIntakeFormUITab                                                                                                                                 |
| `g2p_intake_form_ui_tab_sections` | G2PIntakeFormUITabSection                                                                                                                          |
| `g2p_register_sections`           | [G2PRegisterSection](/products/registry/registry/developer-zone/building-a-registry/concepts/registry-and-register-metadata/g2pregistersection.md) |

Input channel linkage (staff portal, agent portal, etc.) may be configured in `meta_data/registry-configurations/g2p_input_mechanisms.sql`.


---

# 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.openg2p.org/products/registry/registry/developer-zone/building-a-registry/concepts/registry-and-register-metadata/g2pintakeformdefinition.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.