> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/works/reference-implementations/muktasoft-v2.2/implementation/training-resources/user-manual/web-application-user-manual/registries/wage-seekers.md).

# Wage Seekers

## **Search Wage Seekers**

**Home > Wage Seekers / Sidebar Menu > Wage Seekers**

![](https://content.gitbook.com/content/Oahp3xBKoPsr1r1NAaNj/blobs/TV4f0TDzyXhTEZtVoybC/0.png)

1. From the homepage, click on Wage Seeker to search Wage Seeker.
2. Fill all the details inquired and click on Search.

**Search Criteria**

1. Ward
2. Wage Seeker Name
3. Wage Seeker ID
4. Mobile Number
5. Social Category
6. Created from Date
7. Created to Date

**Search Result**

Once you have filled in all details and clicked on Search, it displays the following details:

1. Wage Seeker ID
2. Wage Seeker Name
3. Father/ Husband Name
4. Social Category
5. City
6. Ward
7. Locality

![](https://content.gitbook.com/content/Oahp3xBKoPsr1r1NAaNj/blobs/nBHVRoJ4jTmBNqn2JFlj/1.png)

## **View Wage Seekers**

**Sidebar Menu / Homepage > Wage Seeker > Search Wage Seeker > Wage Seeker Result > Wage Seeker ID > View Wage Seeker**

1. To View the Wage Seeker, one must Search Wage Seeker.
2. Once you have filled in all the details click on the Search button. This will display the search results.
3. Click on the Wage Seeker ID in orange. This displays the View Wage Seeker option.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXdLoSlWbMZBQ_pCcbBU-Xj0-xpmUqnxx_gVmpTC4aiyt5AAWxfFi0Xg40w8gX7sL0kL8SSY17am33hV-mwB9pU3u5ILh5M4UOQRuP1ocgndmNcaswvngVORqxwo7MO90fhSyIL4fA?key=7xt9KYpRfaW1p-OjcYhu-Rx0" alt=""><figcaption></figcaption></figure>

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXdyOhjLnE_kRBIwf-gVDIe2709J9DeQrzBrc8y0B7_lycLnftq5hfFEPlSAL-X-98BQl0tQYZeESst019UlBv2z6I2dl3anFuwFml9CiU3Gk9SV5kVN0bpO5L6_oSaCNhvupipB_w?key=7xt9KYpRfaW1p-OjcYhu-Rx0" alt=""><figcaption></figcaption></figure>

### **Modify Wage Seeker**

**Sidebar Menu/ Homepage > Wage Seeker > Search Wage Seeker > Wage Seeker Result > Wage Seeker ID > View Wage Seeker > Modify Wage Seeker**

To modify any details regarding Wage Seekers, one must view the Wage Seeker and then click on Modify at the bottom of the page. This will display all the details of the Wage Seeker. Make necessary changes and click on Save at the bottom.

<figure><img src="https://content.gitbook.com/content/Oahp3xBKoPsr1r1NAaNj/blobs/pQwpfQtU5XFq917JquQ7/7.png" alt=""><figcaption></figcaption></figure>

<figure><img src="https://content.gitbook.com/content/Oahp3xBKoPsr1r1NAaNj/blobs/8EIYBphK3SyFO72Fs3KN/8.png" alt=""><figcaption></figcaption></figure>

<figure><img src="https://content.gitbook.com/content/Oahp3xBKoPsr1r1NAaNj/blobs/oimcK6L9K1dumfWjbU9H/9.png" alt=""><figcaption></figcaption></figure>

<figure><img src="https://content.gitbook.com/content/Oahp3xBKoPsr1r1NAaNj/blobs/kLj2DJEJViU78x8hDQ0w/10.png" 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.digit.org/works/reference-implementations/muktasoft-v2.2/implementation/training-resources/user-manual/web-application-user-manual/registries/wage-seekers.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.