> For the complete documentation index, see [llms.txt](https://features.scnd.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://features.scnd.com/v2.0/core-concepts/user-search-feature.md).

# User search feature

Allows platform users to search for other users within the platform

* [Why](#id-1.14.x-usersearchbundle-businessrules-why)
* [Which context](#id-1.14.x-usersearchbundle-businessrules-whichcontext)
* [Configuration](#configuration)
* [Interfaces](#id-1.14.x-usersearchbundle-businessrules-interfaces)
* [Configurations](#id-1.14.x-usersearchbundle-businessrules-configurations)
* [Workflows](#id-1.14.x-usersearchbundle-businessrules-workflows)
* [Special rules](#id-1.14.x-usersearchbundle-businessrules-specialrules)

### Why <a href="#id-1.14.x-usersearchbundle-businessrules-why" id="id-1.14.x-usersearchbundle-businessrules-why"></a>

The User Search feature enables platform users to search for other users within the platform based on user-specific categories, attributes, and locations.

This feature is especially useful for encouraging users to form a strong network and community. This also serves as an additional means for proactive opportunity searches.

### Which context <a href="#id-1.14.x-usersearchbundle-businessrules-whichcontext" id="id-1.14.x-usersearchbundle-businessrules-whichcontext"></a>

This feature is available for all types of configurations.

### Configuration

To enable user search functionality, ensure that both the ***User Search*** and ***Display Search Form*** configurations are activated.

### Interfaces <a href="#id-1.14.x-usersearchbundle-businessrules-interfaces" id="id-1.14.x-usersearchbundle-businessrules-interfaces"></a>

**SBO:**

* [User categories management](https://features.scnd.com/v2.0/superadmin/users/user-categories-management.md)
* [User attributes management](https://features.scnd.com/v2.0/superadmin/users/user-attributes-management.md)

**Front:**

* [Homepage (User search feature)](https://features.scnd.com/v2.0/front-office/homepage/homepage-user-search-feature.md)
* [Users search results page (User search feature)](https://features.scnd.com/v2.0/front-office/search-result-pages/users-search-results-page-user-search-feature.md)

**Dashboard:**

* [User profile dashboard (User search feature)](https://features.scnd.com/v2.0/dashboards/user-profile-dashboard/user-profile-dashboard-user-search-feature.md)

### Workflows <a href="#id-1.14.x-usersearchbundle-businessrules-workflows" id="id-1.14.x-usersearchbundle-businessrules-workflows"></a>

There is no specific workflow for the user search feature.

### Special rules <a href="#id-1.14.x-usersearchbundle-businessrules-specialrules" id="id-1.14.x-usersearchbundle-businessrules-specialrules"></a>

There are no specific rules for the user search feature.


---

# 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://features.scnd.com/v2.0/core-concepts/user-search-feature.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.
