What Can Be Edited

Applications are built from a managed package — a set of questions and sections defined during your onboarding and maintained by Public House. This structure keeps applications secure and consistent, and means some elements are fixed while others can be tailored to your organization.

Sections

Applications are organized into sections. You can hide sections that aren't relevant to your program, but you cannot add new sections or change the order they appear in.

Section headings are editable. If the default heading doesn't match your organization's language or program context, you can update it. Changes to section headings apply to your organization only and don't affect other organizations.

Warnings

Each section can include a warning — a message displayed to applicants to provide context, set expectations, or flag important information before they proceed. Warnings are fully customizable per section and per organization.

Questions

The questions available in your application are those defined in your onboarding mapping documents. These questions are part of the managed package and draw from existing Salesforce fields.

Question text and help text are editable for all questions, essential or not. You can update the wording of any question and the help text shown alongside it to better match your organization's language.

Essential questions are marked as such because they're required for the application to function correctly. These cannot be removed from their section.

Non-essential questions can be hidden if they aren't needed for your program.

Repurposing unused questions: If a non-essential question isn't being used, it can be repurposed to serve a different organizational need — but the question type must stay the same. For example, a picklist field must remain a picklist, a multi-select picklist must remain a multi-select picklist, a number field must remain a number field, and so on.

Custom questions cannot be created. Because the application works within Salesforce's managed package framework, adding fields outside of what the package supports isn't possible — doing so would conflict with the security model and field restrictions that the managed package enforces.

If you need a question that isn't currently available, reach out to Public House to discuss whether it can be supported within the existing structure.

Required Documents

Required documents are highly customizable. For each required document you can configure:

• Description — the text applicants see explaining what the document is
• "I don't have it" instructions — guidance for applicants on how to obtain or replace the document
• Staff instructions — internal notes for staff reviewing submissions
• Condition — whether the document only appears under certain circumstances
• Required — whether the document is mandatory or optional
• Section — where in the application the document request appears

Required documents can be shared across multiple programs. If the same document works the same way in every program — same description, same conditions, same requirements — one document can be reused across all of them.

However, if the description needs to differ between programs, separate required documents are needed for each. For example, if one program requires one month of bank statements and another requires three months, those would need to be two distinct required documents — since any change to the description updates it everywhere the document is used.

Other Configuration

Additional customization is available through your campaign screening configuration and the Public House app program configuration. Those settings are managed separately from the application itself.

Summary