> For the complete documentation index, see [llms.txt](https://docs.welkinhealth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.welkinhealth.com/admin/users/custom-user-attributes.md).

# Custom User Attributes

Custom User Attributes extend the standard Welkin user profile with additional fields specific to your organization — for example, clinical specialty, NPI number, department, or any other property you need to track per user.

***

## Attribute types

### Predefined attributes

Predefined attributes are built and maintained by the Welkin team to accommodate known use cases. They cannot be deleted, but their display settings can be adjusted. To edit a predefined attribute, click the **pencil icon** next to it.

### Custom attributes

Custom attributes are created and managed entirely by your organization. They can hold any data relevant to your users and have no predefined purpose in Welkin. Custom attributes can be:

* **Created** — define a name, label, type, and visibility
* **Edited** — update the configuration at any time
* **Deleted** — remove attributes that are no longer needed (using the trash icon)

***

## Attribute statuses

Each attribute can be set to one of the following visibility/editability states:

| Status        | Description                             |
| ------------- | --------------------------------------- |
| **Editable**  | Visible and editable by users or admins |
| **Read-Only** | Visible but cannot be changed by users  |
| **Hidden**    | Not visible in the user profile         |
| **Inactive**  | Disabled; not used                      |

***

## Searching attributes

You can search and filter the attribute list by:

* Name
* Status (Inactive, Hidden, Read-Only, Editable)
* Field type
* Predefined vs. Custom

***

## Related articles

* [Admin Portal Overview](/admin/admin.md)
* [Setting up Welkin Users](/admin/users/users.md)
* [Add, Delete, Modify Users](/admin/users/add-new-users.md)


---

# 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.welkinhealth.com/admin/users/custom-user-attributes.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.