# Intended Audience

The documentation on this site is intended to support a range of technical users:

* **Admins** configuring business settings, permissions, and platform behavior
* **Technical Builders** creating integrations, orchestrations, and extensions across enterprise systems
  * **Developers** building integrations, <code class="expression">space.vars.automations</code>, and plugins
  * **Technical Teams** orchestrating AI-driven workflows
  * **Solution Architects** connecting enterprise systems
  * **Platform Engineers** extending <code class="expression">space.vars.Kizen\_company\_name</code> across complex environments
  * **Implementers** creating specialized industry flows (insurance, healthcare, and financial services)

If you work with APIs, <code class="expression">space.vars.automations</code>, system integrations or just need to understand how <code class="expression">space.vars.Kizen\_company\_name</code> works, this is your home base!

### Industry-Specific Use Cases

<code class="expression">space.vars.Kizen\_company\_name</code> supports a wide range of industry workflows. The use cases below show how insurance, healthcare, and financial services teams leverage <code class="expression">space.vars.automations</code>, integrations, and data orchestration to power their core processes.

{% tabs %}
{% tab title="Insurance" %}

### Insurance

#### **Admins**

* Configure agent permissions, compliance rules, and required enrollment fields
* Set up business settings for quoting, enrollment, and multi-carrier workflows

#### **Technical Builders (Developers, Architects, Implementers)**

* Build integrations with quoting and enrollment platforms (SunFire, Connecture, carrier APIs)
* Automate end-to-end insurance workflows such as plan comparisons, eligibility checks, and renewals
* Sync agent, member, and policy data across external systems
* Create custom plugins for lead routing, quoting tools, or compliance logic
  {% endtab %}

{% tab title="Healthcare" %}

### **Healthcare**

#### **Admins**

* Manage provider permissions, data-sharing rules, user roles, and HIPAA-aligned configurations
* Set up scheduling preferences, intake settings, and clinic-level workflows

#### **Technical Builders (Developers, Architects, Implementers)**

* Integrate EHR/EMR systems (Epic, Cerner, Athena) with operational workflows
* Automate patient journeys such as referrals, prior auth requests, and clinical follow-ups
* Sync clinical and operational data from HL7/FHIR endpoints
* Build plugins for data validation, scheduling logic, or care management tools
  {% endtab %}

{% tab title="Financial Services" %}

### **Financial Services**

#### **Admins**

* Configure compliance rules, approval flows, and access permissions
* Set up business logic for onboarding, transactions, underwriting, or servicing

#### **Technical Builders (Developers, Architects, Implementers)**

* Connect CRMs, loan origination systems, underwriting engines, and servicing platforms
* Automate workflows like KYC/AML checks, risk evaluation, onboarding, and transaction processing
* Sync customer and financial data across internal and external systems
* Customize <code class="expression">space.vars.Kizen\_company\_name</code> with plugins for verification, payment flows, document extraction, or reporting
  {% endtab %}
  {% endtabs %}

<details>

<summary>Related Topics</summary>

* [Introduction](/docs/readme.md)
* [Contributing to Kizen Docs](/docs/readme/contributing-to-kizen-docs.md)
* [Submitting Documentation Updates](/docs/readme/contributing-to-kizen-docs/submitting-documentation-updates.md)
* [Pull Request Review and Publishing Process](/docs/readme/contributing-to-kizen-docs/pull-request-review-and-publishing-process.md)

</details>


---

# 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://developer.kizen.com/docs/readme/intended-audience.md?ask=<question>
```

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.