> 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/designer/programs-and-profiles/designer-profiles-overview.md).

# Designer Profiles Overview

## Overview

Profiles in the Designer define the structure of information displayed in the Care Portal for different entity types – primarily patients, but also for contacts and other record types. A profile consists of fields, sections, and layout configurations that determine what information care team members see and can edit.

***

## What Profiles Control

* **Which fields are displayed** – standard fields (name, DOB, contact info) and custom fields (CDTs)
* **Field order and grouping** – how fields are arranged into sections
* **Field editability** – which fields are read-only vs. editable
* **Conditional display** – fields that appear only when certain conditions are met

***

## Types of Profiles

* **Patient Profile** – the main record view for patients
* **Contact Profile** – the view for non-patient contacts linked to patients
* **Custom entity profiles** – if your organization uses custom entity types

***

## Configuring a Profile

1. In the Designer, navigate to **Profiles**.
2. Select the profile type you want to configure (e.g., Patient).
3. Click to open the profile editor.
4. Add, remove, or reorder **sections** and **fields**.
5. Configure field properties (label, editability, required status).
6. Create a draft and publish.

***

## Adding Custom Fields to a Profile

Custom fields from your Custom Data Types (CDTs) can be added to profiles. See [CDT Designer](/designer/custom-data-types/custom-data-types-cdt-designer.md) for how to create CDTs and their fields.

***

## Publishing

Profile changes must be published in the Designer before they appear in the Care Portal. Always test profile changes in a sandbox environment before publishing to production.


---

# 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/designer/programs-and-profiles/designer-profiles-overview.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.