# Participant Overview In Maica, Participant's, and all other individuals for that matter, are managed as `Contact` records. It's that simple. Contact records are the place where you capture and manage the attributes and information about people you interact with, for example: * Personal Information (i.e. Name) * Contact Information (i.e. Phone and Email) * Address Information * Demographic Information (i.e. Birthdate, Age, Primary Language) * NDIS Number * Communication Preferences Whether you are an existing Salesforce user, or new to the application, you will likely interact with Contact records frequently and quickly learn how they are used. {% hint style="info" %} If you are looking for an overview of how Contacts work in Salesforce, [Trailhead](https://trailhead.salesforce.com/content/learn/modules/accounts_contacts_lightning_experience/accounts-and-contacts-lightning) has a number of great learning resources, including hands-on challenges and modules. {% endhint %} ## Participant Record Maica provides dedicated `Contact` **Page** and **Lightning Page** layouts, containing some key pieces of information you will likely want to access and manage for your Participants. The section below describes the key Maica components of these layouts in more detail. ### Synchronise Participant Information Quick Action Accurate Participant data is critical to servicing your clients and bringing **certainty** to your NDIS engagement. Use the `Synchronise Participant Information` Quick Action to do exactly that and ensure you always have the latest information about the Participant from PRODA. The Sync performs quite a few functions, so it has its own dedicated Knowledge Base page so that you can read up on all the features. Check it out :point\_down: {% content-ref url="/pages/VKNMrPFFiA4eVgetalQw" %} [Participant PRODA Sync](/participant-management/participant-proda-sync.md) {% endcontent-ref %} ![Sync Participant information to get the latest information from PRODA](/files/Er3q6gdhhWnSpIXeir3U) ### Participant Funding Statement Quick Action Send your Participant a Funding Statement at any time with our handy Quick Action. Like the Participant Sync, the Statement has a dedicated Knowledge Base page so that you can read up on how the Statement is put together and what data is displayed. Check it out :point\_down: {% content-ref url="/pages/dQ80Ei3roQrFLZmevVhX" %} [Participant Statement](/ndis-management/participant-statement.md) {% endcontent-ref %} ![Send an ad-hoc funding Statement to the Participant](/files/9RcOuZZh1B80rTU1q60j) ### Plan Summary Component This handy component summarises key information from the Participant's `Plan` directly on the `Contact` record. Meaning, you don't have to go digging around related records to get a quick, at a glance view of the Participant's `Plan` information.....win! ![Plan Summary Component on the Maica Contact Layout](/files/fBXDwolDELKvpHpuhjF8) ### Service Booking Summary Component Like a sibling to the `Plan` component :point\_up:, this one summarises the key period and budget information for any **active** `Service Booking` records associated with the Participant. ![Service Booking Component on the Maica Contact Layout](/files/oXdkDD5eVtfudz2ak7M3) {% hint style="info" %} These components are hidden if the Participant has no **active** record(s) {% endhint %} ### Report Charts We like charts, who doesn't and the Salesforce ones are some of the best at visually representing data in your system. So, it would make sense then that the `Maica Contact Layout` includes a few of these. Our layout includes the following charts to quickly render a view of the Participant's `Service Booking` data: {% tabs %} {% tab title="Active Service Booking Overview (Purpose)" %} **Description**: This chart displays a view of the Participant's Active `Service Booking` funding grouped by `Support Purpose` **Report**: `Active Service Booking Utilisation (Pur)` ![](/files/ebMHRwUzIMX3RfxcJFG9) {% endtab %} {% tab title="Active Service Booking Overview (Category)" %} **Description**: This chart displays a view of the Participant's Active `Service Booking` funding grouped by `Support Category` **Report**: `Active Service Booking Utilisation (Cat)` ![](/files/i0Yeqqkz9eKKg18YiZRl) {% endtab %} {% endtabs %} ### Using the Maica Contact Layouts If you would like to utilise our Page and/or Lightning Layouts, all you need to do is assign it to the relevant Profile/App etc as per the images below and voila! :tada: #### Page Layout This is done via the Setup or Object Manager view of the `Contact` object. From the `Contact` object menu, go to **Page Layouts** and click **Page Layout Assignment**. ![Assigning the Maica Contact Page Layout](/files/GPPrJUauYDjBozS4eNKa) #### Lightning Layout This is also done via the Setup or Object Manager view of the `Contact` object. From the `Contact` object menu, go to **Lightning Record Pages** --> **Maica Contact Record Page** and click **View**. The Lightning Page will open in read-only mode (as it is part of a managed package) and you can then click **Activation** to display the screen below. ![Activating the Maica Lightning Record Page in your own way](/files/dV2VILjFHWittBm8VAQN) {% hint style="info" %} If you already have a `Contact Page Layout` that works for you, you by no means have to use our layout. If you like specific elements, feel free to add them to your layout. Also, you can also take our layouts--> **clone them** and reconfigure/extend them further with your own attributes and related lists to ensure they really suit your way of working and how you capture and manage Participant information. Up to you! {% endhint %} --- # 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://kb.maica.com.au/ndis-management/plan-management/participant-overview.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.