> For the complete documentation index, see [llms.txt](https://docs.arthajobboard.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arthajobboard.com/admin/manage-portal/fields.md). # Fields This module contains all the fields added by the admin in the "Forms" module ## Fields 1. This module is directly related to the "Forms" module in the admin panel. 2. Any fields in the candidate signup or profile form added manually by you will be reflected here for modification. 3. You can add a new field and use it in the "Forms" module when adding a new field in the form by selecting an option to choose an existing field. Here's the tutorial video followed by detailed steps: {% embed url="" %} ### Steps to add a field 1. Click on the "Add" button from the top right of the page.

2. Enter the display name, placeholder and field type 3. Select the required and editable checkbox as per your requirement. 4. Click on the add button from the bottom of the page. 5. The field will be added to the system and can be used in the form by selecting an existing field option while adding a field. ### Modify Field

1. Click on the edit icon from the action column a sidebar will open as shown below image.

2. Update the Label and Placeholder. 3. Click "Update" and your field is updated!! --- # 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.arthajobboard.com/admin/manage-portal/fields.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.