Skip to main content

Zendesk help site

note

Samples are genericized to mask proprietary information. Product images are mockups generated by Claude.

Overview​

I built this Zendesk help site, including a customized theme that added features to support content about two products that had some parity but not all. For example, two How to audit rosters articles existed - one for the first software app and one for the second - but they contained different steps.

Home page​

Article page​

clearpathSupport
Search questions, keywords, or topics
Clearpath Help Center›Clearpath Roster Guide›Create a template

Choose a relationship type

Clearpath ForgeGroup audits

First, choose objects to store carriers and producers.

Fill out the following field:

FieldWhat to select
Select Relationship TypeSelect a relationship type to determine how carrier and producer objects are associated.

Choose between two relationship types:

  • About a related record
  • About a junction object

About a related record

A related record is based on the concept of a one-to-many relationship. This means you can reference contacts that are direct children of the account, like accessing all producers under a carrier.

Example 1

The Carrier table defines the type of object you're using to group producers by, like if you want to run a roster for a program and you plan to use the Account object.

The Producer table defines the type of object you're using for producers.

The reference field (Account ID) identifies which carrier's contacts you want to use, like pulling all contacts that are children of a carrier.

Related record relationshipA Carrier card, the Account object in Clearpath, has an Account ID field. A Producer card, the Contact object in Clearpath, lists Producer A, Producer B, and Producer C, each with its own Account ID field. Arrows run from each producer's Account ID to the carrier's Account ID, labeled Related record.CarrierAccount object in ClearpathAccount IDProducerContact object in ClearpathProducer AAccount IDProducer BAccount IDProducer CAccount IDRelated record

Example 2

Related record exampleContact (Producer) points up to Account (Carrier) through its Account ID field. Seven sub-objects - Education, Training, Branch Locations, Designations, License, Non-Resident Licenses, and E&O Insurance - each point up to Contact.Account IDAccount(Carrier)Contact(Producer)EducationTrainingBranchLocationsDesignationsLicenseNon-ResidentLicensesE&OInsuranceSub-objects of Contact

About a junction object

Based on the concept of a many-to-many relationship, a junction object makes it possible to link multiple rows in one table to multiple rows in another table. This selection will be most commonly used to generate rosters.

A common use case is to reference producers connected via an indirect grouping who aren't direct children of the carrier, like an object that relates the producer to the carrier object, such as the Producer Appointment object. This makes it possible to access producers linked to a specific program.

Example 1

In this example, producer A is associated with multiple carriers. Producer B is associated with only one carrier.

Junction object relationshipThe Producer Appointment junction object has a Carrier parent field and a Producer child field, with three rows: Carrier A with Producer A, Carrier B with Producer A, and Carrier B with Producer B. Arrows link each row's carrier to the Carrier table, the Account object, and each row's producer to the Producer table, the Contact object. Producer A is linked to two carriers; Producer B to one.CarrierAccount objectCarrier ACarrier BProducerContact objectProducer AProducer BProducer AppointmentJunction objectCarrierParent fieldProducerChild fieldCarrier AProducer ACarrier BProducer ACarrier BProducer B

Example 2

In this example, Producer Appointment is the junction object.

Junction object exampleProducer Appointment, the junction object, points up to Account or Carrier Network (Carrier) through its parent field, and has a two-way link down to Contact (Producer) through its child field. Seven sub-objects - Education, Training, Branch Locations, Designations, License, Non-Resident Licenses, and E&O Insurance - each point up to Contact.Parent fieldChild fieldAccount or Carrier Network(Carrier)Producer AppointmentJunction objectContact(Producer)EducationTrainingBranchLocationsDesignationsLicenseNon-ResidentLicensesE&OInsuranceSub-objects of Contact

Recently viewed articles

  • About rosters
  • Generate a roster
  • Configure a template's layout
  • Create filters
  • Activate or deactivate a template
© Clearpath Inc. All rights reserved.

Custom search filters​

clearpathSupport
How do I fix a coverage gap before an audit closes?
Clearpath Help Center›Search results

Quick answer

To fix a coverage gap, open the audit's findings, request updated coverage documents from the vendor, and then resolve or waive the gap before you close the audit.

AI suggestion based onReview coverage gaps before an audit closes

10 results for "How do I fix a coverage gap before an audit closes?"

  • Clearpath Help Center›FAQ and troubleshooting›Audits

    Review coverage gaps before an audit closes

    Clearpath ForgeClearpath ConnectIndividual auditsGroup audits

    Open the Findings tab to see every coverage gap. Resolve or waive each gap before you close the audit.

    Updated October 2, 2026
  • Clearpath Help Center›Clearpath Forge Guide›Audit settings

    Set coverage minimums for an audit

    Clearpath ForgeIndividual auditsGroup audits

    Define the minimum coverage each vendor must carry. Audits flag any coverage below the limits you set as a gap.

    Updated September 24, 2026
  • Clearpath Help Center›Clearpath Connect Guide›Document requests

    Request coverage documents from a vendor

    Clearpath ConnectIndividual audits

    Send a vendor a secure link to upload proof of coverage. Connect tracks the request until it's complete.

    Updated August 18, 2026
  • Clearpath Help Center›Clearpath Forge Guide›Group audits

    Run coverage checks across a vendor group

    Clearpath ForgeGroup audits

    Check coverage for every vendor in a group at once. Any gaps roll up into a single coverage report.

    Updated September 24, 2026
  • Clearpath Help Center›Clearpath Forge Guide›Findings

    Flag a vendor's lapsed coverage

    Clearpath ForgeIndividual audits

    When coverage lapses mid-audit, Forge flags the vendor and notifies the audit owner.

    Updated July 30, 2026
  • Clearpath Help Center›Clearpath Connect Guide›Document requests

    Send bulk coverage requests to a group

    Clearpath ConnectGroup audits

    Request updated coverage from every vendor in a group with one request. Each vendor gets their own link.

    Updated August 18, 2026
  • Clearpath Help Center›FAQ and troubleshooting›Vendors

    Why is a vendor's coverage marked incomplete?

    Clearpath ForgeClearpath ConnectIndividual audits

    Coverage is marked incomplete when a required endorsement or policy page is missing from the upload.

    Updated October 6, 2026
  • Clearpath Help Center›Clearpath Forge Guide›Reports

    Compare coverage across audit periods

    Clearpath ForgeIndividual auditsGroup audits

    See how coverage changed between audit periods, including new policies, renewals, and lapses.

    Updated June 12, 2026
  • Clearpath Help Center›Clearpath Connect Guide›Renewals

    Track coverage renewals for a vendor group

    Clearpath ConnectGroup audits

    Connect sends reminders as coverage nears expiration, so renewals arrive before the next audit.

    Updated September 3, 2026
  • Clearpath Help Center›Source Integrations Guide›Sync data between apps

    Sync coverage data from Connect into an audit

    Clearpath ForgeClearpath ConnectIndividual auditsGroup audits

    Coverage documents collected in Connect sync to the matching audit in Forge automatically.

    Updated June 12, 2026
© Clearpath Inc. All rights reserved.

Paligo integration​

How Paligo's CCMS strengths and Zendesk's CMS strengths combinePaligo is an XML component content management system: a single topic is written once and reused across many guides and outputs, giving structured, consistent, reusable authoring. That content publishes into Zendesk, which manages it as published articles organized into categories, sections, and articles for customers to search and browse. Together, the two systems combine the CCMS's strengths in structure and reuse with Zendesk's strengths in customer-facing delivery and support.Paligo — XML CCMSZendesk — help center CMSShared topicwritten in XMLGuide AGuide BOne topic, reused across outputsPublishCategoryManaged in ZendeskSectionManaged in ZendeskArticleCustomer-facingTwo systems, two strengthsCCMS: structured, reusable authoringCMS: customer-facing publishing and delivery
Paligo's structured, reusable XML authoring feeds a Zendesk help center built to organize and deliver published articles to customers—combining the strengths of a CCMS with the strengths of a CMS.
tip

See Structured XML authoring in Paligo for details on the information architecture of the site and how content was structured as XML in a CCMS.