odoo-forge-bundle 0.1.0

package/payload/skills/odoo18-docs/references/docs/applications/hr/recruitment.md

@@ -0,0 +1,387 @@
+---
+title: ""
+source_url: "https://docs.odoo.sbggai.top/applications/hr/recruitment.html"
+---
+
+:show-content:
+# 
+# Recruitment
+
+Odoo keeps all job applicants organized with a pre-configured series of steps and stages that each
+applicant goes through. Each stage has a specific step(s) that should be performed. These range from
+scheduling a phone call, conducting an interview, or sending a job offer, for example. This process
+is referred to as the 'applicant flow.'
+
+When an applicant applies for a job position, an *applicant card* is automatically created in Odoo's
+*Recruitment* app for that specific job position. As the applicant progresses through the
+recruitment pipeline, the recruitment team moves their card from one stage to the next.
+
+:ref:`Stages can be configured <recruitment/modify-stages>` so that an email is automatically sent
+out using a set, pre-configured template as soon as an applicant's card enters a stage. These
+automated emails are defined on each stage in the applicant flow.
+
+The applicant flow explained in this document is the default flow in Odoo, and goes through the
+applicant flow when using the *Recruitment* application's default configuration. The applicant flow
+is able to be modified to suit the specific recruitment flow for any business.
+
+> **note**:
+>    The applicant flow with all its stages are universal and applies to all job positions, unless
+   specified. :ref:`A specific stage can be configured <recruitment/customize-stages>` to be
+   job-specific, meaning that specific stage is only visible for that specific job position.
+   Otherwise, if a new stage is created, or an existing stage is modified, those changes are
+   visible on all job positions.
+
+.. _recruitment/settings:
+
+# Settings
+
+Before creating a job position in Odoo, configure the necessary settings for the *Recruitment* app.
+To view and edit the settings, navigate to :menuselection:`Recruitment app --> Configuration -->
+Settings`. After any changes are made, click the :guilabel:`Save` button in the top-left corner to
+save all the changes.
+
+## Job posting
+
+The :guilabel:`Job Posting` section of the *Recruitment* app settings has only one selection to
+make. If job positions are to be posted to the company's website, enable the :guilabel:`Online
+Posting` option.
+
+> **note**:
+>    The :guilabel:`Online Posting` is only available if the *Website* application is also installed.
+
+## Recruitment process
+
+The :guilabel:`Recruitment process` section of the settings page specifies what the database can and
+cannot do during the recruitment process.
+
+### Send interview survey
+
+Odoo is capable of having a survey sent to an applicant to gather more information about them.
+Surveys can be thought of as exams, or questionnaires, and can be customized in various ways to
+provide the recruitment team with valuable insights into the applicant
+
+Enable the :guilabel:`Send Interview Survey` option to send surveys to applicants. Once enabled, an
+:icon:`fa-arrow-right` :guilabel:`Interview Survey` internal link appears. Click the
+:icon:`fa-arrow-right` :guilabel:`Interview Survey` link to navigate to a list of all created
+surveys.
+
+This list includes all surveys that were created in the database, not just surveys used in the
+*Recruitment* app. If no surveys have been created, the surveys list displays a :guilabel:`No Survey
+Found` message, and presents options to create a survey from several pre-configured survey
+templates.
+
+.. seealso::
+   For more detailed information about surveys, refer to the :doc:`survey essentials
+   <../marketing/surveys/create>` documentation.
+
+> **note**:
+>    Enabling the :guilabel:`Send Interview Survey` option will install the *Surveys* application once
+   the settings are saved, if it is not installed already.
+
+### Send SMS
+
+It is possible to send text messages to applicants directly through the *Recruitment* app. To do so,
+enable the :guilabel:`Send SMS` option. This option requires credits to use, which can be obtained
+by clicking the :icon:`fa-arrow-right` :guilabel:`Buy credits` internal link that emerges when the
+feature is enabled.
+
+.. seealso::
+   For more information, refer to the :doc:`SMS pricing and FAQs
+   <../marketing/sms_marketing/pricing_and_faq>` documentation.
+
+.. _recruitment/cv-display:
+
+### CV display
+
+When applicants submit an application, one of the default required fields is a resumé, or :abbr:`CV
+(curriculum vitae)`. All resumés are stored in the *Documents* application, and are accessible on
+the applicant's card.
+
+A resumé has the option to appear on the applicant's form, which can be viewed by clicking on the
+applicant's card. The resumé appears on the right-side of the screen. If this is not enabled, the
+resumé is accessed via a link in the chatter, where it needs to be clicked to expand and view it, or
+downloaded.
+
+Enable the :guilabel:`CV Display` option to show the resumé on the applicant's card by default, and
+in addition to the document link. When enabled, the resumé appears on the right side of the
+applicant's card.
+
+> **note**:
+>    For the resumé to appear on the right-side, the browser window must be in full-screen mode (where
+   the browser spans the entire screen).
+
+   If the browser window is set to a size smaller than the entire width of the screen (not
+   full-screen), then the resumé does not appear on the right-side. Instead, the resumé appears in
+   the :guilabel:`Files` section of the chatter, below the applicant's card.
+
+.. image:: recruitment/cv-display.png
+   :align: center
+   :alt: The resumé on an applicant's card, appearing on the right side.
+
+.. _recruitment/cv-ocr:
+
+### CV digitization (OCR)
+
+When an application is submitted using any of the available methods, such as an online application
+submission, emailing a resume to the job position alias, or creating an applicant record directly
+from the database, it is possible to have Odoo extract the applicant's name, phone number, and email
+address from the resumé and populate the applicant's form. To do so, enable the :guilabel:`CV
+Digitization (OCR)` option.
+
+When enabled, additional options appear. Click on the corresponding radio button to select one of
+the following options:
+
+- :guilabel:`Do not digitize`: this option turns off resumé digitization.
+- :guilabel:`Digitize on demand only`: this option only digitizes resumes when requested. A
+  :guilabel:`Digitize document` buttons appears on applicant cards. When clicked, the resumé is
+  scanned and the applicant's card is updated.
+- :guilabel:`Digitize automatically`: this option automatically digitizes all resumés when they are
+  submitted.
+
+Beneath these options are two additional links. Click the :icon:`fa-arrow-right` :guilabel:`Buy
+credits` button to purchase credits for CV digitization. Click the :icon:`fa-arrow-right`
+:guilabel:`View My Services` to view a list of all current services, and their remaining credit
+balances.
+
+For more information on document digitization and :abbr:`IAP's (in-app purchases)`, refer to the
+:doc:`In-app purchase (IAP) <../essentials/in_app_purchase>` documentation.
+
+> **note**:
+>    The :guilabel:`Do not digitize` option for :guilabel:`CV digitization (OCR)` at first may seem
+   like a redundancy. It seems to be the same as disabling the :guilabel:`CV digitization (OCR)`
+   option.
+
+   When the :guilabel:`CV digitization (OCR)` option is enabled, a module is installed so that
+   resumés can be scanned. Disabling this option would uninstall the module.
+
+   If at some point, there is a desire to temporarily stop digitizing resumés, the :guilabel:`Do not
+   digitize` option is selected. The reason this option is available is so that the module is not
+   uninstalled, allowing for digitization to be enabled in the future by selecting one of the other
+   two options.
+
+### Salary package configurator
+
+When sending an offer to an applicant, an expiration date can be set on the offer. Enter the number
+of days an offer is valid for in the :guilabel:`days` field. After the set amount of days has
+passed, if the applicant has not accepted the offer, the offer is no longer available.
+
+# Kanban view
+
+To access the Kanban view for a job position, navigate to the main :menuselection:`Recruitment app`
+dashboard, which is the default view when opening the application. All job positions appear on the
+main dashboard. Click the :guilabel:`(#) New Applications` smart button on a job position card to
+navigate to the Kanban view for all the applicants for that particular job position.
+
+.. image:: recruitment/new-applicants-button.png
+   :align: center
+   :alt: Main dashboard view of job position card, showing new applications button.
+
+Inside the job application, the Kanban stages appear, with all the applicants populated in their
+respective columns, indicating what stage they are currently in. There are six default stages in
+Odoo:
+
+- :ref:`New <recruitment/new>`
+- :ref:`Initial Qualification <recruitment/initial-qualification>`
+- :ref:`First Interview <recruitment/first-interview>`
+- :ref:`Second Interview <recruitment/second-interview>`
+- :doc:`Contract Proposal <recruitment/offer_job_positions>`
+- :ref:`Contract Signed <recruitment/offer_job_positions/contract-signed>`
+
+The last column, :guilabel:`Contract Signed`, is folded by default. Folded columns appear gray, and
+the applicants in it are hidden from view. To expand the folded stage and view the applicant cards
+for that column, click anywhere on the thin gray column that says the stage name and the column
+expands, revealing the applicants.
+
+.. image:: recruitment/stages.png
+   :align: center
+   :alt: Expand a folded column by clicking on it in the Kanban view.
+
+Each stage has a color-coded bar beneath the stage name, providing status information for the
+applicant's in that specific stage. The status colors are:
+
+- :guilabel:`Green`: the applicant is ready to move to the next stage.
+- :guilabel:`Red`: the applicant is blocked from moving to the next stage.
+- :guilabel:`Gray`: the applicant is still in progress in the current stage and is neither ready nor
+  blocked from the next stage.
+
+The status for each card is set manually. To set the status, click on the small circle in the
+lower-left of the applicant card. A status pop-up window appears. Click on the desired status for
+the applicant. The status dot on the applicant card as well as the status bar updates.
+
+.. image:: recruitment/status-dots.png
+   :align: center
+   :alt: The applicant card statuses, and status bar.
+
+> **tip**:
+>    The names for the three status colors (`In Progress`, `Blocked`, and `Ready for Next Stage`)
+   :ref:`can be modified <recruitment/modify-stages>`, if desired.
+
+.. _recruitment/customize-stages:
+
+# Customize stages
+
+Stages can be modified, added, or deleted to best meet the needs of the particular hiring steps of
+a business.
+
+## New stage
+
+To create a new stage, click on :icon:`fa-plus` :guilabel:`Stage` and a new column appears. Enter
+the title for the new stage in the :guilabel:`Stage title` field, then click :guilabel:`Add`. The
+new column appears, and another new stage is available to create. If no new stages are needed, click
+anywhere on the screen to exit the new stage creation.
+
+.. image:: recruitment/add-column.png
+   :align: center
+   :alt: The plus sign to click to add a new column to the Kanban stages.
+
+.. _recruitment/modify-stages:
+
+## Modify stage
+
+To modify the settings of a stage, hover over the name of the stage, and a :icon:`fa-cog`
+:guilabel:`(gear)` icon appears in the upper right hand side of the stage. Click on the
+:icon:`fa-cog` :guilabel:`(gear)` icon and a menu appears. Then click on the :guilabel:`Edit`
+option. An :guilabel:`Edit: (Stage)` form appears. Make any desired modifications to the form, then
+click :guilabel:`Save & Close` when done.
+
+.. image:: recruitment/gear.png
+   :align: center
+   :alt: The gear icon that appears when a column name is moused over, and the drop-down menu it
+         displays when clicked.
+
+.. _recruitment/edit-stage:
+
+### Edit stage form
+
+The :guilabel:`Edit: (Stage)` form is where the stage's settings are configured. The only required
+field is the :guilabel:`Stage Name`.
+
+The fields to be populated or modified are:
+
+- :guilabel:`Stage Name`: type in a name for the stage.
+- :guilabel:`Email Template`: select an email template to be used from the drop-down menu. If a
+  template is selected, when the applicant card enters the stage, an email is automatically sent to
+  the applicant using the selected template.
+- :guilabel:`Folded in Kanban`: check the box to have the stage appear folded (hidden) at all times
+  in the default view.
+- :guilabel:`Hired Stage`: check the box if this stage indicates that the applicant is hired. When
+  an applicant's card enters this stage, the card displays a :guilabel:`Hired` banner in the upper
+  right corner. If this box is checked, this stage is used to determine the hire date of an
+  applicant.
+- :guilabel:`Job Specific`: if the stage only applies to specific job positions, select the job
+  positions from the drop-down menu. Multiple job positions can be selected.
+- :guilabel:`Show in Referrals`: check the box if this stage should be seen in the *Referrals*
+  application, and allow the referrer to accrue points when a referral of theirs reaches this stage.
+  If this is active, a :guilabel:`Points` field appears. Enter the amount of referral points the
+  employee receives when an applicant enters this stage. The *Referrals* app must be installed in
+  order to use this option.
+- :guilabel:`Tooltips` section: there are three pre-configured status labels (colored circles) for
+  each applicant's card, indicating its status. These colors are displayed at the top of each stage
+  to reflect the statuses of the applicants in the stage. The *names* for the label can be modified,
+  but the label itself (the color) cannot. The default names and labels are: :guilabel:`In Progress`
+  (gray), :guilabel:`Blocked` (red), and :guilabel:`Ready for Next Stage` (green).
+- :guilabel:`Requirements`: enter any internal notes for this stage explaining any requirements of
+  the stage.
+
+## Delete stage
+
+If a stage is no longer needed, the stage can be deleted. To delete a stage, hover over the name of
+the stage, and a :icon:`fa-cog` :guilabel:`(gear)` icon appears. First, click on the :icon:`fa-cog`
+:guilabel:`(gear)` icon to reveal a drop-down menu, then click :guilabel:`Delete`. A
+:guilabel:`Confirmation` pop-up warning appears, asking :guilabel:`Are you sure you want to delete
+this column?` Click :guilabel:`Delete` to delete the column.
+
+> **important**:
+>    If there are applicants currently in the stage being deleted, an error pops up when attempting to
+   delete the stage. The records currently in the stage to need to be either deleted, archived, or
+   moved to a different stage before the stage can be deleted.
+
+# Email templates
+
+To communicate with the applicant, Odoo has several pre-configured email templates that can be used.
+The pre-configured email templates and when to use them are as follows:
+
+- :guilabel:`Recruitment: Applicant Acknowledgement`: this template is used to let the applicant
+  know that their application was received. This email is automatically sent out once the applicant
+  is in the :guilabel:`New` stage.
+- :guilabel:`Recruitment: Interest`: this template is used to let the applicant know that their
+  application caught the recruiter's attention, and they have been shortlisted for either a phone
+  call or an interview.
+- :guilabel:`Recruitment: Schedule Interview`: this template is used to let the applicant know that
+  they have passed the :guilabel:`Initial Qualification` stage, and they will be contacted to set up
+  an interview with the recruiter. This email is automatically sent out once the applicant is in the
+  :guilabel:`Initial Qualification` stage.
+- :guilabel:`Recruitment: Not interested anymore`: this template is used when an applicant
+  communicates that they are no longer interested in the position, and thanks them for their time
+  and consideration.
+- :guilabel:`Recruitment: Refuse`: this template is used when an applicant is no longer being
+  considered for the position.
+
+> **note**:
+>    Email templates can be created, modified, and deleted to suit the needs of a business. For more
+   information on email templates, refer to the :doc:`../general/companies/email_template` document.
+
+To manually send an email, click :guilabel:`Send message` in the chatter. A text box appears, as
+well as the applicant's email address.
+
+.. image:: recruitment/full-composer.png
+   :align: center
+   :alt: Send an email from the chatter.
+
+Click the :icon:`fa-expand` :guilabel:`(expand)` full composer icon in the bottom right corner of
+the :guilabel:`Send Message` tab in the chatter. A :guilabel:`Compose Email` pop-up window loads,
+with the :guilabel:`Recipients` and :guilabel:`Subject` pre-populated. The applicant's email address
+is entered in the :guilabel:`Recipients` line, and the :guilabel:`Subject` is `(Job Position)`. The
+email body is empty by default.
+
+To use a pre-configured email template, click the field next to :guilabel:`Load template` in the
+bottom section of the window. Select the email template to use from the drop-down menu.
+
+Pre-configured email templates may contain dynamic placeholders so unique information can be
+populated in the email for a more personalized message to the applicant. There are several
+pre-configured email templates to choose from. Depending on the template selected, the email subject
+and/or body may change.
+
+> **note**:
+>    Only the email templates that are configured for the model load. There are other email templates
+   pre-configured in Odoo, but if they are not configured for the recruitment application, they do
+   not appear in the list of available templates.
+
+If any attachments are to be added, click the :guilabel:`Attachments` button in the lower left
+corner. Navigate to the file to be attached, then click :guilabel:`Open` to attach it. To delete an
+attachment, click the :icon:`fa-close` :guilabel:`(delete)` icon to the right of the attachment.
+
+If any changes need to be made to the email, edit the body of the email. If the edits should be
+saved to be used in the future, the email can be saved as a new template. Click the :guilabel:`Save
+Template` button in the bottom. To send the email, click :guilabel:`Send` and the email is sent to
+the applicant. The email then appears in the chatter.
+
+.. image:: recruitment/send-survey.png
+   :align: center
+   :alt: Send a custom survey, also referred to as an interview form, to an applicant using a
+         pre-configured template.
+
+.. seealso::
+   - :doc:`recruitment/new_job`
+   - :doc:`recruitment/add-new-applicants`
+   - :doc:`recruitment/schedule_interviews`
+   - :doc:`recruitment/offer_job_positions`
+   - :doc:`recruitment/refuse_applicant`
+   - :doc:`recruitment/source_analysis`
+   - :doc:`recruitment/recruitment_analysis`
+   - :doc:`recruitment/time_in_stage`
+   - :doc:`recruitment/team_performance`
+
+.. toctree::
+   :titlesonly:
+
+   recruitment/new_job
+   recruitment/recruitment-flow
+   recruitment/add-new-applicants
+   recruitment/schedule_interviews
+   recruitment/offer_job_positions
+   recruitment/refuse_applicant
+   recruitment/source_analysis
+   recruitment/recruitment_analysis
+   recruitment/time_in_stage
+   recruitment/team_performance

package/payload/skills/odoo18-docs/references/docs/applications/hr/referrals/alerts.md

@@ -0,0 +1,62 @@
+---
+title: "Alerts"
+source_url: "https://docs.odoo.sbggai.top/applications/hr/referrals/alerts.html"
+---
+
+======
+# Alerts
+
+In the *Referrals* application, it is possible to post a message, also referred to as an *alert*, at
+the top of the dashboard to share important information with users.
+
+Alerts remain on the main *Referrals* dashboard for the specified amount of time configured on the
+individual alert.
+
+.. image:: alerts/alerts.png
+   :align: center
+   :alt: Two alert banners appear above the user's photo.
+
+# Create an alert
+
+Only users with *Administrator* access rights for the *Recruitment* application can create alerts.
+To add a new alert, navigate to the :menuselection:`Referrals app --> Configuration --> Alerts`.
+
+Click :guilabel:`New` to open a blank alert form. Enter the following information on the form:
+
+- :guilabel:`Date From`: the date the alert starts. On this date, the alert is visible on the
+  dashboard.
+- :guilabel:`Date To`: the date the alert ends. After this date, the alert is hidden from view.
+- :guilabel:`Company`: the current company populates this field, by default. To modify the company
+  the alert should be displayed for, select the desired company from the drop-down menu in this
+  field.
+
+  If this field remains blank, the alert is visible to everyone with access to the *Referrals*
+  application.
+
+  If a company is specified, only users within that company (who also have access to the *Referrals*
+  application) see the alert. This field **only** appears when in a multi-company database.
+- :guilabel:`Alert`: enter the text for the alert. This message appears inside the alert banner on
+  the main *Referrals* dashboard.
+- :guilabel:`On Click`: there are three options for the alert. Click the radio button next to the
+  desired selection. The options are:
+
+  - :guilabel:`Not Clickable`: the alert only displays text, there is no link to click.
+  - :guilabel:`Go to All Jobs`: the alert contains a link that, when clicked, navigates to the
+    website with all the job positions that are currently posted.
+  - :guilabel:`Specify URL`: the alert contains a link to a specific URL that, when clicked,
+    navigates to that URL. When selected, a :guilabel:`URL` field appears below the :guilabel:`On
+    Click` section. Enter the desired URL in that field.
+
+.. image:: alerts/alert-form.png
+   :align: center
+   :alt: An alert form completely filled in with all selections entered.
+
+# Dismiss an alert
+
+It is possible to dismiss an alert, if a user does not wish to see a specific alert again.
+
+To dismiss an alert, click the :icon:`fa-times` :guilabel:`(remove)` icon on the far-right side of
+the alert to remove the alert from the dashboard.
+
+This prevents the alert from appearing again, even when opening the *Referrals* application for the
+first time in a new session.

package/payload/skills/odoo18-docs/references/docs/applications/hr/referrals/points.md

@@ -0,0 +1,74 @@
+---
+title: "Referral points"
+source_url: "https://docs.odoo.sbggai.top/applications/hr/referrals/points.html"
+---
+
+===============
+# Referral points
+
+The *Referrals* application allows employees to earn points that are then exchanged for
+:doc:`rewards <rewards>`.
+
+Current referral points can be viewed on the main *Referrals* app dashboard, which appears when the
+application is opened, after the :ref:`onboarding <referrals/onboarding>` slides have been viewed or
+skipped.
+
+At the top, a summary of the user's current points is displayed. The left side of the summary
+displays the :guilabel:`Total` points earned, and the right side displays the points that are
+available :guilabel:`To Spend`.
+
+To view the various referral stages, and their respective earned points, click one of the referral
+statuses beneath the avatar. The options are: :guilabel:`Referrals`, :guilabel:`Ongoing`, and
+:guilabel:`Successful`.
+
+The current number of referrals that are still active in the recruitment pipeline, but have not yet
+been hired or refused, appear above :guilabel:`Ongoing`. The number of referrals that have been
+hired, appear above :guilabel:`Successful`. The total number of referrals, both the ongoing and
+successful referrals combined, appears above :guilabel:`Referrals`.
+
+# My referrals
+
+To see all the referrals, both ongoing and successful, click :guilabel:`Referrals`. The
+:guilabel:`My Referral` screen page displays all the referrals, with each individual referral housed
+in its own referral card.
+
+A successful referral displays a white :icon:`fa-check` :guilabel:`Hired` badge in the top-right
+corner of the card, along with a vertical green stripe on the left-side of the card. Referrals that
+are in process have a purple :guilabel:`In Progress` badge in the top-right corner.
+
+Each referral card lists the name of the applicant, the subject/application title as it appears on
+the applicant card in the *Recruitment* app, the name of the job position, the person responsible
+for filling the role (i.e. the recruiter), and the points earned.
+
+For referrals that have been hired, the selected avatar also appears on the card.
+
+.. image:: points/referrals.png
+   :align: center
+   :alt: Two referral cards, one hired and one in-progress.
+
+## Points
+
+The points that can be earned for a referral are the same across all job positions. Each stage of
+the recruitment process has corresponding points assigned to it. The stages listed correspond to the
+stages configured in the *Recruitment* application.
+
+On each individual referral card, beneath the points earned, is a progress bar that displays how
+many points have been earned out of the total possible points that can be earned, if the applicant
+is hired.
+
+Beneath the bar chart is a list of the various recruitment stages, and the points earned when the
+referral moves to that stage. If a stage has been achieved, and the points have been earned, a green
+:icon:`fa-check` :guilabel:`(checkmark)` appears next to the stage.
+
+> **note**:
+>    The preconfigured point structure for referrals is as follows:
+
+   - :guilabel:`Initial Qualification`: 1 point
+   - :guilabel:`First Interview`: 20 points
+   - :guilabel:`Second Interview`: 9 points
+   - :guilabel:`Contract Proposal`: 5 points
+   - :guilabel:`Contract Signed`: 50 points
+
+   The default total points earned for a referral that is hired is 85 points. Modifications of the
+   points earned for each stage are made in the *Recruitment* application. Refer to the
+   :ref:`Recruitment <recruitment/modify-stages>` documentation to modify the points for each stage.

package/payload/skills/odoo18-docs/references/docs/applications/hr/referrals/reporting.md

@@ -0,0 +1,89 @@
+---
+title: "Reporting"
+source_url: "https://docs.odoo.sbggai.top/applications/hr/referrals/reporting.html"
+---
+
+=========
+# Reporting
+
+The reporting function in the **Referrals** app helps recruiters and managers learn where applicants
+are applying from, when referred by a current employee. Additionally, the reporting feature shows
+the number of applicants hired, refused, and still in the recruitment pipeline, for each medium.
+
+> **important**:
+>    Only users with *Administrator* rights for the **Recruitment** app have access to the reporting
+   feature in the **Referrals** app.
+
+# Employees referral analysis report
+
+To access the *Employees Referral Analysis* report, navigate to :menuselection:`Referrals app -->
+Reporting`. This loads the :guilabel:`Employees Referral Analysis` report, in a default
+:icon:`fa-bar-chart` :guilabel:`Bar Chart`.
+
+The graph is presented in a :icon:`fa-database` :guilabel:`Stacked` view, with the number of
+referrals on the y-axis, and the source, referred to as the :guilabel:`Medium`, of the applicant
+(e.g.: *Facebook*, *LinkedIn*, *Email*, etc.) on the x-axis. If a medium does **not** appear on the
+report, that indicates there are no referrals from that particular medium.
+
+Referral amounts for all stages are displayed, including :guilabel:`Not Hired` (refused),
+:guilabel:`In Progress`, and :guilabel:`Hired`. The default filter is set to the current month.
+
+Hover over any bar to view a popover containing specific data for that particular bar.
+
+In this view, it is easy to see which :guilabel:`Medium` is the most successful.
+
+.. example::
+   In this example, both :guilabel:`Email` and :guilabel:`LinkedIn` are the mediums with the most
+   referrals, but :guilabel:`Email` has the most referrals that were hired.
+
+   .. image:: reporting/employee-report.png
+      :align: center
+      :alt: The default report in the Referrals app.
+
+## Use case: hired referrals
+
+One way to use the reporting feature is to assess which employees are referring the highest quality
+applicants. This is done by examining how many of their referrals go on to become employees.
+
+In this example, data is examined to determined which employee has the highest number of hired
+referrals for the current year.
+
+To view this information, first click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the
+upper-right corner. Next, remove the current filter in the search bar.
+
+Click the :icon:`fa-caret-down` :guilabel:`(down arrow)` in the search bar to reveal a drop-down
+menu. Click :guilabel:`Date` in the :icon:`fa-filter` :guilabel:`Filters` column, revealing a
+drop-down menu of available time periods, and click the current year (in this example,
+:guilabel:`2024`).
+
+Next, click :guilabel:`Measures` :icon:`fa-caret-down`, then deselect :guilabel:`Earned Points` and
+:guilabel:`Employee Referral Refused` to hide those metrics. Click anywhere on the screen to close
+the drop-down menu.
+
+The information displayed shows how many total applicants each employee referred, and how many of
+those applicants were hired, for the current year.
+
+In this example, it can be determined that :guilabel:`Bob Wilson` is the most successful referrer,
+with three hired referrals, and nine total referred applicants. Additionally, :guilabel:`Mitchell
+Admin` has the lowest performance in terms of referrals, as he has only one applicant, and no hires.
+
+This information can be helpful to the recruitment team, so they can determine the most active
+referrers in the company, and who is the most successful in terms of hires.
+
+.. image:: reporting/employee-counts.png
+   :align: center
+   :alt: The customized report showing which employees have the most referrals and hires.
+
+> **tip**:
+>    The pivot table can be inserted into a new or existing :doc:`spreadsheet
+   <../../productivity/spreadsheet/insert>`, if desired.
+
+   To do so, click the :guilabel:`Insert in Spreadsheet` button right above the chart. A pop-up
+   window appears, asking which spreadsheet to insert the pivot chart into. Select the desired
+   spreadsheet or dashboard from the presented options. Alternatively, select :guilabel:`Blank
+   Spreadsheet` to create a new one.
+
+   Click :guilabel:`Confirm`, and the selected spreadsheet loads, with the new table in it.
+
+   The spreadsheet is stored in the *Documents* application. This application **must** be installed
+   to use the :guilabel:`Insert in Spreadsheet` option.