> 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/_archive/social-registry/features/configurability/user-guide/configure-group-types.md).
# Configure Group Types
This document provides instructions to configure group types in the ***Social Registry*** module.
## Prerequisites
* The user must have Registrar and Administrator role.
* The user must have access to the Social Registry module.
## Procedure
1. Use the link ***socialregistry.explore.openg2p.org*** to access Social Registry.
2. Click the main menu icon  and select ***Social Registry***.
***Social Registry*** screen is displayed.
3. Click the ***Configuration*** in the menu bar and then select ***Group types***.
***Group Types*** screen is displayed.
4. Click the ***New*** button. It enables an empty field.
5. Enter the relevant [Group Types](/products/registry/registry/_archive/social-registry/features/configurability.md#group-types) in the ***Kind*** field.
For example, here, enter the School in Kind field.
6. Click the ***Save*** button to save the group types.
7. Click the ***Discard*** button to exit from the screen.
The newly created group type is added to the group types list.
8. Repeat the steps 4, 5, and 6 to add the relevant group type.
This completes the configuration of group type in Social Registry module.
## Delete Group Types
Refer to the user guide's [Configure Registrant Tags](/products/registry/registry/_archive/social-registry/features/configurability/user-guide/configure-registrant-tags.md#delete-registrant-tags) section to delete group types.
---
# 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.openg2p.org/products/registry/registry/_archive/social-registry/features/configurability/user-guide/configure-group-types.md?ask=&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.
