# Designer Overview
## Welkin Designer Overview
Welkin Designer is Welkin's no-code configuration environment for the Care platform. Administrators and implementation teams use it to configure care programs, patient profiles, forms and assessments, custom data types, automations, navigation layouts, security policies, webhooks, and homepage settings.
Everything care teams use in the Care portal is configured here. That includes patient data collection, care workflows, role-based layouts, outbound communications, notifications, and reporting inputs.
Welkin has three applications: **Care**, **Designer**, and **Admin**. Designer sits between them. It uses settings from Admin and publishes the configuration that care teams use in Care every day.
***
## Designer Version Control and Configuration
Every change made in the Designer is tracked. The **Change Summary** shows a full audit trail of modifications by date, user, and section. Configurations can also be exported as a snapshot for backup or migration to another environment.
→ [Change Summary and Version History](/designer/version-and-configuration/change-summary-and-version-history.md) · [Export Designer Configuration](/designer/version-and-configuration/export-designer-configuration.md)
***
## Care Programs, Phases, and Profiles
Programs are structured care pathways that patients follow. Each program contains one or more **phases** that represent where a patient is in their care journey. Programs drive patient workflows, assessment scheduling, automations, and reporting.
**Profiles** define the layout of what care team members see when they open a patient record — which tabs, data panels, and components are visible per role or encounter type.
→ [Programs and Phases](/designer/programs-and-profiles/programs-and-phases.md) · [Designer Profiles Overview](/designer/programs-and-profiles/designer-profiles-overview.md) · [Patient Data View](/designer/programs-and-profiles/patient-data-view.md) · [Enable Patient Delete](/designer/programs-and-profiles/designer-enable-patient-delete.md)
***
## Custom Data Types (CDTs)
Custom Data Types are structured data models that extend the patient record with your organization's specific fields. CDTs can hold any type of structured data — clinical measurements, intake information, insurance details, and more. Fields can be text, numbers, dates, dropdowns, or formulaic calculations derived from other fields.
→ [Custom Data Types](/designer/custom-data-types/custom-data-types.md) · [CDT Designer](/designer/custom-data-types/custom-data-types-cdt-designer.md) · [CDT Configuration](/designer/custom-data-types/cdt-configuration.md) · [Formulaic CDT Fields](/designer/custom-data-types/create-formulaic-custom-data-type-fields.md) · [Custom Field Types](/designer/custom-data-types/custom-field-types.md)
***
## Assessments, Forms, and Patient-Facing Forms
Assessments and forms are structured questionnaires completed by care teams or patients. They can be scored, include conditional logic (show/hide fields based on responses), and be associated with programs or encounter types. Assessment results can populate CDT fields, trigger automations, or generate PDF documents.
**Patient Facing Assessments (PFAs)** are forms sent directly to patients to complete on their own device.
→ [Create an Assessment or Form Template](/designer/documents-and-assessments/how-to-create-an-assessment-or-form-template.md) · [Add Conditionality to Assessments](/designer/documents-and-assessments/how-to-add-conditionality-to-assessments.md) · [Configure Scored Assessments](/designer/documents-and-assessments/designer-how-to-configure-scored-assessments.md) · [Forms Conditional Logic](/designer/documents-and-assessments/forms-conditional-logic.md) · [Create PDFs from Forms/Assessments](/designer/documents-and-assessments/create-pdfs-from-forms-assessments.md) · [Create PFA Folders](/designer/documents-and-assessments/create-pfa-folders.md) · [Associate Assessments with Programs](/designer/documents-and-assessments/how-to-associate-assessments-with-programs.md) · [Add Assessments to a Template](/designer/documents-and-assessments/how-to-add-assessments-to-a-template.md)
***
## Documents
Document types define what categories of files care teams can upload and store in patient records — lab results, signed forms, clinical notes, and more. Each document type can have metadata fields and access controls.
→ [Configure Document Types](/designer/documents-and-assessments/document-types-how-to-configure.md)
***
## Charts & Graphs
Charts and graphs surface visual summaries of patient data — trending clinical values, assessment scores over time, and other longitudinal views. They are configured against CDT fields and displayed in the patient profile.
→ [How to Configure Charts and Graphs](/designer/charts-and-graphs/charts-graphs-how-to-configure.md) · [Filter, Change Date, and Data Points](/designer/charts-and-graphs/charts-graphs-filter-change-date-and-by-data-point.md)
***
## Care Portal Navigation and Layout
Navigation layouts define what sections appear in the left sidebar of the Care portal per role. The action bar can also be customized to surface frequently used actions at the top of patient profiles.
→ [How to Create Navigation Layouts](/designer/navigation-and-layout/how-to-create-navigation-layouts.md) · [Customize Action Bar](/designer/navigation-and-layout/customize-action-bar.md)
***
## Workflow Automations
Automations are rule-based workflows that trigger actions when conditions are met — sending a message, creating a task, updating a CDT field, changing a program phase, or generating a notification. Conditions can be based on patient data changes, calendar events, assessment completions, program enrollments, and more.
Advanced automations support multi-step logic, time delays (postponed tasks), and branching conditions.
→ [How to Create Automations](/designer/automations/designer-how-to-create-automations.md) · [Create Advanced Automations](/designer/automations/create-advanced-automations.md) · [Automations that Trigger Outbound Communications](/designer/automations/automations-that-trigger-outbound-communications.md) · [Create Automated Appointment Reminders](/designer/automations/create-automated-appointment-reminders.md)
***
## Tasks
Task types and configurations are defined in the Designer — including which categories of tasks care teams can create, required fields, and automation rules that trigger task creation automatically.
→ [Task Management (Designer)](/designer/tasks/task-management-designer.md) · [Create Tasks](/designer/tasks/create-tasks.md)
***
## Notifications, Messages, and Communications
The Designer controls when and how care team members are notified — triggered by automations, communication events, or system activity. Communication methods (SMS, email, calls, chat) are configured and enabled here, and message templates can be built with dynamic variables.
→ [Automated Notifications](/designer/automations/automated-notifications.md) · [Create User Notifications](/designer/notifications-and-communications/create-user-notifications.md) · [Turning On Notifications for Communications](/designer/notifications-and-communications/turning-on-notifications-for-communications.md) · [Encounters and Dependencies](/designer/notifications-and-communications/encounters-and-dependencies.md) · [SMS Opt-Out](/designer/notifications-and-communications/sms-opt-out.md) · [Configure Phone Names](/designer/notifications-and-communications/configure-phone-names.md)
***
## Webhooks
Webhooks allow Welkin to push real-time event data to external systems when specific actions occur — a patient enrolls, an assessment is completed, a CDT field changes. Each webhook is configured with an endpoint URL, event type, and optional filtering.
→ [Webhooks](/designer/webhooks/webhooks.md) · [How to Create Webhooks](/designer/webhooks/how-to-create-webhooks.md)
***
## Security
Security policies define attribute-based access control (ABAC) rules — who can see and do what, based on user roles, patient attributes, regions, and territories. Policies are created in the Designer and assigned to users in Admin.
→ [Configuring Security Policies](/designer/security/configuring-security-policies.md) · [Setup Security Policies](/designer/security/setup-security-policies.md) · [Security Policy Detail](/designer/security/security-policy-detail.md) · [Defining Regions and Territories](/designer/security/defining-regions-and-territories.md)
***
## Care Homepage Configuration
The new homepage layout — which widgets, dashboards, and sections appear on a care team member's home screen — is configured in the Designer.
→ [New Homepage Configuration](/designer/homepage-configuration/new-homepage-designer.md)
***
## Terminology & Help
Welkin supports customizable terminology so organizations can use their own language — renaming "patients" to "members," "encounters" to "visits," and so on. The Help section in Care can also be configured to surface custom documentation links.
→ [Welkin Naming Conventions Dictionary](/designer/terminology-and-help/welkin-naming-conventions-dictionary.md) · [Brand Terminology Flexibility](/designer/terminology-and-help/brand-terminology-flexibility.md) · [Help Section](/designer/terminology-and-help/help-section.md) · [Configure Help Section](/designer/terminology-and-help/configure-help-section.md)
***
## Visual Components
Visual components are configurable UI elements — data tables, panels, and other display elements — that can be added to patient profiles. Dependencies between visual components define how changes in one component affect others.
→ [Visual Components](/designer/documents-and-assessments/visual-components.md) · [Visual Components Dependencies](/designer/documents-and-assessments/visual-components-dependencies.md)
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.welkinhealth.com/designer/readme.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.