documentation/locale/he/LC_MESSAGES/hr.po

# SOME DESCRIPTIVE TITLE.
# Copyright (C) Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
# 
# Translators:
# yacov mosbacher <ymosba@gmail.com>, 2024
# Adi Sharashov <Adi@laylinetech.com>, 2024
# MichaelHadar, 2024
# Ha Ketem <haketem@gmail.com>, 2024
# ExcaliberX <excaliberx@gmail.com>, 2024
# דודי מלכה <Dudimalka6@gmail.com>, 2024
# Orel Nahmany, 2024
# Amit Spilman <amit@laylinetech.com>, 2024
# yael terner, 2024
# NoaFarkash, 2024
# Yihya Hugirat <hugirat@gmail.com>, 2024
# Martin Trigaux, 2024
# ZVI BLONDER <ZVIBLONDER@gmail.com>, 2024
# tomerlayline, 2024
# or balmas, 2025
# 
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-12-02 12:38+0000\n"
"PO-Revision-Date: 2024-03-30 23:40+0000\n"
"Last-Translator: or balmas, 2025\n"
"Language-Team: Hebrew (https://app.transifex.com/odoo/teams/41243/he/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: he\n"
"Plural-Forms: nplurals=3; plural=(n == 1 && n % 1 == 0) ? 0 : (n == 2 && n % 1 == 0) ? 1: 2;\n"

#: ../../content/applications/hr.rst:5
msgid "Human resources"
msgstr ""

#: ../../content/applications/hr/appraisals.rst:5
#: ../../content/applications/hr/appraisals.rst:52
msgid "Appraisals"
msgstr "הערכות"

#: ../../content/applications/hr/appraisals.rst:7
msgid ""
"In Odoo, the *Appraisals* application can be used to evaluate employee "
"performance on a recurring basis. Managers can evaluate the performance of "
"their employees, and also allow employees to do a self-assessment of their "
"own. Appraisals are customizable, and can be set for any kind of schedule "
"desired."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:12
msgid ""
"Appraisals give employees valuable feedback, including actionable goals to "
"work toward, and measurable skills to improve upon. Additionally, appraisals"
" may form the basis for raises, promotions, and other benefits."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:16
msgid ""
"Regular appraisals are good for both the employees and the company, since "
"they can accurately measure performance based on company goals, and show "
"employees where they need to improve."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:20
#: ../../content/applications/hr/attendances.rst:59
#: ../../content/applications/hr/attendances/kiosks.rst:22
#: ../../content/applications/hr/frontdesk.rst:15
#: ../../content/applications/hr/time_off.rst:30
msgid "Configuration"
msgstr "תצורה"

#: ../../content/applications/hr/appraisals.rst:22
msgid ""
"The :guilabel:`Configuration` menu in the *Appraisals* application is where "
"the settings can be configured, feedback templates can be edited, "
"frequencies can be set, evaluation scales can be managed, data for 360 "
"feedback can be stored, and goal tags can be viewed/created."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:27
#: ../../content/applications/hr/fleet.rst:13
#: ../../content/applications/hr/lunch.rst:15
#: ../../content/applications/hr/payroll.rst:15
#: ../../content/applications/hr/recruitment.rst:34
msgid "Settings"
msgstr "הגדרות"

#: ../../content/applications/hr/appraisals.rst:29
msgid ""
"To access the *Settings* menu, navigate to :menuselection:`Appraisals "
"application --> Configuration --> Settings`."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:33
msgid "Feedback templates"
msgstr ""

#: ../../content/applications/hr/appraisals.rst:35
msgid ""
"Feedback templates are form outlines used during an employee appraisal. Any "
"edits made to a template are, ultimately, reflected in the appraisals sent "
"to employees."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:38
msgid ""
"There are two default templates pre-configured in Odoo *Appraisals*: one for"
" employee feedback, and one for manager feedback. Each contains several "
"sections, along with questions, and brief explanations for how to respond to"
" the questions."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:42
msgid ""
"The :guilabel:`Employee Feedback Template` has the following sections: "
":guilabel:`My work`, :guilabel:`My future`, and :guilabel:`My feelings`."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:45
msgid ""
"The :guilabel:`Manager Feedback Template` has the following sections: "
":guilabel:`Feedback`, :guilabel:`Evaluation`, and :guilabel:`Improvements`."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:48
msgid ""
"Any desired changes to the default feedback templates can be made by making "
"changes directly in each template."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:54
msgid ""
"The :guilabel:`Appraisals` section of the settings menu determines the "
"frequency that appraisals are performed, and if it is possible to request "
"additional feedback."
msgstr ""

#: ../../content/applications/hr/appraisals.rst-1
msgid ""
"The appraisals sections with the timeline filled in and 360 feedback "
"enabled."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:64
msgid "Appraisals plans"
msgstr ""

#: ../../content/applications/hr/appraisals.rst:66
msgid ""
"By default, appraisals are pre-configured to be automatically created six "
"months after an employee is hired, with a second appraisal exactly six "
"months after that."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:69
msgid ""
"Once those two initial appraisals have been completed in the employee's "
"first year, following appraisals are only created once a year (every twelve "
"months)."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:72
msgid ""
"To modify this schedule, change the number of months in the blank fields "
"under the :guilabel:`Appraisals Plans` section."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:76
msgid ""
"If the :guilabel:`Appraisals Plans` section is modified, **all** empty "
":guilabel:`Next Appraisal Dates` are modified for **all** employees."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:80
#: ../../content/applications/hr/appraisals.rst:122
msgid "360 feedback"
msgstr ""

#: ../../content/applications/hr/appraisals.rst:82
msgid ""
"The :guilabel:`360 Feedback` option can be enabled to allow managers to "
"request feedback from other employees using a different survey form, at any "
"time, independent of the appraisal schedule."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:85
msgid ""
"Typically, managers ask for feedback from other people who work with an "
"employee they manage. This includes the employee's various managers, peers, "
"and direct reports."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:88
msgid ""
"To view the :guilabel:`360 Feedback` survey, click the :guilabel:`→ Internal"
" link` icon at the end of the :guilabel:`Default Template` field. The "
":guilabel:`360 Feedback` survey loads, and any desired changes to the survey"
" can be made."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:92
msgid ""
"For more information on how to edit a survey, refer to the "
":doc:`../marketing/surveys/create` document."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:96
msgid ""
"The :guilabel:`360 Feedback` form is a pre-configured survey within the "
"*Surveys* application. In order to use the :guilabel:`360 Feedback` option, "
"including the ability to edit the survey, the *Surveys* application **must**"
" be installed."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:101
msgid "Evaluation scale"
msgstr ""

#: ../../content/applications/hr/appraisals.rst:103
msgid ""
"On each employee appraisal form, final rating options appear by default. To "
"view and edit these options, navigate to :menuselection:`Appraisals "
"application --> Configuration --> Evaluation Scale`. This presents the "
"ratings in a list view."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:107
msgid ""
"The pre-configured ratings are :guilabel:`Needs Improvement`, "
":guilabel:`Meets Expectations`, :guilabel:`Exceeds Expectations`, and "
":guilabel:`Strongly Exceeds Expectations`. To add another rating, click the "
":guilabel:`New` button."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:111
msgid ""
"When the :guilabel:`New` button is clicked on the :guilabel:`Evaluation "
"Scale` page, a blank line appears at the bottom of the list. Enter the name "
"of the rating in the field."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:114
msgid ""
"To rearrange the order of the ratings, click the :guilabel:`(six small gray "
"boxes)` icon to the left of a rating, and drag the rating to the desired "
"position on the list."
msgstr ""

#: ../../content/applications/hr/appraisals.rst-1
msgid ""
"The evaluation scale, with the new button and click and drag icons "
"highlighted."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:124
msgid ""
"The :guilabel:`360 Feedback` section displays information for all the "
"surveys currently configured in the *Appraisals* application. To view the "
"surveys, and their statistics, navigate to :menuselection:`Appraisals "
"application --> Configuration --> 360 Feedback`."
msgstr ""

#: ../../content/applications/hr/appraisals.rst-1
msgid "A list view of all available surveys in the Appraisals application."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:132
msgid ""
"Each appraisal (or survey) is presented in its own line on the "
":guilabel:`360 Feedback` page, along with various information related to "
"that particular appraisal."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:135
msgid "Each appraisal includes the following information:"
msgstr ""

#: ../../content/applications/hr/appraisals.rst:137
msgid ":guilabel:`Survey Name`: the name of the specific survey."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:138
msgid ""
":guilabel:`Responsible`: the employee responsible for the survey, including "
"the month and year they were given that designation."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:140
msgid ""
":guilabel:`Questions`: the number of questions in that particular survey."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:141
msgid ""
":guilabel:`Average Duration`: the average time a user spends completing the "
"survey."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:142
msgid ""
":guilabel:`Registered`: the number of people who have been sent the survey."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:143
msgid ""
":guilabel:`Completed`: the number of people who have completed the survey."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:145
msgid ""
"Each appraisal also has two buttons at the end of each line: a "
":guilabel:`Test` button and a :guilabel:`See Results` button."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:148
msgid ""
"To see what an appraisal looks like for the end user (i.e. an employee), "
"click the :guilabel:`Test` button, and the appraisal loads in a new browser "
"tab. The entire appraisal loads, and can be clicked through without having "
"to enter any answers."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:152
msgid ""
"To exit, close the tab. Or, click :guilabel:`This is a Test Survey. → Edit "
"Survey` at the top of the page to be taken to the detail form for that "
"particular survey."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:155
msgid ""
"To view the results from everyone who completed an appraisal, click the "
":guilabel:`See Results` button. This presents all the answers for the survey"
" in a new tab. Each question provides information on how many people "
"responded to a question, and how many people skipped it. All answers for "
"each question are visible."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:160
msgid ""
"To exit, close the tab. Or, click :guilabel:`→ Edit Survey` at the top of "
"the page to be taken to the detail form for that particular survey."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:163
msgid ""
"In addition to viewing the responses from past appraisals and surveys, new "
"surveys can also be created from the :guilabel:`360 Feedback` page. Simply "
"click the :guilabel:`New` button in the top-left of the page to create a new"
" survey."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:167
msgid ""
"For more information on how to create a survey, refer to the "
":doc:`../marketing/surveys/create` document."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:171
msgid ""
"In previous versions of Odoo, this section was referred to as "
":guilabel:`Surveys`."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:174
msgid ":doc:`appraisals/new_appraisals`"
msgstr ""

#: ../../content/applications/hr/appraisals.rst:175
msgid ":doc:`appraisals/goals`"
msgstr ""

#: ../../content/applications/hr/appraisals.rst:176
msgid ":doc:`appraisals/appraisal_analysis`"
msgstr ""

#: ../../content/applications/hr/appraisals.rst:177
msgid ":doc:`appraisals/skills_evolution`"
msgstr ""

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:3
msgid "Appraisal analysis"
msgstr ""

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:5
msgid ""
"The **Appraisals** app has the ability to report on all the appraisals in "
"the system, including past, present, and future appraisals, and their "
"respective statuses. This report helps managers track scheduled appraisals, "
"and identify any overdue or unconfirmed ones."
msgstr ""

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:9
msgid ""
"To access the *Appraisal Analysis* report, navigate to "
":menuselection:`Appraisals app --> Reporting --> Appraisal Analysis`."
msgstr ""

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:12
msgid ""
"On the :guilabel:`Appraisal Analysis` page, a report loads, displaying all "
"the appraisals in the database. Each entry is highlighted in a different "
"color to represent their status:"
msgstr ""

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:16
msgid "Color"
msgstr "צבע"

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:16
msgid "Status"
msgstr "סטטוס"

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:16
msgid "Meaning"
msgstr ""

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:18
msgid "Yellow"
msgstr "צהוב"

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:18
msgid ":guilabel:`Done`"
msgstr ""

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:18
msgid "The appraisal was completed."
msgstr ""

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:20
msgid "Orange"
msgstr "כתום"

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:20
msgid ":guilabel:`Appraisal Sent`"
msgstr ""

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:20
msgid "The appraisal was confirmed, but not completed."
msgstr ""

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:22
msgid "Red"
msgstr "אדום"

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:22
msgid ":guilabel:`Cancelled`"
msgstr ""

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:22
msgid "The appraisal was cancelled."
msgstr ""

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:24
msgid "Gray"
msgstr "אפור"

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:24
msgid ":guilabel:`To Start`"
msgstr ""

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:24
msgid "The appraisal was scheduled, but not confirmed."
msgstr ""

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:28
msgid ""
"Appraisals are scheduled automatically (appear in gray), according to their "
"respective :ref:`appraisals/appraisal-plan`."
msgstr ""

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:31
msgid ""
"The report displays the current year, in a default Gantt view, grouped by "
"department, with the current month highlighted."
msgstr ""

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:34
msgid ""
"To change the period of time that is presented, adjust the date settings in "
"the top-left corner of the report by clicking the default :guilabel:`Year` "
"to reveal a drop-down menu of options. The options to display are "
":guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, and :guilabel:`Year`. "
"Use the adjacent arrows to move forward or backward in time."
msgstr ""

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:39
msgid ""
"At any point, click the :guilabel:`Today` button to have the Gantt view "
"include today's date in the view."
msgstr ""

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:42
msgid ""
"To view the details of any appraisal, click on any appraisal. A pop-over "
"window appears, displaying the due date for the appraisal. To view more "
"details, click the :guilabel:`View` button, and further details appear in a "
"pop-up window."
msgstr ""

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:46
msgid ""
"The report can have other :ref:`filters <search/filters>` and "
":ref:`groupings <search/group>` set in the search bar at the top."
msgstr ""

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst-1
msgid "A report showing all the appraisals for the Appraisal Analysis report."
msgstr ""

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:56
msgid "Group by status"
msgstr ""

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:58
msgid ""
"When a company has a large number of employees, the default "
":guilabel:`Appraisal Analysis` report may display too much information to "
"view easily. In this scenario, viewing the data by status can be beneficial."
msgstr ""

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:62
msgid ""
"First, remove the default :icon:`oi-group` :guilabel:`Department` grouping "
"from the search bar. Next, click the :icon:`fa-caret-down` :guilabel:`(down "
"arrow)` icon in the far-right of the search bar. Click :guilabel:`Status` in"
" the :icon:`oi-group` :guilabel:`Group By` column. Click away from the drop-"
"down menu to close it."
msgstr ""

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:67
msgid ""
"All the appraisals are now organized by status, in the following order: "
":guilabel:`Cancelled`, :guilabel:`Done`, :guilabel:`To Start`, and "
":guilabel:`Appraisal Sent`."
msgstr ""

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:70
msgid ""
"This view makes it easy to see which appraisals need to be completed, and "
"when, as well as which appraisals still need to be confirmed."
msgstr ""

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst-1
msgid "A report showing all the appraisals, grouped by status."
msgstr ""

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:78
msgid "Use case: view only the user's appraisals"
msgstr ""

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:80
msgid ""
"When viewing the :guilabel:`Appraisal Analysis` report, it can save time to "
"only view the appraisals the signed-in user is responsible for, and hide the"
" rest."
msgstr ""

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:83
msgid ""
"To only view this data, click the :icon:`fa-caret-down` :guilabel:`(down "
"arrow)` icon in the far-right of the search bar, revealing a drop-down menu."
msgstr ""

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:87
msgid ""
"It is not necessary to remove the default :icon:`oi-group` "
":guilabel:`Department` grouping. If it remains active, the results are "
"grouped by department. If it is removed, the results appear in a list, "
"alphabetically."
msgstr ""

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:91
msgid ""
"Click :guilabel:`Add Custom Filter` at the bottom of the :icon:`fa-filter` "
":guilabel:`Filters` column, and a :guilabel:`Add Custom Filter` pop-up "
"window appears."
msgstr ""

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:94
msgid ""
"Click into the first field, and a pop-over appears with a variety of "
"options. Click the :icon:`fa-chevron-right` :guilabel:`(right arrow)` icon "
"after the word :guilabel:`Employee`, then scroll down and click on "
":guilabel:`Manager`. Next, set the middle field to :guilabel:`=` "
":guilabel:`(equal)`. Last, click the third field and select the desired user"
" from the list. When all the fields are set, click :guilabel:`Add`."
msgstr ""

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst-1
msgid "A customized filter to show only the user's employees."
msgstr ""

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:104
msgid ""
"Now, the only appraisals that appear are the appraisals that the selected "
"user is responsible for, instead of viewing *all* the appraisals."
msgstr ""

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:107
msgid ""
"This report can also be :ref:`grouped by status <appraisals/group-status>`."
msgstr ""

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst-1
msgid ""
"A report showing only the appraisals the user is responsible for, by status."
msgstr ""

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:114
#: ../../content/applications/hr/appraisals/skills_evolution.rst:102
msgid ":doc:`Odoo essentials reporting <../../essentials/reporting>`"
msgstr ""

#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:115
#: ../../content/applications/hr/appraisals/skills_evolution.rst:103
msgid ":doc:`../../essentials/search`"
msgstr ""

#: ../../content/applications/hr/appraisals/goals.rst:3
msgid "Goals"
msgstr "יעדים"

#: ../../content/applications/hr/appraisals/goals.rst:5
msgid ""
"The Odoo *Appraisals* application allows managers to set goals for their "
"employees. That way, employees know what to work toward before their next "
"review."
msgstr ""

#: ../../content/applications/hr/appraisals/goals.rst:8
msgid ""
"To view all goals, navigate to :menuselection:`Appraisals app --> Goals`. "
"This presents all the goals for every employee, in a default Kanban view."
msgstr ""

#: ../../content/applications/hr/appraisals/goals.rst:13
msgid "Each goal card contains the following information:"
msgstr ""

#: ../../content/applications/hr/appraisals/goals.rst:15
msgid ":guilabel:`Goal`: the name of the goal."
msgstr ""

#: ../../content/applications/hr/appraisals/goals.rst:16
msgid ":guilabel:`Employee`: the employee the goal is assigned to."
msgstr ""

#: ../../content/applications/hr/appraisals/goals.rst:17
msgid ""
":icon:`fa-clock-o` :guilabel:`(clock)` icon: displays the corresponding "
":doc:`activity icon <../../essentials/activities>` for the record. If no "
"activities are scheduled, the default icon is the :icon:`fa-clock-o` "
":guilabel:`(clock)`. If any activities have been scheduled, the icon "
"represents the activity scheduled soonest."
msgstr ""

#: ../../content/applications/hr/appraisals/goals.rst:21
msgid ":guilabel:`Deadline`: the due date for the goal."
msgstr ""

#: ../../content/applications/hr/appraisals/goals.rst:22
msgid ""
":guilabel:`Progress`: the percentage of competency set for the goal. The "
"options are :guilabel:`0%`, :guilabel:`25%`, :guilabel:`50%`, "
":guilabel:`75%`, or :guilabel:`100%`."
msgstr ""

#: ../../content/applications/hr/appraisals/goals.rst:24
msgid ""
":guilabel:`Employee Icon`: the profile icon of the employee the goal is "
"assigned to."
msgstr ""

#: ../../content/applications/hr/appraisals/goals.rst:26
msgid ""
"If a goal is completed, a :guilabel:`Done` banner appears in the top-right "
"corner of the goal card."
msgstr ""

#: ../../content/applications/hr/appraisals/goals.rst-1
msgid "The goals Kanban view, with nine goal cards."
msgstr ""

#: ../../content/applications/hr/appraisals/goals.rst:33
msgid ""
"Every individual goal requires its own record for each employee. If multiple"
" employees have the same goal, a goal card for each employee appears on the "
"list."
msgstr ""

#: ../../content/applications/hr/appraisals/goals.rst:36
msgid ""
"For example, if Bob and Sara have the same goal of `Typing`, two cards "
"appear in the Kanban view: one `Typing` goal for Bob, and another `Typing` "
"goal for Sara."
msgstr ""

#: ../../content/applications/hr/appraisals/goals.rst:40
msgid "New goal"
msgstr ""

#: ../../content/applications/hr/appraisals/goals.rst:42
msgid ""
"To create a new goal, navigate to :menuselection:`Appraisals app --> Goals`,"
" and click :guilabel:`New` top-left corner to open a blank goal form."
msgstr ""

#: ../../content/applications/hr/appraisals/goals.rst:45
msgid ""
"Input the :guilabel:`Goal`, :guilabel:`Employee`, :guilabel:`Progress`, and "
":guilabel:`Deadline`, information on the goal card, as discussed in the "
":ref:`goal card <appraisals/goal-card>` section of this document."
msgstr ""

#: ../../content/applications/hr/appraisals/goals.rst:49
msgid ""
"The information requested is all the same information that appears on the "
"goal card in the Kanban view, with the addition of a :guilabel:`Tags` field "
"and a :guilabel:`Description` tab."
msgstr ""

#: ../../content/applications/hr/appraisals/goals.rst:53
msgid ""
"The *Appraisals* application does **not** have any pre-configured tags, so "
"all tags need to be added. To add a tag, enter the name of the tag on the "
"line, then click :guilabel:`Create \"(tag)\"`. Repeat this for all tags that"
" need to be added."
msgstr ""

#: ../../content/applications/hr/appraisals/goals.rst:57
msgid ""
"The current user populates the :guilabel:`Employee` field, by default, and "
"the :guilabel:`Manager` field populates with the manager set on the employee"
" profile."
msgstr ""

#: ../../content/applications/hr/appraisals/goals.rst:60
msgid ""
"Make any necessary changes to the form, and add any notes that might be "
"useful to clarify the goal in the :guilabel:`Description` tab."
msgstr ""

#: ../../content/applications/hr/appraisals/goals.rst-1
msgid "A goal form filled out for a Python skill, set to 50% proficiency."
msgstr ""

#: ../../content/applications/hr/appraisals/goals.rst:68
msgid "Completed goals"
msgstr ""

#: ../../content/applications/hr/appraisals/goals.rst:70
msgid ""
"When a goal has been met, it is important to update the record. A goal can "
"be marked as `Done` in one of two ways: from the main :guilabel:`Goals` "
"dashboard, or from the individual goal card."
msgstr ""

#: ../../content/applications/hr/appraisals/goals.rst:73
msgid ""
"To mark a goal as `Done` from the main :guilabel:`Goals` dashboard, click on"
" the :icon:`fa-ellipsis-v` :guilabel:`(vertical ellipsis)` icon in the top-"
"right of a goal card."
msgstr ""

#: ../../content/applications/hr/appraisals/goals.rst:77
msgid ""
"The :icon:`fa-ellipsis-v` :guilabel:`(vertical ellipsis)` icon **only** "
"appears when the mouse hovers over the top-right corner of a goal card."
msgstr ""

#: ../../content/applications/hr/appraisals/goals.rst:80
msgid ""
"Then, click :guilabel:`Mark as Done` from the resulting drop-down menu. A "
"green :guilabel:`Done` banner appears in the top-right corner of the goal "
"card."
msgstr ""

#: ../../content/applications/hr/appraisals/goals.rst:83
msgid ""
"To mark a goal as `Done` from the goal card itself, click on a goal card to "
"open that goal's form. Then, click the :guilabel:`Mark as Done` button in "
"the top-left of the form. When clicked, a green :guilabel:`Done` banner "
"appears in the top-right corner of the goal form."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:3
msgid "New appraisals"
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:5
msgid ""
"To create a new appraisal for an employee, first navigate to the main "
"*Appraisals* dashboard by opening the :menuselection:`Appraisals` app. The "
":guilabel:`Appraisals` dashboard is the default view."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:10
msgid "Appraisals dashboard"
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:12
msgid ""
"All appraisals are displayed on the dashboard in a default Kanban view, with"
" a list of groupings on the left side of the dashboard, including "
":guilabel:`COMPANY`, :guilabel:`DEPARTMENT`, and :guilabel:`STATUS`."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:16
msgid ""
"Click any grouping option to view appraisals for **only** the chosen "
"selection."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:19
msgid ""
"Only groupings with multiple selections appear in the list. For example, if "
"a database only has one company, the :guilabel:`COMPANY` grouping does "
"**not** appear, since there is no other company to select."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:23
msgid "Each appraisal card displays the following information:"
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:25
msgid "**Name**: the employee's name."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:26
msgid "**Department**: the department the employee is associated with."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:27
msgid ""
"**Company**: the company the employee works for. This only appears in a "
"multi-company database."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:28
msgid ""
"**Date**: the date the appraisal was requested, or is scheduled for in the "
"future."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:29
msgid ""
"**Activities**: any :doc:`activities <../../essentials/activities>` that are"
" scheduled for the appraisal, such as *Meetings* or *Phone Calls*."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:31
msgid ""
"**Manager**: the employee's manager, indicated by the profile icon in the "
"bottom-right corner of an appraisal card."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:33
msgid ""
"**Status banner**: the status of the appraisal. A banner appears if an "
"appraisal is marked as either *Canceled* or *Done*. If no banner is present,"
" that means the appraisal has not happened, or has not been scheduled yet."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:37
msgid ""
"To view the details of any appraisal, click on the card to open the "
"appraisal form."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst-1
msgid "The Appraisals dashboard with each appraisal in its own box."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:44
msgid "Create an appraisal"
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:46
msgid ""
"To create a new appraisal, click the :guilabel:`New` button in the upper-"
"left corner of the :guilabel:`Appraisals` dashboard. Doing so reveals a "
"blank appraisal form. After entering a name in the first blank field, "
"proceed to enter the following information on the form:"
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:50
msgid ""
":guilabel:`Manager`: select the employee's manager from the drop-down menu. "
"The manager is responsible for completing the *Manager's Feedback* section "
"of the appraisal. This field auto-populates after the employee is selected, "
"if they have a manager set on their employee profile."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:54
msgid ""
":guilabel:`Appraisal Date`: the current date is automatically entered in "
"this field. This field is automatically updated once the appraisal is "
"completed or cancelled, with the corresponding date of completion or "
"cancellation."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:57
msgid ""
":guilabel:`Department`: select the employee's department from the drop-down "
"menu. This field auto-populates after the employee is selected, if they have"
" a department set on their employee profile."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:60
msgid ""
":guilabel:`Company`: select the employee's company from the drop-down menu. "
"This field auto-populates after the employee is selected, if they have a "
"company set on their employee profile."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:65
msgid ""
"The only required fields for the appraisal form are the employee's name, the"
" :guilabel:`Manager`, and the :guilabel:`Company`."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:68
msgid ""
"Once the form is complete, click the :guilabel:`Confirm` button to confirm "
"the appraisal request."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:70
msgid ""
"Once confirmed, the employee receives an email stating that an appraisal was"
" requested, and is then prompted to schedule an appraisal date."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:73
msgid ""
"The status changes to :guilabel:`Confirmed`, and the :guilabel:`Employee's "
"Feedback` section of the :guilabel:`Appraisal` tab is grayed out. The "
"information in that section only appears after the self-assessment is "
"published by the employee. The :guilabel:`Final Rating` field also appears "
"once the appraisal request is confirmed."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:78
msgid ""
"If there are any existing appraisals for the employee, an "
":guilabel:`Appraisal` smart button appears at the top of the page, listing "
"the total number of appraisals there are for the employee."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:82
msgid "Ask for feedback"
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:84
msgid ""
"As part of the appraisal process, the manager can request feedback on an "
"employee from anyone in the company. Feedback is usually requested from co-"
"workers and other people who interact with, or work with, the employee. This"
" is to get a more well-rounded view of the employee, and aid in the "
"manager's overall assessment."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:89
msgid ""
"To request feedback, the appraisal **must** be confirmed. Once confirmed, an"
" :guilabel:`Ask Feedback` button appears at the top of the form."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:92
msgid ""
"When the :guilabel:`Ask Feedback` button is clicked, an :guilabel:`Ask "
"Feedback` email pop-up form appears, using the :guilabel:`Appraisal: Ask "
"Feedback` email template, which sends the :guilabel:`360 Feedback` survey."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:96
msgid ""
"Enter the employees being asked to complete the survey in the "
":guilabel:`Recipients` field. Multiple employees may be selected."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:99
msgid ""
"The email template has dynamic placeholders to personalize the message. Add "
"any additional text to the email, if desired."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:102
msgid "If required, an :guilabel:`Answer Deadline` can be added, as well."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:104
msgid ""
"If any attachments are needed, click the :icon:`fa-paperclip` "
":guilabel:`Attachments` button, and a file explorer window appears. Navigate"
" to the file(s), select them, then click :guilabel:`Open`."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:107
msgid "When the email is ready to send, click :guilabel:`Send.`"
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst-1
msgid "The email pop-up when requesting feedback from other employees."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:114
msgid "Appraisal form"
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:116
msgid ""
"Once an appraisal is confirmed, the next steps require the employee to fill "
"out the self-assessment, after which the manager completes their assessment."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:122
msgid "Employee's feedback"
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:124
msgid ""
"To complete their portion of feedback, employees should navigate to the main"
" :menuselection:`Appraisals application` dashboard, where the only entries "
"visible are appraisals for the employee, themselves, and/or anyone they "
"manage and have to provide manager feedback for."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:128
msgid ""
"Click on the appraisal to open the appraisal form. Enter responses in the "
":guilabel:`Employee's Feedback` section, under the :guilabel:`Appraisal` "
"tab."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:131
msgid ""
"When completed, click the :guilabel:`Not Visible to Manager` toggle (the "
"default setting once an appraisal is confirmed). When clicked, the toggle "
"changes to :guilabel:`Visible to Manager`."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst-1
msgid ""
"The feedback section for the employee with the toggle button highlighted."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:141
msgid "Manager's feedback"
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:143
msgid ""
"After the employee has completed the :guilabel:`Employee's Feedback` "
"section, under the :guilabel:`Appraisal` tab, it is time for the manager to "
"fill out the :guilabel:`Manager's Feedback` section."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:147
msgid ""
"The manager enters their responses in the fields in the :ref:`same manner as"
" the employee <appraisals/employee-feedback>`."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:150
msgid ""
"When the feedback section is completed, click the :guilabel:`Not Visible to "
"Employee` toggle (the default setting once an appraisal is confirmed). When "
"clicked, the toggle changes to :guilabel:`Visible to Employee`."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst-1
msgid ""
"The feedback section for both employees and managers. The toggle buttons are"
" highlighted."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:159
#: ../../content/applications/hr/recruitment/add-new-applicants.rst:167
msgid "Skills tab"
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:161
msgid ""
"Part of an appraisal is evaluating an employee's skills, and tracking their "
"progress over time. The :guilabel:`Skills` tab of the appraisal form auto-"
"populates with the skills from the :ref:`employee form <employees/skills>`, "
"once an appraisal is confirmed."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:165
msgid ""
"Each skill is grouped with like skills, and the :guilabel:`Skill Level`, "
":guilabel:`Progress`, and :guilabel:`Justification` are displayed for each "
"skill."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:168
msgid ""
"Update any skills, or add any new skills to the :guilabel:`Skills` tab."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:170
msgid ""
"If a skill level has increased, a reason for the improved rating can be "
"entered into the :guilabel:`Justification` field, such as `took a fluency "
"language test` or `received Javascript certification`."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:175
msgid ""
"Refer to the :ref:`Create a new employee <employees/skills>` document for "
"detailed instructions on adding or updating a skill."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:178
msgid ""
"After an appraisal is completed, and the skills have been updated, the next "
"time an appraisal is confirmed, the updated skills populate the "
":guilabel:`Skills` tab."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst-1
msgid "The skills tab of an appraisal form, all filled out."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:186
msgid ""
"The :guilabel:`Skills` tab can be modified **after** the employee and their "
"manager have met and discussed the employee's appraisal."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:189
msgid ""
"This is a common situation as the manager may not have all the necessary "
"information to properly assess and update the employee's skills before "
"meeting."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:193
msgid "Private Note tab"
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:195
msgid ""
"If managers want to leave notes that are only visible to other managers, "
"they can be entered in the :guilabel:`Private Note` tab. This can be done "
"before or after meeting with the employee to discuss the appraisal."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:199
msgid ""
"The employee being evaluated does **not** have access to this tab, and the "
"tab does **not** appear on their appraisal."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:203
msgid "Schedule a meeting"
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:205
msgid ""
"Once both portions of an appraisal are completed (the :ref:`employee "
"<appraisals/employee-feedback>` and :ref:`manager <appraisals/manager-"
"feedback>` feedback sections), it is time for the employee and manager to "
"meet and discuss the appraisal."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:209
msgid ""
"A meeting can be scheduled in one of two ways: either from the *Appraisals* "
"application dashboard, or from an individual appraisal card."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:212
msgid ""
"To schedule an appraisal from the dashboard of the *Appraisals* application,"
" first navigate to :menuselection:`Appraisals app --> Appraisals`."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:215
msgid ""
"Click the :icon:`fa-clock-o` :guilabel:`(clock)` icon, beneath the appraisal"
" date on the desired appraisal card, and a pop-up window appears. Then, "
"click :icon:`fa-plus` :guilabel:`Schedule an activity` to create an activity"
" from a :guilabel:`Schedule Activity` pop-up form that appears."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:219
msgid ""
"Select :guilabel:`Meeting` for the :guilabel:`Activity Type` from the drop-"
"down menu. Doing so causes the form to change, so only the "
":guilabel:`Activity Type` and :guilabel:`Summary` fields appear."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:223
msgid ""
"Enter a brief description in the :guilabel:`Summary` field of the "
":guilabel:`Schedule Activity` pop-up form, such as `Annual Appraisal for "
"(Employee)`."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:226
msgid ""
"Next, click the :guilabel:`Open Calendar` button. From the calendar page "
"that appears, navigate to, and double-click on, the desired date and time "
"for the meeting."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:229
msgid ""
"Doing so opens a :guilabel:`New Event` pop-up form. From this pop-up form, "
"make any desired modifications, such as designating a :guilabel:`Start` "
"time, or modifying the default :guilabel:`Title` to the meeting."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:233
msgid ""
"Add the appraisee in the :guilabel:`Attendees` section, and include anyone "
"else who should also be in the meeting, if necessary."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:236
msgid ""
"To make the meeting a video call, instead of an in-person meeting, click "
":icon:`fa-plus` :guilabel:`Odoo meeting`, and a :guilabel:`Videocall URL` "
"link appears in the field."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:239
msgid ""
"Once all the desired changes are complete, click :guilabel:`Save & Close`."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:241
msgid ""
"The meeting now appears on the calendar, and the invited parties are "
"informed, via email."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst-1
msgid ""
"The meeting form with all information entered for Ronnie Hart's annual "
"appraisal."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:247
msgid ""
"The other way to schedule a meeting is from the individual appraisal form. "
"To do this, navigate to the :menuselection:`Appraisal app` dashboard, then "
"click on an appraisal card."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:250
msgid ""
"Next, click on the :icon:`fa-calendar` :guilabel:`Meeting` smart button, and"
" the calendar loads. Follow the same directions above to create the meeting."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:253
msgid ""
"For more detailed information on how to schedule activities, refer to the "
":doc:`activities <../../essentials/activities>` documentation."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:257
msgid ""
"If no meetings are scheduled, the :guilabel:`Meeting` smart button reads "
":guilabel:`No Meeting`."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:260
msgid "Complete an appraisal"
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:262
msgid ""
"After the appraisal is complete, and both the manager and employee have met "
"to discuss the appraisal, the appraisal can be marked as *Done*. When "
"completed, click the :guilabel:`Mark as Done` button on the appraisal form, "
"located in the top-left corner."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:266
msgid ""
"Once the appraisal is marked as *Done*, the :guilabel:`Mark as Done` button "
"disappears, and a :guilabel:`Reopen` button appears."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:270
msgid ""
"Modifications are **not** possible once the appraisal is marked as done."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:272
msgid ""
"To make any changes to an appraisal that is marked as *Done*, click the "
":guilabel:`Reopen` button."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:275
msgid ""
"Then, click the :guilabel:`Confirm` button that appears, and make any "
"modifications needed. Once all modifications are complete, click the "
":guilabel:`Mark as Done` button again."
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:279
msgid ":doc:`../appraisals/goals`"
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:280
msgid ":doc:`../appraisals/appraisal_analysis`"
msgstr ""

#: ../../content/applications/hr/appraisals/new_appraisals.rst:281
msgid ":doc:`../appraisals/skills_evolution`"
msgstr ""

#: ../../content/applications/hr/appraisals/skills_evolution.rst:3
msgid "Skills evolution"
msgstr ""

#: ../../content/applications/hr/appraisals/skills_evolution.rst:5
msgid ""
"In Odoo's **Appraisals** app, it is possible to view employee's skills as "
"they progress over time in the :ref:`Skills Evolution <appraisals/identify-"
"skills-evolution>` report, also known as the *Appraisal Skills Report*."
msgstr ""

#: ../../content/applications/hr/appraisals/skills_evolution.rst:9
msgid ""
"Managers can use this to see who is achieving their various skill goals set "
"on their appraisals, who is meeting their skill deadlines, who has the "
"highest performance in terms of skill development, and more."
msgstr ""

#: ../../content/applications/hr/appraisals/skills_evolution.rst:13
msgid ""
"The *Skills Evolution* report also provides the ability to :ref:`search for "
"employees with specific skills <appraisals/identify-skills>` at certain "
"levels, which can be helpful for scenarios where specific skills are "
"required."
msgstr ""

#: ../../content/applications/hr/appraisals/skills_evolution.rst:20
msgid "Skills evolution report"
msgstr ""

#: ../../content/applications/hr/appraisals/skills_evolution.rst:22
msgid ""
"To access this *Skills Evolution* report, navigate to "
":menuselection:`Appraisals app --> Reporting --> Skills Evolution`."
msgstr ""

#: ../../content/applications/hr/appraisals/skills_evolution.rst:25
msgid ""
"Doing so reveals the :guilabel:`Appraisal Skills Report` page, which "
"displays a report of all skills, grouped by employee, in alphabetical order,"
" by default."
msgstr ""

#: ../../content/applications/hr/appraisals/skills_evolution.rst:29
msgid ""
"Skill levels are **only** updated after an appraisal is marked as done. Any "
"skill level changes from ongoing appraisals that have **not** been finalized"
" are **not** included in this report."
msgstr ""

#: ../../content/applications/hr/appraisals/skills_evolution.rst:32
msgid ""
"All the :guilabel:`Employee` lines are expanded, with all the various skill "
"types nested below. Each individual skill type is collapsed, by default. To "
"view the individual skills contained within a skill type, click anywhere on "
"the skill type line to expand the data."
msgstr ""

#: ../../content/applications/hr/appraisals/skills_evolution.rst:36
msgid "Each skill has the following information listed:"
msgstr ""

#: ../../content/applications/hr/appraisals/skills_evolution.rst:38
#: ../../content/applications/hr/attendances.rst:218
msgid ":guilabel:`Employee`: the name of the employee."
msgstr ""

#: ../../content/applications/hr/appraisals/skills_evolution.rst:39
msgid ":guilabel:`Skill Type`: the category the skill falls under."
msgstr ""

#: ../../content/applications/hr/appraisals/skills_evolution.rst:40
msgid ":guilabel:`Skill`: the specific, individual skill."
msgstr ""

#: ../../content/applications/hr/appraisals/skills_evolution.rst:41
msgid ""
":guilabel:`Previous Skill Level`: the level the employee had previously "
"achieved for the skill."
msgstr ""

#: ../../content/applications/hr/appraisals/skills_evolution.rst:42
msgid ""
":guilabel:`Previous Skill Progress`: the previous percentage of competency "
"achieved for the skill (based on the :guilabel:`Skill Level`)."
msgstr ""

#: ../../content/applications/hr/appraisals/skills_evolution.rst:44
msgid ""
":guilabel:`Current Skill Level`: the current level the employee has achieved"
" for the skill."
msgstr ""

#: ../../content/applications/hr/appraisals/skills_evolution.rst:45
msgid ""
":guilabel:`Current Skill Progress`: the current percentage of competency "
"achieved for the skill."
msgstr ""

#: ../../content/applications/hr/appraisals/skills_evolution.rst:46
msgid ""
":guilabel:`Justification`: any notes entered on the skill, explaining the "
"progress."
msgstr ""

#: ../../content/applications/hr/appraisals/skills_evolution.rst:48
msgid ""
"The color of the skill text indicates any changes from the previous "
"appraisal. Skill levels that have increased since the last appraisal appear "
"in green, as an *Improvement*. Skill levels that have **not** changed appear"
" in black, as *No Change*. Skills that have regressed appear in red, as "
"*Regression*."
msgstr ""

#: ../../content/applications/hr/appraisals/skills_evolution.rst:53
msgid ""
"This report can be modified to find specific information by adjusting the "
":ref:`filters <search/filters>` and :ref:`groupings <search/group>` set in "
"the search bar at the top."
msgstr ""

#: ../../content/applications/hr/appraisals/skills_evolution.rst-1
msgid "A report showing all the skills grouped by employee."
msgstr ""

#: ../../content/applications/hr/appraisals/skills_evolution.rst:63
msgid "Use case: Identify employees with specific skills"
msgstr ""

#: ../../content/applications/hr/appraisals/skills_evolution.rst:65
msgid ""
"Since the :guilabel:`Appraisal Skills Report` organizes all skills by "
"employee, it can be difficult to find employees with a specific skill at a "
"specific level. To find these employees, a custom filter must be used."
msgstr ""

#: ../../content/applications/hr/appraisals/skills_evolution.rst:69
msgid ""
"In this example, the report is modified to show employees with an expert "
"level of Javascript knowledge. To view only those employees, first remove "
"all active filters in the search bar."
msgstr ""

#: ../../content/applications/hr/appraisals/skills_evolution.rst:72
msgid ""
"Next, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon in the "
"search bar, then click :guilabel:`Add Custom Filter` beneath the :icon:`fa-"
"filters` :guilabel:`Filters` column to load an :guilabel:`Add Custom Filter`"
" pop-up window."
msgstr ""

#: ../../content/applications/hr/appraisals/skills_evolution.rst:76
msgid ""
"Using the drop-down menu in the first field, select :guilabel:`Skill`. Then,"
" keep the second field as-is, and select :guilabel:`Javascript` from the "
"third drop-down menu in the third field."
msgstr ""

#: ../../content/applications/hr/appraisals/skills_evolution.rst:79
msgid ""
"Next, click :guilabel:`New Rule`, and another line appears. In this second "
"line, select :guilabel:`Current Skill Level` for the first drop-down field, "
"leave the second field as-is, then select :guilabel:`Expert` for the third "
"drop-down field."
msgstr ""

#: ../../content/applications/hr/appraisals/skills_evolution.rst:83
msgid ""
"After the :guilabel:`New Rule` button is clicked, the word "
":guilabel:`\"any\"` in the sentence :guilabel:`Match any of the following "
"rules:`, changes from plain text into a drop-down menu. Click the :icon:`fa-"
"caret-down` :guilabel:`(down arrow)` icon after the word :guilabel:`any`, "
"and select :guilabel:`all`."
msgstr ""

#: ../../content/applications/hr/appraisals/skills_evolution.rst:88
msgid "Finally, click the :guilabel:`Add` button."
msgstr ""

#: ../../content/applications/hr/appraisals/skills_evolution.rst-1
msgid "The Custom Filter pop-up with the parameters set."
msgstr ""

#: ../../content/applications/hr/appraisals/skills_evolution.rst:94
msgid ""
"Now, only employees that have an :guilabel:`Expert` level for the skill "
":guilabel:`Javascript` appear. In this example, only :guilabel:`Marc Demo` "
"meets these criteria."
msgstr ""

#: ../../content/applications/hr/appraisals/skills_evolution.rst-1
msgid "The employees with expert Javascript skills."
msgstr ""

#: ../../content/applications/hr/attendances.rst:5
msgid "Attendances"
msgstr "נוכחות"

#: ../../content/applications/hr/attendances.rst:7
msgid ""
"Odoo's *Attendances* application functions as a time clock. Employees are "
"able to check in and out of work using a dedicated device in kiosk mode, "
"while users are also able to check in and out of work directly from the "
"database. Managers can quickly see who is available at any given time, "
"create reports to see everyone's hours, and gain insights on which employees"
" are working overtime, or checking out of work earlier than expected."
msgstr ""

#: ../../content/applications/hr/attendances.rst:16
msgid "Access rights"
msgstr ""

#: ../../content/applications/hr/attendances.rst:18
msgid ""
"It is important to understand how the different access rights affect what "
"options and features users can access in the *Attendances* application."
msgstr ""

#: ../../content/applications/hr/attendances.rst:21
msgid ""
"Every user in the database is able to check in and out directly from the "
"database, without needing access to the *Attendances* application. "
"Additionally, all users can access their own attendance records from their "
"employee form in the *Employees* app."
msgstr ""

#: ../../content/applications/hr/attendances.rst:25
msgid ""
"Access to both the *Attendances* application, and the various features "
"within the application is determined by access rights."
msgstr ""

#: ../../content/applications/hr/attendances.rst:28
msgid ""
"To see what access rights a user has, navigate to the "
":menuselection:`Settings app --> Users & Companies: Users`, and click on an "
"individual user. The :guilabel:`Access Rights` tab is visible by default. "
"Scroll down to the :guilabel:`Human Resources` section to see the setting. "
"For the :guilabel:`Attendances` field, the options are either to leave the "
"field blank or select :guilabel:`Administrator`."
msgstr ""

#: ../../content/applications/hr/attendances.rst:34
msgid ""
"If the :guilabel:`Administrator` option is selected, the user has full "
"access to the entire *Attendances* application, with no restrictions. They "
"can view all employee attendance records, enter *Kiosk mMode* from the "
"application, access all reporting metrics, and make modifications to the "
"settings. If left blank, the user does **not** have access to the "
"*Attendances* application."
msgstr ""

#: ../../content/applications/hr/attendances.rst:42
msgid "Approvers"
msgstr "מאשרים"

#: ../../content/applications/hr/attendances.rst:44
msgid ""
"The **only** other scenario where different information may be accessible in"
" the *Attendances* application is for approvers. If a user does *not* have "
"administrative rights for the *Attendances* application, but they are set as"
" an employee's approver for the *Attendances* application, that user is able"
" to view the attendance records for that specific employee, as well as make "
"modifications to that employee's attendance records, if necessary. This "
"applies to all employees for whom the user is listed as the *Attendances* "
"application approver. Approvers are typically managers, though this is not "
"required."
msgstr ""

#: ../../content/applications/hr/attendances.rst:52
msgid ""
"To see who the attendance approver is for an employee, navigate to the "
":menuselection:`Employees application` and click on the specific employee. "
"Click on the :guilabel:`Work Information` tab, scroll to the "
":guilabel:`Approvers` section, and check the :guilabel:`Attendance` field. "
"The person selected is able to view that employees' attendance records, both"
" on the *Attendances* application dashboard as well as in the attendance "
"reports, and make modifications to their records."
msgstr ""

#: ../../content/applications/hr/attendances.rst:61
msgid ""
"Few configurations are needed in the *Attendances* application. Determining "
"how employees check in and out, defining how the kiosks function, and "
"determining how extra hours are computed are all set in the Configuration "
"menu. Navigate to the :menuselection:`Attendances application --> "
"Configuration` to access the configuration menu."
msgstr ""

#: ../../content/applications/hr/attendances.rst:67
msgid "Modes"
msgstr ""

#: ../../content/applications/hr/attendances.rst:69
msgid ""
":guilabel:`Attendances from Backend`: activate this selection to allow users"
" to check in and out directly from the Odoo database. If this is not "
"activated, users must use a kiosk to check in and out of work."
msgstr ""

#: ../../content/applications/hr/attendances.rst:74
msgid "Extra hours"
msgstr ""

#: ../../content/applications/hr/attendances.rst:76
msgid ""
"This section specifies how extra time is calculated, including when extra "
"time is counted and what time is not logged."
msgstr ""

#: ../../content/applications/hr/attendances.rst:79
msgid ""
":guilabel:`Count of Extra Hours`: enable this box to allow employees to log "
"extra hours beyond their set working hours (sometimes referred to as "
"*overtime*). Activating this selection displays the following settings as "
"well. If this is not activated, no other configurations appear."
msgstr ""

#: ../../content/applications/hr/attendances.rst:83
msgid ""
":guilabel:`Start From`: the current date is automatically entered in this "
"field. If desired, click on this field and use the calendar selector to "
"modify the start date on which extra hours are logged."
msgstr ""

#: ../../content/applications/hr/attendances.rst:86
msgid ""
":guilabel:`Tolerance Time In Favor Of Company`: enter the amount of time, in"
" minutes, that is **not** counted towards an employee's overtime. When an "
"employee checks out, and the extra time logged is below the specified "
"minutes, the extra time is **not** counted as overtime for the employee."
msgstr ""

#: ../../content/applications/hr/attendances.rst:90
msgid ""
":guilabel:`Tolerance Time In Favor Of Employee`: enter the amount of time, "
"in minutes, that an employee is given, that does **not** adversely affect "
"their attendance if they log less time than their working hours. When an "
"employee checks out, and the total time logged for the day is less than "
"their specified working hours and less than this specified grace period, "
"they are **not** penalized for their reduced hours."
msgstr ""

#: ../../content/applications/hr/attendances.rst:97
msgid ""
"A company sets both of the :guilabel:`Tolerance` fields to `15` minutes, and"
" the working hours for the entire company are set from 9:00 AM to 5:00 PM."
msgstr ""

#: ../../content/applications/hr/attendances.rst:100
msgid ""
"If an employee checks in at 9:00 AM, and checks out at 5:14 PM, the extra 14"
" minutes are **not** counted towards their overtime."
msgstr ""

#: ../../content/applications/hr/attendances.rst:103
msgid ""
"If an employee checks in at 9:05 AM, and checks out at 4:55 PM, even though "
"they logged a total of 10 minutes less than their full working hours, they "
"are **not** penalized for this discrepancy."
msgstr ""

#: ../../content/applications/hr/attendances.rst:107
msgid ""
":guilabel:`Display Extra Hours`: activate this box to display the extra "
"hours logged by an employee when they check out with a kiosk, or when a user"
" checks out in the database."
msgstr ""

#: ../../content/applications/hr/attendances.rst:111
msgid ""
"Employees are still able to log overtime hours even if the :guilabel:`Count "
"of Extra Hours` option is not activated. The difference is that when "
":guilabel:`Count of Extra Hours` is activated, the extra hours can be "
":ref:`deducted from an approved time off request <time_off/deduct-extra-"
"hours>`."
msgstr ""

#: ../../content/applications/hr/attendances.rst:117
#: ../../content/applications/hr/time_off.rst:467
msgid "Overview"
msgstr "סקירה כללית"

#: ../../content/applications/hr/attendances.rst:119
msgid ""
"When entering the *Attendances* application, the :guilabel:`Overview` "
"dashboard is presented, containing all the check in and check out "
"information for the signed in user. If the user has specific :ref:`access "
"rights <attendances/access-rights>` and/or are :ref:`approvers "
"<attendances/approvers>` for specific employees, then those additional "
"employee's check in and check out information is also visible on the "
":guilabel:`Overview` dashboard."
msgstr ""

#: ../../content/applications/hr/attendances.rst:126
msgid "Views"
msgstr "תצוגות"

#: ../../content/applications/hr/attendances.rst:128
msgid ""
"To change the view from the default Gantt chart to a list view, click the "
":guilabel:`List` icon in the top right of the dashboard, beneath the user's "
"photo. To switch back to the Gantt chart, click the :guilabel:`Gantt` "
"button, located next to the :guilabel:`List` button."
msgstr ""

#: ../../content/applications/hr/attendances.rst:132
msgid ""
"The default view presents the current day's information. To present the "
"information for the :guilabel:`Week`, :guilabel:`Month`, or "
":guilabel:`Year`, click on the :guilabel:`Day` button to reveal a drop-down,"
" displaying those other options. Select the desired view, and the dashboard "
"updates, presenting the selected information. To change the :guilabel:`Day`,"
" :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` presented, click "
"the :guilabel:`← (left arrow)` or :guilabel:`→ (right arrow)` buttons on "
"either side of the drop-down menu. To jump back to a view containing the "
"current day, click the :guilabel:`Today` button. This refreshes the "
"dashboard, presenting information containing the current day's information."
msgstr ""

#: ../../content/applications/hr/attendances.rst:141
msgid ""
"In the :guilabel:`Day` view, the column for the current hour is highlighted "
"in yellow. If the :guilabel:`Week` or :guilabel:`Month` view is selected, "
"the column for the current day is highlighted. If the :guilabel:`Year` view "
"is selected, the current month is highlighted."
msgstr ""

#: ../../content/applications/hr/attendances.rst-1
msgid ""
"The overview dashboard presenting the information for the week, with the current day\n"
"highlighted."
msgstr ""

#: ../../content/applications/hr/attendances.rst:150
msgid ""
"Any entries that have errors appear in red, indicating they need to be "
"resolved by a user with the proper :ref:`access rights <attendances/access-"
"rights>` and/or are :ref:`approvers <attendances/approvers>` for the "
"employee(s) with the errors."
msgstr ""

#: ../../content/applications/hr/attendances.rst:157
msgid "Filters and groups"
msgstr ""

#: ../../content/applications/hr/attendances.rst:159
msgid ""
"To filter the results in the overview dashboard, or to present different "
"groups of information, click the :guilabel:`🔻 (triangle drop down)` button "
"in the right side of the :guilabel:`Search` bar above the dashboard, and "
"select one of the available :guilabel:`Filters` or :guilabel:`Group By` "
"options. There are several pre-configured filters and groups to choose from,"
" as well as an option to create custom ones."
msgstr ""

#: ../../content/applications/hr/attendances.rst:166
#: ../../content/applications/hr/payroll/reporting.rst:190
msgid "Filters"
msgstr "מסננים"

#: ../../content/applications/hr/attendances.rst:168
msgid "The default filters that can be selected are:"
msgstr ""

#: ../../content/applications/hr/attendances.rst:170
msgid ""
":guilabel:`My Attendances`: this filter only presents the user's attendance "
"data."
msgstr ""

#: ../../content/applications/hr/attendances.rst:171
msgid ""
":guilabel:`My Team`: this filter presents the attendance data for the user's"
" team."
msgstr ""

#: ../../content/applications/hr/attendances.rst:172
msgid ""
":guilabel:`At Work`: this filter displays the attendance data for everyone "
"currently checked in."
msgstr ""

#: ../../content/applications/hr/attendances.rst:173
msgid ""
":guilabel:`Errors`: this filter displays any entries with :ref:`errors "
"<attendances/errors>` that need to be resolved."
msgstr ""

#: ../../content/applications/hr/attendances.rst:175
msgid ""
":guilabel:`Check In`: this filter has a drop-down to further select a "
"specific time period. Select the desired time period from the options "
"presented, a specific month, quarter, or year."
msgstr ""

#: ../../content/applications/hr/attendances.rst:177
msgid ""
":guilabel:`Last 7 days`: this filter presents the attendance data for the "
"last seven days."
msgstr ""

#: ../../content/applications/hr/attendances.rst:178
msgid ""
":guilabel:`Add Custom Filter`: create a custom filter using the pop-up that "
"appears when this is selected."
msgstr ""

#: ../../content/applications/hr/attendances.rst:182
msgid "Groups"
msgstr "קבוצות"

#: ../../content/applications/hr/attendances.rst:184
msgid "The default groups that can be selected are:"
msgstr ""

#: ../../content/applications/hr/attendances.rst:186
msgid ""
":guilabel:`Check In`: this grouping presents a drop-down menu containing the"
" following time period options: :guilabel:`Year`, :guilabel:`Quarter`, "
":guilabel:`Month`, :guilabel:`Week`, and :guilabel:`Day`. Selected the time "
"period to display all the check-in information, grouped by the selected time"
" period."
msgstr ""

#: ../../content/applications/hr/attendances.rst:190
msgid ""
":guilabel:`Employee`: this group presents the attendance data organized by "
"employee."
msgstr ""

#: ../../content/applications/hr/attendances.rst:191
msgid ""
":guilabel:`Check Out`: this grouping presents a drop-down menu containing "
"the following time period options: :guilabel:`Year`, :guilabel:`Quarter`, "
":guilabel:`Month`, :guilabel:`Week`, and :guilabel:`Day`. Selected the time "
"period to display all the check-out information, grouped by the selected "
"time period."
msgstr ""

#: ../../content/applications/hr/attendances.rst:195
msgid ""
":guilabel:`Add Custom Group`: this option displays a drop-down menu with a "
"variety of options to group the attendance data by, including "
":guilabel:`City`, :guilabel:`Country`, :guilabel:`Mode`, and :guilabel:`IP "
"Address`."
msgstr ""

#: ../../content/applications/hr/attendances.rst:202
msgid "Attendance log details"
msgstr ""

#: ../../content/applications/hr/attendances.rst:204
msgid ""
"Odoo captures various time and location details when a user checks in and "
"out. The specific details provided are determined by the method the user "
"checked in and out."
msgstr ""

#: ../../content/applications/hr/attendances.rst:207
msgid ""
"To view the specific check in and/or check out details for an employee, "
"click on an individual entry in the overview dashboard."
msgstr ""

#: ../../content/applications/hr/attendances.rst:210
msgid ""
"A detailed attendance log for the user appears in a pop-up window. To close "
"the detailed attendance log, click the :guilabel:`Save & Close` button in "
"the bottom-left corner of the form."
msgstr ""

#: ../../content/applications/hr/attendances.rst:213
msgid "The detailed attendance log contains the following information:"
msgstr ""

#: ../../content/applications/hr/attendances.rst:216
msgid "Main details"
msgstr ""

#: ../../content/applications/hr/attendances.rst:219
msgid ":guilabel:`Check In`: the date and time the employee checked in."
msgstr ""

#: ../../content/applications/hr/attendances.rst:220
msgid ""
":guilabel:`Check Out`: the date and time the employee checked out. This only"
" appears if the employee has checked out."
msgstr ""

#: ../../content/applications/hr/attendances.rst:222
msgid ""
":guilabel:`Worked Hours`: the total amount of time the employee logged for "
"the day, in an hour and minute format (HH:MM). This value calculates all the"
" checks in and check outs for the day, if the employee checked in and out "
"multiple times."
msgstr ""

#: ../../content/applications/hr/attendances.rst:225
msgid ""
":guilabel:`Extra Hours`: any extra hours the employee logged that is beyond "
"their expected working hours."
msgstr ""

#: ../../content/applications/hr/attendances.rst:229
msgid "Check in/check out details"
msgstr ""

#: ../../content/applications/hr/attendances.rst:231
msgid ""
"The following information appears for both the :guilabel:`Check In` and "
":guilabel:`Check Out` sections."
msgstr ""

#: ../../content/applications/hr/attendances.rst:234
msgid ""
":guilabel:`Mode`: the method with which the attendance information was "
"gathered. :guilabel:`Systray` is displayed if the employee logged in and out"
" :ref:`directly from the database <attendances/check-in>`, "
":guilabel:`Manual` is displayed if the employee logged in and out "
":ref:`using an attendance kiosk <attendances/kiosk-mode-entry>`."
msgstr ""

#: ../../content/applications/hr/attendances.rst:238
msgid ""
":guilabel:`IP Address`: the IP address for the computer the employee used to"
" log in or out."
msgstr ""

#: ../../content/applications/hr/attendances.rst:239
msgid ""
":guilabel:`Browser`: the web browser the employee used to log in or out."
msgstr ""

#: ../../content/applications/hr/attendances.rst:240
msgid ""
":guilabel:`Localization`: the city and country associated with the "
"computer's IP address."
msgstr ""

#: ../../content/applications/hr/attendances.rst:241
msgid ""
":guilabel:`GPS Coordinates`: the specific coordinates when the user logged "
"in or out. To view the specific coordinates on a map, click the :guilabel:`→"
" View on Maps` button beneath the :guilabel:`GPS Coordinates`. This opens a "
"map in a new browser tab, with the specific location pointed out."
msgstr ""

#: ../../content/applications/hr/attendances.rst-1
msgid "The detailed information for an attendance entry."
msgstr ""

#: ../../content/applications/hr/attendances.rst:251
#: ../../content/applications/hr/lunch/orders.rst:84
msgid "Errors"
msgstr ""

#: ../../content/applications/hr/attendances.rst:253
msgid ""
"Entries that contain an error appear on the overview dashboard in red. In "
"the :guilabel:`Gantt view`, the entry appears with a red background. If in "
"the :guilabel:`List view`, the entry text appears in red."
msgstr ""

#: ../../content/applications/hr/attendances.rst:257
msgid ""
"An error typically occurs when an employee has checked in but has not "
"checked out within the last 24 hours, or when an employee has a check in and"
" check out period spanning over 16 hours."
msgstr ""

#: ../../content/applications/hr/attendances.rst:260
msgid ""
"To fix the error, the attendance entry must be modified or deleted. Click on"
" the entry to reveal a pop-up containing the details for that particular "
"entry. To modify the :guilabel:`Check In` and/or :guilabel:`Check Out` "
"information, click on the :guilabel:`Check In` or :guilabel:`Check Out` "
"field and a calendar selector appears. Click on the desired date, then use "
"the time selector beneath the calendar to select the specific time for the "
"entry. When the information is correct, click :guilabel:`Apply.`"
msgstr ""

#: ../../content/applications/hr/attendances.rst-1
msgid ""
"The pop-up that allows for modifications to an attendance entry with an error. The calendar\n"
"selector is shown, and the time selector is highlighted."
msgstr ""

#: ../../content/applications/hr/attendances.rst:272
msgid ""
"When all the information on the pop-up is correct, click :guilabel:`Save & "
"Close`. When the entry no longer has an error, the entry appears in gray "
"instead of red."
msgstr ""

#: ../../content/applications/hr/attendances.rst:275
msgid ""
"To delete an entry, click :guilabel:`Remove` on the pop-up instead of making"
" modifications to the entry."
msgstr ""

#: ../../content/applications/hr/attendances.rst:279
#: ../../content/applications/hr/frontdesk.rst:210
#: ../../content/applications/hr/payroll/reporting.rst:3
#: ../../content/applications/hr/referrals/reporting.rst:3
#: ../../content/applications/hr/time_off.rst:511
msgid "Reporting"
msgstr "דו\"חות"

#: ../../content/applications/hr/attendances.rst:281
msgid ""
"To view attendance reports, click :guilabel:`Reporting` in the top menu. The"
" default report displays each employee's attendance information for the past"
" 3 months, in a :guilabel:`Line Chart`."
msgstr ""

#: ../../content/applications/hr/attendances.rst:284
msgid ""
"The default view is a :guilabel:`Graph`. To view the data in a pivot table, "
"click the :guilabel:`Pivot Table` button on the top right of the report. To "
"switch back to the graph view, click the :guilabel:`Graph` button, located "
"next to the :guilabel:`Pivot Table` button."
msgstr ""

#: ../../content/applications/hr/attendances.rst:288
msgid ""
"To present different information, adjust the :ref:`filters and groups "
"<attendances/filters-groups>` in the same way as in the :guilabel:`Overview`"
" dashboard."
msgstr ""

#: ../../content/applications/hr/attendances.rst:291
msgid ""
"The data can be presented in either a :guilabel:`Bar Chart`, :guilabel:`Line"
" Chart`, :guilabel:`Pie Chart`, :guilabel:`Stacked` chart, or in "
":guilabel:`Descending` or :guilabel:`Ascending` order. To change the view to"
" any of these charts, click the corresponding button above the displayed "
"chart."
msgstr ""

#: ../../content/applications/hr/attendances.rst:295
msgid ""
"To change the :guilabel:`Measures`, click the :guilabel:`Measures` button "
"and select the desired measure from the drop-down menu."
msgstr ""

#: ../../content/applications/hr/attendances.rst:298
msgid ""
"The report can also be inserted into a spreadsheet. Click the "
":guilabel:`Insert in Spreadsheet` button and a pop-up appears. Select the "
"desired spreadsheet, and click :guilabel:`Confirm`."
msgstr ""

#: ../../content/applications/hr/attendances.rst-1
msgid ""
"The default report view, with all the optional view buttons highlighted."
msgstr ""

#: ../../content/applications/hr/attendances.rst:306
msgid ":doc:`attendances/check_in_check_out`"
msgstr ""

#: ../../content/applications/hr/attendances.rst:307
msgid ":doc:`attendances/kiosks`"
msgstr ""

#: ../../content/applications/hr/attendances.rst:308
msgid ":doc:`attendances/hardware`"
msgstr ""

#: ../../content/applications/hr/attendances/check_in_check_out.rst:3
msgid "Check in and out"
msgstr ""

#: ../../content/applications/hr/attendances/check_in_check_out.rst:5
msgid ""
"Odoo's *Attendances* application allows users, who are logged into the "
"database, to check in and out, without needing to go into the *Attendances* "
"application, or use a kiosk. For smaller companies, where every employee is "
"also a user, this feature may be useful."
msgstr ""

#: ../../content/applications/hr/attendances/check_in_check_out.rst:9
msgid ""
"A user can check in and/or out on the main database Odoo dashboard, or while"
" inside any application. To do so, in the upper-right corner of the top main"
" header menu, which is always visible regardless of what application the "
"user is in, a :guilabel:`🔴 (red circle)` or :guilabel:`🟢 (green circle)` is "
"visible. Click on the colored circle to reveal the attendance widget, "
"enabling the user to check in and/or out."
msgstr ""

#: ../../content/applications/hr/attendances/check_in_check_out.rst-1
#: ../../content/applications/hr/attendances/check_in_check_out.rst-1
msgid "Top right main menu with check in button highlighted."
msgstr ""

#: ../../content/applications/hr/attendances/check_in_check_out.rst:22
msgid "Check in"
msgstr "כניסה"

#: ../../content/applications/hr/attendances/check_in_check_out.rst:24
msgid ""
"If the attendance widget circle is red, this indicates the user is not "
"currently checked in. Click the :guilabel:`🔴 (red circle)`, and the "
"attendance widget appears, displaying a green :guilabel:`Check in` "
":icon:`fa-sign-in` button."
msgstr ""

#: ../../content/applications/hr/attendances/check_in_check_out.rst:32
msgid ""
"When the user checks in from the database, the *Attendances* app logs the "
"location details for the user, including the IP Address and GPS coordinates."
msgstr ""

#: ../../content/applications/hr/attendances/check_in_check_out.rst:36
msgid ""
"For the *Attendances* app to log the location details, the user must allow "
"their computer to access their location information."
msgstr ""

#: ../../content/applications/hr/attendances/check_in_check_out.rst:39
msgid ""
"If the user has not already checked in and out during the current work day, "
"this button is the only visible item in the widget. If the user has "
"previously checked in and out, a :guilabel:`Total today` field appears above"
" the button, and the total amount of time that has been logged for the day "
"appears in that field, in an :guilabel:`HH:MM` (hours:minutes) format."
msgstr ""

#: ../../content/applications/hr/attendances/check_in_check_out.rst:44
msgid ""
"Click the :guilabel:`Check in` :icon:`fa-sign-in` button to check in. The "
":guilabel:`🔴 (red circle)` in the top menu changes to green, and the widget "
"changes appearance, as well. The widget updates to reflect that the user has"
" checked in, by changing the green :guilabel:`Check in` :icon:`fa-sign-in` "
"button to a yellow :guilabel:`Check out` :icon:`fa-sign-out` button."
msgstr ""

#: ../../content/applications/hr/attendances/check_in_check_out.rst:49
msgid "Click anywhere on the screen to close the attendance widget."
msgstr ""

#: ../../content/applications/hr/attendances/check_in_check_out.rst:52
#: ../../content/applications/hr/frontdesk/visitors.rst:148
msgid "Check out"
msgstr ""

#: ../../content/applications/hr/attendances/check_in_check_out.rst:54
msgid ""
"If the user is checking out for the first time, :guilabel:`Since HH:MM "
"(AM/PM)` appears at the top of the widget, with the time the user checked in"
" populating the time field. Beneath that line, the hours and minutes that "
"have elapsed since checking in are displayed in a :guilabel:`HH:MM` format. "
"As time passes, this value is updated to reflect the hours and minutes that "
"have passed since the user checked in."
msgstr ""

#: ../../content/applications/hr/attendances/check_in_check_out.rst:60
msgid ""
"If the user has previously checked in and out, additional fields are "
"presented. A :guilabel:`Before HH:MM (AM/PM)` field appears, in addition to "
"the :guilabel:`Since HH:MM (AM/PM)` field. The times displayed in both of "
"these fields match, and are populated with the most recent check in time. "
"Beneath the :guilabel:`Before HH:MM (AM/PM)` field, the previously logged "
"time is displayed, in an :guilabel:`HH:MM` (hours:minutes) format."
msgstr ""

#: ../../content/applications/hr/attendances/check_in_check_out.rst:66
msgid ""
"In addition, beneath both of these fields, a :guilabel:`Total today` field "
"appears. This field is the sum of both the :guilabel:`Before HH:MM (AM/PM)` "
"and :guilabel:`Since HH:MM (AM/PM)` fields, and is the total time that is "
"logged for the user, if they were to log out at that moment."
msgstr ""

#: ../../content/applications/hr/attendances/check_in_check_out.rst:70
msgid ""
"As time passes, both the :guilabel:`Since HH:MM (AM/PM)` and "
":guilabel:`Total today` fields are updated live. To check out, click the "
"yellow :guilabel:`Check out` :icon:`fa-sign-out` button. The attendance "
"widget updates again, displaying the :guilabel:`Total today` field with the "
"logged time, while the yellow :guilabel:`Check out` :icon:`fa-sign-out` "
"button changes to a green :guilabel:`Check in` :icon:`fa-sign-in` button."
msgstr ""

#: ../../content/applications/hr/attendances/check_in_check_out.rst:76
msgid ""
"When the user checks out from the database, the *Attendances* app logs the "
"location details for the user. This information is **only** logged if the "
"user allows their computer to access this information."
msgstr ""

#: ../../content/applications/hr/attendances/check_in_check_out.rst-1
msgid ""
"The pop-up that appears when an employee checks in inside the database."
msgstr ""

#: ../../content/applications/hr/attendances/check_in_check_out.rst:85
msgid ""
"There is no limit to the amount of times a user can check in and check out. "
"Users are able to check in and out without any time elapsing (a value of "
"00:00). Each time an employee logs in and out, the information is stored and"
" appears on the main *Attendances* dashboard, including check ins and check "
"outs with no time value."
msgstr ""

#: ../../content/applications/hr/attendances/hardware.rst:3
msgid "Hardware"
msgstr "חומרה"

#: ../../content/applications/hr/attendances/hardware.rst:5
msgid ""
"Employees who are **not** database users, and therefore, do **not** have "
"access to the *Attendances* app, must sign in and out of work using a kiosk."
" The following are the physical requirements for setting up a kiosk."
msgstr ""

#: ../../content/applications/hr/attendances/hardware.rst:10
msgid "Kiosk devices"
msgstr ""

#: ../../content/applications/hr/attendances/hardware.rst:12
msgid ""
"A kiosk is a self-service station, where employees can :ref:`check in and "
"out of work <attendances/kiosk-mode-entry>` with either a :ref:`badge "
"<attendances/hardware/badges>` or an :ref:`RFID key fob "
"<attendances/hardware/rfid>`. Typically, these devices are dedicated as "
"kiosks only, but any device with an internet browser is able to be set up as"
" a kiosk."
msgstr ""

#: ../../content/applications/hr/attendances/hardware.rst:17
msgid ""
"A kiosk is used by navigating to the webpage specified in the "
":ref:`configuration <attendances/kiosk-settings>` section of the "
"*Attendances* app."
msgstr ""

#: ../../content/applications/hr/attendances/hardware.rst:20
msgid "Kiosks are set up using one of the following types of devices:"
msgstr ""

#: ../../content/applications/hr/attendances/hardware.rst:22
msgid "Laptop or Desktop computer"
msgstr ""

#: ../../content/applications/hr/attendances/hardware.rst:23
msgid "Tablet"
msgstr ""

#: ../../content/applications/hr/attendances/hardware.rst:24
msgid "Mobile phone (Android or iOS)"
msgstr ""

#: ../../content/applications/hr/attendances/hardware.rst:27
msgid ""
"Touchscreens are easy to use, and tablets and mobile phones take up less "
"space. That's why most consider using a smaller device with a touchscreen as"
" a kiosk."
msgstr ""

#: ../../content/applications/hr/attendances/hardware.rst:30
msgid ""
"It is recommended to place kiosks on a secure stand, or mount them securely "
"on a wall."
msgstr ""

#: ../../content/applications/hr/attendances/hardware.rst:35
msgid "Badges"
msgstr "תגים"

#: ../../content/applications/hr/attendances/hardware.rst:37
msgid ""
"Badges are a way for employees to quickly sign in and out from a kiosk, as "
"badges are scanned by the kiosk's camera to quickly identify the employee."
msgstr ""

#: ../../content/applications/hr/attendances/hardware.rst:40
msgid ""
"To generate a badge, first navigate to the :menuselection:`Employees app`. "
"Next, click on the desired employee card to open the employee's form, then "
"click the :guilabel:`HR Settings` tab."
msgstr ""

#: ../../content/applications/hr/attendances/hardware.rst:43
msgid ""
"Under the :guilabel:`ATTENDANCE/POINT OF SALE/MANUFACTURING` section, there "
"is a :guilabel:`Badge ID` field. If this field is blank, click "
":guilabel:`Generate` at the end of the :guilabel:`Badge ID` line, and the "
"field is automatically populated with a new badge ID number. Then, click "
":guilabel:`Print Badge` at the end of the badge ID number to create a PDF "
"file of the badge."
msgstr ""

#: ../../content/applications/hr/attendances/hardware.rst:48
msgid ""
"If a badge ID number is already present on the employee form, there is no "
":guilabel:`Generate` button, only a :guilabel:`Print Badge` button."
msgstr ""

#: ../../content/applications/hr/attendances/hardware.rst:51
msgid ""
"The employee's badge contains the employee's photo, name, job position, "
"company logo, and a barcode that can be scanned at a kiosk to check in and "
"out."
msgstr ""

#: ../../content/applications/hr/attendances/hardware.rst:54
msgid ""
"Badges can be printed for employees using any thermal or inkjet printer."
msgstr ""

#: ../../content/applications/hr/attendances/hardware.rst-1
msgid "A badge for an employee that is created from the Employees app."
msgstr ""

#: ../../content/applications/hr/attendances/hardware.rst:61
msgid ""
"Badges are **not** required, as employees can manually identify themselves "
"on the kiosk."
msgstr ""

#: ../../content/applications/hr/attendances/hardware.rst:64
msgid "Barcode scanners"
msgstr ""

#: ../../content/applications/hr/attendances/hardware.rst:66
msgid ""
"When using badges to check in and out, the barcode **must** be scanned to "
"identify the employee. This can be done with the kiosk's camera, if one is "
"available on the device."
msgstr ""

#: ../../content/applications/hr/attendances/hardware.rst:69
msgid ""
"If a camera is **not** available on the kiosk device, an external barcode "
"scanner must be used to scan badges."
msgstr ""

#: ../../content/applications/hr/attendances/hardware.rst:72
msgid ""
"Kiosks work with most USB barcode scanners. Bluetooth barcode scanners are "
"also supported for devices without USB ports, or if a wireless connection is"
" desired."
msgstr ""

#: ../../content/applications/hr/attendances/hardware.rst:75
msgid ""
"Follow the manufacturer's instructions on the barcode scanner to properly "
"connect the barcode scanner to the kiosk device."
msgstr ""

#: ../../content/applications/hr/attendances/hardware.rst:79
msgid ""
"If the barcode scanner is connected directly to a computer, it :doc:`must be"
" configured <../../inventory_and_mrp/barcode/setup/hardware>` to use the "
"computer's keyboard layout."
msgstr ""

#: ../../content/applications/hr/attendances/hardware.rst:83
msgid "An IoT box is **not** required to use a barcode scanner."
msgstr ""

#: ../../content/applications/hr/attendances/hardware.rst:88
msgid "RFID key fob readers"
msgstr ""

#: ../../content/applications/hr/attendances/hardware.rst:90
msgid ""
"Instead of using a :ref:`badge <attendances/hardware/badges>`, employees can"
" scan a personal RFID key fob with an RFID reader to check in and out of "
"work."
msgstr ""

#: ../../content/applications/hr/attendances/hardware.rst:93
msgid ""
"It is **required** to purchase *both* RFID key fobs and an RFID reader to "
"use this method to check in and out. Follow the manufacturer's directions to"
" install the RFID reader, and set up the RFID key fob."
msgstr ""

#: ../../content/applications/hr/attendances/hardware.rst-1
msgid "An RFID key fob is placed on an RFID reader."
msgstr ""

#: ../../content/applications/hr/attendances/hardware.rst:103
msgid ""
"A recommended RFID reader is the `Neuftech USB RFID Reader "
"<https://neuftech.net/Neuftech-USB-RFID-Reader-ID-"
"Kartenleseger%C3%A4t-Kartenleser-Kontaktlos-Card-Reader-f%C3%BCr-EM4100>`_."
msgstr ""

#: ../../content/applications/hr/attendances/hardware.rst:107
msgid "An IoT box is **not** required to use RFID key fobs."
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:3
msgid "Kiosks"
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:5
msgid ""
"Odoo's *Attendances* app allows employees to check in and out of work "
"directly from the database, or from a kiosk."
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:8
msgid ""
"A kiosk is a :doc:`dedicated device <hardware>` (a PC, tablet, or mobile "
"phone) for employees to use when they check in and out."
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:11
msgid ""
"Kiosks are needed for employees who do **not** have access to the database."
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:13
msgid ""
"Only employees with access to the database can check in and out from the "
"*Attendances* app, and they are referred to as *users*."
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:17
msgid ""
"If employees :ref:`check in and out <attendances/kiosk-mode-entry>` using a "
"badge or an RFID, then an :doc:`accessible device <hardware>` in :ref:`Kiosk"
" Mode <attendances/kiosk-mode>` **must** be available in order to use these "
"two methods."
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:24
msgid ""
"There are only a few configurations needed to use kiosks in the "
"*Attendances* application. Navigate to :menuselection:`Attendances app --> "
"Configuration` to access the :guilabel:`Settings` page to configure the "
":ref:`attendances/kiosk-mode` and the :ref:`attendances/kiosk-settings`."
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:28
msgid ""
"Once all desired settings have been configured, click the :guilabel:`Save` "
"button on the :guilabel:`Settings` page, to activate and enable them."
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:34
msgid "Kiosk Mode section"
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:36
msgid ""
"Using the drop-down menu, select how an employee checks in when using a "
"kiosk. Options are :guilabel:`Barcode/RFID`, :guilabel:`Barcode/RFID and "
"Manual Selection`, or :guilabel:`Manual Selection`."
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:41
msgid ""
"The *Barcode* application **does not** need to be installed to use one of "
"the Barcode/RFID settings."
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:47
msgid "Kiosk Settings section"
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:49
msgid ""
"The various settings in the :guilabel:`Kiosk Settings` section determine how"
" employees check in and out with kiosks."
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:52
msgid ""
":guilabel:`Barcode Source`: this setting **only** appears if one of the two "
"*Barcode/RFID* selections were configured for the :ref:`Kiosk Mode "
"<attendances/kiosk-mode>` setting."
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:55
msgid ""
"If available, select how barcodes are scanned at the kiosk, via one of the "
"drop-down menu options. Barcodes can be scanned with a dedicated "
":guilabel:`Scanner`, or with a device's camera (:guilabel:`Front Camera` or "
":guilabel:`Back Camera`)."
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:58
msgid ""
":guilabel:`Employee PIN Identification`: tick this checkbox if employees "
"should use a unique PIN to check in. PINs are configured on each individual "
"employee record. Refer to the :ref:`new employee documentation "
"<employees/hr-settings>` documentation for more information on setting up "
"PINs."
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:62
msgid ""
":guilabel:`Display Time`: determine how many seconds a check-in/check-out "
"confirmation message remains on the kiosk screen before returning to the "
"main check in screen."
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:64
msgid ""
":guilabel:`Attendance Kiosk Url`: Odoo generates a unique web address (URL) "
"to use a device as a kiosk, without having to sign in to the Odoo database. "
"When setting up a kiosk device, navigate to this unique web address in a web"
" browser to present the *Attendances* app kiosk."
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:69
msgid ""
"These kiosk URLs are **not** secured with any type of access code. Anyone "
"who has the URL can access the *Attendances* app kiosk. If the URL is "
"compromised for any reason, such as in the event of a security breach, click"
" :guilabel:`Generate a new Kiosk Mode URL`, located beneath the link, to "
"generate a new URL, and update the kiosk, accordingly."
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:75
msgid "Kiosk mode"
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:77
msgid ""
"Entering *Kiosk Mode* is **only** available for users with specific "
":ref:`access rights <attendances/access-rights>`."
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:80
msgid "*Kiosk Mode* can be activated in two different ways:"
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:82
msgid ""
"Navigate to the :menuselection:`Attendances app`, and click :guilabel:`Kiosk"
" Mode` in the top menu. The device then signs out of Odoo and enters *Kiosk "
"Mode*."
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:84
msgid ""
"Navigate to the :menuselection:`Attendances app --> Configuration`. In the "
":guilabel:`Kiosk Settings` section, use the link in the "
":guilabel:`Attendance Kiosk Url` field to open *Kiosk Mode* on any device."
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst-1
msgid ""
"The Attendances Kiosk URL field in the settings section of the Attendances "
"application."
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:92
msgid ""
"As a security measure, once a device is in *Kiosk Mode*, it is not possible "
"to go back into the database without signing back in."
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:96
msgid ""
"At any time, a new kiosk URL can be generated, if needed. Click the "
":icon:`fa-refresh` :guilabel:`Generate a new Kiosk Mode URL`"
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:99
msgid ""
"To exit *Kiosk Mode*, just close the tab in the web browser or return to the"
" main log-in screen of Odoo."
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:105
msgid "Check in and out with a kiosk"
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:108
msgid "Badge"
msgstr "תג"

#: ../../content/applications/hr/attendances/kiosks.rst:110
msgid ""
"To check in or out using a badge, tap the :icon:`fa-camera` :guilabel:`Tap "
"to scan` image in the center of the kiosk."
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst-1
msgid "The Attendances Kiosk view displaying the scan badge image."
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:117
msgid ""
"Then, scan the barcode on the badge using the method configured in the "
":ref:`Kiosk Settings <attendances/kiosk-settings>` section of the "
"configuration menu."
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:120
msgid ""
"Once the barcode is scanned, the employee is checked in or out, and a "
":ref:`confirmation message <attendances/confirmation>` appears with all the "
"information."
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:124
msgid "RFID"
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:126
msgid ""
"To check in or out using an RFID key fob, simply scan the fob with an RFID "
"reader."
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:128
msgid ""
"Once scanned, the employee is either checked in or checked out, and a "
":ref:`confirmation message <attendances/confirmation>` appears with all the "
"information."
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:132
msgid "Manually"
msgstr "ידני"

#: ../../content/applications/hr/attendances/kiosks.rst:134
msgid ""
"Users who do not have a scannable badge, or an RFID fob, can manually check "
"in and out at a kiosk."
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:136
msgid ""
"Tap the :guilabel:`Identify Manually` button on the kiosk, and a screen "
"appears with all the employees that can be checked in or out. The "
"*Employees* application dashboard has the same display."
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:139
msgid ""
"Tap on a person to check them in or out, and a :ref:`confirmation message "
"<attendances/confirmation>` appears."
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:142
msgid "There are two ways to quickly find a specific person:"
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:144
msgid ""
":guilabel:`Search...`: tap on the :guilabel:`Search...` field, and enter the"
" desired person's name. As the name is typed in, the matching results are "
"displayed on the screen."
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:146
msgid ""
":guilabel:`Department`: tap on any desired selection in the "
":guilabel:`Department` section, located on the left-side of the screen, to "
"**only** view employees from that specific department. The number at the end"
" of each listed :guilabel:`Department` represents how many employees that "
"department has."
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:152
msgid "PIN"
msgstr "קוד סודי"

#: ../../content/applications/hr/attendances/kiosks.rst:154
msgid ""
"If the :guilabel:`Employee PIN Identification` checkbox was ticked in the "
":ref:`Kiosk Settings <attendances/kiosk-settings>` section of the "
"configuration menu, the employee is prompted to enter a PIN when manually "
"checking in or out."
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:158
msgid ""
"After the employee is selected, a number pad appears with a message. When "
"checking in, :guilabel:`(Employee) Welcome! Please enter your PIN to check "
"in` appears above the numbers. When checking out, :guilabel:`(Employee) Want"
" to check out? Please enter your PIN to check out` appears above the "
"numbers."
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:163
msgid ""
"Tap in the PIN using the number pad, then tap :guilabel:`OK` when done. The "
"employee is then checked in or out, and a :ref:`confirmation message "
"<attendances/confirmation>` appears."
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst-1
msgid "The pop-up that appears when prompted to enter a pin."
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:173
msgid "Confirmation message"
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:175
msgid ""
"When an employee checks in or out, a confirmation message appears, with all "
"the check in or check out information. When checking in, a welcome message "
"appears, as well as the date and time of check in."
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:179
msgid ""
"An :guilabel:`Hours Previously Today: HH:MM` field also appears, displaying "
"any time that has already been logged for that employee for the day. If no "
"time has been logged, the value displayed is: `00:00`. Beneath the message "
"is an :guilabel:`OK` button."
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:183
msgid ""
"To exit the screen before the preset time in the kiosk, tap the "
":guilabel:`OK` button."
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst:185
msgid ""
"When checking out, the screen displays a goodbye message, with the date and "
"time of check out, and the total hours logged for the day. Beneath the "
"message is a :guilabel:`Goodbye` button. To exit the screen before the "
"preset time, tap the :guilabel:`Goodbye` button."
msgstr ""

#: ../../content/applications/hr/attendances/kiosks.rst-1
msgid "The goodbye message with all the employee's check out information."
msgstr ""

#: ../../content/applications/hr/employees.rst:7
msgid "Employees"
msgstr "עובדים"

#: ../../content/applications/hr/employees.rst:9
msgid ""
"Odoo *Employees* organizes a company's employee records, contracts, and "
"departments."
msgstr ""

#: ../../content/applications/hr/employees/certifications.rst:3
msgid "Certifications"
msgstr "תעודות"

#: ../../content/applications/hr/employees/certifications.rst:5
msgid ""
"When jobs require specific knowledge, it is necessary to track employee "
"certifications to ensure the necessary knowledge and certifications are in "
"place."
msgstr ""

#: ../../content/applications/hr/employees/certifications.rst:8
msgid ""
"Certifications include classes, tests, professional seminars, and more. "
"There are no restrictions in terms of what type of certification records can"
" be added in Odoo."
msgstr ""

#: ../../content/applications/hr/employees/certifications.rst:12
msgid ""
"To access the *Employee Certifications* report, the **Surveys** app **must**"
" be installed."
msgstr ""

#: ../../content/applications/hr/employees/certifications.rst:15
msgid "View certifications"
msgstr ""

#: ../../content/applications/hr/employees/certifications.rst:17
msgid ""
"To view a full list of all employee certifications, navigate to "
":menuselection:`Employees app --> Reporting --> Certifications`."
msgstr ""

#: ../../content/applications/hr/employees/certifications.rst:20
msgid ""
"All certifications appear in a list view, grouped by employee. Each "
"certification entry displays the following:"
msgstr ""

#: ../../content/applications/hr/employees/certifications.rst:23
msgid ""
":guilabel:`Employee`: the employee's name, along with their avatar image."
msgstr ""

#: ../../content/applications/hr/employees/certifications.rst:24
msgid ":guilabel:`Name`: the title of the certification."
msgstr ""

#: ../../content/applications/hr/employees/certifications.rst:25
msgid ""
":guilabel:`Validity Start`: when the employee received the certification."
msgstr ""

#: ../../content/applications/hr/employees/certifications.rst:26
msgid ":guilabel:`Validity End`: when the certification expires."
msgstr ""

#: ../../content/applications/hr/employees/certifications.rst:27
msgid ""
":guilabel:`Certification`: the corresponding course in the **Surveys** app "
"that was completed by the employee, if applicable."
msgstr ""

#: ../../content/applications/hr/employees/certifications.rst:30
msgid ""
"The entries are also color-coded. Current certifications that are still "
"valid appear in black, expired certifications appear in red, and "
"certifications that are going to expire within the next 90 days appear in "
"orange."
msgstr ""

#: ../../content/applications/hr/employees/certifications.rst-1
msgid "The list of employee certifications."
msgstr ""

#: ../../content/applications/hr/employees/certifications.rst:39
msgid ""
"**Only** certification records with the *Display Type* set to "
"*Certification* on their :ref:`certification form <employees/certifications-"
"form>` appear on the :guilabel:`Employee Certifications` report. All other "
"certifications appear in the resume section of the :doc:`employee form "
"<new_employee>`."
msgstr ""

#: ../../content/applications/hr/employees/certifications.rst:45
msgid "View certifications by expiration status"
msgstr ""

#: ../../content/applications/hr/employees/certifications.rst:47
msgid ""
"When managing a large number of employees with a variety of certifications, "
"it can be difficult to determine which employees need to keep necessary "
"certifications current in the default list view. In this scenario, it is "
"beneficial to view the certifications by expiration status."
msgstr ""

#: ../../content/applications/hr/employees/certifications.rst:51
msgid ""
"To do so, navigate to :menuselection:`Employees app --> Reporting --> "
"Certifications`. Next, click the :icon:`fa-caret-down` :guilabel:`(down "
"arrow)` in the search bar, then click :guilabel:`Add Custom Group`, "
"revealing a drop-down menu. Click :guilabel:`Expiration Status`, then click "
"away from the drop-down menu to close it."
msgstr ""

#: ../../content/applications/hr/employees/certifications.rst:56
msgid ""
"After doing so, all the certifications are organized by status, starting "
"with :guilabel:`Expired` certifications, then certifications that are "
":guilabel:`Expiring` soon (within the next 90 days), and lastly, "
"certifications that are still :guilabel:`Valid`."
msgstr ""

#: ../../content/applications/hr/employees/certifications.rst:60
msgid ""
"This view provides an easy way to see which employees have certifications "
"that are going to expire soon, to determine which employees need to take "
"action to keep their certifications current."
msgstr ""

#: ../../content/applications/hr/employees/certifications.rst-1
msgid "The list of employee certifications, grouped by status."
msgstr ""

#: ../../content/applications/hr/employees/certifications.rst:70
msgid "Log a certification"
msgstr ""

#: ../../content/applications/hr/employees/certifications.rst:72
msgid ""
"To log a certification for an employee, navigate to "
":menuselection:`Employees app --> Reporting --> Certifications`. Click "
":guilabel:`New`, and a blank certification form loads. Enter the following "
"information on the form:"
msgstr ""

#: ../../content/applications/hr/employees/certifications.rst:76
msgid ""
":guilabel:`Title`: Enter a short description for the certification in this "
"field."
msgstr ""

#: ../../content/applications/hr/employees/certifications.rst:77
msgid ""
":guilabel:`Employee`: Using the drop-down menu, select the employee who "
"received the certification."
msgstr ""

#: ../../content/applications/hr/employees/certifications.rst:79
msgid ""
":guilabel:`Type`: Using the drop-down menu, select the type of certification"
" received. This field determines where on the employee's resume the "
"certification appears. To create a new :guilabel:`Type`, enter the type in "
"the field, then click :guilabel:`Create \"type\"`."
msgstr ""

#: ../../content/applications/hr/employees/certifications.rst:83
msgid "The default options are:"
msgstr ""

#: ../../content/applications/hr/employees/certifications.rst:85
msgid ""
":guilabel:`Experience`: Select this option to have the certification appear "
"in the *Experience* section of the *Resume* tab on the :doc:`employee form "
"<new_employee>`."
msgstr ""

#: ../../content/applications/hr/employees/certifications.rst:87
msgid ""
":guilabel:`Education`: Select this option to have the certification appear "
"in the *Education* section of the *Resume* tab on the :doc:`employee form "
"<new_employee>`."
msgstr ""

#: ../../content/applications/hr/employees/certifications.rst:89
msgid ""
":guilabel:`Internal Certification`: Select this option to have the "
"certification appear in the *Internal Certification* section of the *Resume*"
" tab on the :doc:`employee form <new_employee>`."
msgstr ""

#: ../../content/applications/hr/employees/certifications.rst:91
msgid ""
":guilabel:`Completed Internal Training`: Select this option to have the "
"certification appear in *Completed Internal Training* section of the "
"*Resume* tab on the :doc:`employee form <new_employee>`."
msgstr ""

#: ../../content/applications/hr/employees/certifications.rst:95
msgid ""
":guilabel:`Display Type`: Select the visibility of the certification in this"
" field. The default options are:"
msgstr ""

#: ../../content/applications/hr/employees/certifications.rst:98
msgid ""
":guilabel:`Classic`: Select this option to have the certification appear in "
"the *Resume* section of the employee form, and **not** appear on the "
"*Employee Certifications* report."
msgstr ""

#: ../../content/applications/hr/employees/certifications.rst:100
msgid ""
":guilabel:`Course`: Select this option to have the certification appear in "
"the *Resume* section of the employee form, and **not** appear on the "
"*Employee Certifications* report. Once this option is selected, a "
":guilabel:`Course` field appears beneath the :guilabel:`Display Type` field."
" Using the drop-down menu, select the course the employee took. The course "
"is created in the **Surveys** app."
msgstr ""

#: ../../content/applications/hr/employees/certifications.rst:105
msgid ""
":guilabel:`Certification`: Select this option to have the certification "
"appear in the *Resume* section of the employee form, **and** appear on the "
"*Employee Certifications* report. Once this is selected, a "
":guilabel:`Certification` field appears beneath the :guilabel:`Display Type`"
" field. Using the drop-down menu, select the certification the employee "
"took."
msgstr ""

#: ../../content/applications/hr/employees/certifications.rst:110
msgid ""
":guilabel:`Description`: Enter a description for the certification in this "
"field."
msgstr ""

#: ../../content/applications/hr/employees/certifications.rst:111
msgid ""
":guilabel:`Duration`: Click into the first field, and a calendar pop-over "
"window appears. Click on the start and end dates for the certification "
"validity period. When the correct dates are selected, click :icon:`fa-check`"
" :guilabel:`Apply`, and both fields are populated."
msgstr ""

#: ../../content/applications/hr/employees/certifications.rst-1
msgid ""
"A certification form filled out for an OSHA certificate for construction."
msgstr ""

#: ../../content/applications/hr/employees/departments.rst:3
msgid "Departments"
msgstr "מחלקות"

#: ../../content/applications/hr/employees/departments.rst:5
msgid ""
"All employees in the *Employees* app fall under specific departments within "
"a company."
msgstr ""

#: ../../content/applications/hr/employees/departments.rst:8
msgid "Create new departments"
msgstr ""

#: ../../content/applications/hr/employees/departments.rst:10
msgid ""
"To make a new department, navigate to :menuselection:`Employees app --> "
"Departments`, then click :guilabel:`New` in the top-left to reveal a blank "
"department form. Fill out the following information on the department form:"
msgstr ""

#: ../../content/applications/hr/employees/departments.rst-1
msgid "The department for with all fields filled out."
msgstr ""

#: ../../content/applications/hr/employees/departments.rst:18
msgid ":guilabel:`Department Name`: enter a name for the department."
msgstr ""

#: ../../content/applications/hr/employees/departments.rst:19
msgid ""
":guilabel:`Manager`: using the drop-down menu, select the department "
"manager."
msgstr ""

#: ../../content/applications/hr/employees/departments.rst:20
msgid ""
":guilabel:`Parent Department`: if the new department is housed within "
"another department (has a parent department), select the parent department "
"using the drop-down menu."
msgstr ""

#: ../../content/applications/hr/employees/departments.rst:22
msgid ""
":guilabel:`Custom Appraisal Templates`: if employees in this department "
"require a specific appraisal form that is different from the default "
"appraisal form, tick the checkbox. If this option is activated, an "
":guilabel:`Appraisal Templates` tab appears below the form. This field "
"**only** appears if the *Appraisals* app is installed."
msgstr ""

#: ../../content/applications/hr/employees/departments.rst:26
msgid ""
":guilabel:`Company`: using the drop-down menu, select the company the "
"department is part of."
msgstr ""

#: ../../content/applications/hr/employees/departments.rst:27
msgid ""
":guilabel:`Appraisal Survey`: using the drop-down menu, select the default "
"survey to use for the department when requesting feedback from employees. "
"This field **only** appears if the *Appraisals* app is installed, **and** "
"the *360 Feedback* option is enabled in the settings."
msgstr ""

#: ../../content/applications/hr/employees/departments.rst:30
msgid ""
":guilabel:`Color`: select a color for the department. Click the default "
"white color box to display all the color options. Click on a color to select"
" it."
msgstr ""

#: ../../content/applications/hr/employees/departments.rst:32
msgid ""
":guilabel:`Appraisal Templates` tab: this tab **only** appears if the "
":guilabel:`Custom Appraisal Templates` options is activated on the form. "
"Make any desired edits to the appraisal form. The appraisal form is used for"
" appraisals for all employees within this department."
msgstr ""

#: ../../content/applications/hr/employees/departments.rst:36
msgid ""
"After the form is completed, click the :icon:`fa-cloud-upload` "
":guilabel:`(cloud upload)` icon to manually save the changes. When saved, a "
":guilabel:`Department Organization` chart appears in the top-right of the "
"department card."
msgstr ""

#: ../../content/applications/hr/employees/departments.rst:41
msgid ""
"The form auto-saves while data is entered, however the :guilabel:`Department"
" Organization` chart does **not** appear until the form is manually saved. "
"If the form is not saved, the :guilabel:`Department Organization` chart is "
"visible upon opening the department card from the :guilabel:`Departments` "
"dashboard."
msgstr ""

#: ../../content/applications/hr/employees/departments.rst:47
msgid "Refer to the :doc:`../appraisals` documentation for more information."
msgstr ""

#: ../../content/applications/hr/employees/departments.rst:50
msgid "Departments dashboard"
msgstr ""

#: ../../content/applications/hr/employees/departments.rst:52
msgid ""
"To view the currently configured departments, navigate to "
":menuselection:`Employees app --> Departments`. All departments appear in a "
"Kanban view, by default, and are listed in alphabetical order."
msgstr ""

#: ../../content/applications/hr/employees/departments.rst-1
msgid ""
"The departments dashboard view with all the department cards in a Kanban "
"view."
msgstr ""

#: ../../content/applications/hr/employees/departments.rst:61
#: ../../content/applications/hr/fleet/accidents.rst:142
#: ../../content/applications/hr/fleet/service.rst:329
#: ../../content/applications/hr/recruitment.rst:174
msgid "Kanban view"
msgstr ""

#: ../../content/applications/hr/employees/departments.rst:63
msgid ""
"Each department has its own Kanban card on the main :guilabel:`Departments` "
":icon:`oi-view-kanban` :guilabel:`(Kanban)` dashboard view, that can display"
" the following information:"
msgstr ""

#: ../../content/applications/hr/employees/departments.rst:66
msgid "Department name: the name of the department."
msgstr ""

#: ../../content/applications/hr/employees/departments.rst:67
msgid "Company: the company the department is part of."
msgstr ""

#: ../../content/applications/hr/employees/departments.rst:68
msgid ":guilabel:`Employees`: the number of employees within the department."
msgstr ""

#: ../../content/applications/hr/employees/departments.rst:69
msgid ""
":guilabel:`Appraisals`: the number of appraisals scheduled for employees in "
"the department."
msgstr ""

#: ../../content/applications/hr/employees/departments.rst:70
msgid ""
":guilabel:`Time Off Requests`: the number of unapproved time off requests "
"for employees in the department :ref:`awaiting approval <time_off/manage-"
"time-off>` . This **only** appears if there are requests to approve."
msgstr ""

#: ../../content/applications/hr/employees/departments.rst:73
msgid ""
":guilabel:`Allocation Requests`: the number of unapproved allocation "
"requests for employees in the department :ref:`awaiting approval "
"<time_off/manage-allocations>`. This **only** appears if there are requests "
"to approve."
msgstr ""

#: ../../content/applications/hr/employees/departments.rst:76
msgid ""
":guilabel:`New Applicants`: the number of :ref:`new applicants "
"<recruitment/new>` for a position in this department. This **only** appears "
"if there are new applicants."
msgstr ""

#: ../../content/applications/hr/employees/departments.rst:78
msgid ""
":guilabel:`Expense Reports`: the number of employees in the department with "
":doc:`open expense reports to approve "
"<../../finance/expenses/approve_expenses>`. This **only** appears if there "
"are any expense reports waiting for approval."
msgstr ""

#: ../../content/applications/hr/employees/departments.rst:81
msgid ":guilabel:`Absence`: the number of absences for the current day."
msgstr ""

#: ../../content/applications/hr/employees/departments.rst:82
msgid ""
"Color bar: the selected color for the department appears as a vertical bar "
"on the left side of the department card."
msgstr ""

#: ../../content/applications/hr/employees/departments.rst:86
msgid ""
"Click on an alert in a department card, such as :guilabel:`Time Off "
"Requests`, to reveal a list view of the requests to approve. This list "
"includes **all** open requests to approve, not just from the specific "
"department."
msgstr ""

#: ../../content/applications/hr/employees/departments.rst:90
msgid ""
"The default view for the :guilabel:`Departments` dashboard is a Kanban view."
" It is possible to view the departments in two other forms: a list view and "
"a hierarchy view."
msgstr ""

#: ../../content/applications/hr/employees/departments.rst:94
#: ../../content/applications/hr/fleet/service.rst:302
msgid "List view"
msgstr ""

#: ../../content/applications/hr/employees/departments.rst:96
msgid ""
"To view the departments in a list view, click the :icon:`fa-align-justify` "
":guilabel:`(list)` icon in the top-right corner. The departments appear in a"
" list view, which displays the :guilabel:`Department Name`, "
":guilabel:`Company`, :guilabel:`Manager`, :guilabel:`Employees`, "
":guilabel:`Parent Department`, and :guilabel:`Color` for each department."
msgstr ""

#: ../../content/applications/hr/employees/departments.rst:101
msgid ""
"The departments are sorted alphabetically by :guilabel:`Department Name`, by"
" default."
msgstr ""

#: ../../content/applications/hr/employees/departments.rst-1
msgid "The departments presented in a list view."
msgstr ""

#: ../../content/applications/hr/employees/departments.rst:108
msgid ""
"When in list view, departments can be managed in batch by selecting one or "
"multiple record's checkbox, then select the :icon:`fa-cog` "
":guilabel:`Actions` button to reveal a drop-down menu of actions."
msgstr ""

#: ../../content/applications/hr/employees/departments.rst:113
msgid "Hierarchy view"
msgstr ""

#: ../../content/applications/hr/employees/departments.rst:115
msgid ""
"To view the departments in a hierarchy view, click the :icon:`fa-share-alt "
"fa-rotate-90` :guilabel:`(hierarchy)` icon in the top-right corner. The "
"departments appear in an organizational chart format, with the highest-level"
" department at the top (typically :guilabel:`Management`), and all other "
"departments beneath it. All child departments of the first-level child "
"departments are folded."
msgstr ""

#: ../../content/applications/hr/employees/departments.rst:121
msgid ""
"Each department card displays the :guilabel:`Department Name`, the "
":guilabel:`Manager` (and their profile image), the :guilabel:`Number of "
"Employees` in the department, and the ability to expand the department "
"(:guilabel:`Unfold`) if there are child departments beneath it."
msgstr ""

#: ../../content/applications/hr/employees/departments.rst:125
msgid ""
"Click the :guilabel:`Unfold` button on a department card to expand it. Once "
"expanded, the :guilabel:`Unfold` button changes to a :guilabel:`Fold` "
"button. To collapse the department, click the :guilabel:`Fold` button. Only "
"**one** department *per row* can be unfolded at a time."
msgstr ""

#: ../../content/applications/hr/employees/departments.rst:129
msgid ""
"Click anywhere on a department card to open the department form. Click the "
":guilabel:`(#) Employees` smart button to view a list of all the employees "
"in that department, including all employees in the child departments beneath"
" it, organized by individual department."
msgstr ""

#: ../../content/applications/hr/employees/departments.rst:134
msgid ""
"In the hierarchy view, if the :guilabel:`(2) Employees` button on the "
":guilabel:`Management` card is clicked (the highest-level department card), "
"**all** employees appear in a list view, grouped by department. This is "
"because **all** departments are children of the :guilabel:`Management` "
"department."
msgstr ""

#: ../../content/applications/hr/employees/departments.rst:139
msgid ""
"If the :guilabel:`(3) Employees` button in the :guilabel:`Sales` department "
"card is clicked, the employees from the :guilabel:`Sales` department, as "
"well as its two child departments (:guilabel:`East Coast Territory` and "
":guilabel:`West Coat Territory`), appear in the list."
msgstr ""

#: ../../content/applications/hr/employees/departments.rst:0
msgid "The departments presented in a hierarchy view."
msgstr ""

#: ../../content/applications/hr/employees/departments.rst:0
msgid ""
"The list view of employees for the department that was clicked, including all child\n"
"departments."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:3
msgid "New employees"
msgstr "עובדים חדשים"

#: ../../content/applications/hr/employees/new_employee.rst:5
msgid ""
"When a new employee is hired, the first step is to create a new employee "
"record. This record is a centralized place where all important information "
"about the employee is stored, including :ref:`general information "
"<employees/general-info>`, :ref:`job history and skills <employees/resume>`,"
" :ref:`various work information <employees/work-info-tab>`, :ref:`personal "
"details <employees/private-info>`, :ref:`documents <employees/docs>`, and "
"more."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:11
msgid ""
"To begin, open the :menuselection:`Employees` app, then click the "
":guilabel:`New` button in the upper-left corner. Doing so reveals a blank "
"employee form."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:14
msgid ""
"Proceed to fill out the required information, along with any additional "
"details."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst-1
msgid "Create a new employee form with all fields filled out."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:21
msgid ""
"The current company phone number and name are populated in the "
":guilabel:`Work Phone` and :guilabel:`Company` fields. If the *Appraisals* "
"application is installed, the :guilabel:`Next Appraisal Date` field is "
"populated with a date six months from the current date."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:28
#: ../../content/applications/hr/fleet/new_vehicle.rst:108
#: ../../content/applications/hr/fleet/service.rst:117
msgid "General information"
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:30
msgid ""
"The employee form automatically saves as data is entered. However, the form "
"can be saved manually at any time by clicking the :guilabel:`Save manually` "
"option, represented by a :guilabel:`(cloud with an upwards arrow)` icon."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:35
msgid "Required fields"
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:37
msgid ":guilabel:`Employee's Name`: enter the employee's name."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:38
msgid ""
":guilabel:`Company`: from the drop-down menu in this field, select the "
"company the new employee was hired by, or create a new company by typing the"
" name in the field, and clicking :guilabel:`Create` or :guilabel:`Create and"
" edit...` from the mini drop-down menu that appears."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst-1
msgid "A new employee form with the required fields highlighted."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:47
msgid "Optional fields"
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:49
msgid ""
":guilabel:`Photo`: in the top-right image box of the employee form, click on"
" the :guilabel:`✏️ (pencil)` edit icon to select a photo to upload."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:51
msgid ""
":guilabel:`Job Position`: enter the employee's job title under their name, "
"or select it from the :guilabel:`Job Position` field drop-down menu below to"
" have this top field auto-populate. The :guilabel:`Job Position` field under"
" the employee name can be modified, and does *not* need to match the "
"selection made in the :guilabel:`Job Position` drop-down menu in the field "
"below."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:57
msgid ""
"While it is recommended to have the job positions match, the typed-in "
"description in this top field can contain more specific information than the"
" selected drop-down :guilabel:`Job Position`, if desired."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:61
msgid ""
"For instance, if someone is hired for a sales representative position "
"configured as :guilabel:`Sales Representative` in the *Recruitment* app, "
"that can be selected in the drop-down :guilabel:`Job Position` field."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:65
msgid ""
"In the typed-in :guilabel:`Job Position` field beneath the "
":guilabel:`Employee's Name` field, the position could be more specific, such"
" as `Sales Representative - Subscriptions` if the employee is focused solely"
" on subscription sales."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:0
msgid "Both job position fields entered but with different information."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:73
msgid ""
":guilabel:`Tags`: select a tag from the drop-down menu to add relevant tags "
"to the employee. Any tag can be created in this field by typing it in. Once "
"created, the new tag is available for all employee records. There is no "
"limit to the amount of tags that can be added."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:76
msgid ""
":guilabel:`Work Contact Information`: enter the employee's :guilabel:`Work "
"Mobile`, :guilabel:`Work Phone`, :guilabel:`Work Email`, and/or "
":guilabel:`Company` name, if not already auto-populated."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:79
msgid ""
":guilabel:`Department`: select the employee's department from the drop-down "
"menu."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:80
msgid ""
":guilabel:`Job Position`: select the employee's job position from the drop-"
"down menu. Once a selection is made, the :guilabel:`Job Position` field "
"beneath the :guilabel:`Employee's Name` field automatically updates to "
"reflect the currently selected job position. These positions are from the "
":doc:`Recruitment <../../hr/recruitment/new_job/>` application, and reflect "
"the currently configured job positions."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:85
msgid ""
":guilabel:`Manager`: select the employee's manager from the drop-down menu."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:86
msgid ""
":guilabel:`Coach`: select the employee's coach from the drop-down menu."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:87
msgid ""
":guilabel:`Next Appraisal Date`: this field is **only** visible if the "
"*Appraisals* application is installed. The date automatically populates with"
" a date that is computed according to the settings configured in the "
"*Appraisals* application. This date can be modified using the calendar "
"selector."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:92
msgid ""
"After a :guilabel:`Manager` is selected, if the :guilabel:`Coach` field is "
"blank, the selected manager automatically populates the :guilabel:`Coach` "
"field."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:96
msgid ""
"To make edits to the selected :guilabel:`Department`, :guilabel:`Manager`, "
":guilabel:`Coach`, or :guilabel:`Company`, click the :guilabel:`Internal "
"Link` arrow next to the respective selection. The :guilabel:`Internal Link` "
"arrow opens the selected form, allowing for modifications. Click "
":guilabel:`Save` after any edits are made."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:102
msgid "Additional information tabs"
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:107
msgid "Resumé tab"
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:110
#: ../../content/applications/hr/payroll.rst:855
#: ../../content/applications/hr/recruitment/recruitment-flow.rst:38
msgid "Resumé"
msgstr "קורות חיים"

#: ../../content/applications/hr/employees/new_employee.rst:112
msgid ""
"Next, enter the employee's work history in the :guilabel:`Resumé` tab. Each "
"resumé line must be entered individually. When creating an entry for the "
"first time, click :guilabel:`Create a new entry`, and the :guilabel:`Create "
"Resumé lines` form appears. After an entry is added, the :guilabel:`Create a"
" new entry` button is replaced with an :guilabel:`Add` button. Enter the "
"following information for each entry."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst-1
msgid "A resumé entry form with all the information populated."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:122
msgid ":guilabel:`Title`: type in the title of the previous work experience."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:123
msgid ":guilabel:`Employee`: select the employee from the drop-down menu."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:124
msgid ""
":guilabel:`Type`: from the drop-down menu, select either "
":guilabel:`Experience`, :guilabel:`Education`, :guilabel:`Side Projects`, "
":guilabel:`Internal Certification`, :guilabel:`Completed Internal Training`,"
" or type in a new entry, then click :guilabel:`Create \"(Type)\"`."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:128
msgid ""
":guilabel:`Display Type`: from the drop-down menu, choose "
":guilabel:`Classic` for typical work experience, :guilabel:`Certification` "
"for experience gained through a certification, or :guilabel:`Course` for "
"non-certified classes."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:131
msgid ""
":guilabel:`Duration`: enter the start and end dates for the work experience."
" To select a date, click the first empty field to reveal a calendar pop-up "
"window. Proceed to use the :guilabel:`< (left arrow)` and :guilabel:`> "
"(right arrow)` icons to scroll to the desired month, then click on the day "
"to select it. Repeat this process to locate and select the end date. When "
"the desired dates have been selected, click :guilabel:`✔️ Apply`."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:136
msgid ":guilabel:`Description`: enter any relevant details in this field."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:138
msgid ""
"Once all the information is entered, click the :guilabel:`Save & Close` "
"button if there is only one entry to add, or click the :guilabel:`Save & "
"New` button to save the current entry and create another resumé line."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:143
msgid ""
"After the new employee form is saved, the current position and company is "
"automatically added to the :guilabel:`Resumé` tab, with the end date listed "
"as `current`."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:149
msgid "Skills"
msgstr "כישורים"

#: ../../content/applications/hr/employees/new_employee.rst:151
msgid ""
"An employee's skills can be entered in the :guilabel:`Resumé` tab in the "
"same manner that a resumé line is created."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:154
msgid ""
"In order to add a skill to an employee record, the skill types must be "
"configured first. If no skill types are configured, a :guilabel:`Create new "
"Skills` button appears in the :guilabel:`Skills` section of the "
":guilabel:`Resumé` tab. :ref:`Configure the skill types <employees/skill-"
"types>` before adding any skills to the employee record."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:159
msgid ""
"If the skill types are configured, a :guilabel:`Pick a skill from the list` "
"button appears instead. Click the :guilabel:`Pick a skill from the list` "
"button, and select the following information for each skill."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst-1
msgid "A skill form with the information filled out."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:167
msgid ""
":guilabel:`Skill Type`: select a :ref:`skill type <employees/skill-types>` "
"by clicking the radio button next to the skill type."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:169
msgid ""
":guilabel:`Skill`: after selecting a :guilabel:`Skill Type`, the "
"corresponding skills associated with that selected :guilabel:`Skill Type` "
"appear in a drop-down menu. For example, selecting :guilabel:`Language` as "
"the :guilabel:`Skill Type` presents a variety of languages to select from "
"under the :guilabel:`Skills` field. Select the appropriate pre-configured "
"skill, or type in a new skill, then click :guilabel:`Create \"(new "
"skill)\"`."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:174
msgid ""
":guilabel:`Skill Level`: pre-defined skill levels associated with the "
"selected :guilabel:`Skill Type` appear in a drop-down menu. First, select a "
":guilabel:`Skill Level`, then the progress bar automatically displays the "
"pre-defined progress for that specific skill level. Skill levels and "
"progress can be modified in the :guilabel:`Skill Level` pop-up form, which "
"is accessed via the :guilabel:`Internal Link` arrow next to :guilabel:`Skill"
" Level` field."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:180
msgid ""
"Click the :guilabel:`Save & Close` button if there is only one skill to add,"
" or click the :guilabel:`Save & New` button to save the current entry and "
"immediately add another skill."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:183
msgid ""
"To delete any line from the :guilabel:`Resumé` tab, click the :guilabel:`🗑️ "
"(trash can)` icon to delete the entry. Add a new line by clicking the "
":guilabel:`Add` button next to the corresponding section."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:188
msgid ""
"Only users with :guilabel:`Officer: Manage all employees` or "
":guilabel:`Administrator` rights for the *Employees* app can add or edit "
"skills."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:194
msgid "Skill types"
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:196
msgid ""
"In order to add a skill to an employee's form, the :guilabel:`Skill Types` "
"must be configured. Go to :menuselection:`Employees app --> Configuration "
"--> Employee: Skill Types` to view the currently configured skill types and "
"create new skill types."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:201
msgid ""
"The default skill of :guilabel:`Languages` is pre-configured as a skill "
"*type*, but there are no specific language *skills* listed within that skill"
" type. The :guilabel:`Languages` skill type must be fully configured before "
"it can be used."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:205
msgid ""
"Click :guilabel:`New` and a new :guilabel:`Skill Type` form appears. Fill "
"out all the details for the new skill type. Repeat this for all the needed "
"skill types."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:208
msgid ""
":guilabel:`Skill Type`: enter the name of the skill type. This acts as the "
"parent category for more specific skills and should be generic."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:210
msgid ""
":guilabel:`Skills`: click :guilabel:`Add a line`, and enter the "
":guilabel:`Name` for the new skill, then repeat for all other needed skills."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:212
msgid ""
":guilabel:`Levels`: click :guilabel:`Add a line`, and enter the "
":guilabel:`Name` of the level. Next, click into the :guilabel:`Progress` "
"field, and enter a percentage (0-100) for that level. Repeat for all "
"additional levels, as needed."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:215
msgid ""
":guilabel:`Default Level`: click the toggle on the level line to set that "
"level as the default. Typically, the lowest level is set as the default, but"
" any level can be chosen. The toggle turns green, indicating it is the "
"default level for the skill. Only one level can be set as the default."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:220
msgid ""
"To add a math skill set, enter `Math` in the :guilabel:`Name` field. Next, "
"in the :guilabel:`Skills` field, enter `Algebra`, `Calculus`, and "
"`Trigonometry`. Last, in the :guilabel:`Levels` field enter `Beginner`, "
"`Intermediate`, and `Expert`, with the :guilabel:`Progress` listed as `25`, "
"`50`, and `100`, respectively. Last, click :guilabel:`Set Default` on the "
"`Beginner` line to set this as the default skill level."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:0
msgid "A skill form for a Math skill type, with all the information entered."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:230
msgid ""
"The :guilabel:`Skill Type` form automatically saves as data is entered."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:233
msgid ""
"Once the form is completely filled out, click the :guilabel:`Save manually` "
"button, represented by a :guilabel:`cloud with an upwards arrow` icon at the"
" top of the screen, and the :guilabel:`Levels` rearrange in descending "
"order, with the highest level at the top, and the lowest at the bottom, "
"regardless of the default level and the order they were entered."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:241
msgid "Work information tab"
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:243
msgid ""
"The :guilabel:`Work Information` tab is where the employee's specific job "
"related information is found. Their working schedule, various roles, who "
"approves their specific requests (time off, timesheets, and expenses), their"
" remote work schedule, and specific work location details are listed here."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:248
msgid ""
"Click on the :guilabel:`Work Information` tab to access this section, and "
"enter the following information for the new employee:"
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:251
msgid ""
":guilabel:`Location`: select the :guilabel:`Work Address` from the drop-down"
" menu. To modify the address, hover over the first line (if there are "
"multiple lines) of the address to reveal an :guilabel:`Internal Link` arrow."
" Click the :guilabel:`Internal Link` arrow to open up the company form, and "
"make any edits."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:256
#: ../../content/applications/hr/employees/new_employee.rst:273
msgid ""
"Use the breadcrumb links to navigate back to the new employee form when "
"done."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:258
msgid ""
"If a new work address is needed, add the address by typing it in the field, "
"then click :guilabel:`Create (new address)` to add the address, or "
":guilabel:`Create and edit...` to add the new address and edit the address "
"form."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:261
msgid ""
":guilabel:`Approvers`: to see this section, the user must have either "
":guilabel:`Administrator` or :guilabel:`Officer: Manage all employees` "
"rights set for the *Employees* application. Using the drop-down menus, "
"select the users responsible for approving an :guilabel:`Expense`, a "
":guilabel:`Time Off` request, :guilabel:`Timesheet` entries, and "
":guilabel:`Attendance` records for the employee."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:267
msgid ""
"Hover over any of the selections to reveal the :guilabel:`Internal Link` "
"arrow."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:269
msgid ""
"Click the :guilabel:`Internal Link` arrow to open a form with the approver's"
" :guilabel:`Name`, :guilabel:`Email Address`, :guilabel:`Company`, "
":guilabel:`Phone`, :guilabel:`Mobile`, and :guilabel:`Default Warehouse` "
"fields. These can be modified, if needed."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:276
#: ../../content/applications/hr/employees/new_employee.rst:351
msgid ""
"The users that appear in the drop-down menu for the :guilabel:`Approvers` "
"section **must** have *Administrator* rights set for the corresponding human"
" resources role."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:279
msgid ""
"To check who has these rights, go to :menuselection:`Settings app --> Users "
"--> → Manage Users`. Then, click on an employee, and check the "
":guilabel:`Human Resources` section of the :guilabel:`Access Rights` tab."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:283
#: ../../content/applications/hr/employees/new_employee.rst:358
msgid ""
"In order for the user to appear as an approver for :guilabel:`Expenses`, "
"they **must** have either :guilabel:`Team Approver`, :guilabel:`All "
"Approver`, or :guilabel:`Administrator` set for the :guilabel:`Expenses` "
"role."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:286
msgid ""
"In order for the user to appear as an approver for :guilabel:`Time Off`, "
"they **must** have either :guilabel:`Officer:Manage all Requests` or "
":guilabel:`Administrator` set for the :guilabel:`Time Off` role."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:289
msgid ""
"In order for the user to appear as an approver for :guilabel:`Timesheets`, "
"they **must** have either :guilabel:`Manager`, :guilabel:`Officer:Manage all"
" contracts`, or :guilabel:`Administrator` set for the :guilabel:`Payroll` "
"role."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:293
msgid ""
":guilabel:`Remote Work`: use the drop-down menu to select the default "
"location the employee works from each day of the week. The default options "
"are :guilabel:`Home`, :guilabel:`Office`, or :guilabel:`Other`."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:297
msgid ""
"A new location can be typed into the field, then click either "
":guilabel:`Create (new location)` to add the location, or :guilabel:`Create "
"and edit...` to add the new location and edit the form."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:300
msgid ""
"After edits are done, click :guilabel:`Save & Close`, and the new location "
"is added, and populates the field."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:303
msgid ""
"Leave the field blank (:guilabel:`Unspecified`) for non-working days like "
"Saturday and Sunday."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:306
msgid ""
"It is also possible to add or modify work locations by navigating to "
":menuselection:`Employees app --> Configuration --> Employee: Work "
"Locations`. To modify a location, click on an existing location, then make "
"any changes on the form."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:310
msgid ""
"Click :guilabel:`New` to create a new location, then enter the following "
"information on the form. All fields are **required**."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:313
msgid ""
":guilabel:`Work Location`: enter the name for the location. This can be as "
"general or as specific, as needed, such as `Home` or `Building 1, Second "
"Floor`, respectfully."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:315
msgid ""
":guilabel:`Work Address`: using the drop-down menu, select the address for "
"the location."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:316
msgid ""
":guilabel:`Cover Image`: click on the icon to select it for the "
":guilabel:`Cover Image`. Options are a :guilabel:`house` icon, an "
":guilabel:`office building` icon, and a :guilabel:`GPS location marker` "
"icon."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:319
msgid ""
":guilabel:`Company`: using the drop-down menu, select the company the "
"location applies to. The current company populates this field, by default."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:0
msgid "A new work location form with all fields filled out."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:326
msgid ""
":guilabel:`Schedule`: select the :guilabel:`Working Hours` and "
":guilabel:`Timezone` for the employee. The :guilabel:`Internal Link` arrow "
"opens a detailed view of the specific daily working hours. Working hours can"
" be modified or deleted here."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:331
msgid ""
":guilabel:`Working Hours` are related to a company's working schedules, and "
"an Employee **cannot** have working hours that are outside of a company's "
"working schedule."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:334
msgid ""
"Each individual working schedule is company-specific. So, for multi-company "
"databases, each company needs to have its own working schedules set."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:337
msgid ""
"If an employee's working hours are not configured as a working schedule for "
"the company, new working schedules can be added, or existing working "
"schedules can be modified."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:340
msgid ""
"Working hours can be modified in the *Payroll* application, where they are "
"referred to as :guilabel:`Working Schedules`."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:343
msgid ""
"For more information on how to create or modify :guilabel:`Working "
"Schedules` in the *Payroll* application, refer to the "
":doc:`../../hr/payroll` documentation."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:346
msgid ""
":guilabel:`Planning`: select a role from the drop-down menu for both the "
":guilabel:`Roles` and the :guilabel:`Default Role` fields. If the "
":guilabel:`Default Role` is selected as a role, it is automatically added to"
" the list of :guilabel:`Roles`."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:354
msgid ""
"To check who has these rights, go to :menuselection:`Settings app --> Users "
"--> → Manage Users`. Click on an employee, and check the :guilabel:`Human "
"Resources` section of the :guilabel:`Access Rights` tab."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:361
msgid ""
"In order for the user to appear as an approver for :guilabel:`Time Off`, "
"they **must** have either :guilabel:`Officer` or :guilabel:`Administrator` "
"set for the :guilabel:`Time Off` role."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:363
msgid ""
"In order for the user to appear as an approver for :guilabel:`Timesheets`, "
"they **must** have either :guilabel:`Manager`, :guilabel:`Officer`, or "
":guilabel:`Administrator` set for the :guilabel:`Payroll` role."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:368
msgid ""
":guilabel:`Working Hours` are related to a company's working times, and an "
"employee **cannot** have working hours that are outside of a company's "
"working times."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:371
msgid ""
"Each individual working time is company-specific. So, for multi-company "
"databases, each company **must** have its own working hours set."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:374
msgid ""
"If an employee's working hours are not configured as a working time for the "
"company, new working times can be added, or existing working times can be "
"modified."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:377
msgid ""
"To add or modify a working time, go to the :menuselection:`Payroll app --> "
"Configuration --> Working Schedules`. Then, either add a new working time by"
" clicking :guilabel:`New`, or edit an existing one by selecting a "
":guilabel:`Working Time` from the list to modify it."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:381
msgid ""
"Refer to the :ref:`Working schedules <payroll/working-times>` section of the"
" payroll documentation for specific details on creating and editing working "
"schedules."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:384
msgid ""
"After the new working time is created, or an existing one is modified, the "
":guilabel:`Working Hours` can be set on the employee form. In the "
":guilabel:`Schedule` section of the :guilabel:`Work Information` tab, select"
" the employee's working hours using the drop-down menu."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:391
msgid "Private information tab"
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:393
msgid ""
"No information in the :guilabel:`Private Information` tab is required to "
"create an employee, however, some information in this section may be "
"critical for the company's payroll department. In order to properly process "
"payslips and ensure all deductions are accounted for, the employee's "
"personal information should be entered."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:398
msgid ""
"Here, the employee's :guilabel:`Private Contact`, :guilabel:`Family Status`,"
" :guilabel:`Emergency` contact, :guilabel:`Education`, :guilabel:`Work "
"Permit`, and :guilabel:`Citizenship` information is entered. Fields are "
"entered either using a drop-down menu, ticking a checkbox, or typing in the "
"information."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:403
msgid ""
":guilabel:`Private Contact`: enter the :guilabel:`Private Address`, "
":guilabel:`Email`, and :guilabel:`Phone` for the employee. Then, enter the "
"employee's :guilabel:`Bank Account Number` using the drop-down menu."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:407
msgid ""
"If the bank is not already configured (the typical situation when creating a"
" new employee), enter the bank account number, and click :guilabel:`Create "
"and edit..`. A :guilabel:`Create Bank Account Number` form loads. Fill in "
"the necessary information, then click :guilabel:`Save & Close`."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:411
msgid ""
"Next, select the employee's preferred :guilabel:`Language` from the drop-"
"down menu. Then enter the :guilabel:`Home-Work Distance` in the field. This "
"field is only necessary if the employee is receiving any type of commuter "
"benefits."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:415
msgid ""
"Lastly, enter the employee's license plate information in the "
":guilabel:`Private Car Plate` field."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:416
msgid ""
":guilabel:`Family Status`: select the current :guilabel:`Marital Status` "
"using the drop-down menu, either :guilabel:`Single`, :guilabel:`Married`, "
":guilabel:`Legal Cohabitant`, :guilabel:`Widower`, or :guilabel:`Divorced`. "
"If the employee has any dependent children, enter the :guilabel:`Number of "
"Dependent Children` in the field."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:420
msgid ""
":guilabel:`Emergency`: type in the :guilabel:`Contact Name` and "
":guilabel:`Contact Phone` number of the employee's emergency contact in the "
"respective fields."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:422
msgid ""
":guilabel:`Education`: select the highest level of education completed by "
"the employee from the :guilabel:`Certificate Level` drop-down menu. Default "
"options include :guilabel:`Graduate`, :guilabel:`Bachelor`, "
":guilabel:`Master`, :guilabel:`Doctor`, or :guilabel:`Other`."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:426
msgid ""
"Type in the :guilabel:`Field of Study`, and the name of the "
":guilabel:`School` in the respective fields."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:428
msgid ""
":guilabel:`Work Permit`: if the employee has a work permit, enter the "
"information in this section. Type in the :guilabel:`Visa No` (visa number), "
"and/or :guilabel:`Work Permit No` (work permit number) in the corresponding "
"fields."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:432
msgid ""
"Using the calendar selector, select the :guilabel:`Visa Expiration Date`, "
"and/or the :guilabel:`Work Permit Expiration Date`, to enter the expiration "
"date(s)."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:435
msgid ""
"If available, upload a digital copy of the :guilabel:`Work Permit` document."
" Click :guilabel:`Upload your file`, navigate to the work permit file in the"
" file explorer, and click :guilabel:`Open`."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:438
msgid ""
":guilabel:`Citizenship`: this section contains all the information relevant "
"to the citizenship of the employee. Some fields use a drop-down menu, as the"
" :guilabel:`Nationality (Country)`, :guilabel:`Gender`, and "
":guilabel:`Country of Birth` fields do."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:442
msgid ""
"The :guilabel:`Date of Birth` uses a calendar selector to select the date. "
"First, click on the name of the month, then the year, to access the year "
"ranges. Use the :guilabel:`< (left)` and :guilabel:`> (right)` arrow icons, "
"navigate to the correct year range, and click on the year. Next, click on "
"the month. Last, click on the day to select the date."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:447
msgid ""
"Type in the information for the :guilabel:`Identification No` "
"(identification number), :guilabel:`Passport No` (passport number), and "
":guilabel:`Place of Birth` fields."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:450
msgid ""
"Lastly, if the employee is **not** a resident of the country they are "
"working in, activate the checkbox next to the :guilabel:`Non-resident` "
"field."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:454
msgid ""
"Depending on the localization setting, other fields may be present. For "
"example, for the United States, a :guilabel:`SSN No` (Social Security "
"Number) field is present."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:460
msgid "HR settings tab"
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:462
msgid ""
"This tab provides various fields for different information, depending on the"
" country the company is located. Different fields are configured for "
"different locations, however some sections appear regardless."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:466
msgid ""
":guilabel:`Status`: select an :guilabel:`Employee Type` and, if applicable, "
"a :guilabel:`Related User`, with the drop-down menus. The "
":guilabel:`Employee Type` options include :guilabel:`Employee`, "
":guilabel:`Student`, :guilabel:`Trainee`, :guilabel:`Contractor`, or "
":guilabel:`Freelancer`."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:472
msgid ""
"Employees do **not** also need to be users. *Employees* do **not** count "
"towards the Odoo subscription billing, while *Users* **do** count towards "
"billing. If the new employee should also be a user, the user **must** be "
"created."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:476
msgid ""
"After the employee is created, click the :guilabel:`⚙️ (gear)` icon, then "
"click :guilabel:`Create User`. A :guilabel:`Create User` form appears."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:479
msgid ""
"Type in the :guilabel:`Name` and :guilabel:`Email Address`. Next, select the"
" :guilabel:`Company` from the drop-down menu."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:482
msgid ""
"Then, enter the :guilabel:`Phone` and :guilabel:`Mobile` numbers in the "
"respective fields."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:484
msgid ""
"If a photo is available, click the :guilabel:`Edit` icon (which appears as a"
" :guilabel:`✏️ (pencil)` icon) in the lower-left corner of the image box, "
"which is located in the top-right corner of the form."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:488
msgid ""
"A file explorer pops up. Navigate to the file, then click :guilabel:`Open` "
"to select it. Finally, click :guilabel:`Save` after all the information is "
"entered, and the employee record is automatically updated with the newly-"
"created user populating the :guilabel:`Related User field`."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:493
msgid ""
"Users can also be created manually. For more information on how to manually "
"add a user, refer to the :doc:`../../general/users/` document."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:496
msgid ""
":guilabel:`Attendance/Point of Sale/Manufacturing`: the employee's "
":guilabel:`PIN Code` and :guilabel:`Badge ID` can be entered here, if the "
"employee needs/has one. Click :guilabel:`Generate` next to the "
":guilabel:`Badge ID` to create a badge ID."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:500
msgid ""
"The :guilabel:`PIN Code` is used to sign in and out of the *Attendance* app "
"kiosk, and a :abbr:`POS (Point Of Sale)` system."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:502
msgid ""
":guilabel:`Payroll`: if applicable, enter the :guilabel:`Registration Number"
" of the Employee` in this section."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:505
msgid ""
"Depending on the localization setting, the other items that appear in this "
"field vary based on location. In addition, other sections may appear in this"
" tab based on location. It is recommended to check with the payroll and/or "
"accounting departments to ensure this section, as well as any other sections"
" relating to payroll that may appear, are filled in correctly."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:509
msgid ""
":guilabel:`Application Settings`: enter the employee's :guilabel:`Billing "
"Time Target` for the billing rate leader board in the *Timesheets* "
"application. Next, enter the :guilabel:`Hourly Cost` in a XX.XX format. This"
" is factored in when the employee is working at a :doc:`work center "
"<../../inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers>`."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:514
msgid "If applicable, enter the :guilabel:`Fleet Mobility Card` number."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:517
msgid ""
"Manufacturing costs are added to the costs for producing a product, if the "
"value of the manufactured product is **not** a fixed amount. This cost does "
"**not** affect the *Payroll* application."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst-1
msgid ""
"Enter any information prompted in the HR Settings tab for the employee."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:528
msgid "Documents"
msgstr "מסמכים"

#: ../../content/applications/hr/employees/new_employee.rst:530
msgid ""
"All employee-related documents are stored in the *Documents* app. The number"
" of associated documents is displayed in the :guilabel:`Documents` smart "
"button above the employee record. Click on the smart button to access all "
"documents."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst:534
msgid ""
"Refer to :doc:`documentation <../../productivity/documents>` on the "
"*Documents* app for more information."
msgstr ""

#: ../../content/applications/hr/employees/new_employee.rst-1
msgid ""
"All uploaded documents associated with the employee appear in the documents "
"smart-button."
msgstr ""

#: ../../content/applications/hr/employees/offboarding.rst:3
msgid "Offboarding"
msgstr ""

#: ../../content/applications/hr/employees/offboarding.rst:5
msgid ""
"When an employee leaves the company, it is important to ensure their "
"employee record is updated to reflect their departure, log the reason why, "
"close any open activities associated with the employee, and provide them "
"with any important documents."
msgstr ""

#: ../../content/applications/hr/employees/offboarding.rst:10
msgid "Archive an employee"
msgstr ""

#: ../../content/applications/hr/employees/offboarding.rst:12
msgid ""
"In Odoo, when an employee leaves the company they must be *archived*. To "
"archive an employee, first navigate to the :menuselection:`Employees app`. "
"From here, locate the employee who is leaving the company, and click on "
"their employee card."
msgstr ""

#: ../../content/applications/hr/employees/offboarding.rst:16
msgid ""
"The employee form loads, displaying all their information. Click the "
":icon:`fa-gear` :guilabel:`(gear)` icon in the top-left corner, and a drop-"
"down menu appears. Click :icon:`oi-archive` :guilabel:`Archive`, and an "
":guilabel:`Employee Termination` pop-up window appears."
msgstr ""

#: ../../content/applications/hr/employees/offboarding.rst:21
#: ../../content/applications/hr/payroll/contracts.rst:343
#: ../../content/applications/hr/time_off.rst:280
msgid "Fill out the following fields on the form:"
msgstr ""

#: ../../content/applications/hr/employees/offboarding.rst:23
msgid ""
":guilabel:`Departure Reason`: Select a reason the employee is leaving from "
"the drop-down menu. The default options are:"
msgstr ""

#: ../../content/applications/hr/employees/offboarding.rst:26
msgid ""
":guilabel:`Fired`: Select this option when an employee is being let go, and "
"the company has given notice."
msgstr ""

#: ../../content/applications/hr/employees/offboarding.rst:28
msgid ""
":guilabel:`Resigned`: Select this option when the employee no longer wishes "
"to be employed, and the employee has given notice."
msgstr ""

#: ../../content/applications/hr/employees/offboarding.rst:30
msgid ":guilabel:`Retired`: Select this option when the employee is retiring."
msgstr ""

#: ../../content/applications/hr/employees/offboarding.rst:31
msgid ""
":guilabel:`Became Freelance`: Select this option when the employee is no "
"longer working for the company, but is becoming a freelance worker instead."
msgstr ""

#: ../../content/applications/hr/employees/offboarding.rst:34
msgid ""
":guilabel:`Contract End Date`: Using the calendar selector, select the last "
"day the employee is working for the company."
msgstr ""

#: ../../content/applications/hr/employees/offboarding.rst:36
msgid ""
":guilabel:`Detailed Reason`: Enter a short description for the employee's "
"departure in this field."
msgstr ""

#: ../../content/applications/hr/employees/offboarding.rst:37
msgid ""
":guilabel:`Close Activities`: Tick the checkbox next to each type of "
"activity to close or delete any open activities associated with it. It is "
"recommended to tick **all** checkboxes that are applicable. The available "
"options are:"
msgstr ""

#: ../../content/applications/hr/employees/offboarding.rst:41
msgid ""
":guilabel:`Appraisals`: cancels all appraisals scheduled after the contract "
"end date."
msgstr ""

#: ../../content/applications/hr/employees/offboarding.rst:42
msgid ":guilabel:`Contract`: applies an end date for the current contract."
msgstr ""

#: ../../content/applications/hr/employees/offboarding.rst:43
msgid ""
":guilabel:`Company Car`: removes the employee as the driver for their "
"current company car, and :ref:`assigns the next driver "
"<fleet/new_vehicle/new-driver>`, if applicable."
msgstr ""

#: ../../content/applications/hr/employees/offboarding.rst:45
msgid ""
":guilabel:`Time Off`: cancels any time off requests after the contract end "
"date."
msgstr ""

#: ../../content/applications/hr/employees/offboarding.rst:46
msgid ""
":guilabel:`Allocations`: removes the employee from any accrual plans they "
"are on."
msgstr ""

#: ../../content/applications/hr/employees/offboarding.rst:48
msgid ""
":guilabel:`HR Info`: Tick the checkbox next to :guilabel:`Send Access Link` "
"to send a download link to the employee's personal email address, containing"
" all their personal HR files."
msgstr ""

#: ../../content/applications/hr/employees/offboarding.rst:50
msgid ""
":guilabel:`Private Email`: This field appears if the :guilabel:`HR Info` "
"checkbox is ticked. Enter the private email address for the employee."
msgstr ""

#: ../../content/applications/hr/employees/offboarding.rst:53
msgid ""
"When the form is complete, click :guilabel:`Apply`. The employee record is "
"archived, an email with a download link to their personal documents is sent "
"to the employee's private email address (if selected), and a red "
":guilabel:`Archived` banner appears in the top-right corner of the employee "
"form. The chatter logs the :guilabel:`Departure Date` and "
":guilabel:`Departure Reason`, and if an access link was emailed."
msgstr ""

#: ../../content/applications/hr/employees/offboarding.rst-1
msgid "The employee termination form with all fields filled out."
msgstr ""

#: ../../content/applications/hr/employees/offboarding.rst:64
msgid ""
"While attempting to send the HR documents access link, an :guilabel:`Invalid"
" Operation` pop-up window may appear, displaying the following error "
"message:"
msgstr ""

#: ../../content/applications/hr/employees/offboarding.rst:67
msgid ""
":guilabel:`Employee's related user and private email must be set to use "
"\"Send Access Link\" function: (Employee Name)`"
msgstr ""

#: ../../content/applications/hr/employees/offboarding.rst:70
msgid ""
"If this error appears, click :guilabel:`Close` to close the pop-up window, "
"then tick the :guilabel:`Send Access Link` checkbox to deselect it on the "
":guilabel:`Employee Termination` pop-up window."
msgstr ""

#: ../../content/applications/hr/employees/offboarding.rst:74
msgid ""
"Click :guilabel:`Apply` to archive the employee and close the selected "
"activities on the :guilabel:`Employee Termination` pop-up window, returning "
"to the employee form."
msgstr ""

#: ../../content/applications/hr/employees/offboarding.rst:77
msgid "Once the employee form, ensure the following fields are populated:"
msgstr ""

#: ../../content/applications/hr/employees/offboarding.rst:79
msgid ""
":guilabel:`Private Information` tab: Ensure an email address is entered in "
"the :guilabel:`Email` field."
msgstr ""

#: ../../content/applications/hr/employees/offboarding.rst:81
msgid ""
":guilabel:`HR Settings` tab: Ensure a :guilabel:`Related User` is selected "
"in the corresponding field."
msgstr ""

#: ../../content/applications/hr/employees/offboarding.rst:84
msgid ""
"After the necessary information is entered, :ref:`resend the HR documents "
"access link <employees/send-link>`"
msgstr ""

#: ../../content/applications/hr/employees/offboarding.rst:90
msgid "Send HR documents access link"
msgstr ""

#: ../../content/applications/hr/employees/offboarding.rst:92
msgid ""
"If the access link was not sent when first archiving the employee on the "
"*Employee Termination* form, it can be sent after the employee is archived "
"at any point."
msgstr ""

#: ../../content/applications/hr/employees/offboarding.rst:95
msgid ""
"After an employee is archived, they are no longer visible on the main "
"**Employees** app dashboard. To view the archived employees, navigate to the"
" :menuselection:`Employees app` dashboard, and click the :icon:`fa-caret-"
"down` :guilabel:`(down arrow)` in the search bar to reveal a drop-down menu."
" Select :guilabel:`Archived`, towards the bottom of the :icon:`fa-filter` "
":guilabel:`Filters` column, then click away from the drop-down window to "
"close it."
msgstr ""

#: ../../content/applications/hr/employees/offboarding.rst:101
msgid ""
"Now, only archived employees appear on the dashboard. Click on the desired "
"employee to open their employee form. On this form, click the :icon:`fa-"
"gear` :guilabel:`(gear)` icon in the top-left corner, then click "
":guilabel:`Send HR Documents Access Link` from the resulting drop-down menu."
" The chatter logs that the link was sent."
msgstr ""

#: ../../content/applications/hr/employees/retention_report.rst:3
msgid "Employee retention report"
msgstr ""

#: ../../content/applications/hr/employees/retention_report.rst:5
msgid ""
"It is possible to determine the retention rate for a company by modifying an"
" existing report."
msgstr ""

#: ../../content/applications/hr/employees/retention_report.rst:7
msgid ""
"First, navigate to :menuselection:`Employees app --> Reporting --> "
"Contracts` to open the :guilabel:`Employee Analysis` report. This report "
"shows the number of all employees for the :guilabel:`Last 365 Days`, in a "
"default :icon:`fa-line-chart` :guilabel:`Line Chart`."
msgstr ""

#: ../../content/applications/hr/employees/retention_report.rst-1
msgid "The default Employees Analysis report."
msgstr ""

#: ../../content/applications/hr/employees/retention_report.rst:15
msgid ""
"Next, click the :guilabel:`Measures` :icon:`fa-caret-down` button in the "
"upper-left corner, revealing a drop-down menu. Click :guilabel:`# Departure "
"Employee` in the list, then click away from the drop-down menu to close it. "
"Now, the report shows all the employees who were archived for the "
":guilabel:`Last 365 Days`."
msgstr ""

#: ../../content/applications/hr/employees/retention_report.rst:20
msgid ""
"To view this information in an easier format, click the :icon:`oi-view-"
"pivot` :guilabel:`(Pivot)` icon in the upper-right corner, and the data is "
"presented in a pivot table."
msgstr ""

#: ../../content/applications/hr/employees/retention_report.rst:23
msgid ""
"The various employees, organized by department, populate the rows. The "
"columns display the following totals: the monthly :guilabel:`Wage`, the "
":guilabel:`Fuel Card` budget, total :guilabel:`Annual Employee Budget` (also"
" referred to as the *annual salary*), the number of :guilabel:`New "
"Employees`, as well as the number of :guilabel:`Departure Employees` "
"(employees who left)."
msgstr ""

#: ../../content/applications/hr/employees/retention_report.rst-1
msgid ""
"The Employees Analysis report, modified to show departed employees only."
msgstr ""

#: ../../content/applications/hr/employees/retention_report.rst:33
msgid "Employee retention rate comparison report"
msgstr ""

#: ../../content/applications/hr/employees/retention_report.rst:35
msgid ""
"It is possible to compare data only for employees who left, compared to the "
"total current employees, between two separate time periods. This is commonly"
" referred to as the *employee retention rate*."
msgstr ""

#: ../../content/applications/hr/employees/retention_report.rst:38
msgid ""
"To view these metrics, first open the :guilabel:`Employee Analysis` report "
"by navigating to :menuselection:`Employees app --> Reporting --> Contracts`."
" Click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the upper-right"
" corner to view the information in a pivot table."
msgstr ""

#: ../../content/applications/hr/employees/retention_report.rst:42
msgid ""
"Next, click the :guilabel:`Measures` :icon:`fa-caret-down` button in the "
"upper-left corner, revealing a drop-down menu. Click :guilabel:`# New "
"Employees`, :guilabel:`Annual Employee Budget`, :guilabel:`Fuel Card`, and "
":guilabel:`Wage` in the list, to deselect these metrics and hide them in the"
" table. Then, click :guilabel:`Count` at the bottom of the list to enable "
"that metric."
msgstr ""

#: ../../content/applications/hr/employees/retention_report.rst:47
msgid ""
"Click away from the drop-down menu to close it. Now, the report shows all "
"the employees who left the company (:guilabel:`# Departure Employee`), as "
"well as the total number of employees (:guilabel:`Count`), for the "
":guilabel:`Last 365 Days`."
msgstr ""

#: ../../content/applications/hr/employees/retention_report.rst:51
msgid ""
"To compare the data for the current year with the previous year, click the "
":icon:`fa-caret-down` :guilabel:`(down arrow)` in the search bar, revealing "
"multiple filter and grouping options. Click :guilabel:`Last 365 Days` in the"
" :icon:`fa-filter` :guilabel:`Filters` column, to turn off that filter. "
"Then, click :guilabel:`Date`, and click the current year (in this example, "
":guilabel:`2024`) from the resulting drop-down menu."
msgstr ""

#: ../../content/applications/hr/employees/retention_report.rst:57
msgid ""
"Once a selection is made beneath :guilabel:`Date` in the :icon:`fa-filter` "
":guilabel:`Filters` column, a :icon:`fa-adjust` :guilabel:`Comparison` "
"column appears. Click :guilabel:`Date: Previous Year` in the new column, "
"then click off of the drop-down menu to close it."
msgstr ""

#: ../../content/applications/hr/employees/retention_report.rst:62
msgid ""
"In Odoo, in order to access the :icon:`fa-adjust` :guilabel:`Comparison` "
"column, a specific time *other than* :guilabel:`Last 365 Days` **must** be "
"selected. If not, the :icon:`fa-adjust` :guilabel:`Comparison` column is "
"**not** visible."
msgstr ""

#: ../../content/applications/hr/employees/retention_report.rst:66
msgid ""
"Now, the pivot table displays the total number of employees who left the "
"company (:guilabel:`# Departure Employee`), as well as the total number of "
"employees (:guilabel:`Count`) in the columns. These are further divided by "
"the two different years, and also displays the :guilabel:`Variation` between"
" the two."
msgstr ""

#: ../../content/applications/hr/employees/retention_report.rst:71
msgid ""
"The rows display the departments, and lists each individual employee for "
"each department, in the rows."
msgstr ""

#: ../../content/applications/hr/employees/retention_report.rst:74
msgid ""
"For a more concise view of this report, click :icon:`fa-minus-square-o` "
":guilabel:`Total` above the top row of the departments and employees, to "
"collapse the rows. Now, the table presents the total number of employees who"
" left the company for both years, compared to the total number of employees "
"for both years, including the difference, in a percentage."
msgstr ""

#: ../../content/applications/hr/employees/retention_report.rst:80
msgid ""
"In this example, :guilabel:`3` employees out of :guilabel:`83` left in 2023,"
" and :guilabel:`8` employees out of :guilabel:`202` left in 2024. There was "
"a :guilabel:`166.67%` increase in the employees who left in 2024 as compared"
" to 2023. Additionally, there was a :guilabel:`143.37%` increase in the "
"total number of employees in 2024 as compared to 2023."
msgstr ""

#: ../../content/applications/hr/employees/retention_report.rst:0
msgid ""
"The report modified to show the difference between two years of employees "
"who left."
msgstr ""

#: ../../content/applications/hr/employees/retention_report.rst:89
msgid ""
"To view more detailed rates for each department, click :icon:`fa-plus-"
"square` :guilabel:`Total` in the single row, revealing a drop-down menu, and"
" click :guilabel:`Department`. Click away from the drop-down to close it, "
"and now the pivot table displays the total number of employees who left "
"(:guilabel:`# Departure Employee`), the total number of employees "
"(:guilabel:`Count`), and the :guilabel:`Variation` (in a percentage) for "
"both 2023 and 2024, organized by department."
msgstr ""

#: ../../content/applications/hr/employees/retention_report.rst:96
msgid ""
"In this example, it can be determined that the :guilabel:`Management` "
"department had the best retention rate in 2024 as compared to 2023, with a "
":guilabel:`Variation` rate of :guilabel:`-100%`. Additionally, it can be "
"determined that the :guilabel:`Management / Research & Development` "
"department had the most turnover, with a :guilabel:`Variation` of "
":guilabel:`300%`."
msgstr ""

#: ../../content/applications/hr/employees/retention_report.rst:0
msgid "The expanded employee retention report by department."
msgstr ""

#: ../../content/applications/hr/fleet.rst:5
msgid "Fleet"
msgstr "צי רכב"

#: ../../content/applications/hr/fleet.rst:7
msgid ""
"This document outlines the configurations and settings for the *Fleet* "
"application, for both :ref:`settings <fleet/settings>` and "
":ref:`manufacturers <fleet/manufacturers>`."
msgstr ""

#: ../../content/applications/hr/fleet.rst:15
msgid ""
"To access the settings menu, go to :menuselection:`Fleet app --> "
"Configuration --> Settings`. Only two settings need configuration: "
":guilabel:`End Date Contract Alert` and :guilabel:`New Vehicle Request`."
msgstr ""

#: ../../content/applications/hr/fleet.rst-1
msgid "Settings available for the Fleet application."
msgstr ""

#: ../../content/applications/hr/fleet.rst:24
msgid "End Date Contract Alert"
msgstr ""

#: ../../content/applications/hr/fleet.rst:26
msgid ""
"The :guilabel:`End Date Contract Alert` field how many days before the end "
"of a vehicle contract an alert should be sent. The responsible people "
"receive an email informing them a vehicle contract is about to expire in the"
" number of days defined in this field."
msgstr ""

#: ../../content/applications/hr/fleet.rst:31
msgid ""
"To determine who the responsible person is for a contract, open an "
"individual contract. The person listed as :guilabel:`Responsible` under the "
":guilabel:`Contract Information` section of the contract is the person who "
"will receive the alert."
msgstr ""

#: ../../content/applications/hr/fleet.rst:35
msgid ""
"To access all contracts, navigate to :menuselection:`Fleet app --> Fleet -->"
" Contracts` and all contracts appear in the list. Click on a "
":guilabel:`Contract` to view it."
msgstr ""

#: ../../content/applications/hr/fleet.rst:38
msgid ""
"An individual contract can also be found by navigating to "
":menuselection:`Fleet app --> Fleet --> Fleet` and clicking on an individual"
" vehicle. On the vehicle form, click the :guilabel:`Contracts` smart button "
"at the top of the page. The contract(s) associated with this vehicle only "
"appears in the list. Click on an individual contract to open it. The "
":guilabel:`Responsible` person is listed on the contract."
msgstr ""

#: ../../content/applications/hr/fleet.rst:45
msgid "New Vehicle Request"
msgstr ""

#: ../../content/applications/hr/fleet.rst:47
msgid ""
"The :guilabel:`New Vehicle Request` field sets a limit on how many new "
"vehicles are requested based on fleet availability. An employee filling out "
"the salary configurator form (after being offered a position), will *not* be"
" able to request a new car if the number of existing cars is greater than "
"the number specified in the :guilabel:`New Vehicle Request` field. Enter the"
" specific number limit for existing available cars in this field."
msgstr ""

#: ../../content/applications/hr/fleet.rst:54
msgid ""
"If the :guilabel:`New Vehicle Request` limit is set to 20 vehicles, and "
"there are 25 vehicles available, an employee would not be able to request a "
"new vehicle. If there are only 10 cars available, then the employee would be"
" able to request a new vehicle."
msgstr ""

#: ../../content/applications/hr/fleet.rst:61
msgid "Manufacturers"
msgstr "יצרנים"

#: ../../content/applications/hr/fleet.rst:63
msgid ""
"Odoo *Fleet* comes pre-configured with sixty-six commonly used car and "
"bicycle manufacturers in the database, along with their logos. To view the "
"pre-loaded manufacturers, go to :menuselection:`Fleet app --> Configuration "
"--> Manufacturers`."
msgstr ""

#: ../../content/applications/hr/fleet.rst:67
msgid ""
"The manufacturers appear in an alphabetical list. Each manufacturer's card "
"lists how many specific models are configured for each particular "
"manufacturer. Odoo comes with forty-six preconfigured :doc:`models "
"<fleet/models>` from four major auto manufacturers, and one major bicycle "
"manufacturer: Audi, BMW, Mercedes, Opel (cars), and Eddy Merckx (bicycle)."
msgstr ""

#: ../../content/applications/hr/fleet.rst-1
msgid "Manufacturer card with the amount of models listed."
msgstr ""

#: ../../content/applications/hr/fleet.rst:77
msgid "Add a manufacturer"
msgstr ""

#: ../../content/applications/hr/fleet.rst:79
msgid ""
"To add a new manufacturer to the database, click :guilabel:`Create`. A "
"manufacturer form will load. Only two pieces of information are needed, the "
":guilabel:`Name` of the manufacturer, and the logo. Type the name of the "
"manufacturer in the name field, and select an image to upload for the logo. "
"When the information is entered, click :guilabel:`Save`."
msgstr ""

#: ../../content/applications/hr/fleet.rst:85
msgid ":doc:`fleet/models`"
msgstr ""

#: ../../content/applications/hr/fleet.rst:86
msgid ":doc:`fleet/new_vehicle`"
msgstr ""

#: ../../content/applications/hr/fleet.rst:87
msgid ":doc:`fleet/service`"
msgstr ""

#: ../../content/applications/hr/fleet.rst:88
msgid ":doc:`fleet/accidents`"
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:3
msgid "Accidents"
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:5
msgid ""
"When managing a fleet, accidents are inevitable. Tracking accidents is "
"crucial for understanding vehicle maintenance costs and identifying safe "
"drivers."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:8
msgid ""
"Odoo's *Fleet* app offers multiple ways to track accidents. Below are step-"
"by-step instructions for only **one** method to monitor accidents and repair"
" costs."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:12
msgid "Structure"
msgstr "מבנה"

#: ../../content/applications/hr/fleet/accidents.rst:14
msgid ""
"For this example, to track accidents, two :ref:`service types <fleet/new-"
"type>` are created: `Accident - Driver's Fault` and `Accident - No Fault`."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:17
msgid ""
"This tracks various repairs associated with accidents, organized by who was "
"at fault."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:19
msgid ""
"When an accident occurs, a service record is created. The specific repairs "
"needed for the accident are logged in the *Description* of the service "
"record, and the details about the accident are logged in the *Notes* "
"section."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:23
msgid ""
"With this organizational structure, it is possible to view all accidents "
"organized by fault, car, driver, or cost."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:27
msgid "To manage accidents, the creation of service records is **required**."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:29
msgid ""
"Refer to the :doc:`service` documentation for detailed instructions on "
"creating service records in Odoo's *Fleet* app."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:33
msgid "Log accidents and repairs"
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:35
msgid ""
"To log an accident, and initiate the repair process, the first step is to "
":ref:`create a service record <fleet/service-form>` detailing the specific "
"repairs needed."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:39
msgid ""
"Some accidents require multiple repairs with several different vendors. For "
"these scenarios, a separate service record is needed for each vendor "
"performing repairs. To keep records organized, it is recommended to keep the"
" *Notes* field identical, as well as attaching the same important "
"documentation, such as a police report."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:44
msgid ""
"Navigate to :menuselection:`Fleet app --> Fleet --> Services` to view the "
"main :guilabel:`Services` dashboard. Click :guilabel:`New` in the top-left "
"corner, and a blank service form loads."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:47
#: ../../content/applications/hr/fleet/service.rst:380
#: ../../content/applications/hr/frontdesk.rst:33
#: ../../content/applications/hr/lunch/products.rst:12
#: ../../content/applications/hr/payroll.rst:875
#: ../../content/applications/hr/payroll/work_entries.rst:56
#: ../../content/applications/hr/time_off.rst:221
msgid "Enter the following information on the form:"
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:49
msgid ""
":guilabel:`Description`: enter the description of repairs needed to fully "
"repair the vehicle, such as `Bodywork`, `Windshield Replacement`, or "
"`Replacement Bumper, Tires, and Windows`."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:51
msgid ""
":guilabel:`Service Type`: for this example, select either `Accident - "
"Driver's Fault` or `Accident - No Fault`, depending on the situation."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:54
msgid ""
"When entering either of these two :guilabel:`Service Types` for the first "
"time, type in the new service type, then click :guilabel:`Create (new "
"service type)`. A :guilabel:`Create Service Type` pop-up window appears, "
"with the new service type populating the :guilabel:`Name` field. In the "
":guilabel:`Category` field, select :guilabel:`Service` from the drop-down "
"menu, then click the :guilabel:`Save & Close` button."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:60
msgid ""
"Once an accident service type has been added to the database, it is "
"available to select from the drop-down menu in the :guilabel:`Service Type` "
"field."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:62
msgid ""
":guilabel:`Date`: using the calendar popover window, select the date the "
"accident occurred. Navigate to the desired month using the :icon:`fa-"
"chevron-left` :icon:`fa-chevron-right` :guilabel:`(arrow)` icons, then click"
" the date to select it."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:65
msgid ""
":guilabel:`Cost`: leave this field blank, as the repair cost is not yet "
"known."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:66
msgid ""
":guilabel:`Vendor`: select the vendor performing the repairs using the drop-"
"down menu. If the vendor has not already been entered in the system, type in"
" the vendor name, and click either :guilabel:`Create` to add them, or "
":guilabel:`Create and edit...` to :ref:`add and configure the vendor "
"<fleet/new-vendor>`."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:70
msgid ""
":guilabel:`Vehicle`: select the vehicle that was in the accident from the "
"drop-down menu. When the vehicle is selected, the :guilabel:`Driver` field "
"is populated, and the unit of measure for the :guilabel:`Odometer Value` "
"field appears."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:73
msgid ""
":guilabel:`Driver`: the current driver listed for the selected vehicle "
"populates this field when the :guilabel:`Vehicle` is selected. If a "
"different driver was operating the vehicle when the accident occurred, "
"select the correct driver from the drop-down menu."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:76
msgid ""
":guilabel:`Odometer Value`: enter the odometer reading when the accident "
"occurred. The units of measure are either in kilometers (:guilabel:`km`) or "
"miles (:guilabel:`mi`), depending on how the selected vehicle was "
"configured."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:79
msgid ""
":guilabel:`NOTES`: enter the specific details of the accident at the bottom "
"of the service form, such as `Hit a deer` or `Rear-ended at an intersection "
"while stopped`."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:82
msgid ""
"Odoo provides the ability to attach any important paperwork, such as repair "
"estimates and police reports, to the service record. To do so, click the "
":icon:`fa-paperclip` :guilabel:`(paperclip)` icon, located in the *chatter* "
"of the form, and a file explorer pop-up window appears. Navigate to the "
"desired record, and click :guilabel:`Open` to upload the file."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:88
msgid ""
"Once a file is added to a service record, a :guilabel:`Files` section "
"appears in the *chatter*. To attach more records, click :icon:`fa-plus-"
"square` :guilabel:`Attach files` to add more documents."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst-1
msgid "Enter the information for an accident repair."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:97
msgid "Service stages"
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:99
msgid "In Odoo's *Fleet* app, there are four default service stages:"
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:103
#: ../../content/applications/hr/recruitment/recruitment-flow.rst:18
msgid "New"
msgstr "חדש"

#: ../../content/applications/hr/fleet/accidents.rst:105
msgid ""
"The default stage when a service record is created. The service has been "
"requested, but repairs have not begun. The :guilabel:`Cost` field for this "
"stage remains zero."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:108
msgid "Running"
msgstr "רץ"

#: ../../content/applications/hr/fleet/accidents.rst:110
msgid ""
"The repair is in-process, but not yet complete. The estimate for repairs is "
"listed in the :guilabel:`Cost` field."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:113
msgid "Completed"
msgstr "הושלם"

#: ../../content/applications/hr/fleet/accidents.rst:115
msgid ""
"All repairs listed on the service form have been completed. The "
":guilabel:`Cost` field is updated to reflect the final total cost charged "
"for the repairs."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:118
msgid "Cancelled"
msgstr "בוטל"

#: ../../content/applications/hr/fleet/accidents.rst:120
msgid "The service request has been cancelled."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:122
msgid ""
"During the repair process, change the service status to reflect the "
"vehicle's current state in one of two ways: on the individual :ref:`service "
"record <fleet/service_record>`, or in the :ref:`Kanban service view "
"<fleet/Kanban>`."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:129
msgid "Service record"
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:131
msgid ""
"Open the main *Services* dashboard, by navigating to :menuselection:`Fleet "
"app --> Fleet --> Services`. Next, click on the individual service record to"
" open the detailed service form. Click the desired stage in the top-right "
"corner, above the service form, to change the status."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst-1
msgid "The stages as seen from the service form."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:144
msgid ""
"Open the main *Services* dashboard, by navigating to :menuselection:`Fleet "
"app --> Fleet --> Services`. First, click the :icon:`oi-view-kanban` "
":guilabel:`Kanban` icon in the top-right of the screen, which organizes all "
"repairs by vehicle."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:148
msgid ""
"Next, remove the default :guilabel:`Service Type` filter in the search bar. "
"Upon doing so, all services appear in a Kanban view, organized by their "
"respective :guilabel:`Status`."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:151
msgid "Drag-and-drop the service record to the desired stage."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst-1
msgid ""
"The Kanban view of stages, with a card being dragged and dropped to the "
"Running stage."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:158
msgid "Accident reporting"
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:160
msgid ""
"One of the main reasons to track accidents using the method outlined in this"
" document is the ability to view the total accident cost, determine the "
"safest drivers, and calculate the actual total cost for specific vehicles."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:164
msgid ""
"The main :ref:`Services dashboard <fleet/services_dashboard>` displays all "
"the various accident information, while the :ref:`Reporting dashboard "
"<fleet/reporting_dashboard>` displays the total cost for specific vehicles."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:171
msgid "Services dashboard"
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:173
msgid ""
"Navigate to :menuselection:`Fleet app --> Fleet --> Services` to view the "
":guilabel:`Services` dashboard. All service records are displayed in a "
":icon:`oi-view-list` :guilabel:`(List)` view, grouped alphabetically, by "
":guilabel:`Service Type`."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:177
msgid ""
"The two service types created for accident tracking appear in the list: "
":guilabel:`Accident - Driver Fault` and :guilabel:`Accident - No Fault`."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:180
msgid ""
"Each grouping displays the number of records within each type, and lists the"
" individual records beneath each grouping title."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:184
msgid ""
"In this example, there are six accidents where the driver was at fault, and "
"four accidents that were not the driver's fault. This dashboard also "
"displays the estimated total :guilabel:`Cost` for all the accidents in each "
"group."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:188
msgid ""
"An estimated `$19,164.81` dollars are for driver-caused accident repairs, "
"and an estimated `$2,548.21` dollars are for no-fault accidents."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:0
msgid "Accident services, with the total costs highlighted."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:196
msgid ""
"The total :guilabel:`Cost` calculates **all** costs on the repair form, "
"including estimated costs, as well as final repair costs. This number may "
"not be accurate, if there are any repairs in the *Running* stage, and the "
"final bill has not yet been calculated."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:203
msgid "Reporting dashboard"
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:205
msgid ""
"Navigate to :menuselection:`Fleet app --> Reporting --> Costs` to view the "
":menuselection:`Cost Analysis` report. This report displays a  :icon:`fa-"
"bar-chart` :guilabel:`(Bar Chart)` of all :guilabel:`Contract` and "
":guilabel:`Service` costs for the current year, organized by month "
"(:guilabel:`Date : (year)`), by default. The :guilabel:`Sum`, represented by"
" a gray dotted line, is the combined total of both the :guilabel:`Contract` "
"and :guilabel:`Service` costs."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:211
msgid ""
"To view the total cost by vehicle, click the :icon:`fa-caret-down` "
":guilabel:`(down arrow)` icon at the right of the search bar, revealing a "
"drop-down menu. Click :guilabel:`Vehicle` in the :icon:`oi-group` "
":guilabel:`Group By` column, and the data is organized by vehicle."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:215
msgid ""
"This displays the true cost for each vehicle, including both the contract "
"cost (such as the monthly vehicle lease cost) and all service costs, "
"including all accidents. Hover over a column to reveal a data popover "
"window, which displays the vehicle name and the total cost. This allows for "
"a more complete view of the vehicle cost."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst-1
msgid "The Cost Analysis report, displaying total costs by vehicle."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:224
msgid ""
"To view the individual cost details for both contract costs and repairs, "
"click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the top-right "
"corner of the :guilabel:`Cost Analysis` dashboard. This displays each "
"vehicle on a separate line, and displays the :guilabel:`Contract` cost and "
":guilabel:`Service` cost, as well as the :guilabel:`Total` cost."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst-1
msgid ""
"The Cost Analysis report, displaying the contract and service costs separately, as well as\n"
"the total."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:235
msgid ""
"The :icon:`oi-view-pivot` :guilabel:`(Pivot)` view organizes the data by "
"vehicle, by default, therefore grouping the data by :guilabel:`Vehicle` is "
"not required. If this filer is already activated, it does not affect the "
"presented data."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:240
msgid "Manage accident repairs"
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:242
msgid ""
"For companies with multiple employees, who manage a large fleet of vehicles,"
" displaying only service records in the :guilabel:`New` and "
":guilabel:`Running` stages can be time-saving, if there are a large number "
"of records in the *Services* dashboard."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:246
msgid ""
"Navigate to :menuselection:`Fleet app --> Fleet --> Services`, where all "
"service requests are organized by :guilabel:`Service Type`. Next, click the "
":icon:`fa-caret-down` :guilabel:`(down arrow)` icon at the right of the "
"search bar, revealing a drop-down menu. Click :guilabel:`Add Custom Filter` "
"in the :icon:`fa-filter` :guilabel:`Filters` column, and a :guilabel:`Add "
"Custom Filter` pop-up window appears."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:252
msgid "Three drop-down fields need to be configured on the pop-up window."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:254
msgid "In the first field, scroll down, and select :guilabel:`Stage`."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:256
msgid "Leave the second field set to :guilabel:`=`."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:258
msgid "Select :guilabel:`Running` from the drop-down menu in the last field."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:260
msgid ""
"Next, click the :icon:`fa-plus` :guilabel:`(plus)` icon to the right of the "
"last field, and an identical rule appears beneath the current rule."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:263
msgid ""
"Then, change :guilabel:`Running` to :guilabel:`New` in the third field of "
"the second rule, leaving the other fields as-is."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:266
msgid ""
"Click the :guilabel:`Add` button at the bottom to add the new custom filter."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst-1
msgid ""
"The filter settings to be added to only display new and running services."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:272
msgid ""
"This slight modification only presents services in the :guilabel:`New` and "
":guilabel:`Running` stages. This is a helpful report for a company managing "
"a high number of repairs at any given time."
msgstr ""

#: ../../content/applications/hr/fleet/accidents.rst:275
msgid ""
"To have this report appear as the default report when opening the "
":guilabel:`Services` dashboard, click the :icon:`fa-caret-down` "
":guilabel:`(down arrow)` icon at the far-right of the search bar. Next, "
"click :guilabel:`Save current search`, beneath the :icon:`fa-star` "
":guilabel:`Favorites` column, which reveals another drop-down column beneath"
" it. Tick the checkbox beside :guilabel:`Default Filter`, then click "
":guilabel:`Save`. Then, this customized :guilabel:`Services` dashboard "
"appears, by default, anytime the :guilabel:`Services` dashboard is accessed."
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:3
msgid "Vehicle models"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:5
msgid ""
"When adding a vehicle to the fleet, specify the vehicle model to maintain "
"updated records, which keeps track of specific details, like maintenance "
"schedules and parts compatibility."
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:8
msgid ""
"Odoo comes with preconfigured car models from four major auto manufacturers:"
" Audi, BMW, Mercedes, and Opel."
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:11
msgid ""
"If a new vehicle model joins the fleet, and it is not one of the "
"preconfigured models from these manufacturers, the model (and/or "
"manufacturer) **must** be :ref:`added to the database <fleet/add-model>`."
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:16
msgid "Preconfigured models"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:18
msgid ""
"The following models are preconfigured in Odoo, and do not need to be added "
"to the database:"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:21
msgid "AUDI"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:21
msgid "BMW"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:21
msgid "Mercedes"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:21
msgid "Opel"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:23
msgid "A1"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:23
msgid "Serie 1"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:23
msgid "Class A"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:23
msgid "Agilia"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:25
msgid "A3"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:25
msgid "Serie 3"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:25
msgid "Class B"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:25
msgid "Ampera"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:27
msgid "A4"
msgstr "A4"

#: ../../content/applications/hr/fleet/models.rst:27
msgid "Serie 5"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:27
msgid "Class C"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:27
msgid "Antara"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:29
msgid "A5"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:29
msgid "Serie 6"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:29
msgid "Class CL"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:29
msgid "Astra"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:31
msgid "A6"
msgstr "A6"

#: ../../content/applications/hr/fleet/models.rst:31
msgid "Serie 7"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:31
msgid "Class CLS"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:31
msgid "AstraGTC"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:33
msgid "A7"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:33
msgid "Serie Hybrid"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:33
msgid "Class E"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:33
msgid "Combo Tour"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:35
msgid "A8"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:35
msgid "Serie M"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:35
msgid "Class GL"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:35
msgid "Corsa"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:37
msgid "Q3"
msgstr "רבעון 3"

#: ../../content/applications/hr/fleet/models.rst:37
msgid "Serie X"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:37
msgid "Class GLK"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:37
msgid "Insignia"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:39
msgid "Q5"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:39
msgid "Serie Z4"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:39
msgid "Class M"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:39
msgid "Meriva"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:41
msgid "Q7"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:41
msgid "Class R"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:41
msgid "Mokka"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:43
msgid "TT"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:43
msgid "Class S"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:43
msgid "Zafira"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:45
msgid "Class SLK"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:45
msgid "Zafira Tourer"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:47
msgid "Class SLS"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:53
msgid "Add a new model"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:55
msgid ""
"To add a new vehicle model, navigate to :menuselection:`Fleet app --> "
"Configuration --> Models: Models`. Click :guilabel:`New`, and in a new "
"vehicle model form, enter the following information on the form."
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:60
msgid ""
"Be advised, some fields are specific to Belgian based companies, so not all "
"fields or sections may be visible depending on the location of the company."
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:63
msgid ":guilabel:`Model name`: enter the model name in the field."
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:64
msgid ""
":guilabel:`Manufacturer`: select the manufacturer from the drop-down menu. "
"If the manufacturer is not configured, type in the manufacturer, and click "
":guilabel:`Create` or :guilabel:`Create and edit..`."
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:69
msgid ""
"When the manufacturer is selected, if it is one of the default manufacturers"
" in *Odoo*, the logo for the manufacturer automatically loads in the image "
"box in the top-right corner."
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:72
msgid ""
":guilabel:`Vehicle Type`: select one of two preconfigured vehicle types, "
"either :guilabel:`Car` or :guilabel:`Bike`, from the drop-down menu. The "
"vehicle types are hardcoded in Odoo, and are integrated with the *Payroll* "
"application, since vehicles can be part of an employee's benefits. Adding "
"additional vehicle types is *not* possible as it affects payroll."
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:76
msgid ""
":guilabel:`Category`: select a category for the vehicle from the drop-down "
"menu. To create a new category, type in the category and then click "
":guilabel:`Create (new category)`."
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:80
msgid "Information tab"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:82
msgid ""
"In the :guilabel:`Information` tab, specify details about the car model, "
"such as the car size, passenger capacity, cost settings (applicable to the "
"Belgium localization only), and engine information."
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:87
msgid "Model section"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:89
msgid ""
":guilabel:`Seats Number`: enter how many passengers the vehicle can "
"accommodate."
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:90
msgid ":guilabel:`Doors Number`: enter the number of doors the vehicle has."
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:91
msgid ":guilabel:`Color`: enter the color of the vehicle."
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:92
msgid ":guilabel:`Model Year`: enter the year the vehicle was manufactured."
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:93
msgid ""
":guilabel:`Trailer Hitch`: tick this checkbox if the vehicle has a trailer "
"hitch installed."
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:96
msgid "Salary section"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:99
msgid ""
"The :guilabel:`Salary` section **only** appears for Belgian-based companies,"
" and **only** if the company has their localization setting set to Belgium. "
"The cost values are all *monthly*, with the exception of the "
":guilabel:`Catalog Value (VAT Incl.)`."
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:103
msgid ""
":guilabel:`Can be requested`: tick this checkbox if employees can request "
"this model vehicle, if a vehicle is part of their employee contract."
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:105
msgid ""
":guilabel:`Catalog Value (VAT Incl.)`: enter the :abbr:`MSRP (Manufacturer's"
" Suggested Retail Price)` for the vehicle at the time of purchase or lease."
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:107
msgid ""
":guilabel:`C02 fee`: represents the carbon dioxide emission fee paid to the "
"Belgian government. This value is automatically calculated, based on Belgian"
" laws and regulations, and **cannot** be modified. The value is based on the"
" figure entered in the :guilabel:`CO2 Emissions` field (in the "
":guilabel:`Engine` section of the :guilabel:`Information` tab) on the "
"vehicle form."
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:113
msgid ""
"Modifying the :guilabel:`CO2 Emissions` field adjusts the value in the "
":guilabel:`CO2 fee` field."
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:115
msgid ""
":guilabel:`Cost (Depreciated)`: enter the monthly vehicle cost, which "
"appears in the salary configurator for future employees. This value impacts "
"the gross and net salary of the employee assigned to the vehicle. This "
"figure is depreciated over time, according to local tax laws. The "
":guilabel:`Cost (Depreciated)` does **not** depreciate automatically on the "
"*vehicle model*, it only depreciates based on the *contract* linked to a "
"specific vehicle."
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:120
msgid ""
":guilabel:`Total Cost (Depreciated)`: this value is the combination of the "
":guilabel:`Cost (Depreciated)` and the :guilabel:`C02 fee` fields. It also "
"depreciated over time."
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:124
msgid "Engine"
msgstr "מנוע"

#: ../../content/applications/hr/fleet/models.rst:126
msgid ""
":guilabel:`Fuel Type`: select the type of fuel the vehicle uses from the "
"drop-down menu. The options are :guilabel:`Diesel`, :guilabel:`Gasoline`, "
":guilabel:`Hybrid Diesel`, :guilabel:`Hybrid Gasoline`, :guilabel:`Plug-in "
"Hybrid Diesel`, :guilabel:`Plug-in Hybrid Gasoline`, :guilabel:`CNG`, "
":guilabel:`LPG`, :guilabel:`Hydrogen`, or :guilabel:`Electric`."
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:130
msgid ""
":guilabel:`CO2 Emissions`: enter the average carbon dioxide emissions the "
"vehicle produces in grams per kilometer (g/km). This information is provided"
" by the car manufacturer."
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:132
msgid ""
":guilabel:`CO2 Standard`: enter the standard amount of carbon dioxide in "
"grams per kilometer (g/km) for a similar-sized vehicle."
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:134
msgid ""
":guilabel:`Transmission`: select :guilabel:`Manual` or :guilabel:`Automatic`"
" transmission from the drop-down menu."
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:136
msgid ""
":guilabel:`Power`: if the vehicle is electric or hybrid, enter the power the"
" vehicle uses in kilowatts (kW)."
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:138
msgid ":guilabel:`Horsepower`: enter the vehicle's horsepower in this field."
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:139
msgid ""
":guilabel:`Horsepower Taxation`: enter the amount that is taxed, based on "
"the size of the vehicle's engine. This is determined by local taxes and "
"regulations, and varies depending on the location. It is recommended to "
"check with the accounting department to ensure this value is correct."
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:143
msgid ""
":guilabel:`Tax Deduction`: this field auto-populates, according to the "
"engine specifications, and **cannot** be modified. The percentage is based "
"on the localization settings and local tax laws."
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:147
msgid "Vendors tab"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:149
msgid ""
"Specify the vendors a vehicle can be purchased from in this tab. With proper"
" setup, requests for quotations for vehicles can be easily created through "
"Odoo's *Purchase* app."
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:152
msgid ""
"To add a vendor, click :guilabel:`Add`, which opens an :guilabel:`Add: "
"Vendors` pop-up window, with a list of all the vendors currently in the "
"database. Add a vendor by ticking the checkbox next to the vendor name, then"
" click :guilabel:`Select`. There is no limit to the number of vendors that "
"can be added to this list."
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:157
msgid ""
"If a vendor is not in the database, add a vendor by clicking :guilabel:`New`"
" in the bottom-left of the :guilabel:`Add: Vendors` pop-up window. In the "
":guilabel:`Create Vendors` form that appears, enter the necessary "
"information, then click :guilabel:`Save & Close` to add the vendor, or click"
" :guilabel:`Save & New` to add the current vendor and create another new "
"vendor."
msgstr ""

#: ../../content/applications/hr/fleet/models.rst-1
msgid "Vendor form to fill out when adding a new vendor."
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:169
msgid "Model category"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:171
msgid ""
"To best organize a fleet, it is recommended to have vehicle models housed "
"under a specific category, to easily see what kinds of vehicles are in the "
"fleet. Model categories are set on the :ref:`vehicle model form <fleet/add-"
"model>`."
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:175
msgid ""
"Odoo does **not** come with any models preconfigured; all models **must** be"
" added."
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:177
msgid ""
"To view any models currently set up in the database, navigate to "
":menuselection:`Fleet app --> Configuration --> Models: Categories`. All "
"models are displayed in a list view."
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:181
msgid "Add a new model category"
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:183
msgid ""
"To add a new category, click the :guilabel:`New` button in the top-left "
"corner of the :guilabel:`Categories` page. A new entry line appears at the "
"bottom of the list. Type in the new category, then either click "
":guilabel:`Save`, or click anywhere on the screen, to save the entry."
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:187
msgid ""
"To reorganize how the categories appear in the list, click on the :icon:`oi-"
"draggable` :guilabel:`(draggable)` icon to the left of any desired category "
"name, and drag the line to the desired position."
msgstr ""

#: ../../content/applications/hr/fleet/models.rst:191
msgid ""
"The order of the list does not affect the database in any way. However, it "
"may be preferable to view the vehicle categories in a specific order, for "
"example, by size, or the numbers of passengers the vehicle can carry."
msgstr ""

#: ../../content/applications/hr/fleet/models.rst-1
msgid "List view of the models in the fleet."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:3
msgid "New vehicles"
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:5
msgid ""
"Odoo's *Fleet* app manages all vehicles, and the accompanying documentation "
"that comes with vehicle maintenance, and drivers records."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:8
msgid ""
"Upon opening the :menuselection:`Fleet` application, all vehicles are "
"organized within the :guilabel:`Vehicles` dashboard, which is the default "
"dashboard for the *Fleet* application. Each vehicle is displayed in its "
"corresponding Kanban stage, based on its status. The default stages are "
":guilabel:`New Request`, :guilabel:`To Order`, :guilabel:`Registered`, and "
":guilabel:`Downgraded`."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:13
msgid ""
"To add a new vehicle to the fleet from the :guilabel:`Vehicles` page, click "
"the :guilabel:`New` button in the top-left corner, and a blank vehicle form "
"loads. Then, proceed to enter the vehicle information on the vehicle form."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:17
msgid ""
"The form auto-saves as data is entered. However, the form can be saved "
"manually at any time by clicking the *save manually* option, represented by "
"a :guilabel:`(cloud upload)` icon, located in the top-left corner of the "
"page."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:24
msgid "Vehicle form fields"
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:26
msgid ""
":guilabel:`Model`: select the vehicle's model from the drop-down menu. Once "
"a model is selected, additional fields may appear on the form."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:29
msgid ""
"If the model is not listed, type in the model name, and click either "
":guilabel:`Create \"model\"`, or :guilabel:`Create and edit...` to "
":ref:`create a new model and edit the model details <fleet/add-model>`."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:32
msgid ""
":guilabel:`License Plate`: enter the vehicle's license plate number in this "
"field."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:33
msgid ""
":guilabel:`Tags`: select any tags from the drop-down menu, or type in a new "
"tag. There is no limit on the amount of tags that can be selected."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst-1
msgid "The new vehicle form, showing the model section."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:41
msgid ""
"The :guilabel:`Model` is the only required field on the new vehicle form. "
"When a model is selected, other fields appear on the vehicle form, and "
"relevant information auto-populates the fields that apply to the model. If "
"some of the fields do not appear, this may indicate there is no model "
"selected."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:49
msgid "Driver section"
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:51
msgid ""
"This section of the vehicle form relates to the person who is currently "
"driving the car, as well as any plans for a change in the driver in the "
"future, and when."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:54
msgid ""
":guilabel:`Driver`: select the driver from the drop-down menu, or type in a "
"new driver and click either :guilabel:`Create \"driver\"` or "
":guilabel:`Create and edit...` to :ref:`create a new driver, and edit the "
"driver details <fleet/new_vehicle/add-driver>`."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:59
msgid ""
"A driver does **not** have to be an employee. When creating a new driver, "
"the driver is added to the *Fleet* application, **not** the *Employees* "
"application."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:62
msgid ""
"If the *Contacts* application is installed, the driver information is also "
"stored in the *Contacts* application."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:65
msgid ""
":guilabel:`Mobility Card`: if the selected driver has a mobility card listed"
" on their employee card in the *Employees* application, the mobility card "
"number appears in this field. If there is no mobility card listed, and one "
"should be added, :ref:`edit the employee record <employees/hr-settings>` in "
"the *Employees* application."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:69
msgid ""
":guilabel:`Future Driver`: if the next driver for the vehicle is known, "
"select the next driver from the drop-down menu. Or, type in the next driver "
"and click either :guilabel:`Create \"future driver\"` or :guilabel:`Create "
"and edit...` to :ref:`create a new future driver, and edit the driver "
"details <fleet/new_vehicle/add-driver>`."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:73
msgid ""
":guilabel:`Plan To Change Car`: if the current driver set for this vehicle "
"plans to change their vehicle - either because they are waiting on a new "
"vehicle that is being ordered, or this is a temporary vehicle assignment, "
"and they know which vehicle they are driving next - check this box. Do "
"**not** check this box if the current driver does not plan to change their "
"vehicle."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:77
msgid ""
":guilabel:`Assignment Date`: using the drop-down calendar, select when the "
"vehicle is available for another driver. Select the date by navigating to "
"the correct month and year using the :guilabel:`⬅️ (left arrow)` and "
":guilabel:`➡️ (right arrow)` icons. Then, click on the specific day. If this"
" field is left blank, that indicates the vehicle is currently available, and"
" can be reassigned to another driver. If it is populated, the vehicle is not"
" available for another driver until the selected date."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:83
msgid ""
":guilabel:`Company`: select the company from the drop-down menu. This field "
"only appears in a multi-company database."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:89
msgid "Create a new driver"
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:91
msgid ""
"If a driver is not already in the system, the new driver should first be "
"configured and added to the database. A new driver can be added either from "
"the :guilabel:`Driver` or :guilabel:`Future Driver` fields on the "
":ref:`vehicle form <fleet/new_vehicle/vehicle-form>`."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:95
msgid ""
"First, type in the name of the new driver in either the :guilabel:`Driver` "
"or :guilabel:`Future Driver` field, then click :guilabel:`Create and "
"edit...`. A :guilabel:`Create Driver` or :guilabel:`Create Future Driver` "
"form appears, depending on which field initiated the form."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:99
msgid ""
"Both the :guilabel:`Create Driver` and :guilabel:`Create Future Driver` "
"forms are identical."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:104
msgid ""
"Depending on the installed applications, different tabs or fields may be "
"visible on the :guilabel:`Create Driver` and :guilabel:`Create Future "
"Driver` forms."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:110
msgid "Fill out the following information on the top-half of the form:"
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:112
msgid ""
":guilabel:`Individual` or :guilabel:`Company`: choose if the driver being "
"added is an individual driver or a company. Click the radio button to make a"
" selection."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:115
msgid ""
"When a selection is made, some fields may disappear from the form. If any of"
" the fields below are not visible, that is because :guilabel:`Company` was "
"selected instead of :guilabel:`Individual`."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:117
msgid ""
":guilabel:`Name`: enter the name of the driver or company in this field."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:118
msgid ""
":guilabel:`Company Name...`: using the drop-down menu, select the company "
"the driver is associated with."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:121
#: ../../content/applications/hr/fleet/new_vehicle.rst:147
msgid ""
"If the :guilabel:`Company` radio button is selected at the top of the form, "
"this field does not appear."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:123
#: ../../content/applications/hr/fleet/service.rst:132
msgid ":guilabel:`Contact`: enter the contact information in this section."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:125
#: ../../content/applications/hr/fleet/service.rst:134
msgid ""
"If desired, the :guilabel:`Contact` field can be changed to a different type"
" of contact. Click on :guilabel:`Contact` to reveal a drop-down menu. The "
"available options to select are :guilabel:`Contact`, :guilabel:`Invoice "
"Address`, :guilabel:`Delivery Address`, :guilabel:`Follow-up Address`, or "
":guilabel:`Other Address`."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:130
#: ../../content/applications/hr/fleet/service.rst:139
msgid ""
"If desired, select one of these other options for the :guilabel:`Contact` "
"field, and enter the corresponding information."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:133
msgid ""
"If the :guilabel:`Company` radio button is selected at the top of the form, "
"this field is labeled :guilabel:`Address` and cannot be modified."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:136
msgid ""
":guilabel:`Tax ID`: enter the driver or company's tax ID in this field."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:137
msgid ""
":guilabel:`Job Position`: enter the driver's job position in this field. If "
"the :guilabel:`Company` radio button is selected at the top of the form, "
"this field does not appear."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:139
msgid ""
":guilabel:`Phone`: enter the driver or company's phone number in this field."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:140
msgid ""
":guilabel:`Mobile`: enter the driver or company's mobile number in this "
"field."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:141
msgid ""
":guilabel:`Email`: enter the driver or company's email address in this "
"field."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:142
msgid ""
":guilabel:`Website`: enter the driver or company's website address in this "
"field."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:143
msgid ""
":guilabel:`Title`: using the drop-down menu, select the driver's title in "
"this field. The default options are :guilabel:`Doctor`, :guilabel:`Madam`, "
":guilabel:`Miss`, :guilabel:`Mister`, and :guilabel:`Professor`."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:149
msgid ""
":guilabel:`Tags`: using the drop-down menu, select any tags that apply to "
"the driver or company."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:151
#: ../../content/applications/hr/fleet/service.rst:160
msgid "To add a new tag, type in the tag, then click :guilabel:`Create \"tag\"`."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:153
#: ../../content/applications/hr/fleet/service.rst:162
msgid "There is no limit to the number of tags that can be selected."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst-1
msgid "The top portion of the create driver form."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:160
#: ../../content/applications/hr/fleet/service.rst:173
msgid "Contacts & Addresses tab"
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:162
msgid ""
"After completing the top-half of the :guilabel:`Create Driver` or "
":guilabel:`Create Future Driver` form, add any other contacts and addresses "
"associated with the driver or company in this tab."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:165
msgid ""
"To add a new contact, click the :guilabel:`Add` button, and a "
":guilabel:`Create Contact` pop-up window appears."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:168
msgid ""
"Before entering the necessary information on the form, select the type of "
"contact being added from a series radio button options located at the top of"
" the form. Those options are:"
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:171
msgid ""
":guilabel:`Contact`: select this option to add general contact details for "
"employees of the associated company."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:173
msgid ""
":guilabel:`Invoice Address`: select this option to add a preferred address "
"for all invoices. When added to the form, this address is selected by "
"default when sending an invoice to the associated company."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:176
msgid ""
":guilabel:`Delivery Address`: select this option to add a preferred address "
"for all deliveries. When added to the form, this address is selected by "
"default when delivering an order to the associated company."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:179
#: ../../content/applications/hr/fleet/service.rst:192
msgid ""
":guilabel:`Follow-up Address`: select this option to add a preferred address"
" for all follow-up correspondence. When added to the form, this address is "
"selected by default when sending reminders about overdue invoices."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:182
msgid ""
":guilabel:`Other Address`: select this option to add any other necessary "
"addresses for the company or driver."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst-1
#: ../../content/applications/hr/fleet/new_vehicle.rst:0
#: ../../content/applications/hr/fleet/service.rst-1
#: ../../content/applications/hr/fleet/service.rst:0
msgid "The create contact form with all parts filled in."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:189
msgid ""
"Depending on the :guilabel:`Contact Type`, some optional fields may not be "
"visible. The available fields are identical to the fields in the "
":ref:`general information <fleet/new_vehicle/general-info>` section of the "
"new driver form."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:193
#: ../../content/applications/hr/fleet/service.rst:206
msgid ""
"Add any notes to the :guilabel:`Internal notes...` section of the form."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:195
msgid ""
"After entering all of the information, click either :guilabel:`Save & Close`"
" to add the one new contact, or :guilabel:`Save & New` to add the current "
"address record and create another address record."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:199
#: ../../content/applications/hr/fleet/service.rst:212
msgid ""
"As contacts are added to this tab, each contact appears in a separate box, "
"with an icon indicating what type of contact is listed."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:203
msgid ""
"An :guilabel:`Invoice Address` displays a :guilabel:`💲 (dollar sign)` icon "
"inside that specific address box, whereas a :guilabel:`Delivery Address` "
"displays a :guilabel:`🚚 (truck)` icon inside."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:212
#: ../../content/applications/hr/fleet/service.rst:224
msgid "Sales & Purchase tab"
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:214
msgid ""
"Enter the following sales and purchasing information, in the "
":guilabel:`Sales & Purchase` tab of the :guilabel:`Create Driver` or "
":guilabel:`Create Future Driver` pop-up form for the various sections below."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:218
msgid ""
"Depending on the other installed applications, additional fields and "
"sections may appear. The following are all default fields for the *Fleet* "
"application **only**."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:222
msgid "Sales section"
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:224
msgid ""
":guilabel:`Salesperson`: using the drop-down menu, select the user who is "
"the main point of contact for sales with this driver's company."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:227
#: ../../content/applications/hr/fleet/service.rst:236
msgid ""
"This person **must** be an internal user of the company, meaning they can "
"log into the database as a user."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:231
#: ../../content/applications/hr/fleet/service.rst:240
msgid "Misc"
msgstr "שונות"

#: ../../content/applications/hr/fleet/new_vehicle.rst:233
msgid ""
":guilabel:`Company ID`: if the company has an ID number, **other than** its "
"*tax ID*, enter it in this field."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:235
msgid ""
":guilabel:`Reference`: enter any text to give more information regarding the"
" contact person. This is an internal note to provide any additional "
"information."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:239
msgid ""
"A company has several people with the same name, John Smith. The "
":guilabel:`Reference` field could state `John Smith at X205 - purchaser` to "
"provide additional details."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:243
#: ../../content/applications/hr/fleet/service.rst:252
msgid "Internal Notes tab"
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:245
msgid ""
"Add any notes that pertain to the driver, or any other necessary "
"information, in this tab."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:248
msgid "Vehicle section"
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:250
msgid ""
"This section of the vehicle form relates to the physical details of the "
"vehicle."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:252
msgid ""
"If a preexisting vehicle in the database was selected for the "
":guilabel:`Model` field in the top portion of the form, some fields may "
"auto-populate, and additional fields may also appear."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:255
msgid "Fill in the following fields on the form:"
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:257
msgid ""
":guilabel:`Category`: using the drop-down menu, select the vehicle category "
"from the available options. To create a new category, type in the new "
"category name, then click :guilabel:`Create \"category\"`."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:260
msgid ""
":guilabel:`Order Date`: using the drop-down calendar, select the date the "
"vehicle was ordered."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:261
msgid ""
":guilabel:`Registration Date`: using the drop-down calendar, select the date"
" the vehicle was registered."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:263
msgid ""
":guilabel:`Cancellation Date`: using the drop-down calendar, select the date"
" the vehicle lease expires, or when the vehicle is no longer available."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:265
msgid ""
":guilabel:`Chassis Number`: enter the chassis number in the field. This is "
"known in some countries as the :abbr:`VIN (Vehicle Identification Number)` "
"number."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:267
msgid ""
":guilabel:`Last Odometer`: enter the last known odometer reading in the "
"number field. Using the drop-down menu next to the number field, select "
"whether the odometer reading is in kilometers :guilabel:`(km)` or miles "
":guilabel:`(mi)`."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:270
msgid ""
":guilabel:`Fleet Manager`: select the fleet manager from the drop-down menu,"
" or type in a new fleet manager, and click either :guilabel:`Create` or "
":guilabel:`Create and Edit`."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:272
msgid ""
":guilabel:`Location`: type in the specific location where the vehicle is "
"typically located in this field. The entry should clearly explain where the "
"vehicle can be found, such as `Main Garage` or `Building 2 Parking Lot`."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst-1
#: ../../content/applications/hr/fleet/new_vehicle.rst-1
#: ../../content/applications/hr/fleet/new_vehicle.rst-1
msgid "The new vehicle form, showing the vehicle tax section."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:281
msgid "Tax Info tab"
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:283
msgid ""
"Depending on the localization setting for the database, and what additional "
"applications are installed, other fields may be present on the form."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:286
msgid ""
"The sections below are default and appear for all vehicles, regardless of "
"other installed applications or localization settings."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:290
msgid "Fiscality"
msgstr "יכולת"

#: ../../content/applications/hr/fleet/new_vehicle.rst:292
msgid ""
":guilabel:`Horsepower Taxation`: enter the amount that is taxed based on the"
" size of the vehicle's engine. This is determined by local taxes and "
"regulations, and varies depending on the location. It is recommended to "
"check with the accounting department to ensure this value is correct."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:297
msgid "Contract"
msgstr "חוזה"

#: ../../content/applications/hr/fleet/new_vehicle.rst:299
msgid ""
":guilabel:`First Contract Date`: select the start date for the vehicle's "
"first contract using the drop-down calendar. Typically this is the day the "
"vehicle is purchased or leased."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:301
msgid ""
":guilabel:`Catalog Value (VAT Incl.)`: enter the MSRP (Manufacturer's "
"Suggested Retail Price) for the vehicle at the time of purchase or lease."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:303
msgid ""
":guilabel:`Purchase Value`: enter the purchase price or the value of the "
"lease for the vehicle."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:304
msgid ":guilabel:`Residual Value`: enter the current value of the vehicle."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:307
msgid ""
"The values listed above affect the accounting department. It is recommended "
"to check with the accounting department for more information and/or "
"assistance with these values."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:315
msgid "Model tab"
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:317
msgid ""
"If the model for the new vehicle is already configured in the database, the "
":guilabel:`Model` tab will be populated with the corresponding information. "
"If the model is not already in the database and the :guilabel:`Model` tab "
"needs to be configured, :ref:`configure the new vehicle model <fleet/add-"
"model>`."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:322
msgid ""
"Check the information in the :guilabel:`Model` tab to ensure it is accurate."
" For example, the color of the vehicle, or if a trailer hitch is installed, "
"are examples of common information that may need updating."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:331
msgid "Note tab"
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:333
msgid "Enter any notes for the vehicle in this section."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:3
msgid "Services"
msgstr "שירותים"

#: ../../content/applications/hr/fleet/service.rst:5
msgid ""
"To properly maintain a fleet of vehicles, regular maintenance as well as "
"periodic repairs are needed. Scheduling repairs and managing services for an"
" entire fleet is necessary to ensure all vehicles are in good working order "
"when they are needed."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:12
msgid "Create service records"
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:14
msgid ""
"To log a service for a vehicle, go to the main :guilabel:`Services` "
"dashboard by navigating to :menuselection:`Fleet app --> Fleet --> "
"Services`. Open a new service form by clicking the :guilabel:`New` button in"
" the top-left corner."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:18
msgid ""
"Fill out the information on the form. The only two fields that are required "
"to be populated are :guilabel:`Service Type` and :guilabel:`Vehicle`."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:21
msgid ""
"The service form automatically saves as data is entered. However, the form "
"can be saved manually at any time by clicking the :guilabel:`Save manually` "
"option, represented by a :guilabel:`(cloud upload)` icon."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:25
msgid "The fields on the form are:"
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:27
msgid ":guilabel:`Description`: enter a brief description of the service."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:28
msgid ""
":guilabel:`Service Type`: select the type of service performed using the "
"drop-down menu. Or, enter a new type of service, and click either "
":guilabel:`Create \"service type\"` or :guilabel:`Create and edit...` to "
":ref:`add the service type and configure it <fleet/new-type>`."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:33
msgid ""
":guilabel:`Service Types` are **not** pre-configured in Odoo. When logging a"
" service for the first time, the *type* of service needs to be :ref:`created"
" <fleet/new-type>` before it can be selected."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:37
msgid ""
":guilabel:`Date`: using the calendar popover window, select the date the "
"service was provided, or is scheduled to be performed. Navigate to the "
"desired month using the :guilabel:`< > (arrow)` icons, then click on the "
"date to select it."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:40
msgid ":guilabel:`Cost`: enter the cost of the service."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:41
msgid ""
":guilabel:`Vendor`: select the vendor who performed the service using the "
"drop-down menu. If the vendor has not already been entered in the system, "
"type in the vendor name, and click either :guilabel:`Create` to add them, or"
" :guilabel:`Create and edit...` to :ref:`add and configure the vendor "
"<fleet/new-vendor>`."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:45
msgid ""
":guilabel:`Vehicle`: select the vehicle that was serviced from the drop-down"
" menu. When the vehicle is selected, the :guilabel:`Driver` field is "
"populated, and the unit of measure for the :guilabel:`Odometer Value` field "
"appears."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:48
msgid ""
":guilabel:`Driver`: the current driver listed for the selected vehicle is "
"populated when the :guilabel:`Vehicle` is selected. If the driver needs to "
"be changed, another driver can be selected from the drop-down menu."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:51
msgid ""
":guilabel:`Odometer Value`: enter the odometer reading when the service was "
"done. The units of measure are either in kilometers (:guilabel:`km`) or "
"miles (:guilabel:`mi`), depending on how the selected vehicle was "
"configured."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:55
msgid ""
"When the :guilabel:`Vehicle` is selected, the unit of measure for this field"
" is populated. This comes from the vehicle form."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:59
msgid ""
"To change from kilometers to miles, or vice versa, click the "
":guilabel:`Internal Link` button to the right of the vehicle selected in the"
" :guilabel:`Vehicle` field."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:62
msgid ""
"Change the unit of measure, then navigate back to the service form, via the "
"breadcrumb links. The unit of measure is then updated in the "
":guilabel:`Odometer Value` field."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:65
msgid ""
":guilabel:`Notes`: enter any notes for the repair at the bottom of the "
"service form."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst-1
msgid ""
"Enter the information for a new service. The required fields are Service "
"Type and Vehicle."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:74
msgid "Create service type"
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:76
msgid ""
"Service types must be created from a service form. There is no other way to "
"access the list of service types."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:79
msgid ""
"On the :ref:`service form <fleet/service-form>`, type in the name of the new"
" :guilabel:`Service Type` in the corresponding field. Then, click "
":guilabel:`Create and edit...`, and a :guilabel:`Create Service Type` pop-up"
" form appears."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:83
msgid ""
"The service type entered on the service form automatically populates the "
":guilabel:`Name` field, which can be modified, if desired."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:86
msgid ""
"Then, select the :guilabel:`Category` for the new service type from the "
"drop-down menu in that field. The two default options to choose from are "
":guilabel:`Contract` or :guilabel:`Service`. Additional categories "
"**cannot** be created."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:90
msgid ""
"If the service applies to **only** contracts or services, select the "
"corresponding :guilabel:`Category`. If the service applies to **both** "
"contracts *and* services, leave this field blank."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:94
msgid "When done, click :guilabel:`Save & Close`."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:99
msgid "Create vendor"
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:101
msgid ""
"When a service is done for the first time, typically, the vendor is not in "
"the database yet. It is best practice to add the full details for a vendor "
"in the database, so that any necessary information can be easily retrieved."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:105
msgid ""
"On the :ref:`service form <fleet/service-form>`, type in the name of the new"
" :guilabel:`Vendor` in the corresponding field. Then, click "
":guilabel:`Create and edit...`, and a :guilabel:`Create Vendor` form "
"appears."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:109
msgid ""
"The vendor name entered on the service form populates the :guilabel:`Name` "
"field, by default. This field can be modified, if desired."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:113
msgid ""
"Different tabs or fields may be visible on the :guilabel:`Create Vendor` "
"form, depending on what other applications are installed."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:119
msgid "Fill out the following information in the top-half of the form:"
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:121
msgid ""
":guilabel:`Individual` or :guilabel:`Company`: select whether the new vendor"
" being added is an individual or a company, by clicking the corresponding "
"radio button."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:124
msgid ""
"When a selection is made, some fields may disappear from the form. If any of"
" the fields below are not visible, that is because :guilabel:`Company` was "
"selected, instead of :guilabel:`Individual`."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:126
msgid ""
":guilabel:`Name`: enter a name for the individual or company in this field."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:127
msgid ""
":guilabel:`Company Name`: using the drop-down menu, select the company that "
"the vendor is associated with, if any."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:130
#: ../../content/applications/hr/fleet/service.rst:156
msgid ""
"If the :guilabel:`Company` radio button at the top of the form is selected, "
"this field does not appear."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:142
msgid ""
"If :guilabel:`Company` is selected for the  :guilabel:`Individual` or "
":guilabel:`Company` field, this field is labeled :guilabel:`Address`, and "
"**cannot** be modified."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:145
msgid ":guilabel:`Tax ID`: enter the vendor's tax ID in this field."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:146
msgid ""
":guilabel:`Job Position`: enter the vendor's job position in this field. If "
"the :guilabel:`Company` radio button at the top of the form is selected, "
"this field does not appear."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:148
msgid ":guilabel:`Phone`: enter the vendor's phone number in this field."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:149
msgid ":guilabel:`Mobile`: enter the vendor's mobile number in this field."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:150
msgid ":guilabel:`Email`: enter the vendor's email address in this field."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:151
msgid ":guilabel:`Website`: enter the vendor's website address in this field."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:152
msgid ""
":guilabel:`Title`: using the drop-down menu, select the vendor's title in "
"this field. The default options are :guilabel:`Doctor`, :guilabel:`Madam`, "
":guilabel:`Miss`, :guilabel:`Mister`, and :guilabel:`Professor`."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:158
msgid ""
":guilabel:`Tags`: using the drop-down menu, select any tags that apply to "
"the vendor."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:163
msgid ""
":guilabel:`Image`: a photo of either the main contact person, or the company"
" logo, can be added to the form. Hover over the :guilabel:`📷 (camera)` box, "
"in the top-right of the form, to reveal a :guilabel:`✏️ (pencil)` icon, and "
"click it. A file explorer window appears. Navigate to the desired file, then"
" click :guilabel:`Open` to select it."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst-1
msgid "The top portion of the create vendor form."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:175
msgid ""
"After the top-half of the :guilabel:`Create Vendor` form is filled out, add "
"any other contacts and addresses associated with the vendor in this tab."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:178
msgid ""
"Click the :guilabel:`Add` button to add a new contact, and a "
":guilabel:`Create Contact` pop-up window appears."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:181
msgid ""
"Select one of the appropriate contact type options from the radio buttons, "
"located at the top of the pop-up window. Those options are as follows:"
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:184
msgid ""
":guilabel:`Contact`: select this option to add general contact details for "
"employees of the associated vendor."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:186
msgid ""
":guilabel:`Invoice Address`: select this option to add a preferred address "
"for all invoices. When added to the form, this address is selected by "
"default when sending an invoice to the associated vendor."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:189
msgid ""
":guilabel:`Delivery Address`: select this option to add a preferred address "
"for all deliveries. When added to the form, this address is selected by "
"default when delivering an order to the associated vendor."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:195
msgid ""
":guilabel:`Other Address`: select this option to add any other necessary "
"addresses for the vendor."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:202
msgid ""
"If an option *other than* :guilabel:`Contact` is selected for the contact "
"type, an :guilabel:`Address` section appears on the form. Enter the address "
"details in the :guilabel:`Address` section."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:208
msgid ""
"After all of the information is added, click either :guilabel:`Save & Close`"
" to add the one new contact, or :guilabel:`Save & New` to add the current "
"address record and create another address record."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:216
msgid ""
"A :guilabel:`Delivery Address` displays a :guilabel:`⛟ (truck)` icon inside "
"that specific address box, whereas an :guilabel:`Invoice Address` displays a"
" :guilabel:`💵 (dollar bill)` icon inside."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:226
msgid ""
"Enter the following sales and purchasing information for the various "
"sections below. Depending on the other installed applications, additional "
"fields and sections may appear. The following are all default fields for the"
" *Fleet* application only."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:231
msgid "Sales"
msgstr "מכירות"

#: ../../content/applications/hr/fleet/service.rst:233
msgid ""
":guilabel:`Salesperson`: using the drop-down menu, select a user as the main"
" point of contact for sales with this vendor."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:242
msgid ""
":guilabel:`Company ID`: if the company has an ID number **other than** its "
"*tax ID*, enter it in this field."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:244
msgid ""
":guilabel:`Reference`: enter any text to give more information regarding the"
" contact. This is an internal note to provide any additional information."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:248
msgid ""
"A company has several people with the same name, Mary Jones. The "
":guilabel:`Reference` field could state `Mary Jones at X108 - returns` to "
"provide additional details."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:254
msgid ""
"Add any notes that pertain to the vendor, or any other necessary "
"information, in this tab."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:257
msgid "List of services"
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:259
msgid ""
"To view all services logged in the database, including old and new requests,"
" navigate to :menuselection:`Fleet app --> Fleet --> Services`. All services"
" appear in a list view, including all the details for each service."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:263
msgid ""
"The service records are grouped by :ref:`service type <fleet/new-type>`. The"
" number of repairs for each service type appears in parentheses after the "
"name of the service type."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:266
msgid "Each service listed displays the following information:"
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:268
msgid ""
":guilabel:`Date`: the date that the service, or repair, was performed (or "
"requested to be performed)."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:270
msgid ""
":guilabel:`Description`: a short description of the specific type of "
"service, or repair, performed to clarify the specific service."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:272
msgid ""
":guilabel:`Service Type`: the type of service, or repair, performed. This is"
" selected from a list of services that :ref:`must be configured <fleet/new-"
"type>`."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:274
msgid ""
":guilabel:`Vehicle`: the specific vehicle the service was performed on."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:275
msgid ":guilabel:`Driver`: the current driver for the vehicle."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:276
msgid ""
":guilabel:`Vendor`: the specific vendor who performed the service, or "
"repair."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:277
msgid ""
":guilabel:`Notes`: any information associated with the service, or repair, "
"that is documented to add clarification."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:279
msgid ":guilabel:`Cost`: the total cost of the service, or repair."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:280
msgid ""
":guilabel:`Stage`: the status of the service, or repair. Options are "
":guilabel:`New`, :guilabel:`Running`, :guilabel:`Done`, or "
":guilabel:`Canceled`."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:283
msgid ""
"At the bottom of the :guilabel:`Cost` column, the total cost of all services"
" and repairs are listed."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst-1
msgid "The full list of services in the Odoo database."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:290
msgid "View services"
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:292
msgid ""
"It is recommended to view the list of services in one of several pre-"
"configured ways to better view the information presented. In the top-right "
"corner of the list, there are several icons that when clicked, sort the data"
" in different ways."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst-1
msgid ""
"The icons in the top right corner than can be clicked to present the information in\n"
"different ways."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:304
msgid ""
"The default view of the service records is a list view. This presents all "
"the services, first grouped alphabetically by type of service, then grouped "
"by status."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:307
msgid ""
"The information can be re-sorted by any column. At the top of each column, "
"hover over the column name, and an arrow appears in the far-right of that "
"column. Click the arrow to sort the data by that specific column."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:311
msgid ""
"The default sorting is in descending alphabetical order (A to Z), "
"represented by a :guilabel:`⌄ (down arrow)` icon. Click the :guilabel:`⌄ "
"(down arrow)` icon to reverse the alphabetical order (Z to A). The "
":guilabel:`⌄ (down arrow)` icon changes to an :guilabel:`^ (up arrow)` icon."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:315
msgid ""
"The two exceptions to this sorting are the default :guilabel:`Date` column "
"and the :guilabel:`Cost` column. The :guilabel:`Date` column sorts the "
"information in chronological order (January to December), instead of "
"alphabetical order. The :guilabel:`Cost` column sorts the information by "
"repair price, from lowest to highest."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:321
#: ../../content/applications/hr/fleet/service.rst:401
msgid "Add a service"
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:323
msgid ""
"To add a service record from the list view, click the :guilabel:`New` "
"button, and a service form loads. :ref:`Enter all the information "
"<fleet/service-form>` on the service form."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:326
msgid "The form automatically saves as data is entered."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:331
msgid ""
"To view services by their stage, click the :guilabel:`Kanban` button, which "
"is the second icon in the top-right corner, and appears as two different "
"length bars beneath a line."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:334
msgid ""
"All services are organized by service type, and appear in the corresponding "
"Kanban column."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:336
msgid ""
"The number of repairs for each type of service appears in the far-right of "
"each Kanban column header."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:339
msgid ""
"The collective status of the scheduled activities for each service type "
"appears in the color-coded bar beneath each Kanban column title. Repairs "
"with activities scheduled in the future appear green, activities due today "
"appear yellow, overdue activities appear red, and repairs with no activities"
" scheduled appear gray."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:344
msgid ""
"Each Kanban card displays a color-coded activity-related icon, such as a "
":guilabel:`🕘 (clock)` icon or :guilabel:`📞 (phone)` icon, for example. These"
" icons indicate both the type of scheduled activity and the status. The "
"status of the activity corresponds to the colors in the status bar. Click on"
" an activity icon to view the details of that specific activity."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:349
msgid ""
"The length of the color bar is proportionate to the number of corresponding "
"activities with that specific status in that particular stage. Hover over a "
"color section to reveal the number of service records in that specific "
"grouping."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst-1
msgid "The service records presented in a Kanban view."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:357
msgid ""
"To view **only** the records with a specific status, click the desired color"
" bar section. The background color for the column changes to a pale hue of "
"the same color (either green, yellow, red, or gray), and the color bar "
"appears striped instead of solid. **Only** repairs and services with the "
"selected status appear in the column."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst-1
msgid ""
"The oil change service records showing only repairs with past-due "
"activities."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:369
msgid "Schedule activities"
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:371
msgid ""
"To schedule an activity for a repair or service from the Kanban view, click "
"the activity icon in the lower-right corner of the service record, and click"
" :guilabel:`+ Schedule an activity`. A :guilabel:`Schedule Activity` pop-up "
"window appears."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:376
msgid ""
"Depending on what kind of activity, if any, is scheduled, the activity icon "
"may appear differently. For example, a :guilabel:`📞 (phone)` appears if a "
"phone call is scheduled, or an :guilabel:`✉️ (envelope)` appears if an email"
" is scheduled."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:382
msgid ""
":guilabel:`Activity Type`: using the drop-down menu, select the activity "
"being scheduled. The default options are :guilabel:`Email`, "
":guilabel:`Call`, :guilabel:`Meeting`, :guilabel:`To-Do`, and "
":guilabel:`Upload Document`."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:385
msgid ""
":guilabel:`Summary`: enter a short description of the activity, such as "
"`Schedule oil change`."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:386
msgid ""
":guilabel:`Due Date`: using the calendar popover, select the date the "
"activity must be completed. Using the :guilabel:`< (left)` and :guilabel:`> "
"(right)` arrow icons, navigate to the desired month, then click on the date "
"to select it."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:389
msgid ""
":guilabel:`Assigned to`: using the drop-down menu, select the user "
"responsible for the activity."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:390
msgid ""
":guilabel:`Notes`: add any notes or details in the blank area in the bottom-"
"half of the form."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:392
msgid ""
"When the :guilabel:`Schedule Activity` is completed, click "
":guilabel:`Schedule` to schedule the activity, or click :guilabel:`Done & "
"Schedule Next` to schedule the current activity and schedule another "
"activity for the same repair."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:397
msgid ""
"For more detailed information regarding activities, refer to the main "
":doc:`activities <../../essentials/activities>` document."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:403
msgid ""
"A new repair can be added from this view. Click the :guilabel:`➕ (plus "
"icon)` in the top-right corner of the Kanban column, and a new block appears"
" at the top of the column, beneath the Kanban title."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:407
msgid ""
"Enter a :guilabel:`Title` for the service or repair, then click "
":guilabel:`Add`. A :guilabel:`Create` service form appears in a pop-up "
"window. :ref:`Enter all the information <fleet/service-form>` on the service"
" form, then click :guilabel:`Save & Close` to add the record. The new record"
" now appears in the Kanban column."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:413
msgid "Graph view"
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:415
msgid ""
"Another way to view the data is in a graph. To change to the graph view, "
"click the :guilabel:`Graph` icon, which is the third icon in the top-right, "
"and appears as a small graph."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:418
msgid ""
"The default graph view displays the service information in a stacked bar "
"chart, grouped by :guilabel:`Service Type`. The X-axis represents the "
":guilabel:`Service Type` and the Y-axis represents the :guilabel:`Cost`."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:422
msgid ""
"Each column visually represents the total cost for all repairs and services "
"for that specific :guilabel:`Service Type`. Hover over any bar to reveal a "
"popover window that displays the total :guilabel:`Cost` for the service and "
"repairs the bar represents."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:426
msgid ""
"The graph can change to either a :guilabel:`Line Chart` or a :guilabel:`Pie "
"Chart` by clicking the corresponding button above the graph. Additionally, "
"the graph can display the data in either :guilabel:`Stacked`, "
":guilabel:`Descending`, or :guilabel:`Ascending` order, by clicking the "
"corresponding buttons."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst-1
msgid ""
"A bar chart view of the services and repairs, with the various option "
"buttons highlighted."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:436
msgid "Pivot view"
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:438
msgid ""
"Another way to view the service data is in a spreadsheet pivot table. Click "
"the :guilabel:`Pivot` icon, which is the fourth icon in the top-right, and "
"appears as a small spreadsheet."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:441
msgid ""
"The default way the data is presented shows the total cost of each type of "
"service. The horizontal rows represent the various types of service, with a "
"different service type in its own line. The vertical columns represent the "
"total costs for each specific type of service, further divided by the type "
"of service."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst-1
msgid "The default pivot table view of the services."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:450
msgid ""
"The table can either be inserted in a spreadsheet or downloaded, if desired."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:452
msgid ""
"To add the pivot table to a spreadsheet in Odoo, first, the appearance of "
"the pivot table must change. The default pivot table view does not allow it "
"to be inserted into a spreadsheet (the :guilabel:`Insert in Spreadsheet` "
"button is grayed out)."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:456
msgid ""
"First, click the :guilabel:`➖ (minus)` icon to the left of :guilabel:`Total`"
" at the top of the pivot table. This collapses the service types, leaving "
"only a single :guilabel:`Cost` column visible."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:459
msgid ""
"Then, click the :guilabel:`Insert in Spreadsheet` button, which is no longer"
" grayed out, and a :guilabel:`Select a spreadsheet to insert your pivot` "
"pop-up window appears. Two tabs are visible in this pop-up window, a "
":guilabel:`Spreadsheets` tab and a :guilabel:`Dashboards` tab."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:463
msgid ""
"Click the desired tab to indicate where the spreadsheet should be placed, "
"either in a :guilabel:`Spreadsheet` or on a :guilabel:`Dashboard`. After "
"clicking the desired option, click :guilabel:`Confirm`. The spreadsheet then"
" loads on the screen."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:468
msgid ""
"Spreadsheets are stored in Odoo's *Documents* application, while dashboards "
"are stored in Odoo's *Dashboards* application."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:471
msgid ""
"Click :guilabel:`Services` in the top-left corner to navigate back to the "
"previous pivot table view."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:473
msgid ""
"To download the table in an *xlsx* format, click the download xlsx icon, "
"represented by a :guilabel:`⬇️ (down arrow above a line)` icon."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:477
msgid ""
"For more detailed information regarding reporting, refer to the main "
":doc:`reporting <../../essentials/reporting>` document."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:481
msgid "Activity view"
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:483
msgid ""
"To view the scheduled activities for services or repairs, click the "
":guilabel:`🕗 (clock)` activity icon in the top-right corner of the screen. "
"This presents all activities, organized by vehicle and activity type."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:487
msgid ""
"The vertical columns are organized by activity type, and the horizontal "
"lines are organized by vehicle."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:490
msgid ""
"The entries are color-coded according to the status of each activity. Green "
"activities are scheduled in the future, yellow activities are due today, and"
" red activities are overdue."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:493
msgid ""
"The user responsible for the activity appears in a photo in the lower-left "
"corner of each activity entry."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:496
msgid ""
"The due date of each activity is written in the top-center of each activity "
"entry."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:498
msgid ""
"A color-coded bar at the top of each activity column indicates the status of"
" the activities within that column."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:501
msgid ""
"The number of activities for each activity type is written on the right side"
" of the color-coded bar beneath the column name."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst-1
msgid ""
"The activity view, with the columns called out, and an activity box "
"highlighted."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:509
msgid "Schedule an activity"
msgstr "תזמן פעילות"

#: ../../content/applications/hr/fleet/service.rst:511
msgid ""
"To add a service record from the activity view, click :guilabel:`+ Schedule "
"an activity` in the bottom-left corner of the list, and a :guilabel:`Search:"
" Services` pop-up window loads. Click the service that the activity is being"
" scheduled for, and a :guilabel:`Schedule Activity` form loads."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:515
msgid ""
":ref:`Enter all the information <fleet/schedule-activity>` on the activity "
"form."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:517
msgid ""
"When the form is complete, click the :guilabel:`Schedule` button. Then, both"
" pop-up windows close, and the activity now appears on the activity view."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:5
msgid "Frontdesk"
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:7
msgid ""
"The Odoo *Frontdesk* application provides a way for visitors to check in to "
"a building or location, and alert the person they are meeting about their "
"arrival. Additionally, they can request a pre-configured beverage to be "
"brought to them, while they wait."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:11
msgid ""
"This application is ideal for businesses that do **not** have someone "
"working at a reception desk, locations **without** a designated waiting area"
" available to guests and visitors."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:17
msgid ""
"The first item to configure with the *Frontdesk* application is the station,"
" followed by any drink selections that might optionally be offered."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:21
msgid "Stations"
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:23
msgid ""
"In Odoo's *Frontdesk* application, a *Station* can be thought of as any "
"location where someone can sign in and wait for an employee. This is "
"typically some form of waiting room, such as a lobby. Each station has a "
"kiosk where visitors check in."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:27
msgid ""
"When setting up the *Frontdesk* application, a minimum of one station "
"**must** be configured, but there is no limit to how many stations can be "
"created and configured."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:30
msgid ""
"To create a station, navigate to :menuselection:`Frontdesk app --> "
"Configuration --> Stations`, and click :guilabel:`New`. When clicked, a "
"blank frontdesk form appears."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:35
msgid ""
":guilabel:`Frontdesk Name`: enter a name for the specific frontdesk "
"location. This should be short and easily identifiable, such as `Reception "
"Desk` or `Main Lobby`. This field is required in order to create a station."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:38
msgid ""
":guilabel:`Responsibles`: select the person (or persons) who are alerted "
"when a visitor checks in using this specific frontdesk. Multiple selections "
"can be entered. This field is required in order to create a station."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:41
msgid ""
":guilabel:`Kiosk URL`: this field auto-populates once the frontdesk form is "
"saved, with at least the :guilabel:`Frontdesk Name` and "
":guilabel:`Responsibles` fields filled. To save manually, click the "
":guilabel:`(cloud with upward arrow)` icon, located at the top of the form."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:45
msgid ""
"Once saved, a URL is generated in the :guilabel:`Kiosk URL` field. This URL "
"is one way the frontdesk kiosk is accessed."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:48
msgid ""
"To access the kiosk, click the :guilabel:`Copy` button at the end of the "
"URL, and navigate to that URL in a web browser. This URL opens that specific"
" station's frontdesk sign-in page."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:52
msgid ""
"To add an image/photo to a frontdesk form, hover over the :guilabel:`(camera"
" with a '+' sign)` icon in the top-right of the form to reveal a "
":guilabel:`✏️ (pencil)` icon."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:55
#: ../../content/applications/hr/frontdesk.rst:168
#: ../../content/applications/hr/frontdesk.rst:184
msgid ""
"Click on the :guilabel:`✏️ (pencil)` icon to open a file explorer, navigate "
"to the desired image/photo file, then click :guilabel:`Open` to select it."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:58
msgid ""
"The image selected for the station photo appears as the background image for"
" the station kiosk."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:61
msgid "Options tab"
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:65
msgid ""
":guilabel:`Host Selection`: if the visitor is attending a meeting, this "
"option allows the visitor to select the meeting host from a presented list, "
"and notify that individual. When enabled, additional fields appear, as "
"detailed below."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:68
msgid ""
":guilabel:`Authenticate Guest`: if additional information is required when a"
" guest checks in, enable this option, and select which of the following are "
"required:"
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:71
msgid ""
":guilabel:`Email`: select whether the guest's email address is "
":guilabel:`Required`, :guilabel:`Optional`, or if the information is not "
"requested at all (:guilabel:`None`)."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:73
msgid ""
":guilabel:`Phone`: select whether the guest's phone number is "
":guilabel:`Required`, :guilabel:`Optional`, or if the information is not "
"requested at all (:guilabel:`None`)."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:75
msgid ""
":guilabel:`Organization`: select whether the guest's organization is "
":guilabel:`Required`, :guilabel:`Optional`, or if the information is not "
"requested at all (:guilabel:`None`)."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:78
msgid ""
":guilabel:`Theme`: select the color mode of the kiosk. Choose either "
":guilabel:`Light` or :guilabel:`Dark`. The :guilabel:`Light` selection "
"displays a pale gray background on the kiosk, whereas the :guilabel:`Dark` "
"selection displays a dark gray and black background."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:81
msgid ""
":guilabel:`Self Check-In`: enable this option to present a check-in QR code "
"on the kiosk. The QR code allows guests to check in using their mobile "
"device, instead of using the kiosk. This option is recommended for a busy "
"kiosk with multiple guests checking in at any time."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:84
msgid ""
":guilabel:`Offer Drinks`: enable this option to offer guests a drink upon "
"check in. If this option is enabled, it is necessary to :ref:`configure the "
"drinks being offered <frontdesk/drinks>`, via the :guilabel:`Configure "
"Drinks` link that appears when the option is enabled. Once all drink options"
" are configured, select each drink to be offered using the drop-down menu."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:90
msgid ""
"The following options are only visible in the :guilabel:`Options` tab if the"
" :ref:`Host Selection <frontdesk/host>` option is enabled."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:93
msgid ""
":guilabel:`Notify by email`: enable this option to have an email sent to the"
" person the guest is visiting upon check in. When enabled, an "
":guilabel:`Email Template` field appears beneath, with the default "
":guilabel:`Frontdesk Email Template` selected."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:97
msgid ""
"To change the default email template, click the drop-down menu in the "
":guilabel:`Email Template` field, then select another email template."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:100
msgid ""
"To modify the currently selected template, click the :guilabel:`Internal "
"link (arrow)` icon at the end of the line, and make any edits to the "
"template."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:102
msgid ""
":guilabel:`Notify by SMS`: enable this option to have an SMS (text) message "
"sent to the person the guest is visiting upon check in. When enabled, an "
":guilabel:`SMS Template` field appears beneath, with the default "
":guilabel:`Frontdesk SMS Template` selected."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:106
msgid ""
"To change the default SMS template, click the drop-down menu in the "
":guilabel:`SMS Template` field, and select another SMS template."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:109
msgid ""
"To modify the currently selected template, click the :guilabel:`Internal "
"link (arrow)` icon at the end of the line, and make any desired edits to the"
" content of the template. The SMS message may have a maximum of 242 "
"characters, which fits in 4 SMS (UNICODE) messages."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:112
msgid ""
":guilabel:`Notify by Discuss`: this option is enabled by default when the "
":guilabel:`Host Selection` option is enabled. This option opens a *Discuss* "
"application message window with the person the guest is visiting upon check "
"in."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:116
msgid ""
"When enabled, a default message appears for the person the guest is "
"visiting. The *Discuss* application **must** be installed in order for this "
"option to work."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:120
msgid ""
"*Discuss* is installed by default when creating an Odoo database, and does "
"not count towards billing. As long as the *Discuss* application is not "
"intentionally uninstalled, the :guilabel:`Notify by Discuss` option works."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:125
msgid ""
"The default message format for the :guilabel:`Notify by Discuss` option is: "
"`(Frontdesk Station) Check-In: (Guest Name) (Guest Phone Number) "
"(Organization) to meet (Name of employee).`"
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:128
msgid ""
"An example of how that might appear in a *Discuss* message is: `Main Lobby "
"Check-In: John Doe (123-555-1234) (Odoo, Inc.) to meet Marc Demo.`"
msgstr ""

#: ../../content/applications/hr/frontdesk.rst-1
msgid "Frontdesk station form with all the information filled out."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:136
msgid "Side Message tab"
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:138
msgid ""
"Enter any desired text to appear on the station kiosk after a guest has "
"checked in, such as a welcome greeting or any necessary instructions. The "
"text appears on the confirmation page, on the right side of the screen after"
" a guest has completed the check-in process."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:145
#: ../../content/applications/hr/frontdesk/visitors.rst:112
msgid "Drinks"
msgstr "משקאות"

#: ../../content/applications/hr/frontdesk.rst:147
msgid ""
"After a station is created, the next step is to configure the drinks to "
"offer visitors, if desired. This step is **not** necessary or required for "
"the *Frontdesk* application to work, and only needs to be configured if "
"drinks are offered to guests."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:151
msgid ""
"To add a drink option, navigate to :menuselection:`Frontdesk app --> "
"Configuration --> Drinks`, and click :guilabel:`New`. Doing so reveals a "
"blank drink form to configure."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:154
msgid "Enter the following information on the drink form:"
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:156
msgid ""
":guilabel:`Drink Name`: type the name of the drink option in this field. "
"This field is required."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:157
msgid ""
":guilabel:`People to Notify`: use the drop-down menu in this field to select"
" who is notified when the drink is selected. Multiple people can be entered "
"in this field. This field is required."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:159
msgid ""
":guilabel:`Sequence`: enter a numerical value in this field to indicate "
"where in the list of drink options this specific option appears. The lower "
"the number, the higher on the list the drink appears. For example, entering "
"the number one would place that drink at the top of the list, and appear "
"first in the sequence."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:165
#: ../../content/applications/hr/frontdesk.rst:181
msgid ""
"To add an image/photo to a drink form, hover over the :guilabel:`(camera "
"with a '+' sign)` icon in the top-right of the form to reveal a "
":guilabel:`✏️ (pencil)` icon."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:171
#: ../../content/applications/hr/frontdesk.rst:187
msgid ""
"The image selected now appears in the picture field, and is set as the image"
" for the drink."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst-1
msgid "Drink form with the information filled out for an espresso."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:178
msgid "Station dashboard"
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:192
msgid "Kiosk setup"
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:194
msgid ""
"Set up each kiosk for use after configuring the various stations. It is "
"recommended to use a dedicated device for each frontdesk kiosk, such as a "
"tablet."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:197
msgid "Navigate to the kiosk in one of two ways:"
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:199
msgid ""
"Navigate to the main *Frontdesk* application dashboard, and click the "
":guilabel:`Open Desk` button on the desired station card. The kiosk loads in"
" a new browser tab."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:201
msgid ""
"Navigate to :menuselection:`Frontdesk app --> Configuration --> Stations`, "
"and click on the desired station. Then, click the :guilabel:`Copy` button at"
" the end of the :guilabel:`Kiosk URL` line, and paste the URL into a new "
"browser tab or window."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:206
msgid ""
"It is recommended to log out of the database, and close the tab, after "
"navigating to the kiosk. That way, there is no possibility of a visitor "
"accessing the database when checking-in."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:212
msgid ""
"The *Frontdesk* application has two reports available: :guilabel:`Visitors` "
"and :guilabel:`Drinks`."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:214
msgid ""
"To access either of these reports, navigate to :menuselection:`Frontdesk app"
" --> Reporting` to reveal a drop-down menu containing the options: "
":guilabel:`Visitors` and :guilabel:`Drinks`."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:217
msgid ""
"The :guilabel:`Visitors` report displays the number of visitors by month, "
"for the current year. The :guilabel:`Drinks` report shows how many total "
"requests were made for each drink."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:220
msgid ""
"As with all reports in Odoo, the filters and groups can be modified to show "
"other metrics, as well."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:223
msgid ":doc:`frontdesk/visitors`"
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:3
msgid "Visitors"
msgstr "מבקרים"

#: ../../content/applications/hr/frontdesk/visitors.rst:5
msgid ""
"In the Odoo *Frontdesk* application, a *visitor* is defined as any non-"
"employee (e.g., repair person, job candidate, etc.). These visitors can be "
"logged upon arrival and departure for security purposes. This ensures an "
"accurate list of people on the premises."
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:12
msgid "Visitor list"
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:14
msgid ""
"To access a complete list of checked-in visitors, navigate to "
":menuselection:`Frontdesk app --> Visitors`."
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:18
msgid ""
"By default, the :guilabel:`Planned or Checked-In` and :guilabel:`Today` "
"filters appear in the :guilabel:`Search...` bar."
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:21
msgid ""
"All visitors are presented in a list view, with the following details that "
"were entered upon check in:"
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:24
msgid ":guilabel:`Name`: the guest's name."
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:25
msgid ":guilabel:`Visitor Company`: the company the guest represents."
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:26
msgid ":guilabel:`Phone`: the guest's phone number."
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:27
msgid ":guilabel:`Drinks`\\*: the drink the guest requested."
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:28
msgid ":guilabel:`Host`: who the guest is waiting to see."
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:29
msgid ":guilabel:`CheckIn`: the date and time the guest checked in."
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:30
msgid ""
":guilabel:`Checkout`\\*: the date and time the guest checked out. In the "
"default view, only guests with a :guilabel:`Checked-In` or "
":guilabel:`Planned` status are visible. Guests with check-out times are only"
" visible if the :guilabel:`Today` filter is not active."
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:33
msgid ""
":guilabel:`Duration`: the amount of time the guest has been checked in for."
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:34
msgid ":guilabel:`Station`: the location of where the guest checked in."
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:35
msgid ""
":guilabel:`Status`: the status of the guest. The options are "
":guilabel:`Checked-In`, :guilabel:`Planned`, :guilabel:`Checked-Out`, or "
":guilabel:`Canceled`."
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:37
msgid ":guilabel:`Email`\\*: the guest's email address."
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:39
msgid ""
"\\* These fields are not visible in the default :guilabel:`Visitor` list. "
"These must be enabled using the :icon:`oi-settings-adjust` "
":guilabel:`(settings adjust)` icon in the top-right of the list."
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:43
msgid ""
"To the far-right of the titled columns on the :guilabel:`Visitors` page, "
"there is an untitled column, where a guest's status can be updated."
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:46
msgid ""
"When a guest leaves, click the available :guilabel:`Check out` button to "
"update the guest's record, and log the date and time they left."
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:49
msgid ""
"If a scheduled guest arrives, and they did not check in using the "
"*Frontdesk* kiosk, they can be checked in here, by clicking the available "
":guilabel:`Check in` button to log the date and time they arrived."
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:53
msgid ""
"Beside the untitled status column, a :guilabel:`Drink Served` button "
"appears, but only if that particular visitor requested a drink."
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:56
msgid ""
"When their drink has been served, click the :guilabel:`Drink Served` button "
"to indicate the drink has been delivered to the guest. Once clicked, that "
"button disappears."
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst-1
msgid ""
"The full list of currently checked in visitors, with the drinks to be served"
" highlighted."
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:63
msgid ""
"If any column is not visible, or if a visible column is preferred to be "
"hidden, click the :icon:`oi-settings-adjust` :guilabel:`(additional "
"options)` icon, located at the end of the column name list. Doing so, "
"reveals a reveals a drop-down menu of column options to enable or disable. A"
" :icon:`fa-check` :guilabel:`(check)` icon indicates the column is visible."
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:69
msgid "Planned visitors"
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:71
msgid ""
"Enter expected guest information in advance by creating a planned guest in "
"the *Frontdesk* app."
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:73
msgid ""
"To create a planned guest, navigate to :menuselection:`Frontdesk app --> "
"Visitors`, and click :guilabel:`New`. Then, enter the same information as "
"any other :ref:`visitor <frontdesk/list>` on the guest form that appears. "
"The only required fields are the visitor's :guilabel:`Name` and the "
":guilabel:`Station` at which they are expected to arrive."
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:79
msgid ""
"If a guest is planned in advance, they must be checked in from the list on "
"the :guilabel:`Visitors` page in the *Frontdesk* application "
"(:menuselection:`Frontdesk app --> Visitors`). If a planned guest checks in "
"using a kiosk, they will be checked in separately, and their planned visitor"
" entry remains listed as :guilabel:`Planned`."
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:84
msgid ""
"The :guilabel:`Planned` status of a planned guest **only** changes to "
":guilabel:`Checked-In` when they are checked in *inside* the application's "
":guilabel:`Visitors` list."
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:87
msgid ""
"If a guest does check in using a kiosk, ensure all records are current, and "
"the list of guests that are currently on-site is correct. Be sure to check "
"in and/or check out the correct entries, so the visitors list correctly "
"reflects who is currently on the premises."
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:91
msgid ""
"Ensure planned guests are informed that they should **not** check in using "
"the kiosk if they are listed as a planned guest in advance."
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:95
msgid "Visitor flow"
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:98
msgid "Visitor check in"
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:100
msgid ""
"When a visitor arrives at a facility, they approach a :ref:`Frontdesk kiosk "
"<frontdesk/kiosk>`, and click :guilabel:`Check in`. The information "
"requested from the visitor is what was configured for that specific "
"*Frontdesk* station. If any information is required, the field displays a "
"red asterisk (\\*). The visitor **must** enter the required information in "
"order to check in."
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:105
msgid ""
"Once all the information is entered, the visitor taps the :guilabel:`Check "
"In` button."
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:108
msgid ""
"At any point in the check-in process, if ten seconds pass with no selection,"
" the kiosk returns to the main welcome screen."
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:114
msgid ""
"If drinks were configured for the station, after tapping :guilabel:`Check "
"In`, a registration confirmation screen loads, along with the question: "
":guilabel:`Do you want something to drink?`"
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:117
msgid ""
"The visitor can tap either :guilabel:`Yes, please`, or :guilabel:`No, thank "
"you`."
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:119
msgid ""
"If they select :guilabel:`Yes, please`, a drink selection screen appears, "
"and the pre-configured options are listed. The visitor then taps the desired"
" selection, or, if they do not want anything, they can tap the "
":guilabel:`Nothing, thanks` button at the bottom of the screen."
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:123
msgid ""
"If a drink selection was made, a :guilabel:`Thank you for registering! Your "
"drink is on the way.` message appears."
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:127
msgid "Notifications"
msgstr "התראות"

#: ../../content/applications/hr/frontdesk/visitors.rst:129
msgid ""
"Once the visitor has checked in, the person they are visiting, and any other"
" users who were configured to be notified when check-ins occur at the kiosk,"
" are notified. The notification is either by email, SMS message, a *Discuss*"
" chat, or any combination of those three options."
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:133
msgid ""
"If the visitor requested a drink, the user(s) configured as the "
":guilabel:`People to Notify` on the drink form, are notified, via the "
"*Discuss* application. The message that appears is: :guilabel:`(Visitor "
"Name) just checked-in. They requested (Drink Name).`"
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:137
msgid ""
"Once the drink has been delivered to the guest, the person who delivered the"
" drink is responsible for marking the drink as delivered."
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:140
msgid ""
"To mark a drink as delivered, navigate to :menuselection:`Frontdesk app --> "
"Stations`, and choose the desired station card displaying :guilabel:`(#) "
"Drinks to serve`."
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:143
msgid ""
"This opens a list of all the visitors checked in at that station, and are "
"waiting for a drink. Click the :guilabel:`Drink Served` button at the end of"
" the line for the visitor who was served. Once they are marked as having "
"their drink served, the visitor disappears from the list."
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:150
msgid ""
"Once the visitor has completed their business, and has left the premises, it"
" is important to check them out for accurate record keeping."
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:153
msgid ""
"To check visitors out properly, navigate to :menuselection:`Frontdesk app "
"--> Stations`, and choose the desired station card displaying :guilabel:`(#)"
" Drinks to serve`. Doing so opens a list of all the visitors who are "
"currently checked-in at that station."
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:157
msgid ""
"Click the :guilabel:`Check out` button near the end of the line for the "
"visitor who left. Once they are marked as checked-out, the visitor "
"disappears from the list."
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:161
msgid ""
"Visitors do **not** check themselves out when they leave. It is important "
"for *Frontdesk* users to check out visitors for accurate record keeping."
msgstr ""

#: ../../content/applications/hr/frontdesk/visitors.rst:164
msgid ""
"Always have an accurate list of who is on the premises at any given time. "
"This is important for security purposes, and in the case of an emergency."
msgstr ""

#: ../../content/applications/hr/lunch.rst:5
msgid "Lunch"
msgstr "ארוחת צהריים"

#: ../../content/applications/hr/lunch.rst:7
msgid ""
"The *Lunch* application in Odoo allows users a convenient way to order food "
"and pay for their meal directly from the database."
msgstr ""

#: ../../content/applications/hr/lunch.rst:10
msgid ""
"Before employees can use the *Lunch* application, there are a number of "
"configurations to consider: settings, vendors, locations, products, product "
"categories, and alerts. Once these are created, employees can view offerings"
" and order food."
msgstr ""

#: ../../content/applications/hr/lunch.rst:17
msgid ""
"Only two settings are needed to configure in the *Lunch* app: overdraft "
"settings and notifications. To access the settings, navigate to "
":menuselection:`Lunch app --> Configuration: Settings`."
msgstr ""

#: ../../content/applications/hr/lunch.rst:20
msgid "Configure the following:"
msgstr ""

#: ../../content/applications/hr/lunch.rst:22
msgid ""
":guilabel:`Lunch Overdraft`: enter the maximum overdraft amount for "
"employees. The currency format is determined by the localization setting of "
"the company."
msgstr ""

#: ../../content/applications/hr/lunch.rst:24
msgid ""
":guilabel:`Reception notification`: set the message users receive via the "
"*Discuss* app when their food has been delivered. The default message `Your "
"lunch has been delivered. Enjoy your meal!` populates this field, but can be"
" modified, if desired."
msgstr ""

#: ../../content/applications/hr/lunch.rst:29
msgid ""
"If in a database with multiple languages installed, many forms in the "
"*Lunch* application have the option of entering translations for various "
"fields."
msgstr ""

#: ../../content/applications/hr/lunch.rst:32
msgid ""
"If translations are available to be configured, a language code appears next"
" to a translatable field on a form. To add translations for that field, "
"click the two letter language code (for example, :guilabel:`EN` for English)"
" and a translation pop-up window appears."
msgstr ""

#: ../../content/applications/hr/lunch.rst:36
msgid ""
"The following is an example for the :guilabel:`Reception notification` field"
" in the settings menu:"
msgstr ""

#: ../../content/applications/hr/lunch.rst:39
msgid ""
"Navigate to :menuselection:`Lunch app --> Configuration: Settings`. Click "
"the :guilabel:`EN` In the top-right of the text box beneath the "
":guilabel:`Reception notification` section. A :guilabel:`Translate: "
"company_lunch_notify_message` pop-up window loads with the option to enter a"
" translation for the other languages used by the database."
msgstr ""

#: ../../content/applications/hr/lunch.rst:44
msgid ""
"The first column lists the different languages in alphabetical order, with "
"the currently selected language in bold. The second column has the currently"
" configured message in each column. The last column in the far-right "
"provides a text box to type in a translation for each language."
msgstr ""

#: ../../content/applications/hr/lunch.rst:48
msgid ""
"Enter the text that should appear for each language, then click "
":guilabel:`Save`."
msgstr ""

#: ../../content/applications/hr/lunch.rst:0
msgid ""
"The translation text box, with the current language highlighted, and the Arabic\n"
"translation field highlighted."
msgstr ""

#: ../../content/applications/hr/lunch.rst:56
msgid "Locations"
msgstr "מיקומים"

#: ../../content/applications/hr/lunch.rst:58
msgid ""
"By default, Odoo creates an `HQ Office` location when the *Lunch* "
"application is installed. If a company has more than one location, they must"
" be configured."
msgstr ""

#: ../../content/applications/hr/lunch.rst:61
msgid ""
"To add a location, navigate to :menuselection:`Lunch app --> Configuration: "
"Locations`. The currently configured locations appear in a list view. Click "
"the :guilabel:`New` button in the top-left corner and a blank line appears "
"beneath the last location in the list."
msgstr ""

#: ../../content/applications/hr/lunch.rst:65
msgid ""
"Enter the name of the location in the field. Next, click into the "
":guilabel:`Address` field to the right of the name, and enter the location's"
" address. It is possible to enter multiple lines in the address field."
msgstr ""

#: ../../content/applications/hr/lunch.rst:69
msgid "Repeat this for all locations that need to be added."
msgstr ""

#: ../../content/applications/hr/lunch.rst-1
msgid "A list view of the locations with the new button highlighted."
msgstr ""

#: ../../content/applications/hr/lunch.rst:76
#: ../../content/applications/hr/referrals/alerts.rst:3
msgid "Alerts"
msgstr "התראות"

#: ../../content/applications/hr/lunch.rst:78
msgid ""
"It is possible to set up alerts that can either be displayed in the *Lunch* "
"app, or be sent to specific employees via the *Discuss* app."
msgstr ""

#: ../../content/applications/hr/lunch.rst:81
msgid ""
"No alerts are pre-configured by default. To set up an alert, navigate to "
":menuselection:`Lunch app --> Configuration: Alerts`. Click the "
":guilabel:`New` button in the top-left corner and a blank lunch alert form "
"loads. Enter the following information on the form:"
msgstr ""

#: ../../content/applications/hr/lunch.rst:85
msgid ""
":guilabel:`Alert Name`: enter a name for the alert. This should be short and"
" descriptive, such as `New Lunch Vendor` or `Order by 11`. This field is "
"**required**."
msgstr ""

#: ../../content/applications/hr/lunch.rst:87
msgid ""
":guilabel:`Display`: select whether the alert is visible in the *Lunch* app "
"(:guilabel:`Alert in app)` or sent to employees via the *Discuss* app in a "
"chat window (:guilabel:`Chat notification`)."
msgstr ""

#: ../../content/applications/hr/lunch.rst:90
msgid ""
":guilabel:`Recipients`: this field only appears if :guilabel:`Chat "
"notification` is selected for the :guilabel:`Display` option. Select who "
"receives the chat alert. The options are: :guilabel:`Everyone`, "
":guilabel:`Employee who ordered last week`, :guilabel:`Employee who ordered "
"last month`, or :guilabel:`Employee who ordered last year`."
msgstr ""

#: ../../content/applications/hr/lunch.rst:95
msgid ""
":guilabel:`Location`: select the locations the alert should appear for from "
"the drop-down menu. Multiple locations can be selected. This field is "
"**required**, therefore, if the alert applies to all locations, select all "
"the locations from the drop-down menu."
msgstr ""

#: ../../content/applications/hr/lunch.rst:98
msgid ""
":guilabel:`Show Until`: if the alert should expire on a specific date, "
"select the date from the calendar picker."
msgstr ""

#: ../../content/applications/hr/lunch.rst:100
msgid ""
":guilabel:`Active`: this option is on (appears green) by default. To turn "
"off the alert, click the toggle so that it no longer appears green."
msgstr ""

#: ../../content/applications/hr/lunch.rst:102
msgid ""
":guilabel:`Message`: Enter the alert message in this field. This field is "
"**required**."
msgstr ""

#: ../../content/applications/hr/lunch.rst:103
msgid ""
":guilabel:`Notification Time`: select the days of the week the alert should "
"be sent. By default, all seven days are active. Click on a checkbox to "
"change the setting from active to inactive."
msgstr ""

#: ../../content/applications/hr/lunch.rst:106
msgid ""
"If :guilabel:`Chat notification` was selected for the :guilabel:`Display` "
"option, a :guilabel:`Time` field also appears. Enter the time the chat "
"message should be sent. Next, select if the time is either :guilabel:`AM` or"
" :guilabel:`PM` using the drop-down menu to the right of the "
":guilabel:`Time` field."
msgstr ""

#: ../../content/applications/hr/lunch.rst-1
msgid ""
"An alert form with all of the information filled out for a chat alert sent at 10:30 AM,\n"
"asking employees to submit orders by 11:30 AM."
msgstr ""

#: ../../content/applications/hr/lunch.rst:117
msgid ":doc:`lunch/vendors`"
msgstr ""

#: ../../content/applications/hr/lunch.rst:118
msgid ":doc:`lunch/products`"
msgstr ""

#: ../../content/applications/hr/lunch.rst:119
msgid ":doc:`lunch/orders`"
msgstr ""

#: ../../content/applications/hr/lunch.rst:120
msgid ":doc:`lunch/user-accounts`"
msgstr ""

#: ../../content/applications/hr/lunch.rst:121
msgid ":doc:`lunch/management`"
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:3
msgid "Lunch management"
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:5
msgid ""
"In Odoo's *Lunch* application, it is required to have someone manage the "
"orders, vendors, and products. In addition, someone must be responsible for "
"the orders, and notifying employees when their orders have arrived. This can"
" be the same person."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:9
msgid ""
"Orders can be :ref:`canceled <lunch/cancel>`, :ref:`sent to the vendor "
"<lunch/send-orders>`, :ref:`confirmed <lunch/confirm-orders>` upon arrival, "
"and :ref:`employees can be notified <lunch/notify>`, either from the "
":ref:`Today's Orders <lunch/todays-orders>` dashboard, or the :ref:`Control "
"Vendors <lunch/control_vendors>` dashboard."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:14
msgid ""
"To manage the *Lunch* app, users need the appropriate "
":guilabel:`Administrator` rights. These can be set by navigating to the "
":menuselection:`Settings app` and selecting :guilabel:`Manage Users`. Then, "
"click on the desired user to view their access rights."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:18
msgid ""
"For more information on access rights, refer to the :doc:`Access rights "
"<../../general/users/access_rights/>` documentation."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:22
msgid ""
"Only users with administration rights are able to view the "
":guilabel:`Manager` and :guilabel:`Configuration` menus in the *Lunch* "
"application."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:28
msgid "Today's Orders"
msgstr "הזמנות היום"

#: ../../content/applications/hr/lunch/management.rst:30
msgid ""
"To view and manage the orders for the day, navigate to :menuselection:`Lunch"
" app --> Manager --> Today's Orders`. All orders for the day are presented "
"in a list view on the :guilabel:`Today's Orders` dashboard, with a filter "
"for :guilabel:`Today`, and grouped by :guilabel:`Vendor`, by default."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:35
#: ../../content/applications/hr/lunch/management.rst:160
msgid "The following information appears in the list:"
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:37
#: ../../content/applications/hr/lunch/management.rst:162
msgid ":guilabel:`Order Date`: the date the order was placed."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:38
#: ../../content/applications/hr/lunch/management.rst:163
msgid ":guilabel:`Vendor`: the vendor the product is being ordered from."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:39
#: ../../content/applications/hr/lunch/management.rst:164
msgid ":guilabel:`Product`: the specific product ordered."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:40
#: ../../content/applications/hr/lunch/management.rst:165
msgid ":guilabel:`Extras`: any extras selected for the product."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:41
#: ../../content/applications/hr/lunch/management.rst:166
msgid ":guilabel:`Notes`: any information needed to be sent to the vendor."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:42
#: ../../content/applications/hr/lunch/management.rst:167
msgid ":guilabel:`User`: the user who ordered the product."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:43
#: ../../content/applications/hr/lunch/management.rst:168
msgid ":guilabel:`Lunch Location`: where the product is set to be delivered."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:44
#: ../../content/applications/hr/lunch/management.rst:169
msgid ""
":guilabel:`Price`: the total price for the product, including all extras."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:45
#: ../../content/applications/hr/lunch/management.rst:170
msgid ":guilabel:`Status`: the current status of the product."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:46
#: ../../content/applications/hr/lunch/management.rst:171
msgid ""
":guilabel:`Company`: the company under which the order was placed. This only"
" appears in a multi-company database."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst-1
msgid ""
"The list that appears in the Today's Orders dashboard, with the filters and top column\n"
"names highlighted."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:57
msgid "Cancel orders"
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:59
msgid "All users can cancel an order, not just managers of the *Lunch* app."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:61
msgid ""
"To cancel an order from a vendor, individual products **must** be canceled "
"one at a time."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:63
msgid ""
"On the :guilabel:`Today's Orders` dashboard, a :guilabel:`✖️ Cancel` button "
"is shown at the far-right of each product line that can be canceled. Click "
"the :guilabel:`✖️ Cancel` button to cancel the order for that individual "
"product."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:68
msgid ""
"Only products with a red :guilabel:`Status` tag of :guilabel:`Ordered` can "
"be canceled."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst-1
msgid "Order lines with the cancel button highlighted."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:77
msgid "Send orders"
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:79
msgid ""
"The first step in managing the *Lunch* app is to send the orders to the "
"vendors."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:81
msgid ""
"When orders are ready to be sent, the manager responsible for sending orders"
" **must** send the orders to the vendor, outside of the database (call, "
"online order, etc.)."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:84
msgid ""
"Once orders have been placed with the vendors, click the :guilabel:`Send "
"Orders` button that appears next to each vendor's name and phone number."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:87
msgid ""
"Once sent, the :guilabel:`Send Orders` button changes to a "
":guilabel:`Confirm Orders` button, and the :guilabel:`Status` column is "
"updated from red :guilabel:`Ordered` tags to blue :guilabel:`Sent` tags, "
"indicating the order has been sent to the vendor. Users who have placed "
"orders in the *Lunch* app rely on the :guilabel:`Status` tags to track their"
" orders."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst-1
msgid ""
"A vendor's order with the X Cancel and Send Orders buttons highlighted."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:99
msgid "Confirm orders"
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:101
msgid ""
"After orders have been sent to the vendor, the next step is to confirm the "
"orders after they have been delivered."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:104
msgid ""
"On the :guilabel:`Today's Orders` dashboard, click the :guilabel:`Confirm "
"Orders` button that appears next to the vendor's name and phone number."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:107
msgid ""
"Once confirmed, the :guilabel:`Confirm Orders` button disappears, and the "
":guilabel:`Status` column is updated from blue :guilabel:`Sent` tags to "
"green :guilabel:`Received` tags, indicating the vendor has delivered the "
"orders."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:111
msgid ""
"In addition, the :guilabel:`✖️ Cancel` button at the end of each product "
"line changes to a :guilabel:`✉️ Send Notification` button."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:114
msgid ""
"If needed, instead of confirming all of the individual products from a "
"vendor, individual products can be confirmed one at a time. To confirm an "
"individual product, click the :guilabel:`✔️ Confirm` button at the end of "
"the individual product line. When confirming individual products with this "
"method, the :guilabel:`Confirm Orders` button remains on the vendor line."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst-1
msgid ""
"The Today's Orders dashboard, with the two different ways to confirm an "
"order highlighted."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:124
msgid ""
"A vendor receives an order for three pizzas, and an order of garlic knots. "
"When the delivery is made to the company, the *Lunch* manager notices the "
"garlic knots are missing."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:127
msgid ""
"The manager first marks the three pizzas as received, by individually "
"confirming the products with the :guilabel:`✔️ Confirm` button at the end of"
" each product line."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:130
msgid ""
"Later, when the vendor delivers the garlic knots, the manager can either "
"click the :guilabel:`✔️ Confirm` button at the end of the line for the "
"garlic knots, or click the :guilabel:`Confirm Orders` button that appears "
"next to the vendor's name and phone number."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:137
msgid "Notify employees"
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:139
msgid ""
"After products are received, and the orders are confirmed, the employees "
"**must** be informed that their orders have been delivered, and are ready to"
" be picked up."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:142
msgid ""
"Unlike sending and confirming orders, notifications must be sent "
"individually, and cannot be sent in a batch."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:145
msgid ""
"To notify the user their product has arrived, click the :guilabel:`✉️ Send "
"Notification` button at the end of each product line. An email is sent to "
"the user informing them their products have been delivered."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:152
msgid "Control Vendors"
msgstr "בקרת ספקים"

#: ../../content/applications/hr/lunch/management.rst:154
msgid ""
"All orders for all vendors, both past and present, can be found in the "
"*Control Vendors* dashboard. To access these records, navigate to "
":menuselection:`Lunch app --> Manager --> Control Vendors`."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:157
msgid ""
"All orders appear in a list view, grouped alphabetically by "
":guilabel:`Vendor`. The list loads with all vendors expanded to show all "
"order lines for every vendor, by default."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:174
msgid ""
"Orders can be :ref:`canceled <lunch/cancel>`, :ref:`sent to the vendor "
"<lunch/send-orders>`, :ref:`confirmed <lunch/confirm-orders>` upon arrival, "
"and :ref:`employees can be notified <lunch/notify>` using the same method as"
" on the :ref:`Today's Orders <lunch/todays-orders>` dashboard."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst-1
msgid ""
"A list view of all the orders as seen in the Control Vendors dashboard."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:184
msgid ""
"The difference between the :ref:`Today's Orders <lunch/todays-orders>` "
"dashboard and the :ref:`Control Vendors <lunch/control_vendors>` dashboard "
"is that the *Today's Orders* dashboard **only** displays orders for the "
"current day, while the :guilabel:`Control Vendors` dashboard displays "
"**all** orders made in the *Lunch* app."
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:190
msgid ":doc:`../lunch`"
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:191
msgid ":doc:`orders`"
msgstr ""

#: ../../content/applications/hr/lunch/management.rst:192
msgid ":doc:`user-accounts`"
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:5
#: ../../content/applications/hr/lunch/vendors.rst:76
msgid "Orders"
msgstr "הזמנות"

#: ../../content/applications/hr/lunch/orders.rst:7
msgid ""
"When the *Lunch* application is opened, the :guilabel:`Order Your Lunch` "
"dashboard loads. This view is also accessed by navigating to "
":menuselection:`Lunch app --> My Lunch --> New Order`."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:10
msgid ""
"The :guilabel:`Order Your Lunch` dashboard provides a summary of lunch "
"offerings, the user's account information, and the current day's orders, "
"along with their statuses."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:14
msgid "Order Your Lunch"
msgstr "הזמן את ארוחת הצהריים שלך"

#: ../../content/applications/hr/lunch/orders.rst:16
msgid ""
"On the main :guilabel:`Order Your Lunch` dashboard, all the necessary "
"information needed to place an order is visible. The default filter for the "
"products is :guilabel:`Available Today`, which is present in the "
":guilabel:`Search...` bar. This filter shows only products that can be "
"purchased that day, based on the :ref:`vendor's availability "
"<lunch/availability>`."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:21
msgid ""
"The left-side of the dashboard displays the various :guilabel:`Categories` "
"of products available, along with the :guilabel:`Vendors` supplying the "
"products. To the right of each line is a number, which indicates how many "
"products are associated with that respective category or vendor."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:25
msgid ""
"To filter the products by categories or vendors, tick the checkbox next to "
"the desired category or vendor to only view items related to those "
"selections. Multiple selections can be made in each section."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:30
msgid ""
"If multiple selections are made, **only** products that fall under **all** "
"the selected options are shown."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:33
msgid ""
"The top portion of the dashboard, which serves as an order summary, displays"
" the user's account information, and the order details for today, if any "
"orders have been placed."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:36
msgid ""
"The main section, beneath the user's information, displays all the products "
"in a default Kanban view. Each product card displays the name, cost, vendor,"
" photo, and description of the product. If the product is configured as new,"
" it also displays a :guilabel:`New` tag."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst-1
msgid "The *Lunch* app dashboard with all areas highlighted."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:45
msgid ""
"Anywhere a vendor's name is listed in the *Lunch* app, such as on Kanban "
"product cards, their phone number is listed, as well."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:48
msgid ""
"The products can also be displayed in a list view, by clicking the "
":guilabel:`≣ (four parallel lines)` icon in the top-right corner of the "
"dashboard."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:52
msgid "Placing orders"
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:54
msgid ""
"To place a lunch order, navigate to the main :guilabel:`Order Your Lunch` "
"dashboard, by either opening the *Lunch* app, or by navigating to "
":menuselection:`Lunch app --> My Lunch --> New Order`."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:58
msgid "Add products to an order"
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:60
msgid ""
"From the :guilabel:`Order Your Lunch` dashboard, click on a desired product "
"to add to an order, and the product appears in a :guilabel:`Configure Your "
"Order` pop-up window."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:63
msgid ""
"At the top of the pop-up window is the product image, name, and price. "
"Beneath that, there is a potential :guilabel:`Extras` field, showcasing any "
":ref:`extra items or options <lunch/extras>`. Tick the checkbox next to any "
"desired extras present in the :guilabel:`Extras` field to add them to the "
"order."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:68
msgid ""
"Each extra option is organized by a category, complete with its name and "
"price. As extras are selected, the displayed price at the top of the pop-up "
"window updates to reflect all current selections."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:72
msgid ""
"Beneath the :guilabel:`Extras` field is the :guilabel:`Description` of the "
"product, followed by a :guilabel:`Notes` field. The :guilabel:`Notes` field "
"is used to enter any vital information, which is then sent to the vendor "
"regarding the order, such as any special requests or food allergies."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:76
msgid ""
"When all selections for the product have been made, click the :guilabel:`Add"
" To Cart` button in the lower-left of the pop-up window. To cancel the "
"order, click the :guilabel:`Discard` button."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst-1
msgid ""
"The pop-up window for a personal pizza, with all the extras highlighted and "
"selected."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:86
msgid ""
"Depending on how the various :ref:`extras <lunch/configure-extras>` are "
"configured for a vendor, it is possible to receive an error when attempting "
"to add products to the cart."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:89
msgid ""
"An error can occur when a configured product **requires** the user to select"
" an option in the :guilabel:`Extras` field, but the user neglects to make "
"one."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:92
msgid ""
"When this occurs, a :guilabel:`Validation Error` pop-up window appears. The "
"error is briefly explained in the pop-up window. Click :guilabel:`Close` to "
"close the window, and make any necessary changes to the :guilabel:`Configure"
" Your Order` pop-up window."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:97
msgid ""
"The vendor, The Pizza Palace, provides a free beverage with any purchase. "
"Their products are configured so that a beverage selection is **required** "
"in the :guilabel:`Extras` field *before* adding one of their products to the"
" cart."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:101
msgid ""
"If a selection is **not** made, an error occurs. The message that appears is"
" `You have to order one and only one Free Beverage with Purchase`."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:0
msgid ""
"The :guilabel:`Validation Error` pop-up window with the specific error for the free\n"
"beverage displayed."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:110
msgid "Your Order summary"
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:112
msgid ""
"When at least one item is added to an order, the items appear at the top of "
"the dashboard in the :guilabel:`Your Order` summary. In addition to the "
"products, users can view the account information, in addition to all the "
"information related to orders placed during the current calendar day."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:116
msgid ""
"As products are added to an order, they appear at the top center of the "
"summary box. Each product is listed beneath the words :guilabel:`Your "
"Order`, with the product name, quantity, and a status tag."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:119
msgid "The available tags that can be displayed for each item are:"
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:121
msgid ""
":guilabel:`To Order`: the product has been added to the cart, but has not "
"been purchased yet by the user."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:123
msgid ""
":guilabel:`Ordered`: the product has been purchased by the user, and is "
"waiting to be sent to the vendor by a *Lunch* app manager."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:125
msgid ""
":guilabel:`Sent`: the order for the product has been sent to the vendor by a"
" *Lunch* app manager."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:126
msgid ""
":guilabel:`Received`: the product has been delivered by the vendor to the "
"user's location, and has been verified as received by a *Lunch* app manager."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:129
msgid ""
"Product quantities can be adjusted by clicking the :guilabel:`➕ (plus sign)`"
" or :guilabel:`➖ (minus sign)` to the left of the listed product. The "
"product price adjusts in real-time to display the cost for the currently "
"selected quantity of the product."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:133
msgid ""
"The right side of the :guilabel:`Your Order` summary displays the purchasing"
" information. The :guilabel:`Total` amount for the entire day's lunch order "
"is displayed. The :guilabel:`Already Paid` field indicates how much has been"
" paid that day towards the :guilabel:`Total` amount. The :guilabel:`To Pay` "
"field displays how much of the remaining :guilabel:`Total` amount must be "
"paid, in order to place the currently configured   order."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst-1
msgid ""
"The Your Orders section of the dashboard, with the purchasing information "
"highlighted."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:144
msgid ""
"Users can place multiple orders throughout the day, and are not restricted "
"to only placing one lunch order each day. Multiple orders might need to be "
"placed, due to users forgetting to add items to an order, or if there are "
"multiple meals that are available to be purchased for the office ()not just "
"lunch), and so on."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:149
msgid ""
"Depending on the various vendors, and how the vendors and products are "
"configured, it is possible to order breakfast, lunch, dinner, coffee, and/or"
" snacks."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:153
msgid "Submit an order"
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:155
msgid ""
"To place the order, click the :guilabel:`Order Now` button on the right-side"
" of the :guilabel:`Your Order` summary. The user is charged the amount that "
"is displayed in the :guilabel:`To Pay` field, and the cost is deducted from "
"their *Lunch* account balance."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:159
msgid ""
"Once the order is placed, the tags for the items just purchased in the "
":guilabel:`Your Order` field change from orange :guilabel:`To Order` tags to"
" red :guilabel:`Ordered` tags."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:163
msgid "Track an order"
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:165
msgid ""
"When orders have been sent to the vendors, the tags for the items in the "
":guilabel:`Your Order` summary change from red :guilabel:`Ordered` tags to "
"blue :guilabel:`Sent` tags."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:168
msgid ""
"Once orders have been received and verified, the tags change from blue "
":guilabel:`Sent` tags to green :guilabel:`Received` tags."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:172
msgid "Receive an order"
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:174
msgid ""
"When orders are received at the delivery location, they are confirmed by a "
"*Lunch* app manager, and a notification is sent to the employee who ordered "
"the food."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:178
msgid "My Orders"
msgstr "ההזמנות שלי"

#: ../../content/applications/hr/lunch/orders.rst:180
msgid ""
"To view a full list of all orders placed in the *Lunch* app for the "
"currently signed-in user, navigate to :menuselection:`Lunch app --> My Lunch"
" --> My Order History`. This navigates to the :guilabel:`My Orders` "
"dashboard. The data is filtered by :guilabel:`My Orders` and grouped by "
":guilabel:`Order Date: Day`, by default, both of which are located in the "
":guilabel:`Search...` bar."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:185
msgid ""
"All products appear in a list view, organized by date. The list displays the"
" :guilabel:`Order Date`, :guilabel:`Vendor`, :guilabel:`Product`, "
":guilabel:`Extras`, :guilabel:`Notes`, :guilabel:`User`, :guilabel:`Lunch "
"Location`, :guilabel:`Price`, and :guilabel:`Status` information. If in a "
"multi-company database, a :guilabel:`Company` column also appears."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:190
msgid ""
"The total cost for each order is displayed on the line containing the order "
"date. At the bottom of the list, beneath all the lines, the overall total "
"amount paid for all the orders appears, under the :guilabel:`Price` column."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:194
msgid ""
"At the end of each product line with a status of :guilabel:`Ordered` or "
":guilabel:`Sent`, an :guilabel:`X Cancel` button appears. Click :guilabel:`X"
" Cancel` to cancel that product order. Once a product order has been "
"canceled, the money paid for that product is refunded, and appears in the "
"user's account."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:199
msgid ""
"At the end of each product line with a status of :guilabel:`Received`, a "
":guilabel:`Re-order` button appears. Click :guilabel:`Re-order` to instantly"
" reorder that same product, with the same extras, if applicable. The new "
"order appears in the list, under the current date, and the product is paid "
"for, with money deducted from the user's account."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst-1
msgid "The list view that appears when navigating to the My Orders dashboard."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:209
msgid "My Account"
msgstr "החשבון שלי"

#: ../../content/applications/hr/lunch/orders.rst:211
msgid ""
"To view a summary of all transactions in the user's account, navigate to "
":menuselection:`Lunch app --> My Lunch --> My Account History`. Doing so "
"reveals the :guilabel:`My Account` dashboard."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:214
msgid ""
"The default presentation of the :guilabel:`My Account` dashboard displays "
"all entries, from newest to oldest. The :guilabel:`Date`, "
":guilabel:`Description`, and :guilabel:`Amount` are the only fields "
"displayed in the list."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:218
msgid ""
"Entries with a negative figure listed in the :guilabel:`Amount` column "
"represent products purchased in the *Lunch* app. These appear in a `$-XX.XX`"
" format."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst:221
msgid ""
"Entries with a positive balance either represent funds added to the user's "
"lunch account, or canceled orders that were eventually refunded to the user."
" These appear in a `$XX.XX` format."
msgstr ""

#: ../../content/applications/hr/lunch/orders.rst-1
msgid ""
"The My Account dashboard with the entry for adding funds to the user's lunch account\n"
"highlighted."
msgstr ""

#: ../../content/applications/hr/lunch/products.rst:3
msgid "Products"
msgstr "מוצרים"

#: ../../content/applications/hr/lunch/products.rst:5
msgid ""
"Odoo's *Lunch* app does **not** come with any products preconfigured. The "
"individual products being offered must first be configured before orders can"
" be placed."
msgstr ""

#: ../../content/applications/hr/lunch/products.rst:8
msgid ""
"To add and configure products for the *Lunch* app, navigate to "
":menuselection:`Lunch app --> Configuration --> Products`. Next, click the "
":guilabel:`New` button in the top-left corner, and a blank product form "
"loads."
msgstr ""

#: ../../content/applications/hr/lunch/products.rst:14
msgid ""
":guilabel:`Product Name`: enter the name for the product. This field is "
"**required**."
msgstr ""

#: ../../content/applications/hr/lunch/products.rst:15
msgid ""
":guilabel:`Product Category`: using the drop-down menu, select the "
":ref:`category <lunch/product-categories>` this product falls under. This "
"field is **required**."
msgstr ""

#: ../../content/applications/hr/lunch/products.rst:17
msgid ""
":guilabel:`Vendor`: using the drop-down menu, select the vendor that "
"supplies this product. This field is **required**."
msgstr ""

#: ../../content/applications/hr/lunch/products.rst:19
msgid ""
":guilabel:`Price`: enter the price for the product. The currency is "
"determined by the company's localization."
msgstr ""

#: ../../content/applications/hr/lunch/products.rst:21
msgid ""
":guilabel:`Description`: enter a description of the product in this field. "
"This description appears beneath the product photo when users are viewing "
"the day's options."
msgstr ""

#: ../../content/applications/hr/lunch/products.rst:23
msgid ""
":guilabel:`New Until`: using the calendar popover, select the date on which "
"the product is no longer labeled as new. Until this date, a green `New` tag "
"appears on the product."
msgstr ""

#: ../../content/applications/hr/lunch/products.rst:25
msgid ""
":guilabel:`Company`: if the product should only be available to a specific "
"company, select it from the drop-down menu. If this field is left blank, "
"this product is available for all companies in the database."
msgstr ""

#: ../../content/applications/hr/lunch/products.rst:28
msgid ""
"**Image**: hover over the image box in the top-right corner of the form, and"
" click the :icon:`fa-pencil` :guilabel:`(pencil)` icon that appears. A file "
"explorer pop-up window appears. Navigate to the image, then click "
":guilabel:`Open`."
msgstr ""

#: ../../content/applications/hr/lunch/products.rst-1
msgid "A product form filled out for a nine inch pizza."
msgstr ""

#: ../../content/applications/hr/lunch/products.rst:39
msgid "Product categories"
msgstr "קטגוריות מוצר"

#: ../../content/applications/hr/lunch/products.rst:41
msgid ""
"Product categories organize the offerings in the *Lunch* app, and allows "
"users to quickly filter them when reviewing the menu for the day."
msgstr ""

#: ../../content/applications/hr/lunch/products.rst:44
msgid ""
"To add or modify categories, navigate to :menuselection:`Lunch app --> "
"Configuration: Product Categories`. The available categories appear in a "
"list view."
msgstr ""

#: ../../content/applications/hr/lunch/products.rst:47
msgid ""
"In the *Lunch* app, there are four default categories: :guilabel:`Sandwich`,"
" :guilabel:`Pizza`, :guilabel:`Burger`, and :guilabel:`Drinks`."
msgstr ""

#: ../../content/applications/hr/lunch/products.rst:50
msgid ""
"To add a new category, click the :guilabel:`New` button in the top-left "
"corner, and a blank category form loads."
msgstr ""

#: ../../content/applications/hr/lunch/products.rst:53
msgid ""
"Enter a name in the :guilabel:`Product Category` field. If the category is "
"company-specific and should only appear for a certain company, select the "
":guilabel:`Company` from the drop-down menu."
msgstr ""

#: ../../content/applications/hr/lunch/products.rst:56
msgid ""
"If desired, add a photo for the category. Hover over the image box in the "
"top-right, and click the :icon:`fa-pencil` :guilabel:`(pencil)` icon that "
"appears. This opens a file explorer pop-up window. Navigate to the image, "
"then click :guilabel:`Open`."
msgstr ""

#: ../../content/applications/hr/lunch/products.rst-1
msgid "The category form, with the fields filled out for a Soup category."
msgstr ""

#: ../../content/applications/hr/lunch/user-accounts.rst:3
msgid "Manage user accounts"
msgstr ""

#: ../../content/applications/hr/lunch/user-accounts.rst:5
msgid ""
"In Odoo's *Lunch* application, users pay for products directly from their "
"*Lunch* app account. For funds to appear in their account, a *Lunch* app "
"manager **must** transfer funds into each user's account."
msgstr ""

#: ../../content/applications/hr/lunch/user-accounts.rst:10
msgid ""
"To add funds and manage user accounts, the user must have "
":guilabel:`Administrator` access rights set for the *Lunch* application. "
"This is verified by navigating to :menuselection:`Settings app --> → Manage "
"Users`. Then, click on a user to view their various settings and access "
"rights."
msgstr ""

#: ../../content/applications/hr/lunch/user-accounts.rst:14
msgid ""
"For more information, refer to the :doc:`Access rights "
"<../../general/users/access_rights/>` documentation."
msgstr ""

#: ../../content/applications/hr/lunch/user-accounts.rst:17
msgid ""
"The *Lunch* application does **not** directly interface in any way with "
"software or products linked to any monetary accounts or billing. Money "
"**cannot** be transferred from users' bank accounts, nor can users' credit "
"cards be charged."
msgstr ""

#: ../../content/applications/hr/lunch/user-accounts.rst:21
msgid ""
"Odoo's *Lunch* application **only** allows for manual entries of cash "
"exchanges that are handled by the *Lunch* app manager. It is up to each "
"individual company to create the method with which lunch accounts are "
"replenished."
msgstr ""

#: ../../content/applications/hr/lunch/user-accounts.rst:26
msgid ""
"Some examples of how money can be organized and transferred within a "
"company:"
msgstr ""

#: ../../content/applications/hr/lunch/user-accounts.rst:28
msgid ""
"Cash is handed to the *Lunch* app manager, who then updates the user's "
"account."
msgstr ""

#: ../../content/applications/hr/lunch/user-accounts.rst:29
msgid ""
"Money is automatically deducted from the user's paychecks, then the *Lunch* "
"app manager updates the account when paychecks are issued. This requires "
":ref:`adding a salary attachment <payroll/worked-days-inputs>` for the "
"user's payslip in the *Payroll* app."
msgstr ""

#: ../../content/applications/hr/lunch/user-accounts.rst:32
msgid ""
"Companies can sell \"lunch tickets\" at a set price (for example, one ticket"
" costs $5.00). Users can purchase tickets from a *Lunch* app manager, who "
"then updates the user's account."
msgstr ""

#: ../../content/applications/hr/lunch/user-accounts.rst:38
msgid "Cash Moves"
msgstr "תנועות מזומן"

#: ../../content/applications/hr/lunch/user-accounts.rst:40
msgid ""
"To add funds to user accounts, each cash move must be individually logged. "
"To view all cash move records, or create a new cash move, navigate to "
":menuselection:`Lunch app --> Manager --> Cash Moves`. Doing so reveals the "
":guilabel:`Cash Moves` dashboard."
msgstr ""

#: ../../content/applications/hr/lunch/user-accounts.rst:44
msgid ""
"On the :guilabel:`Cash Moves` dashboard, all cash moves are presented in a "
"default list view, displaying each record's :guilabel:`Date`, "
":guilabel:`User`, :guilabel:`Description`, and :guilabel:`Amount`. The total"
" of all the cash moves is displayed at the bottom of the :guilabel:`Amount` "
"column."
msgstr ""

#: ../../content/applications/hr/lunch/user-accounts.rst-1
msgid "The list view of all cash moves."
msgstr ""

#: ../../content/applications/hr/lunch/user-accounts.rst:54
msgid "Add funds"
msgstr ""

#: ../../content/applications/hr/lunch/user-accounts.rst:56
msgid ""
"To add funds to a lunch account, click the :guilabel:`New` button, located "
"in the top-left corner of the :guilabel:`Cash Moves` dashboard."
msgstr ""

#: ../../content/applications/hr/lunch/user-accounts.rst:59
msgid ""
"A blank :guilabel:`Cash Moves` form loads. Enter the following information "
"on the form:"
msgstr ""

#: ../../content/applications/hr/lunch/user-accounts.rst:61
msgid ""
":guilabel:`User`: select the user depositing cash into their account from "
"the drop-down menu. If the user is not in the database, they can be created "
"by typing their name in the :guilabel:`User` field, and clicking either "
":guilabel:`Create \"user\"` or :guilabel:`Create and edit...` to create the "
"user and edit the :guilabel:`Create User` form."
msgstr ""

#: ../../content/applications/hr/lunch/user-accounts.rst:65
msgid ""
":guilabel:`Date`: using the calendar popover, select the date the "
"transaction occurred."
msgstr ""

#: ../../content/applications/hr/lunch/user-accounts.rst:66
msgid ":guilabel:`Amount`: enter the amount being added to the lunch account."
msgstr ""

#: ../../content/applications/hr/lunch/user-accounts.rst:67
msgid ":guilabel:`Description`: enter a brief description of the transaction."
msgstr ""

#: ../../content/applications/hr/lunch/user-accounts.rst-1
msgid "The cash move form filled out for a transaction of $40.00."
msgstr ""

#: ../../content/applications/hr/lunch/user-accounts.rst:75
msgid "Control Accounts"
msgstr "בקרת חשבונות"

#: ../../content/applications/hr/lunch/user-accounts.rst:77
msgid ""
"An overview of every transaction in the *Lunch* app, including all cash "
"deposits and purchases, can be viewed on the main *Control Accounts* "
"dashboard. To access this dashboard, navigate to :menuselection:`Lunch app "
"--> Manager --> Control Accounts.`"
msgstr ""

#: ../../content/applications/hr/lunch/user-accounts.rst:81
msgid ""
"All transactions are grouped :guilabel:`By Employee`, and listed "
"alphabetically by the user's first name. At the end of the user's name, a "
"number appears. This indicates the number of individual records logged for "
"that user."
msgstr ""

#: ../../content/applications/hr/lunch/user-accounts.rst:85
msgid ""
"The default view is to have all individual transactions hidden. To view all "
"transactions for a user, click the :guilabel:`▶ (triangle)` icon to the left"
" of the desired name to expand that specific group."
msgstr ""

#: ../../content/applications/hr/lunch/user-accounts.rst:89
msgid ""
"Each record includes the :guilabel:`Date`, :guilabel:`User`, "
":guilabel:`Description`, and :guilabel:`Amount`."
msgstr ""

#: ../../content/applications/hr/lunch/user-accounts.rst-1
msgid ""
"The Control Accounts dashboard with two employee's transactions expanded."
msgstr ""

#: ../../content/applications/hr/lunch/user-accounts.rst:97
msgid ""
"This list only displays the various transactions within the *Lunch* app, and"
" does **not** allow modifications to be made to any records listed."
msgstr ""

#: ../../content/applications/hr/lunch/user-accounts.rst:100
msgid ""
"Cash moves can be modified, but **only** from the :ref:`Cash Moves "
"<lunch/cash-moves>` dashboard, not from the :guilabel:`Control Accounts` "
"dashboard."
msgstr ""

#: ../../content/applications/hr/lunch/user-accounts.rst:103
msgid "It is **not** possible to modify any product-related records."
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:3
msgid "Vendors"
msgstr "ספקים"

#: ../../content/applications/hr/lunch/vendors.rst:5
msgid ""
"Before :doc:`products can be added <products>` to the *Lunch* app, the "
"restaurants that provide the food **must** be configured."
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:8
msgid ""
"To add a new vendor, first navigate to :menuselection:`Lunch app --> "
"Configuration --> Vendors`. Here, all currently configured vendors for the "
"*Lunch* app appear in a default Kanban view. To change to a list view, click"
" the :icon:`oi-view-list` :guilabel:`(list)` icon in the top-right corner."
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:14
msgid ""
"No vendors are preconfigured in the *Lunch* app, so all vendors **must** be "
"added to the database."
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:17
msgid ""
"To add a new vendor, click the :guilabel:`New` button in the top-left "
"corner, and a new lunch supplier form loads."
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:20
msgid "Fill out the following fields on the vendor form:"
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:22
msgid ":ref:`Vendor information <lunch/vendor-info>`"
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:23
msgid ":ref:`Availability <lunch/availability>`"
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:24
msgid ":ref:`Orders <lunch/orders>`"
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:25
msgid ":ref:`Extras <lunch/extras>`"
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:30
msgid "Vendor information"
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:32
msgid ":guilabel:`Vendor`: enter a name for the vendor."
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:33
msgid ""
":guilabel:`Vendor` (beneath the line for vendor name): select the vendor "
"from the drop-down menu. If the vendor has not already been entered in the "
"system, type in the vendor name, and click either :guilabel:`Create \"new "
"vendor name\"` to add them. Alternatively, click :guilabel:`Create and "
"edit...` to create the vendor, and edit the vendor form. The vendor form "
"allows for more detail, aside from the name, to be entered, such as contact "
"information."
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:40
msgid ""
"If a selection is made to the drop-down :guilabel:`Vendor` field, the "
":guilabel:`Vendor` text field (above, for the vendor's name) updates with "
"the name of the vendor chosen from the drop-down menu."
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:44
msgid ""
"The list of vendors that is presented in the drop-down menu is pulled from "
"the *Contacts* application."
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:47
msgid ":guilabel:`Address`: enter the vendor's address in the various fields."
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:48
msgid ":guilabel:`Email`: enter the vendor's email."
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:49
msgid ":guilabel:`Phone`: enter the vendor's phone number."
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:50
msgid ""
":guilabel:`Company`: if this vendor is only available to a specific company,"
" select the company from the drop-down menu. If this field is left blank, "
"the vendor's items are available to **all** companies."
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst-1
msgid "The top portion of the vendor form filled out."
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:61
msgid "Availability"
msgstr "זמינות"

#: ../../content/applications/hr/lunch/vendors.rst:63
msgid ""
"The :guilabel:`AVAILABILITY` section presents a table with two rows. The "
"days of the week populate the top row, and the bottom row has checkboxes. "
"Tick the corresponding checkbox for each day of the week the vendor is "
"available."
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:67
msgid "By default, Monday through Friday are ticked."
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst-1
msgid "The default view of the availability section, with Mon-Fri enabled."
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:78
msgid ""
"The :guilabel:`ORDERS` section of the vendor form details which locations "
"the vendor is available for, in addition to how and when orders are placed "
"and received."
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:81
msgid ""
":guilabel:`Delivery`: using the drop-down menu, select :guilabel:`Delivery` "
"if the vendor delivers to the office, or select :guilabel:`No Delivery` if "
"orders must be picked up."
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:83
msgid ""
":guilabel:`Location`: select which locations are able to order from this "
"vendor. Multiple locations can be selected. If this field is left blank, "
"**all** locations can order from the vendor."
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:88
msgid ""
"An `HQ Office` location is created by default when creating a database, and "
"is available to select from the list."
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:91
msgid ""
":guilabel:`Send Order By`: click the radio button to select how orders are "
"sent to the vendor. The available options are :guilabel:`Phone` or "
":guilabel:`Email`."
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:93
msgid ""
":guilabel:`Order Time`: this field **only** appears if :guilabel:`Email` is "
"selected in the :guilabel:`Send Order By` field. Enter the time that an "
"order must be emailed for it to be accepted. Enter the time in the following"
" format: `HH:MM`. Then select either :guilabel:`AM` or :guilabel:`PM` from "
"the drop-down menu, next to the time field."
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst-1
msgid "The orders section of a vendor form, with all fields filled out."
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:105
msgid "Extras"
msgstr "תוספות"

#: ../../content/applications/hr/lunch/vendors.rst:107
msgid ""
"When ordering an item in the *Lunch* app, optional extra items, sometimes "
"referred to as *add-ons*, can be shown. These can be configured in any "
"manner that suits the products being offered."
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:110
msgid ""
"By default, Odoo allows for three types of extra items, which can be thought"
" of as *categories*. By default, the first type (or *category*) of add-ons "
"is labeled `Extras`, the second is labeled `Beverages`, and the third is "
"labeled `Extra Label 3`."
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:115
msgid ""
"When configuring the extras, it is important to keep in mind that all the "
"extras configured appear for **every item** offered by the vendor. That "
"means that only items which apply to **all** products from the vendor should"
" be added."
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:122
msgid "Configure extras"
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:124
msgid ""
"Enter the following information for each of the three available extra "
"sections:"
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:126
msgid ""
":guilabel:`Extra (#) Label`: enter a name for the type of extra, such as "
"`Toppings`. This can be thought of as a *category*."
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:128
msgid ""
":guilabel:`Extra (#) Quantity`: select how the extras are selected. The "
"options are:"
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:130
msgid ""
":guilabel:`None or More`: select this if the user is not required to make a "
"selection."
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:131
msgid ""
":guilabel:`One or More`: select this to **require** the user to make **at "
"least one** selection."
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:132
msgid ""
":guilabel:`Only One`: select this to **require** the user to **make only "
"one** selection."
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:135
msgid "Add extras"
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:137
msgid ""
"After the labels and quantities have been configured for an extra category, "
"the individual extra items must be added for each category."
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:140
msgid ""
"Click :guilabel:`Add a line` at the bottom of the list that appears on the "
"right-hand side of the extra category. Enter the :guilabel:`Name` and "
":guilabel:`Price` for each item being added. The price can remain at `$0.00`"
" if there is no cost. This is common for items like disposable silverware or"
" condiments."
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:146
msgid ""
"For a pizzeria that only offers personal pizzas, see their extras configured"
" as follows:"
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:148
msgid ""
"The first extra is configured for the various toppings they offer. The "
":guilabel:`Extra 1 Label` is set to `Toppings`, and the :guilabel:`Extra 1 "
"Quantity` is set to :guilabel:`None or More`. The various toppings are then "
"added, with their corresponding costs."
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:0
msgid "The first of the extras configured for pizza toppings."
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:156
msgid ""
"The pizzeria also offers a free beverage with any purchase. To set this up, "
"the :guilabel:`Extra 2 Label` is set to `Beverages`, and the "
":guilabel:`Extra 1 Quantity` is set to :guilabel:`Only One`. The various "
"beverage choices are added, and the cost for each remains zero."
msgstr ""

#: ../../content/applications/hr/lunch/vendors.rst:0
msgid "The second of the extras configured for a free beverage with purchase."
msgstr ""

#: ../../content/applications/hr/payroll.rst:5
#: ../../content/applications/hr/payroll.rst:81
#: ../../content/applications/hr/payroll/reporting.rst:31
msgid "Payroll"
msgstr "שכר"

#: ../../content/applications/hr/payroll.rst:7
msgid ""
"Odoo *Payroll* is used to process work entries and create payslips for "
"employees. *Payroll* works in conjunction with other Odoo apps, such as "
"*Employees*, *Time Off*, *Attendances*, and *Planning*."
msgstr ""

#: ../../content/applications/hr/payroll.rst:10
msgid ""
"The *Payroll* app helps ensure there are no issues or conflicts when "
"validating work entries. It also handles country-specific localizations to "
"ensure payslips follow local rules and taxes, and allows for salary "
"assignments."
msgstr ""

#: ../../content/applications/hr/payroll.rst:17
msgid ""
"Configure the *Payroll* app by navigating to :menuselection:`Payroll app -->"
" Configuration --> Settings`. The various settings for accounting, "
"localizations, time off, alerts, and payslips are specified here."
msgstr ""

#: ../../content/applications/hr/payroll.rst:22
msgid "Accounting"
msgstr "הנהלת חשבונות"

#: ../../content/applications/hr/payroll.rst:24
msgid ""
"The accounting section of the configuration menu relates to three options:"
msgstr ""

#: ../../content/applications/hr/payroll.rst:26
msgid ""
":guilabel:`Payroll Entries`: enable this option to post payroll slips in "
"accounting."
msgstr ""

#: ../../content/applications/hr/payroll.rst:27
msgid ":guilabel:`Payroll SEPA`: enable this option to create SEPA payments."
msgstr ""

#: ../../content/applications/hr/payroll.rst:28
msgid ""
":guilabel:`Batch Account Move Lines`: enable this option to have a single "
"account move line created from all the accounting entries from the same "
"period. This disables the generation of single payments."
msgstr ""

#: ../../content/applications/hr/payroll.rst:33
msgid "Localizations"
msgstr ""

#: ../../content/applications/hr/payroll.rst:35
msgid ""
"*Localizations* are country-specific settings pre-configured in Odoo at the "
"creation of the database, which account for all taxes, fees, and allowances "
"for that particular country."
msgstr ""

#: ../../content/applications/hr/payroll.rst:38
msgid ""
"The :guilabel:`Localization` section of the *Payroll* app "
":guilabel:`Settings` page may include specific settings that need to be set "
"for the specific locality. This selection also provides a detailed view of "
"all benefits provided to employees."
msgstr ""

#: ../../content/applications/hr/payroll.rst:42
msgid ""
"The settings and options shown in this section varies, depending on the "
"localization enabled for the database."
msgstr ""

#: ../../content/applications/hr/payroll.rst:46
msgid ""
"It is **not** recommended to alter the localization settings, unless "
"specifically required."
msgstr ""

#: ../../content/applications/hr/payroll.rst:49
msgid ""
"Odoo can handle a multi-company configuration. This is generally done when "
"there is a main company or office location, such as a headquarters, and "
"there are other offices/branches around the country or globe, that fall "
"under that main company or headquarters. In Odoo, each company, including "
"the headquarters, would be set up as their own company/branch using the "
"multi-company method."
msgstr ""

#: ../../content/applications/hr/payroll.rst:55
msgid ""
"Each individual company can have a different localization setting configured"
" for that specific company, since company locations can vary and be located "
"anywhere in the world, where rules and laws differ."
msgstr ""

#: ../../content/applications/hr/payroll.rst:59
msgid ""
"For more information on companies, refer to the :doc:`Companies "
"<../general/companies>` documentation, which covers how to set up companies."
msgstr ""

#: ../../content/applications/hr/payroll.rst:63
msgid "Time off"
msgstr ""

#: ../../content/applications/hr/payroll.rst:65
msgid ""
":guilabel:`Deferred Time Off`: if time off is taken after payslips are "
"validated, the time off needs to be applied to the following pay period. "
"Select the person responsible for validating these specific time off "
"situations using the drop-down menu in the :guilabel:`Responsible` field."
msgstr ""

#: ../../content/applications/hr/payroll.rst:70
msgid ""
"An employee is paid on the 15th of the month and the last day of the month. "
"Payslips are typically processed a day before."
msgstr ""

#: ../../content/applications/hr/payroll.rst:73
msgid ""
"If an employee's payslip is approved and processed on the 30th, but that "
"same employee takes an unexpected sick day on the 31st, the time off needs "
"to be logged."
msgstr ""

#: ../../content/applications/hr/payroll.rst:76
msgid ""
"Since the employee is already paid for a regular work day on the 31st, to "
"keep the time off balances correct, the sick day is moved/applied to the 1st"
" of the next month (the next pay period)."
msgstr ""

#: ../../content/applications/hr/payroll.rst:83
msgid ""
":guilabel:`Contract Expiration Notice Period`: enter the number of "
":guilabel:`Days` before a contract expires, and Odoo notifies the "
"responsible person about the upcoming expiration at that time."
msgstr ""

#: ../../content/applications/hr/payroll.rst:86
msgid ""
":guilabel:`Work Permit Expiration Notice Period`: enter the number of "
":guilabel:`Days` before a work permit expires, and Odoo notifies the "
"responsible person about the upcoming expiration at that time."
msgstr ""

#: ../../content/applications/hr/payroll.rst:89
msgid ""
":guilabel:`Payslip PDF Display`: enable this option to have payslips display"
" a PDF file on the payslip form."
msgstr ""

#: ../../content/applications/hr/payroll.rst:95
#: ../../content/applications/hr/payroll/contracts.rst:3
msgid "Contracts"
msgstr "חוזים"

#: ../../content/applications/hr/payroll.rst:97
msgid ""
"In order for an employee to be paid, they **must** have an active contract "
"for a specific type of employment. Creating and viewing contract templates, "
"and creating and viewing employment types, is possible from this section of "
"the configuration header menu."
msgstr ""

#: ../../content/applications/hr/payroll.rst:104
msgid "Templates"
msgstr "תבניות"

#: ../../content/applications/hr/payroll.rst:106
msgid ""
"Contract templates are used with the *Recruitment* application when sending "
"an offer to a candidate. The contract template forms the basis of an offer, "
"and can be modified for specific candidates or employees, when necessary. If"
" a contract template is created or modified in the *Payroll* application, "
"the changes are also reflected in the *Recruitment* application."
msgstr ""

#: ../../content/applications/hr/payroll.rst:112
msgid ""
"To access contract templates, the *Salary Configurator* "
"(`hr_contract_salary`) module **must** be :ref:`installed "
"<general/install>`."
msgstr ""

#: ../../content/applications/hr/payroll.rst:115
msgid ""
"To view all the current contract templates in the database, navigate to "
":menuselection:`Payroll app --> Configuration --> Contracts: Templates`."
msgstr ""

#: ../../content/applications/hr/payroll.rst:118
msgid ""
"On the :guilabel:`Contract Templates` page, all current contract templates "
"appear in a list view. To view the details of a contract template, click "
"anywhere on the line to open the contract form. The contract template can be"
" modified from this form. Proceed to make any desired changes to the "
"contract."
msgstr ""

#: ../../content/applications/hr/payroll.rst:123
msgid ""
"To create a new contract template, click the :guilabel:`New` button. Then, "
"enter the following information on the blank contract template form that "
"appears:"
msgstr ""

#: ../../content/applications/hr/payroll.rst:126
msgid ""
":guilabel:`Contract Reference`: enter a brief description for the template. "
"This should be clear and easily understood, as this name appears in the "
"*Recruitment* application, as well."
msgstr ""

#: ../../content/applications/hr/payroll.rst:128
msgid ""
":guilabel:`Working Schedule`: select the desired working schedule the "
"contract applies to from the drop-down menu. If a new working schedule is "
"needed, create a :ref:`new working schedule <payroll/new-working-schedule>`."
msgstr ""

#: ../../content/applications/hr/payroll.rst:131
msgid ""
":guilabel:`Work Entry Source`: select how the work entries are generated. "
"Choices are either:"
msgstr ""

#: ../../content/applications/hr/payroll.rst:133
msgid ""
":guilabel:`Working Schedule`: work entries are generated based on the "
"selected working schedule."
msgstr ""

#: ../../content/applications/hr/payroll.rst:134
msgid ""
":guilabel:`Attendances`: work entries are generated based on the employee's "
"attendance, as they are logged in the *Attendances* application. Refer to "
"the :ref:`Attendances <attendances/check-in>` documentation for information "
"on checking in and out."
msgstr ""

#: ../../content/applications/hr/payroll.rst:137
msgid ""
":guilabel:`Planning`: work entries are generated based on the employee's "
"planning in the *Planning* application."
msgstr ""

#: ../../content/applications/hr/payroll.rst:140
msgid ""
":guilabel:`Salary Structure Type`: select the :ref:`salary structure type "
"<payroll/structure-types>` from the drop-down menu."
msgstr ""

#: ../../content/applications/hr/payroll.rst:142
msgid ""
":guilabel:`Department`: select the department the contract template applies "
"to from the drop-down menu. If blank, the template applies to all "
"departments."
msgstr ""

#: ../../content/applications/hr/payroll.rst:144
msgid ""
":guilabel:`Job Position`: select the :ref:`job position <payroll/job-"
"positions>` the contract template applies to from the drop-down menu. If "
"blank, the template applies to all job positions."
msgstr ""

#: ../../content/applications/hr/payroll.rst:146
msgid ":guilabel:`Wage on Payroll`: enter the monthly wage in the field."
msgstr ""

#: ../../content/applications/hr/payroll.rst:147
msgid ""
":guilabel:`Contract Type`: select the type of contract from the drop-down "
"menu. This list is the same as the :ref:`Employment Types "
"<payroll/employment-types>`."
msgstr ""

#: ../../content/applications/hr/payroll.rst:149
msgid ""
":guilabel:`HR Responsible`: select the employee responsible for validating "
"contracts, using this template, from the drop-down menu."
msgstr ""

#: ../../content/applications/hr/payroll.rst:151
msgid ""
":guilabel:`New Contract Document Template`: select a default document that a"
" new employee has to sign to accept an offer."
msgstr ""

#: ../../content/applications/hr/payroll.rst:153
msgid ""
":guilabel:`Contract Update Document Template`: select a default document "
"that a current employee has to sign to update their contract."
msgstr ""

#: ../../content/applications/hr/payroll.rst-1
msgid "A new contract template form, with the fields filled in."
msgstr ""

#: ../../content/applications/hr/payroll.rst:161
msgid "Salary information tab"
msgstr ""

#: ../../content/applications/hr/payroll.rst:163
msgid ""
":guilabel:`Wage Type`: select either :guilabel:`Fixed Wage` or "
":guilabel:`Hourly Wage` from the drop-down menu."
msgstr ""

#: ../../content/applications/hr/payroll.rst:165
msgid ""
":guilabel:`Schedule Pay`: using the drop-down menu, select how often the "
"employee is paid. Options include :guilabel:`Annually`, :guilabel:`Semi-"
"annually`, :guilabel:`Quarterly`, :guilabel:`Bi-monthly`, "
":guilabel:`Monthly`, :guilabel:`Semi-monthly`, :guilabel:`Bi-weekly`, "
":guilabel:`Weekly`, or :guilabel:`Daily`."
msgstr ""

#: ../../content/applications/hr/payroll.rst:169
msgid ""
":guilabel:`Wage`: enter the gross wage. The time period presented in this "
"field is based on what is selected for the :guilabel:`Scheduled Pay` field. "
"It is recommended to populate the :guilabel:`Yearly Cost (Real)` field "
"*first*, since that entry updates this field automatically."
msgstr ""

#: ../../content/applications/hr/payroll.rst:172
msgid ""
":guilabel:`Yearly Cost (Real)`: enter the total yearly cost the employee "
"costs the employer. When this value is entered, the :guilabel:`Monthly Cost "
"(Real)` is automatically updated."
msgstr ""

#: ../../content/applications/hr/payroll.rst:174
msgid ""
":guilabel:`Monthly Cost (Real)`: this field is **not** editable. The value "
"is automatically populated after the :guilabel:`Yearly Cost (Real)` is "
"entered."
msgstr ""

#: ../../content/applications/hr/payroll.rst:178
msgid ""
"The :guilabel:`Schedule Pay`, :guilabel:`Wage`, and :guilabel:`Yearly Cost "
"(Real)` fields are all linked. If any of these fields are updated, the other"
" two fields automatically update to reflect the change. It is best practice "
"to check these three fields if any modifications have been made, to ensure "
"they are accurate."
msgstr ""

#: ../../content/applications/hr/payroll.rst-1
msgid "The salary information tab, with the fields filled in."
msgstr ""

#: ../../content/applications/hr/payroll.rst:188
msgid "Pre-tax benefits and post-tax deductions"
msgstr ""

#: ../../content/applications/hr/payroll.rst:190
msgid ""
"Depending on the localization settings set for the company, the entries "
"presented in this section either vary, or may not appear at all."
msgstr ""

#: ../../content/applications/hr/payroll.rst:193
msgid ""
"For example, some entries may pertain to retirement accounts, health "
"insurance benefits, and commuter benefits."
msgstr ""

#: ../../content/applications/hr/payroll.rst:196
msgid ""
"Enter the monetary amounts or percentages to specify how much of the "
"employee's salary goes to the various benefits and/or deductions."
msgstr ""

#: ../../content/applications/hr/payroll.rst:202
msgid "Employment types"
msgstr ""

#: ../../content/applications/hr/payroll.rst:204
msgid ""
"To view all the pre-configured employment types, navigate to "
":menuselection:`Payroll application --> Configuration --> Contracts: "
"Employment Types`."
msgstr ""

#: ../../content/applications/hr/payroll.rst:207
msgid ""
"The employment types are presented in a list view on the "
":guilabel:`Employment Types` page."
msgstr ""

#: ../../content/applications/hr/payroll.rst:209
msgid ""
"The default employment types are :guilabel:`Permanent`, "
":guilabel:`Temporary`, :guilabel:`Seasonal`, :guilabel:`Interim`, "
":guilabel:`Full-Time`, :guilabel:`Part-Time`, and :guilabel:`Permanent`."
msgstr ""

#: ../../content/applications/hr/payroll.rst:212
msgid ""
"To make a new employment type, click the :guilabel:`New` button in the "
"upper-left corner, and a blank line appears at the bottom of the "
":guilabel:`Employment Types` page."
msgstr ""

#: ../../content/applications/hr/payroll.rst:215
msgid ""
"On this new blank line, enter the name of the employment type in the "
":guilabel:`Name` column. If the employment type is country-specific, select "
"the country using the drop-down menu in the :guilabel:`Country` column. If a"
" country is selected, then the employment type is *only* applicable for that"
" specific country."
msgstr ""

#: ../../content/applications/hr/payroll.rst:220
msgid ""
"To rearrange the order of the employment types, click the :guilabel:`six "
"small gray boxes` icon to the left of the employment type :guilabel:`Name`, "
"and drag the line to the desired position on the list."
msgstr ""

#: ../../content/applications/hr/payroll.rst-1
msgid "The employment types in the database by default, in a list view."
msgstr ""

#: ../../content/applications/hr/payroll.rst:231
#: ../../content/applications/hr/payroll/work_entries.rst:3
msgid "Work entries"
msgstr ""

#: ../../content/applications/hr/payroll.rst:233
msgid ""
"A *work entry* is an individual record on an employee's timesheet. Work "
"entries can be configured to account for all types of work and time off, "
"such as :guilabel:`Attendance`, :guilabel:`Sick Time Off`, "
":guilabel:`Training`, or :guilabel:`Public Holiday`."
msgstr ""

#: ../../content/applications/hr/payroll.rst:238
msgid ":doc:`Manage work entries <payroll/work_entries>`"
msgstr ""

#: ../../content/applications/hr/payroll.rst:241
msgid "Work entry types"
msgstr ""

#: ../../content/applications/hr/payroll.rst:243
msgid ""
"When creating a work entry in the *Payroll* application, or when an employee"
" enters information in the *Timesheets* application, a :guilabel:`Work Entry"
" Type` needs to be selected. The list of :guilabel:`Work Entry Types` is "
"automatically created based on localization settings set in the database."
msgstr ""

#: ../../content/applications/hr/payroll.rst:248
msgid ""
"To view the current work entry types available, go to "
":menuselection:`Payroll app --> Configuration --> Work Entries --> Work "
"Entry Types`."
msgstr ""

#: ../../content/applications/hr/payroll.rst:251
msgid ""
"Each work entry type has a code to aid in the creation of payslips, and to "
"ensure all taxes and fees are correctly entered."
msgstr ""

#: ../../content/applications/hr/payroll.rst-1
msgid ""
"List of all work entry types currently available for use, with the payroll "
"code and color."
msgstr ""

#: ../../content/applications/hr/payroll.rst:259
msgid "New work entry type"
msgstr ""

#: ../../content/applications/hr/payroll.rst:261
msgid ""
"To create a new :guilabel:`Work Entry Type`, click the :guilabel:`New` "
"button, and enter the information for the following sections on the form."
msgstr ""

#: ../../content/applications/hr/payroll.rst:265
#: ../../content/applications/hr/payroll.rst:711
#: ../../content/applications/hr/payroll/contracts.rst:40
msgid "General information section"
msgstr ""

#: ../../content/applications/hr/payroll.rst:267
msgid ""
":guilabel:`Work Entry Type Name`: the name should be short and descriptive, "
"such as `Sick Time` or `Public Holiday`."
msgstr ""

#: ../../content/applications/hr/payroll.rst:269
msgid ""
":guilabel:`Payroll Code`: this code appears with the work entry type on "
"timesheets and payslips. Since the code is used in conjunction with the "
"*Accounting* application, it is advised to check with the accounting "
"department for a code to use."
msgstr ""

#: ../../content/applications/hr/payroll.rst:272
msgid ""
":guilabel:`DMFA code`: this code is used to identify :abbr:`DMFA (De "
"Multifunctionele Aangifte)` entries on a corresponding :abbr:`DMFA (De "
"Multifunctionele Aangifte)` report. The :abbr:`DMFA (De Multifunctionele "
"Aangifte)` report is a quarterly report that Belgian-based companies are "
"required to submit for social security reporting purposes. This report "
"states the work done by the employees during the quarter, as well as the "
"salaries paid to those employees."
msgstr ""

#: ../../content/applications/hr/payroll.rst:277
msgid ""
":guilabel:`External Code`: this code is used for exporting data to a third-"
"party payroll service. Check with the third-party being used to determine "
"the :guilabel:`External Code` to enter for the new work entry type."
msgstr ""

#: ../../content/applications/hr/payroll.rst:280
msgid ""
":guilabel:`SDWorx code`: this code is only for companies that use SDWorx, a "
"payroll service provider."
msgstr ""

#: ../../content/applications/hr/payroll.rst:282
msgid ":guilabel:`Color`: select a color for the particular work entry type."
msgstr ""

#: ../../content/applications/hr/payroll.rst:285
msgid "Display in payslip section"
msgstr ""

#: ../../content/applications/hr/payroll.rst:287
msgid ""
":guilabel:`Rounding`: the rounding method selected determines how quantities"
" on timesheet entries are displayed on the payslip."
msgstr ""

#: ../../content/applications/hr/payroll.rst:290
msgid ":guilabel:`No Rounding`: a timesheet entry is not modified."
msgstr ""

#: ../../content/applications/hr/payroll.rst:291
msgid ""
":guilabel:`Half Day`: a timesheet entry is rounded to the closest half day "
"amount."
msgstr ""

#: ../../content/applications/hr/payroll.rst:292
msgid ""
":guilabel:`Day`: a timesheet entry is rounded to the closest full day "
"amount."
msgstr ""

#: ../../content/applications/hr/payroll.rst:295
msgid ""
"If the working time is set to an 8-hour work day (40-hour work week), and an"
" employee enters a time of 5.5 hours on a timesheet, and "
":guilabel:`Rounding` is set to :guilabel:`No Rounding`, the entry remains "
"5.5 hours. If :guilabel:`Rounding` is set to :guilabel:`Half Day`, the entry"
" is changed to 4 hours. If it is set to :guilabel:`Day`, it is changed to 8 "
"hours."
msgstr ""

#: ../../content/applications/hr/payroll.rst:301
msgid "Unpaid section"
msgstr ""

#: ../../content/applications/hr/payroll.rst:303
msgid ""
":guilabel:`Unpaid in Structures Types`: if the work entry is for work that "
"is not paid, specify which pay structure the unpaid work entry applies to "
"from the drop-down menu. Some situations where work is logged on a "
"timesheet, but no compensation given would be for unpaid internships, unpaid"
" training, or volunteer work."
msgstr ""

#: ../../content/applications/hr/payroll.rst:309
msgid "Valid for advantages section"
msgstr ""

#: ../../content/applications/hr/payroll.rst:311
msgid ""
":guilabel:`Meal Voucher`: if the work entry should count towards a meal "
"voucher, check the box."
msgstr ""

#: ../../content/applications/hr/payroll.rst:312
msgid ""
":guilabel:`Representation Fees`: if the work entry should count towards "
"representation fees, check the box."
msgstr ""

#: ../../content/applications/hr/payroll.rst:314
msgid ""
":guilabel:`Private Car Reimbursement`: if the work entry should count "
"towards a private car reimbursement, check the box."
msgstr ""

#: ../../content/applications/hr/payroll.rst:318
msgid "Time off options section"
msgstr ""

#: ../../content/applications/hr/payroll.rst:320
msgid ""
":guilabel:`Time Off`: check this box if the work entry type can be selected "
"for a time off request, or entry, in the *Time Off* application."
msgstr ""

#: ../../content/applications/hr/payroll.rst:323
msgid ""
"If :guilabel:`Time Off` is checked, a :guilabel:`Time Off Type` field "
"appears. This field has a drop-down menu to select the specific type of time"
" off, such as `Paid Time Off`, `Sick Time Off`, or `Extra Hours`, for "
"example."
msgstr ""

#: ../../content/applications/hr/payroll.rst:327
msgid ""
"A new type of time off can be entered in the field, if the listed types of "
"time off in the drop-down menu do **not** display the type of time off "
"needed."
msgstr ""

#: ../../content/applications/hr/payroll.rst:329
msgid ""
":guilabel:`Keep Time Off Right`: this is for Belgian-specific companies "
"**only**, and does **not** appear for other localizations. Check this box if"
" the work entry is for time off that affects the time off benefits for the "
"following year. Workers are given time off each year, according to the "
"government, and in some cases, time off taken during a specific time period "
"can affect how much time off the employee receives or accrues the following "
"year."
msgstr ""

#: ../../content/applications/hr/payroll.rst:336
msgid "Reporting section"
msgstr ""

#: ../../content/applications/hr/payroll.rst:338
msgid ""
":guilabel:`Unforeseen Absence`: if the work entry should be visible on the "
"unforeseen absences report, check this box."
msgstr ""

#: ../../content/applications/hr/payroll.rst-1
msgid "New work entry type form with all fields to be filled in."
msgstr ""

#: ../../content/applications/hr/payroll.rst:348
msgid "Working schedules"
msgstr ""

#: ../../content/applications/hr/payroll.rst:350
msgid ""
"To view the currently configured working schedules, go to "
":menuselection:`Payroll app --> Configuration --> Work Entries --> Working "
"Schedules`. The working schedules that are available for an employee's "
"contracts and work entries are found in this list."
msgstr ""

#: ../../content/applications/hr/payroll.rst:354
msgid ""
"Working schedules are company-specific. Each company **must** identify each "
"type of working schedule they use. If the database is created for only one "
"company, the company column is not available."
msgstr ""

#: ../../content/applications/hr/payroll.rst:358
msgid ""
"An Odoo database containing multiple companies that use a standard 40-hour "
"work week needs to have a separate working schedule entry for each company "
"that uses the 40-hour standard work week."
msgstr ""

#: ../../content/applications/hr/payroll.rst:361
msgid ""
"A database with five companies that all use a standard 40-hour work week "
"needs to have five separate 40-hour working schedules configured."
msgstr ""

#: ../../content/applications/hr/payroll.rst-1
msgid ""
"All working schedules available to use currently set up in the database for "
"the company."
msgstr ""

#: ../../content/applications/hr/payroll.rst:371
msgid "New working schedule"
msgstr ""

#: ../../content/applications/hr/payroll.rst:373
msgid ""
"To create a new working schedule, click the :guilabel:`New` button, and "
"enter the information on the form."
msgstr ""

#: ../../content/applications/hr/payroll.rst:376
msgid ""
"The fields are auto-populated for a regular 40-hour work week but can be "
"modified. First, change the name of the working time by modifying the text "
"in the :guilabel:`Name` field. Next, make any adjustments to the days and "
"times that apply to the new working time."
msgstr ""

#: ../../content/applications/hr/payroll.rst:380
msgid ""
"In the :guilabel:`Working Hours` tab, modify the :guilabel:`Day of Week`, "
":guilabel:`Day Period`, and :guilabel:`Work Entry Type` selections by "
"clicking on the drop-down menus in each column and making the desired "
"selection. The :guilabel:`Work From` and :guilabel:`Work To` columns are "
"modified by typing in the time."
msgstr ""

#: ../../content/applications/hr/payroll.rst:386
msgid ""
"The :guilabel:`Work From` and :guilabel:`Work To` times must be in a 24-hour"
" format. For example, `2:00 PM` would be entered as `14:00`."
msgstr ""

#: ../../content/applications/hr/payroll.rst:389
msgid ""
"If the working time should be in a two-week configuration, click the "
":guilabel:`Switch to 2 weeks calendar` button in the top-left. This creates "
"entries for an :guilabel:`Even week` and an :guilabel:`Odd week`."
msgstr ""

#: ../../content/applications/hr/payroll.rst-1
msgid "New working schedule form."
msgstr ""

#: ../../content/applications/hr/payroll.rst:398
msgid "Salary"
msgstr ""

#: ../../content/applications/hr/payroll.rst:403
msgid "Structure types"
msgstr ""

#: ../../content/applications/hr/payroll.rst:405
msgid ""
"In Odoo, an employee's payslip is based on *structures* and *structure "
"types*, which both affect how an employee enters timesheets. Each structure "
"type is an individual set of rules for processing a timesheet entry, which "
"consists of different structures nested within it. Structure types define "
"how often an employee gets paid, the working hours, and if wages are based "
"on a salary (fixed) or how many hours the employee worked (varied)."
msgstr ""

#: ../../content/applications/hr/payroll.rst:411
msgid ""
"For example, a structure type could be `Employee`, and that structure type "
"could have two different structures in it: a `Regular Pay` structure which "
"includes all the separate rules for processing regular pay, as well as a "
"structure for an `End of Year Bonus` which includes the rules only for the "
"end of year bonus. Both the `Regular Pay` structure and `End of Year Bonus` "
"structure are structures within the `Employee` structure type."
msgstr ""

#: ../../content/applications/hr/payroll.rst:417
msgid ""
"The different :guilabel:`Structure Types` can be seen by navigating to "
":menuselection:`Payroll app --> Configuration --> Salary: Structure Types`."
msgstr ""

#: ../../content/applications/hr/payroll.rst:420
msgid ""
"Two default structure types are configured in Odoo: :guilabel:`Employee` and"
" :guilabel:`Worker`."
msgstr ""

#: ../../content/applications/hr/payroll.rst:422
msgid ""
"Typically, :guilabel:`Employee` is used for salaried employees, which is why"
" the wage type is :guilabel:`Monthly Fixed Wage`, and :guilabel:`Worker` is "
"typically used for employees paid by the hour, so the wage type is "
":guilabel:`Hourly Wage`."
msgstr ""

#: ../../content/applications/hr/payroll.rst-1
msgid "List of all currently configured structure types available to use."
msgstr ""

#: ../../content/applications/hr/payroll.rst:433
msgid "New structure type"
msgstr ""

#: ../../content/applications/hr/payroll.rst:435
msgid ""
"To make a new structure type, click the :guilabel:`New` button, and a blank "
"structure type form appears."
msgstr ""

#: ../../content/applications/hr/payroll.rst:438
msgid ""
"Proceed to enter information in the fields. Most fields are pre-populated, "
"but all the fields can be modified."
msgstr ""

#: ../../content/applications/hr/payroll.rst:441
msgid ""
":guilabel:`Structure Type`: enter the name for the new structure type, such "
"as `Employee` or `Worker`."
msgstr ""

#: ../../content/applications/hr/payroll.rst:443
msgid ""
":guilabel:`Country`: select the country that the new structure type applies "
"to from the drop-down menu."
msgstr ""

#: ../../content/applications/hr/payroll.rst:445
msgid ""
":guilabel:`Wage Type`: select what type of wage the new structure type uses,"
" either :guilabel:`Fixed Wage` or :guilabel:`Hourly Wage`."
msgstr ""

#: ../../content/applications/hr/payroll.rst:448
msgid ""
"If the type is to be used for salaried employees, who receive the same wage "
"every pay period, select :guilabel:`Fixed Wage`."
msgstr ""

#: ../../content/applications/hr/payroll.rst:451
msgid ""
"If the type is to be used for employees, who receive wages based on how many"
" hours they worked during a pay period, select :guilabel:`Hourly Wage`."
msgstr ""

#: ../../content/applications/hr/payroll.rst:453
msgid ""
":guilabel:`Default Scheduled Pay`: select the typical pay schedule for the "
"new structure type from the drop-down menu. Options are :guilabel:`Monthly`,"
" :guilabel:`Quarterly`, :guilabel:`Semi-annually`, :guilabel:`Annually`, "
":guilabel:`Weekly`, :guilabel:`Bi-weekly`, :guilabel:`Bi-monthly`. This "
"indicates how often this specific type of structure is paid out."
msgstr ""

#: ../../content/applications/hr/payroll.rst:457
msgid ""
":guilabel:`Default Working Hours`: select the default working hours for the "
"new structure type from the drop-down menu. All available working hours for "
"the currently selected company appear in the drop-down menu. The default "
"working hours that are pre-configured in Odoo is the :guilabel:`Standard 40 "
"hours/week` option. If the needed working hours do not appear in the list, a"
" :ref:`new set of default working hours can be created <new-default-working-"
"hours>`."
msgstr ""

#: ../../content/applications/hr/payroll.rst:462
msgid ""
":guilabel:`Regular Pay Structure`: type in the name for the regular pay "
"structure."
msgstr ""

#: ../../content/applications/hr/payroll.rst:463
msgid ""
":guilabel:`Default Work Entry Type`: select the default type of work entry "
"the new structure type falls under from the drop-down menu. The default "
"options include :guilabel:`Attendance`, :guilabel:`Overtime Hours`, "
":guilabel:`Generic Time Off`, :guilabel:`Compensatory Time Off`, "
":guilabel:`Home Working`, :guilabel:`Unpaid`, :guilabel:`Sick Time Off`, "
":guilabel:`Paid Time Off`, :guilabel:`Out Of Contract`, :guilabel:`Extra "
"Hours`, and :guilabel:`Long Term Time Off`."
msgstr ""

#: ../../content/applications/hr/payroll.rst:469
msgid ""
"To view all the options for the :guilabel:`Default Work Entry Type`, click "
"the :guilabel:`Search More..` button at the bottom of the drop-down list."
msgstr ""

#: ../../content/applications/hr/payroll.rst:472
msgid ""
"Depending on the localization settings, this list may contain more options "
"in addition to the default options."
msgstr ""

#: ../../content/applications/hr/payroll.rst-1
msgid ""
"New structure type form to fill out when creating a new structure type."
msgstr ""

#: ../../content/applications/hr/payroll.rst:482
msgid "New default working hours"
msgstr ""

#: ../../content/applications/hr/payroll.rst:484
msgid ""
"To make new default working hours, type the name for the new working hours "
"in the :guilabel:`Default Working Hours` field on the new structure type "
"form. Click :guilabel:`Create and edit`. A default working hours form pops "
"up. The default working hours form has two sections, a general information "
"section and a tab listing out all the individual working hours by day and "
"time. When the form is completed, click :guilabel:`Save & Close`."
msgstr ""

#: ../../content/applications/hr/payroll.rst:490
msgid ""
":guilabel:`Name`: type in the name for the new default working hours. This "
"should be descriptive and clear to understand, such as `Standard 20 "
"Hours/Week`."
msgstr ""

#: ../../content/applications/hr/payroll.rst:492
msgid ""
":guilabel:`Company`: select the company that can use these new default "
"working hours from the drop-down menu. Keep in mind, working hours are "
"company-specific, and cannot be shared between companies. Each company needs"
" to have their own working hours set."
msgstr ""

#: ../../content/applications/hr/payroll.rst:495
msgid ""
":guilabel:`Average Hour Per Day`: the average hours per day field is auto-"
"populated, based on the working hours configured in the :guilabel:`Working "
"Hours` tab. This entry affects resource planning, since the average daily "
"hours affect what resources can be used, and in what quantity, per work day."
msgstr ""

#: ../../content/applications/hr/payroll.rst:499
msgid ""
":guilabel:`Timezone`: select the time zone to be used for the new default "
"working hours from the drop-down menu."
msgstr ""

#: ../../content/applications/hr/payroll.rst:501
msgid ""
":guilabel:`Company Full Time`: enter the number of hours per week an "
"employee would need to work to be considered a full-time employee. "
"Typically, this is approximately 40 hours, and this number affects what "
"types of benefits an employee can receive, based on their employment status "
"(full-time vs part-time)."
msgstr ""

#: ../../content/applications/hr/payroll.rst:505
msgid ""
":guilabel:`Work Time Rate`: this percentage is auto-generated based on the "
"entry for the :guilabel:`Company Full Time` and the working hours configured"
" in the :guilabel:`Working Hours` tab. This number should be between `0.00%`"
" and `100%`, so if the percentage is above `100%`, it is an indication that "
"the working times and/or :guilabel:`Company Full Time` hours need "
"adjustment."
msgstr ""

#: ../../content/applications/hr/payroll.rst:509
msgid ""
":guilabel:`Working Hours` Tab: this tab is where each day's specific working"
" hours are listed. When a new default working hour form is created, the "
":guilabel:`Working Hours` tab is pre-populated with a default 40-hour week, "
"with each day divided into three timed sections."
msgstr ""

#: ../../content/applications/hr/payroll.rst:513
msgid ""
"Every day has morning (8:00-12:00), lunch (12:00-13:00), and evening "
"(13:00-17:00) hours configured, using a 24 hour time format."
msgstr ""

#: ../../content/applications/hr/payroll.rst:516
msgid ""
"To adjust any of these hours, click on the specific field to adjust, and "
"make the adjustment using the drop-down menus, or in the specific case of "
"the times, type in the desired time."
msgstr ""

#: ../../content/applications/hr/payroll.rst:519
msgid ""
"Keep in mind, working hours are company-specific, and cannot be shared "
"between companies. Each company needs to have their own working hours set."
msgstr ""

#: ../../content/applications/hr/payroll.rst:523
msgid ""
"If the working hours are not consistent each week, and the hours are on a "
"bi-weekly schedule instead, click the :guilabel:`Switch to 2 week calendar` "
"button at the top of the new default working hours form. This changes the "
":guilabel:`Working Hours` tab to display two weeks of working times that can"
" be adjusted."
msgstr ""

#: ../../content/applications/hr/payroll.rst:529
msgid "Structures"
msgstr "מבנים"

#: ../../content/applications/hr/payroll.rst:531
msgid ""
"*Salary structures* are the different ways an employee gets paid within a "
"specific *structure*, and are specifically defined by various rules."
msgstr ""

#: ../../content/applications/hr/payroll.rst:534
msgid ""
"The amount of structures a company needs for each structure type depends on "
"how many different ways employees are paid, and how their pay is calculated."
" For example, a common structure that could be useful to add may be a "
"`Bonus`."
msgstr ""

#: ../../content/applications/hr/payroll.rst:538
msgid ""
"To view all the various structures for each structure type, go to "
":menuselection:`Payroll app --> Configuration --> Salary --> Structures`."
msgstr ""

#: ../../content/applications/hr/payroll.rst:541
msgid ""
"Each :ref:`structure type <payroll/structure-types>` lists the various "
"structures associated with it. Each structure contains a set of rules that "
"define it."
msgstr ""

#: ../../content/applications/hr/payroll.rst-1
msgid "All available salary structures."
msgstr ""

#: ../../content/applications/hr/payroll.rst:548
msgid ""
"Click on a structure to view its :guilabel:`Salary Rules`. These rules are "
"what calculate the payslip for the employee."
msgstr ""

#: ../../content/applications/hr/payroll.rst-1
msgid ""
"Salary structure details for Regular Pay, listing all the specific Salary "
"Rules."
msgstr ""

#: ../../content/applications/hr/payroll.rst:556
#: ../../content/applications/hr/time_off.rst:273
msgid "Rules"
msgstr "כללים"

#: ../../content/applications/hr/payroll.rst:558
msgid ""
"Each structure has a set of *salary rules* to follow for accounting "
"purposes. These rules are configured by the localization, and affect actions"
" in the *Accounting* application, so modifications to the default rules, or "
"the creation of new rules, should only be done when necessary."
msgstr ""

#: ../../content/applications/hr/payroll.rst:562
msgid ""
"To view all the rules, go to :menuselection:`Payroll app --> Configuration "
"--> Salary --> Rules`. Click on a structure (such as :guilabel:`Regular "
"Pay`) to view all the rules."
msgstr ""

#: ../../content/applications/hr/payroll.rst:565
msgid ""
"To make a new rule, click :guilabel:`New`. A new rule form appears. Enter "
"the following information in the fields."
msgstr ""

#: ../../content/applications/hr/payroll.rst:569
msgid "Top section"
msgstr ""

#: ../../content/applications/hr/payroll.rst:571
msgid ""
":guilabel:`Rule Name`: enter a name for the rule. This field is required."
msgstr ""

#: ../../content/applications/hr/payroll.rst:572
msgid ""
":guilabel:`Category`: select a category the rule applies to from the drop-"
"down menu, or enter a new one. This field is required."
msgstr ""

#: ../../content/applications/hr/payroll.rst:574
msgid ""
":guilabel:`Code`: enter a code to be used for this new rule. It is "
"recommended to coordinate with the accounting department for a code to use "
"as this affects accounting reports and payroll processing. This field is "
"required."
msgstr ""

#: ../../content/applications/hr/payroll.rst:577
msgid ""
":guilabel:`Sequence`: enter a number indicating when this rule is calculated"
" in the sequence of all other rules."
msgstr ""

#: ../../content/applications/hr/payroll.rst:579
msgid ""
":guilabel:`Salary Structure`: select a salary structure the rule applies to "
"from the drop-down menu, or enter a new one. This field is required."
msgstr ""

#: ../../content/applications/hr/payroll.rst:581
msgid ""
":guilabel:`Active`: enable this toggle, so the rule is available for use. "
"Disable the toggle to hide the rule without deleting it in the database."
msgstr ""

#: ../../content/applications/hr/payroll.rst:583
msgid ""
":guilabel:`Appears on payslip`: tick the checkbox to have the rule appear on"
" employee payslips."
msgstr ""

#: ../../content/applications/hr/payroll.rst:584
msgid ""
":guilabel:`View on Employer Cost Dashboard`: tick the checkbox to have the "
"rule appear on the :guilabel:`Employer Cost` report, located on the "
"*Payroll* app dashboard."
msgstr ""

#: ../../content/applications/hr/payroll.rst:586
msgid ""
":guilabel:`View on Payroll Reporting`: tick the checkbox to have the rule "
"appear on payroll reports."
msgstr ""

#: ../../content/applications/hr/payroll.rst-1
msgid "Enter the information for the new rule on the new rule form."
msgstr ""

#: ../../content/applications/hr/payroll.rst:594
msgid "General tab"
msgstr ""

#: ../../content/applications/hr/payroll.rst:597
msgid "Conditions"
msgstr "תנאים"

#: ../../content/applications/hr/payroll.rst:599
msgid ""
":guilabel:`Condition Based on`: select from the drop-down menu whether the "
"rule is :guilabel:`Always True` (always applies), a :guilabel:`Range` "
"(applies to a specific range, which is entered beneath the selection), or a "
":guilabel:`Python Expression` (the code is entered beneath the selection). "
"This field is required."
msgstr ""

#: ../../content/applications/hr/payroll.rst:605
msgid "Computation"
msgstr "חישוב"

#: ../../content/applications/hr/payroll.rst:607
msgid ""
":guilabel:`Amount Type`: select from the drop-down menu whether the amount "
"is a :guilabel:`Fixed Amount`, a :guilabel:`Percentage (%)`, or a "
":guilabel:`Python Code`. Depending on what is selected, the fixed amount, "
"percentage, or Python code needs to be entered next. This field is required."
msgstr ""

#: ../../content/applications/hr/payroll.rst:613
msgid "Company contribution"
msgstr ""

#: ../../content/applications/hr/payroll.rst:615
msgid ""
":guilabel:`Partner`: if another company financially contributes to this "
"rule, select the company from the drop-down menu."
msgstr ""

#: ../../content/applications/hr/payroll.rst:619
#: ../../content/applications/hr/payroll.rst:796
msgid "Description tab"
msgstr ""

#: ../../content/applications/hr/payroll.rst:621
msgid ""
"Provide any additional information in this tab to help clarify the rule. "
"This tab only appears in the rule form."
msgstr ""

#: ../../content/applications/hr/payroll.rst:625
msgid "Accounting tab"
msgstr ""

#: ../../content/applications/hr/payroll.rst:627
msgid ""
":guilabel:`Debit Account`: select the debit account from the drop-down menu "
"the rule affects."
msgstr ""

#: ../../content/applications/hr/payroll.rst:628
msgid ""
":guilabel:`Credit Account`: select the credit account from the drop-down "
"menu the rule affects."
msgstr ""

#: ../../content/applications/hr/payroll.rst:629
msgid ""
":guilabel:`Not computed in net accountability`: tick the checkbox to delete "
"the value of this rule in the `Net Salary` rule."
msgstr ""

#: ../../content/applications/hr/payroll.rst:633
msgid "Rule parameters"
msgstr ""

#: ../../content/applications/hr/payroll.rst:636
msgid ""
"Currently, the :guilabel:`Rule Parameters` feature found inside the "
":menuselection:`Payroll app --> Configuration --> Salary --> Rule "
"Parameters` menu is still in development and only serves a specific use case"
" for Belgian markets. The documentation will be updated when this section "
"has matured to more markets."
msgstr ""

#: ../../content/applications/hr/payroll.rst:642
msgid "Other input types"
msgstr ""

#: ../../content/applications/hr/payroll.rst:644
msgid ""
"When creating payslips, it is sometimes necessary to add other entries for "
"specific circumstances, like expenses, reimbursements, or deductions. These "
"other inputs can be configured by navigating to :menuselection:`Payroll app "
"--> Configuration --> Salary --> Other Input Types`."
msgstr ""

#: ../../content/applications/hr/payroll.rst-1
msgid ""
"A list of other input types for payroll that can be selected when creating a new entry for\n"
"a payslip."
msgstr ""

#: ../../content/applications/hr/payroll.rst:653
msgid ""
"To create a new input type, click the :guilabel:`New` button. Enter the "
":guilabel:`Description`, the :guilabel:`Code`, and which structure it "
"applies to in the :guilabel:`Availability in Structure` field."
msgstr ""

#: ../../content/applications/hr/payroll.rst:658
msgid ""
"The :guilabel:`Code` is used in the salary rules to compute payslips. If the"
" :guilabel:`Availability in Structure` field is left blank, it indicates "
"that the new input type is available for all payslips and is not exclusive "
"to a specific structure."
msgstr ""

#: ../../content/applications/hr/payroll.rst-1
msgid "A new Input Type form filled in."
msgstr ""

#: ../../content/applications/hr/payroll.rst:669
#: ../../content/applications/hr/recruitment.rst:167
msgid "Salary package configurator"
msgstr ""

#: ../../content/applications/hr/payroll.rst:671
msgid ""
"The various options under the :guilabel:`Salary Package Configurator` "
"section of the :menuselection:`Payroll app --> Configuration --> Salary "
"Package Configurator` menu all affect an employee's potential salary. These "
"sections (:guilabel:`Benefits`, :guilabel:`Personal Info`, and "
":guilabel:`Resume`) specify what benefits can be offered to an employee in "
"their salary package."
msgstr ""

#: ../../content/applications/hr/payroll.rst:676
msgid ""
"Depending on what information an employee enters (such as deductions, "
"dependents, etc.), their salary is adjusted accordingly. When an applicant "
"applies for a job on the company website, the sections under "
":guilabel:`Salary Package Configurator` directly affect what the applicant "
"sees, and what is populated, as the applicant enters information."
msgstr ""

#: ../../content/applications/hr/payroll.rst:682
msgid "Benefits"
msgstr ""

#: ../../content/applications/hr/payroll.rst:684
msgid ""
"When offering potential employees a position, there can be certain benefits "
"set in Odoo, in addition to the salary, to make an offer more appealing "
"(such as extra time off, the use of a company car, reimbursement for a phone"
" or internet, etc.)."
msgstr ""

#: ../../content/applications/hr/payroll.rst:688
msgid ""
"To view the benefits, go to :menuselection:`Payroll app --> Configuration "
"--> Salary Package Configurator: Benefits`. Benefits are grouped by "
":guilabel:`Structure type`, and the benefit listed for a particular "
"structure type is only available for that specific structure."
msgstr ""

#: ../../content/applications/hr/payroll.rst-1
msgid "A list view of all the benefits available for each structure type."
msgstr ""

#: ../../content/applications/hr/payroll.rst:697
msgid ""
"A company has two structure types, one labeled :guilabel:`Employee`, and "
"another labeled :guilabel:`Intern`. The :guilabel:`Employee` structure type "
"contains the benefit of using a company car, while the :guilabel:`Intern` "
"structure type has a meal voucher benefit available."
msgstr ""

#: ../../content/applications/hr/payroll.rst:701
msgid ""
"A person hired under the :guilabel:`Employee` structure type can use the "
"company car benefit, but cannot have meal vouchers. A person hired under the"
" :guilabel:`Intern` structure type would have meal voucher benefits "
"available to them, not the use of a company car."
msgstr ""

#: ../../content/applications/hr/payroll.rst:705
msgid ""
"To make a new benefit, click the :guilabel:`New` button, and enter the "
"information in the fields on the blank benefits form."
msgstr ""

#: ../../content/applications/hr/payroll.rst:708
msgid "The various fields for creating a benefit are as follows:"
msgstr ""

#: ../../content/applications/hr/payroll.rst:713
msgid ""
":guilabel:`Benefits`: enter the name for the benefit. This field is "
"required."
msgstr ""

#: ../../content/applications/hr/payroll.rst:714
msgid ""
":guilabel:`Benefit Field`: select from the drop-down menu the type of "
"benefit this is."
msgstr ""

#: ../../content/applications/hr/payroll.rst:715
msgid ""
":guilabel:`Cost Field`: select from the drop-down menu the type of cost "
"incurred by the company for this specific benefit. The default options are "
":guilabel:`Calendar Changed`, :guilabel:`Yearly Cost (Real)`, "
":guilabel:`Extra Time Off`, :guilabel:`Hourly Wage`, :guilabel:`Part Time`, "
":guilabel:`Wage`, :guilabel:`Wage with Holidays`, and :guilabel:`Work time "
"rate`. Depending on the localization settings, additional options are "
"available."
msgstr ""

#: ../../content/applications/hr/payroll.rst:720
msgid ""
":guilabel:`Related Type`: select from the drop-down menu what type of "
"benefit it is. Select from :guilabel:`Monthly Benefit in Kind`, "
":guilabel:`Monthly Benefit in Net`, :guilabel:`Monthly Benefit in Cash`, "
":guilabel:`Yearly Benefits in Cash`, or :guilabel:`Non Financial Benefits`. "
"This field is required."
msgstr ""

#: ../../content/applications/hr/payroll.rst:724
msgid ""
":guilabel:`Benefit Field`: select from the drop-down menu the specific field"
" on the contract the benefit appears."
msgstr ""

#: ../../content/applications/hr/payroll.rst:726
msgid ""
":guilabel:`Cost Field`: select the specific field on the contract that the "
"cost of the benefit is linked to, using the drop-down menu. If this field is"
" left blank, the cost of the benefit is not computed in the employee budget."
msgstr ""

#: ../../content/applications/hr/payroll.rst:729
msgid ""
":guilabel:`Impacts Net Salary`: tick the checkbox if the benefit should "
"impact the employee's net salary."
msgstr ""

#: ../../content/applications/hr/payroll.rst:731
msgid ""
":guilabel:`Requested Documents`: select any document that is required to be "
"submitted for this benefit, from the drop-down menu."
msgstr ""

#: ../../content/applications/hr/payroll.rst:733
msgid ""
":guilabel:`Mandatory Benefits`: using the drop-down menu, select the benefit"
" that is required in order for this specific benefit to be offered to the "
"employee."
msgstr ""

#: ../../content/applications/hr/payroll.rst:736
msgid ""
"For example, a benefit for car insurance would populate `Company Car` in "
"this field. This would allow the car insurance benefit to **only** be "
"displayed if the employee has selected/enabled the benefit of a company car."
msgstr ""

#: ../../content/applications/hr/payroll.rst:739
msgid ""
":guilabel:`Salary Structure Type`: select from the drop-down menu which "
"salary structure type this benefit applies to. This field is required."
msgstr ""

#: ../../content/applications/hr/payroll.rst:741
msgid ""
":guilabel:`Unit of Measure`: select the metric that the benefit is granted, "
"using the drop-down menu. The options are :guilabel:`Days`, "
":guilabel:`Percent`, or :guilabel:`Currency`."
msgstr ""

#: ../../content/applications/hr/payroll.rst-1
msgid "A new benefit form filled out for an internet subscription."
msgstr ""

#: ../../content/applications/hr/payroll.rst:749
msgid "Display section"
msgstr ""

#: ../../content/applications/hr/payroll.rst:751
msgid ""
":guilabel:`Show Name`: tick the checkbox to have the benefit name appear in "
"the salary package configurator."
msgstr ""

#: ../../content/applications/hr/payroll.rst:753
msgid ""
":guilabel:`Display Type`: select from the drop-down menu how this benefit is"
" displayed. The options are :guilabel:`Always Selected`, "
":guilabel:`Dropdown`, :guilabel:`Dropdown Group`, :guilabel:`Slider`, "
":guilabel:`Radio Buttons`, :guilabel:`Manual Input`, or :guilabel:`Text`. "
"This field is required."
msgstr ""

#: ../../content/applications/hr/payroll.rst:758
msgid ""
"Depending on the selection made, additional configurations need to be made. "
"For example, if :guilabel:`Radio Buttons` is selected, the individual radio "
"buttons must be entered."
msgstr ""

#: ../../content/applications/hr/payroll.rst:760
msgid ""
":guilabel:`Icon`: an icon from the `Font Awesome 4 library "
"<https://fontawesome.com/v4/icons/>`_ can be visible for this benefit. Enter"
" the text code for the icon in this field. For example, to display a "
"suitcase icon, the code `fa fa-suitcase` is entered on this line."
msgstr ""

#: ../../content/applications/hr/payroll.rst:763
msgid ""
":guilabel:`Hide Description`: tick the checkbox to hide the benefit "
"description if the benefit is not selected by the employee."
msgstr ""

#: ../../content/applications/hr/payroll.rst:765
msgid ""
":guilabel:`Folded`: if the benefit should be folded, or hidden, because it "
"is dependant on another benefit selection, tick the checkbox. The following "
"fields appear when this is active:"
msgstr ""

#: ../../content/applications/hr/payroll.rst:768
msgid ""
":guilabel:`Fold Label`: enter a name for the folded section of the benefit."
msgstr ""

#: ../../content/applications/hr/payroll.rst:769
msgid ""
":guilabel:`Fold Res Field`: select the contract field this benefit is tied "
"to using the drop-down menu. If this field is selected on the contract, then"
" this benefit becomes visible."
msgstr ""

#: ../../content/applications/hr/payroll.rst:773
msgid "Activity section"
msgstr ""

#: ../../content/applications/hr/payroll.rst:775
msgid ""
":guilabel:`Activity Type`: from the drop-down menu, select the activity type"
" that is automatically created when this benefit is selected by the "
"employee."
msgstr ""

#: ../../content/applications/hr/payroll.rst:777
msgid ""
":guilabel:`Activity Creation`: select when the activity is created, either "
"when the :guilabel:`Employee signs his contract`, or when the "
":guilabel:`Contract is countersigned`. Click the radio button next to the "
"desired selection."
msgstr ""

#: ../../content/applications/hr/payroll.rst:780
msgid ""
":guilabel:`Activity Creation Type`: select the parameters for when the "
"activity is created, either :guilabel:`When the benefit is set` or "
":guilabel:`When the benefit is modified`. Click the radio button next to the"
" desired selection."
msgstr ""

#: ../../content/applications/hr/payroll.rst:783
msgid ""
":guilabel:`Assigned to`: select the user the activity is automatically "
"assigned to, using the drop-down menu."
msgstr ""

#: ../../content/applications/hr/payroll.rst:787
#: ../../content/applications/hr/payroll/contracts.rst:163
msgid "Sign section"
msgstr ""

#: ../../content/applications/hr/payroll.rst:789
msgid ""
":guilabel:`Template to Sign`: if the employee is required to sign a document"
" when selecting this benefit, select the document template from the drop-"
"down menu."
msgstr ""

#: ../../content/applications/hr/payroll.rst:792
msgid ""
"For example, a benefit regarding the use of a company car may require the "
"employee to sign a document acknowledging the company's car policies."
msgstr ""

#: ../../content/applications/hr/payroll.rst:798
msgid ""
"Provide any additional information in this tab to help clarify the benefit."
msgstr ""

#: ../../content/applications/hr/payroll.rst:801
msgid "Personal info"
msgstr ""

#: ../../content/applications/hr/payroll.rst:803
msgid ""
"Every employee in Odoo has an *employee card* which is created when a "
"candidate becomes an employee. This card includes all of their personal "
"information, resume, work information, and documents."
msgstr ""

#: ../../content/applications/hr/payroll.rst:807
msgid ""
"The personal information is gathered from the salary package configurator "
"section that a candidate fills out after being offered a position. This "
"personal information is then transferred to the employee card when they are "
"hired."
msgstr ""

#: ../../content/applications/hr/payroll.rst:811
msgid ""
"To view an employee's card, go to the main :menuselection:`Employees` app "
"dashboard, and click on the employee's card."
msgstr ""

#: ../../content/applications/hr/payroll.rst:815
msgid "An employee card can be thought of as an employee personnel file."
msgstr ""

#: ../../content/applications/hr/payroll.rst:817
msgid ""
"The :guilabel:`Personal Info` section lists all of the fields that are "
"available to enter on the employee's card. To access this section, go to "
":menuselection:`Payroll app --> Configuration --> Salary Package "
"Configurator: Personal Info`."
msgstr ""

#: ../../content/applications/hr/payroll.rst-1
msgid ""
"A list of all the personal information that appears on the employee card to "
"enter."
msgstr ""

#: ../../content/applications/hr/payroll.rst:825
msgid ""
"To edit a personal info entry, select an entry from the list on the "
":guilabel:`Personal Info` page, and modify the personal info on the form "
"that appears."
msgstr ""

#: ../../content/applications/hr/payroll.rst:828
msgid "To create a new personal info entry, click the :guilabel:`New` button."
msgstr ""

#: ../../content/applications/hr/payroll.rst:830
msgid ""
"The required fields, aside from entering the :guilabel:`Information` name, "
"are :guilabel:`Related Model`, :guilabel:`Related Field`, and "
":guilabel:`Category`."
msgstr ""

#: ../../content/applications/hr/payroll.rst:833
msgid ""
"Select a :guilabel:`Related Model` from the drop-down menu. "
":guilabel:`Employee` populates the field by default, but the :guilabel:`Bank"
" Account` option is also available if the information is related to a bank "
"account, instead."
msgstr ""

#: ../../content/applications/hr/payroll.rst:837
msgid ""
"Select a :guilabel:`Related Field` from the drop-down menu that best "
"describes what kind of personal information this entry is, and where it is "
"stored in the backend. Then, select a :guilabel:`Category` from the drop-"
"down menu that the personal information should be under, such as "
":guilabel:`Address` or :guilabel:`Personal Documents`."
msgstr ""

#: ../../content/applications/hr/payroll.rst:842
msgid ""
"The two most important fields on the personal info form are :guilabel:`Is "
"Required` and :guilabel:`Display Type`."
msgstr ""

#: ../../content/applications/hr/payroll.rst:845
msgid ""
"Checking the :guilabel:`Is Required` box makes the field mandatory on the "
"employee's card. The :guilabel:`Display Type` drop-down menu allows for the "
"information to be entered in a variety of ways, like a :guilabel:`Text` box,"
" to a customizable :guilabel:`Radio` button, a :guilabel:`Checkbox`, a "
":guilabel:`Document`, and more."
msgstr ""

#: ../../content/applications/hr/payroll.rst-1
msgid "New personal information entry."
msgstr ""

#: ../../content/applications/hr/payroll.rst:857
msgid ""
"The resumé section, housed within the salary package configurator section of"
" the settings menu, is how salary information rules are configured when "
"offering a position to potential employees."
msgstr ""

#: ../../content/applications/hr/payroll.rst:860
msgid ""
"When an offer is sent to a prospective employee, the values for the offer "
"are computed from these settings, and appear on the offer page."
msgstr ""

#: ../../content/applications/hr/payroll.rst:863
msgid ""
"To configure this section, navigate to :menuselection:`Payroll app --> "
"Configuration --> Salary Package Configurator: Resumé`."
msgstr ""

#: ../../content/applications/hr/payroll.rst:866
msgid ""
"By default, there are three :guilabel:`Salary Structure Types` pre-"
"configured in Odoo: :guilabel:`Worker`, :guilabel:`Employee`, and "
":guilabel:`None`."
msgstr ""

#: ../../content/applications/hr/payroll.rst:869
msgid ""
"Each :guilabel:`Salary Structure Type` has several rules configured. These "
"affect how an offer is calculated using that particular :guilabel:`Salary "
"Structure Type`."
msgstr ""

#: ../../content/applications/hr/payroll.rst:872
msgid ""
"To create a new rule, click the :guilabel:`New` button, and a blank "
":guilabel:`Contract Salary Resumé` form loads."
msgstr ""

#: ../../content/applications/hr/payroll.rst:877
msgid ":guilabel:`Information`: type in a name for this field."
msgstr ""

#: ../../content/applications/hr/payroll.rst:878
msgid ""
":guilabel:`Category`: select the category this value is housed under, using "
"the drop-down menu. The default options are :guilabel:`Monthly Salary`, "
":guilabel:`Monthly Benefits`, :guilabel:`Yearly Benefits`, and "
":guilabel:`Total`."
msgstr ""

#: ../../content/applications/hr/payroll.rst:882
msgid "New categories can be made if needed."
msgstr ""

#: ../../content/applications/hr/payroll.rst:884
msgid ""
"Click the :guilabel:`New` button, then enter the name for the new category "
"in the :guilabel:`Name` field. Next, select the :guilabel:`Periodicity` from"
" the drop-down menu, either :guilabel:`Monthly` or :guilabel:`Yearly`. Last,"
" enter a number for the sequence. This corresponds to where this rule "
"appears in the  :guilabel:`Salary Structure Type` rule list."
msgstr ""

#: ../../content/applications/hr/payroll.rst:889
msgid "Finally, click :guilabel:`Save & Close`."
msgstr ""

#: ../../content/applications/hr/payroll.rst:890
msgid ""
":guilabel:`Impacts Monthly Total`: tick the checkbox if this value is added "
"in the monthly total calculation."
msgstr ""

#: ../../content/applications/hr/payroll.rst:892
msgid ""
":guilabel:`Unit of Measure`: select what kind of value this rule is, either "
":guilabel:`Currency`, :guilabel:`Days`, or :guilabel:`Percent`."
msgstr ""

#: ../../content/applications/hr/payroll.rst:895
msgid ""
":guilabel:`Currency` is for a set monetary value, :guilabel:`Days` is for "
"compensation in the form of time off, and :guilabel:`Percent` is for a "
"monetary value awarded that is based upon another metric, such as "
"commissions."
msgstr ""

#: ../../content/applications/hr/payroll.rst:898
msgid ""
":guilabel:`Salary Structure Type`: select which :guilabel:`Salary Structure "
"Type` this rule is nested under, from the drop-down menu."
msgstr ""

#: ../../content/applications/hr/payroll.rst:900
msgid ""
":guilabel:`Value Type`: select how the value is computed, using the drop-"
"down menu. The default options are :guilabel:`Fixed Value`, "
":guilabel:`Contract Value`, :guilabel:`Payslip Value`, :guilabel:`Sum of "
"Benefits Values`, and :guilabel:`Monthly Total`."
msgstr ""

#: ../../content/applications/hr/payroll.rst:903
msgid ""
":guilabel:`Code`: select the code this rule applies to from the drop-down "
"menu."
msgstr ""

#: ../../content/applications/hr/payroll.rst-1
msgid ""
"The net wage rule form filled out, with all the information for net pay."
msgstr ""

#: ../../content/applications/hr/payroll.rst:910
msgid "Jobs"
msgstr "תפקידים"

#: ../../content/applications/hr/payroll.rst:912
msgid ""
"Since the *Payroll* application is responsible for paying employees for "
"specific job positions, the complete list of job positions can be found in "
"both the *Payroll* and *Recruitment* applications."
msgstr ""

#: ../../content/applications/hr/payroll.rst:918
#: ../../content/applications/hr/recruitment/new_job.rst:3
msgid "Job positions"
msgstr ""

#: ../../content/applications/hr/payroll.rst:920
msgid ""
"The job positions listed in the *Payroll* application are identical to the "
"job positions listed in the *Recruitment* application. If a new job position"
" is added in the *Recruitment* application, it is also visible in the "
"*Payroll* application, and vice versa."
msgstr ""

#: ../../content/applications/hr/payroll.rst:924
msgid ""
"To view the job positions, navigate to :menuselection:`Payroll app --> "
"Configuration --> Jobs: Job Positions`."
msgstr ""

#: ../../content/applications/hr/payroll.rst:927
msgid ""
"A list of all the job positions appear, along with the corresponding "
"department, on the :guilabel:`Job Position` page."
msgstr ""

#: ../../content/applications/hr/payroll.rst-1
msgid "A list of all the job positions and corresponding departments."
msgstr ""

#: ../../content/applications/hr/payroll.rst:934
msgid ""
"To create a new job description, click the :guilabel:`New` button and a job "
"form appears."
msgstr ""

#: ../../content/applications/hr/payroll.rst:936
msgid ""
"Enter the information on the form for the new position. The information is "
"identical as to the information entered when creating a new job position in "
"the *Recruitment* application."
msgstr ""

#: ../../content/applications/hr/payroll.rst:939
msgid ""
"Refer to the :doc:`../hr/recruitment/new_job` documentation for more details"
" on how to fill out this form."
msgstr ""

#: ../../content/applications/hr/payroll.rst:943
msgid ":doc:`payroll/contracts`"
msgstr ""

#: ../../content/applications/hr/payroll.rst:944
msgid ":doc:`payroll/work_entries`"
msgstr ""

#: ../../content/applications/hr/payroll.rst:945
msgid ":doc:`payroll/salary_attachments`"
msgstr ""

#: ../../content/applications/hr/payroll.rst:946
msgid ":doc:`payroll/payslips`"
msgstr ""

#: ../../content/applications/hr/payroll.rst:947
msgid ":doc:`payroll/reporting`"
msgstr ""

#: ../../content/applications/hr/payroll.rst:948
msgid ":doc:`payroll/work_entry_analysis`"
msgstr ""

#: ../../content/applications/hr/payroll.rst:949
msgid ":doc:`payroll/salary_attachment`"
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:5
msgid ""
"Every employee in Odoo is required to have a contract in order to be paid. A"
" contract outlines the terms of an employee's position, their compensation, "
"working hours, and any other details about their position."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:10
msgid ""
"Contract documents (PDFs) are uploaded and organized using the *Documents* "
"application, and are signed using the *Sign* application. Ensure these "
"applications are installed to send and sign contracts. Please refer to the "
":doc:`../../productivity/documents` and :doc:`../../productivity/sign` "
"documentation."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:15
msgid ""
"To view the employee contracts, go to the :menuselection:`Payroll app --> "
"Contracts --> Contracts` from the top menu. All employee contracts, and "
"their current contract status, are displayed in a Kanban view, by default. "
"The Kanban view displays running contracts, contracts that require action, "
"expired contracts, and cancelled contracts."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst-1
msgid ""
"Contracts dashboard view showing running contracts and contracts with "
"issues."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:25
msgid ""
"The list of contracts in the *Payroll* application matches the list of "
"contracts in the *Employees* application."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:30
msgid ""
"In order for an employee to be paid, an active contract is required. If a "
"new contract is needed, click the :guilabel:`Create` button on the "
":guilabel:`Contracts` dashboard. A contract form appears where the "
"information can be entered. Required fields are underlined in bold."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:35
msgid "New contract form"
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:42
#: ../../content/applications/hr/payroll/contracts.rst:91
msgid ""
":guilabel:`Contact Reference`: type in the name or title for the contract, "
"such as `John Smith Contract`. This field is **required**."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:44
msgid ""
":guilabel:`Employee`: using the drop-down menu, select the employee that the"
" contract applies to."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:45
msgid ""
":guilabel:`Contract Start Date`: the date the contract starts. To choose a "
"date, click the drop-down menu, navigate to the correct month and year with "
"the :guilabel:`< > (arrow)` icons, then click on the desired date. This "
"field is **required**."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:48
msgid ""
":guilabel:`Contract End Date`: if the contract has a specific end date, "
"click the drop-down menu, navigate to the correct month and year with the "
":guilabel:`< > (arrow)` icons, then click on the desired date."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:51
#: ../../content/applications/hr/payroll/contracts.rst:105
msgid ""
":guilabel:`Working Schedule`: select one of the working schedules from the "
"drop-down menu. This field is **required**."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:55
msgid ""
"The :guilabel:`Working Schedule` drop-down menu displays all the working "
"schedules for the selected company. To modify or add to this list, go to "
":menuselection:`Payroll app --> Configuration --> Working Schedules`. Click "
":guilabel:`New`, and create a new working schedule, or click on an existing "
"working schedule and make edits."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:60
msgid ""
":guilabel:`Work Entry Source`: select how the :doc:`work entries "
"<work_entries>` are generated. This field is **required**. Click the radio "
"button next to the desired selection. The options are:"
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:63
msgid ""
":guilabel:`Working Schedule`: work entries are generated based on the "
"selected :guilabel:`Working Schedule`."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:65
msgid ""
":guilabel:`Attendances`: work entries are generated based on the employee's "
"check-in records in the *Attendances* application. (This requires the "
"*Attendances* application)."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:67
msgid ""
":guilabel:`Planning`: work entries are generated based on the planned "
"schedule for the employee from the *Planning* application. (This requires "
"the *Planning* application)."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:70
msgid ""
":guilabel:`Salary Structure Type`: select one of the salary structure types "
"from the drop-down menu. The default salary structure types are "
":guilabel:`Employee` or :guilabel:`Worker`. A :ref:`new salary structure "
"type <payroll/new-structure-type>` can be created, if needed."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:73
msgid ""
":guilabel:`Department`: select the department the contract applies to from "
"the drop-down menu."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:74
msgid ""
":guilabel:`Job Position`: select the specific job position the contract "
"applies to from the drop-down menu."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:78
msgid ""
"If the selected :guilabel:`Job Position` has a contract template linked to "
"it with a specific :guilabel:`Salary Structure Type`, the :guilabel:`Salary "
"Structure Type` changes to the one associated with that :guilabel:`Job "
"Position`."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:82
msgid ":guilabel:`Wage on Payroll`: enter the employee's monthly wage."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:83
msgid ""
":guilabel:`Contract Type`: choose either :guilabel:`Permanent`, "
":guilabel:`Temporary`, :guilabel:`Seasonal`, :guilabel:`Full-Time`, or "
":guilabel:`Part-Time` from the drop-down menu."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst-1
msgid ""
"New contract form to be filled in when creating a new contract, with required fields\n"
"outlined in red."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:93
msgid ":guilabel:`Employee`: name of the employee the contract applies to."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:94
msgid ""
":guilabel:`Contract Start Date`: the date the contract starts. Choose a date"
" by clicking on the drop-down menu, navigating to the correct month and year"
" by using the :icon:`fa-chevron-left` :icon:`fa-chevron-right` "
":guilabel:`(arrow)` icons, then clicking on the desired date. This field is "
"**required**."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:98
msgid ""
":guilabel:`Contract End Date`: the date the contract ends. Choose a date by "
"clicking on the drop-down menu, navigating to the correct month and year by "
"using the :icon:`fa-chevron-left` :icon:`fa-chevron-right` "
":guilabel:`(arrow)` icons, then clicking on the desired date. This field is "
"**required**."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:102
msgid ""
":guilabel:`Salary Structure Type`: select one of the salary structure types "
"from the drop-down menu. The default salary structure types are "
":guilabel:`Employee` or :guilabel:`Worker`. A new salary structure type can "
"be created by typing the name in the field. This field is **required**."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:107
msgid ":guilabel:`Department`: the department the contract applies to."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:108
msgid ""
":guilabel:`Job Position`: the specific job position the contract applies to."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:109
msgid ""
":guilabel:`Wage on Payroll`: the amount to be paid to the employee each "
"month."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:110
msgid ""
":guilabel:`Contract Type`: choose from :guilabel:`CDI`, :guilabel:`CDD`, or "
":guilabel:`PFI` from the drop-down menu."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:113
msgid ""
":guilabel:`CDI` is an open-ended contract with only a start date, but no end"
" date."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:114
msgid ":guilabel:`CDD` is a contract with both a start date and an end date."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:115
msgid ""
":guilabel:`PFI` is a Belgian-specific contract used when hiring employees "
"that need training, and covers the training period specifically."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:118
msgid ""
":guilabel:`HR Responsible`: if there is a specific person in HR that is "
"responsible for the contract, select the person from the drop-down menu. "
"This field is required."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:122
msgid ""
"The :guilabel:`Working Schedule` drop-down menu displays all the working "
"times for the selected :guilabel:`Company`. To modify or add to this list, "
"go to :menuselection:`Payroll app --> Configuration --> Working Times`, and "
"either :guilabel:`Create` a new working time, or click on an existing "
"working time, then edit it by clicking :guilabel:`Edit`."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:127
msgid ""
":guilabel:`Yearly Cost (Real)`: this field automatically updates after the "
":guilabel:`Schedule Pay` and :guilabel:`Wage` fields are entered. This "
"amount is the total yearly cost for the employer. This field can be "
"modified. However, if this is modified, the :guilabel:`Wage` field updates, "
"accordingly. Ensure both the :guilabel:`Wage` and :guilabel:`Yearly Cost "
"(Real)` are correct if this field is modified."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:132
msgid ""
":guilabel:`Monthly Cost (Real)`: this field automatically updates after the "
":guilabel:`Schedule Pay` and :guilabel:`Wage` fields are entered. This "
"amount is the total monthly cost for the employer. This field **cannot** be "
"modified, and is calculated based on the :guilabel:`Yearly Cost (Real)`."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:0
#: ../../content/applications/hr/payroll/contracts.rst-1
msgid "Optional tabs for a new contract."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:142
msgid "Contract Details tab"
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:144
msgid ""
"The :guilabel:`Contract Details` tab allows for the addition and editing of "
"a contract, along with specifying which template to use when a new contract "
"is created. These fields **must** be populated in order to create a new "
"contract."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:149
msgid ""
"To access the various contract template fields in the :guilabel:`Contract "
"Details` tab, the *Salary Configurator* (`hr_contract_salary`) module "
"**must** be :ref:`installed <general/install>`."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:153
msgid ""
"When the *Salary Configurator* module is installed, the *Salary Configurator"
" - Holidays* and *Salary Configurator - Payroll* modules install, as well."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:156
msgid ""
"Once the modules are installed, the database reverts to the main dashboard."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:158
msgid ""
":guilabel:`Contract Template`: select a pre-existing contract template from "
"the drop-down menu. Contract templates are typically created through the "
"configuration menu, and stored in the *Documents* application."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:165
msgid ""
":guilabel:`HR Responsible`: select the person who is responsible for "
"validating the contract from the drop-down menu. This field is required."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:167
msgid ""
":guilabel:`New Contract Document Template`: select a contract from the drop-"
"down menu to be modified for this new employee contract. These documents are"
" stored in the *Sign* application."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:169
msgid ""
":guilabel:`Contract Update Document Template`: select a contract from the "
"drop-down menu, if the employee has an existing contract that requires "
"updating. These documents are stored in the *Sign* application."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:174
msgid ""
"The :guilabel:`HR Responsible`, :guilabel:`New Contract Document Template`, "
"and :guilabel:`Contract Update Document Template` fields are only visible if"
" the *Sign* application is installed, along with the `hr_contract_salary` "
"and `hr_contract_salary_payroll` :doc:`modules "
"<../../general/apps_modules>`. The *Sign* application is where the contract "
"templates are stored. This application is required for an employee to sign "
"any contract."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:181
msgid "Accounting section"
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:183
msgid ""
":guilabel:`Analytic Account`: select the account the contract affects from "
"the drop-down menu. It is recommended to check with the accounting "
"department to ensure the correct account is selected."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:187
msgid "Part Time section"
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:189
msgid ""
":guilabel:`Part Time`: tick this box if the employee is working part-time. "
"When active, additional fields appear:"
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:192
msgid ""
":guilabel:`% (Percentage)`: enter the percent of time the employee works as "
"compared to a full-time employee."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:194
msgid ""
":guilabel:`Standard Calendar`: select the working hours that a typical full-"
"time worker uses from the drop-down menu."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:196
msgid ""
":guilabel:`Part Time Work Entry Type`: select the work entry type that "
"generates the balance of a full-time working schedule."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:200
msgid ""
"If a full-time employee works 40 hours a week, and the employee works 20, "
"enter `50` in the :guilabel:`% (Percentage)` field (50% of 40 hours = 20 "
"hours). The employee generates twenty (20) hours of work entries under the "
"work entry type `part-time`, and another twenty (20) hours of work entries "
"under the work entry type `generic time off`, for a total of forty (40) "
"hours worth of work entries."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:207
msgid "Notes section"
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:209
msgid ""
":guilabel:`Notes`: a text field where any notes for the employee contract "
"are entered for future reference."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst-1
msgid "Contract details in optional tabs for a new contract."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:216
msgid ""
":guilabel:`Analytic Account`: this field allows a link between the contract "
"and a specific analytic account for accounting purposes."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:218
msgid ""
":guilabel:`Contract Template`: select a pre-existing contract template from "
"the drop-down menu. Contract templates are typically created through the "
"*Recruitment* application."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:220
msgid ""
":guilabel:`New Contract Document Template`: select a contract from the drop-"
"down menu to be modified for this new employee contract."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:222
msgid ""
":guilabel:`Contract Update Document Template`: select a contract from the "
"drop-down menu, if the employee has an existing contract that requires "
"updating."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:224
msgid ""
":guilabel:`Notes`: the notes field is a text field where any notes for the "
"employee contract can be entered for future reference."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:228
msgid "Modify a contract template"
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:230
msgid ""
"Click the :icon:`fa-external-link` :guilabel:`(external Link)` icon at the "
"end of either the :guilabel:`New Contract Document Template` or "
":guilabel:`Contract Update Document Template` to open the corresponding "
"contract template, and proceed to make any desired changes."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:234
msgid ""
"Click the :guilabel:`Upload your file` button next to the corresponding "
"document, navigate to the file, then click :guilabel:`Open` to select the "
"document and add it to the tab."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:238
msgid "Modifying contract templates"
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:240
msgid ""
"Contracts templates can be modified at any point when changes are needed."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:242
msgid ":guilabel:`Tags`: select any tags associated with the contract."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:243
msgid ""
":guilabel:`Signed Document Workspace`: this is where the signatures are "
"stored. Choose a pre-configured workspace, or create a new one. To create a "
"new :guilabel:`Signed Document Workspace`, type in the name of the "
"workspace, then click either :guilabel:`Create` to add the new workspace, or"
" :guilabel:`Create and Edit` to add the workspace and modify the workspace "
"details."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:247
msgid ""
":guilabel:`Signed Document Tags`: select or create any tags that are only "
"associated with the signed contract, as opposed to the original unsigned "
"contract."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:249
msgid ""
":guilabel:`Redirect Link`: enter a redirect link for the employee to access "
"the contract. A redirect link takes the user from one URL to another. In "
"this case, it takes them to the newly-updated contract specifically written "
"for them."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:252
msgid ""
":guilabel:`Who can Sign`: select either :guilabel:`All Users` or "
":guilabel:`On Invitation`."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:254
msgid ""
":guilabel:`All Users`: any user in the organization can sign the contract."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:255
msgid ""
":guilabel:`On Invitation`: only users selected in this field can sign the "
"contract."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:257
msgid ""
":guilabel:`Invited Users`: select the person (or people) that can sign the "
"document."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:258
msgid ""
":guilabel:`Document`: the attached document can be replaced by clicking the "
":icon:`fa-pencil` :guilabel:`(pencil)` icon. A pop-up window appears, so "
"another document can be selected for upload. The file **must** be a PDF. To "
"remove the document, click the :icon:`fa-trash-o` :guilabel:`(trash can)` "
"icon."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:263
msgid ""
"Once the edits are complete, click the :guilabel:`Save` button. All the "
"information for the selected contract template populates the fields in the "
":guilabel:`Salary Information` tab. Any additional tabs, such as "
":guilabel:`Personal Documents`, appears if applicable."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:268
msgid "Salary information"
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:274
msgid ""
"This section is where the specific salary details are defined. This section "
"is country-specific, so these fields vary, depending on where the company is"
" located."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:277
msgid ""
"Enter the amount in the various fields, or tick a checkbox to apply a "
"benefit. Some options that can be entered here include :guilabel:`Group "
"Insurance Sacrifice Rate` and :guilabel:`Canteen Cost`, for example."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:281
msgid ""
"Some fields may be automatically filled in as other fields are entered. For "
"example, the :guilabel:`Yearly Cost (Real)` and :guilabel:`Monthly Cost "
"(Real)` updates once the :guilabel:`Wage` is populated."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:286
msgid "Personal documents"
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:288
msgid ""
"This tab **only** appears after an :guilabel:`Employee` is selected, and "
"houses any documents that are linked to the employee on their employee "
"record. Documents cannot be added to this tab, this tab **only** shows "
"documents that are already uploaded and associated with the employee."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:292
msgid ""
"The available documents in this tab can be downloaded. Click the :icon:`fa-"
"download` :guilabel:`(download)` icon next to the document to download it."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:296
msgid "Save and send the contract"
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:298
msgid ""
"Once a contract has been created and/or modified, save the contract by "
"clicking the :guilabel:`Save` button. Next, the contract must be sent to the"
" employee to be signed."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:301
msgid ""
"Click on one of the following buttons to send the contract to the employee:"
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst-1
msgid "Send the contract to the employee via one of the buttons."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:307
msgid ""
":guilabel:`Generate Simulation Link`: this option is **only** for Belgian "
"companies. Clicking this opens a pop-up window that contains the basic "
"information from the contract, as well as a link for the contract when using"
" the salary configurator. Click :guilabel:`Send` to send an email to the "
"employee, so they can sign the contract."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:312
msgid ""
"At the bottom of the pop-up form is a :guilabel:`Link Expiration Date`. This"
" is the timeframe that the contract offer is valid for. By default, this "
"field is pre-populated with `30 days`, but it can be modified."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:317
msgid ""
"In order to send a contract using the :guilabel:`Generate Simulation Link`, "
"there **must** be a signature field in the contract PDF being sent to the "
"employee, so they can sign it."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:320
msgid ""
":guilabel:`Signature Request`: clicking this reveals a pop-up window, where "
"an email can be typed to the employee. Select the document (such as a "
"contract, NDA, or Homeworking Policy) from the drop-down menu, and fill out "
"the email section. Click :guilabel:`Send` when the email is ready to be "
"sent."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:326
msgid ""
"To send a contract using the :guilabel:`Generate Simulation Link`, there "
"**must** be a signature field in the contract PDF being sent to the "
"employee, so they can sign it."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:330
#: ../../content/applications/hr/payroll/salary_attachments.rst:3
msgid "Salary attachments"
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:332
msgid ""
"Any automatic deductions or allocations for an employee, such as child "
"support payments and wage garnishments, are referred to as a *salary "
"attachment*. This section is where all of these deductions or allocations "
"are set."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:336
msgid ""
"To add a new deduction, first navigate to :menuselection:`Payroll app --> "
"Contracts --> Salary Attachments`. Next, click :guilabel:`Create`, and a new"
" salary attachment form loads."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst-1
msgid ""
"The salary attachment form with everything filled in for Ronnie Hart's child"
" support."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:345
msgid ""
":guilabel:`Employee`: using the drop-down menu, select the employee the "
"salary attachment applies to."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:347
msgid ""
":guilabel:`Description`: enter a short description for the salary "
"attachment, such as `Child Support` or `529 Contribution`."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:349
msgid ""
":guilabel:`Type`: using the drop-down menu, select the type of salary "
"attachment being created. Choose from:"
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:352
msgid ""
":guilabel:`Attachment of Salary`: any payments taken out towards something "
"that is *not* child support. Typically any garnishments, such as lawsuit "
"payments, payments toward taxes owed, etc."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:354
msgid ""
":guilabel:`Assignment of Salary`: any deduction that is not required, but "
"voluntary, such as a pre-tax allocation to a college savings account."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:356
msgid ""
":guilabel:`Child Support`: any payments taken out specifically for child "
"support."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:358
msgid ""
":guilabel:`Start Date`: the date the salary attachment starts. Choose a date"
" by clicking on the drop-down menu, navigating to the correct month and year"
" by using the :icon:`fa-chevron-left` :icon:`fa-chevron-right` "
":guilabel:`(arrow)` icons, then clicking on the desired date. This field is "
"**required**."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:362
msgid ""
":guilabel:`Estimated End Date`: this field automatically populates after "
"both the :guilabel:`Monthly Amount` and :guilabel:`Total Amount` fields are "
"populated. This field is **not** modifiable."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:365
msgid ""
":guilabel:`Document`: attach any documents relevant to the salary "
"attachment. Click the :guilabel:`Upload Your File` button, navigate to the "
"desired document in the file explorer, then click :guilabel:`Open` to select"
" the document, and attach it to the form. To change the attached document, "
"click the :icon:`fa-pencil` :guilabel:`(pencil)` icon, and select a "
"different document. To remove a document, click the :icon:`fa-trash-o` "
":guilabel:`(trash can)` icon."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:370
msgid ""
":guilabel:`Monthly Amount`: enter the amount to be taken out of the "
"employee's paycheck every month for this specific salary attachment."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:372
msgid ""
":guilabel:`Total Amount`: enter the total amount that the employee pays for "
"the salary attachment to be completed."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:3
msgid "Payslips"
msgstr "תלושי שכר"

#: ../../content/applications/hr/payroll/payslips.rst:5
msgid ""
"*Payslips* are created either by the employees themselves or their managers,"
" and are approved by authorized employees (typically managers). Then, once "
"payslips are approved, employees are issued payslips and are paid either by "
"check or direct deposit, depending on how their employee profile is "
"configured."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:10
msgid ""
"The :guilabel:`Payslips` drop-down header of the :menuselection:`Payroll` "
"application consists of three sections: :guilabel:`To Pay`, :guilabel:`All "
"Payslips`, and :guilabel:`Batches`."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:13
msgid ""
"These three sections provide all the tools needed to create payslips for "
"employees, including individual payslips, a batch of payslips, or commission"
" payslips."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst-1
msgid "Payslips menu selection in Payroll."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:23
msgid "To pay"
msgstr "לתשלום"

#: ../../content/applications/hr/payroll/payslips.rst:25
msgid ""
"Click on :menuselection:`Payroll app --> Payslips --> To Pay` to see the "
"payslips that need to be paid. On this page, Odoo displays the payslips that"
" have not been generated yet, and can be created from this dashboard."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst-1
msgid "View all payslips that need to be paid on the Payslips To Pay page."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:33
msgid ""
"Each payslip lists the :guilabel:`Reference` number for the individual "
"payslip, the :guilabel:`Employee` name, the :guilabel:`Batch Name`, the "
":guilabel:`Company`, the :guilabel:`Basic Wage`, :guilabel:`Gross Wage`, "
":guilabel:`Net Wage`, and the :guilabel:`Status` of the payslip."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:37
msgid ""
"Click on an individual payslip entry to view the details for that individual"
" payslip."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:42
msgid "Create a new payslip"
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:44
msgid ""
"A new payslip can be created from either the :ref:`Payslips To Pay "
"<payroll/to-pay>` page or the :ref:`Employee Payslips <payroll/all-"
"payslips>` page."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:47
msgid ""
"Create a new payslip by clicking the :guilabel:`New` button in the top-left "
"corner."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:49
msgid ""
"A blank payslip form is loaded, where the necessary payslip information can "
"be entered."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:52
msgid "Payslip form"
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:54
msgid ""
"On the blank payslip form, several fields are required. Most of the required"
" fields auto-populate after an employee is selected."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:57
msgid "Fill out the following information on the payslip form:"
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:59
msgid ""
":guilabel:`Employee`: type in the name of an employee, or select the desired"
" employee from the drop-down list in this field. This field is **required**."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:63
msgid ""
"It is recommended to **only** create payslips for employees that are already"
" in the database. If there is no current employee record (and therefore no "
"employee contract) it is recommended to create the new employee in the "
"*Employees* application **before** creating payslips for that employee. "
"Refer to the :doc:`new employee <../employees/new_employee>` documentation "
"for instructions on how to add an employee."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:69
msgid ""
":guilabel:`Period`: the first day to the last day of the *current* month "
"auto-populates the :guilabel:`Period` fields by default. The dates can be "
"changed, if desired."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:72
msgid ""
"To change the start date, click on the first date in the :guilabel:`Period` "
"field to reveal a pop-up calendar. On this calendar, use the :guilabel:`< "
"(less-than)` and :guilabel:`> (greater-than)` icons to select the desired "
"month. Then, click on the desired day to select that specific date."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:77
msgid ""
"Repeat this process to modify the end date for the payslip. These fields are"
" **required**."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:78
msgid ""
":guilabel:`Contract`: using the drop-down menu, select the desired contract "
"for the employee. Only the available corresponding contracts for the "
"selected employee appear as options. This field is **required**."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:81
msgid ""
":guilabel:`Batch`: using the drop-down menu in this field, select the batch "
"of payslips this new payslip should be added to."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:83
msgid ""
":guilabel:`Structure`: using the drop-down menu, select the salary structure"
" type. Only the corresponding structures associated with the selected "
"contract for the employee appear as options."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:86
msgid ""
"If no employee and/or no contract is selected yet, all available "
":guilabel:`Structures` appear in the list. Once an employee and/or contract "
"is selected, any unavailable :guilabel:`Structures` set for that employee "
"and/or contract do not appear. This field is **required**."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst-1
msgid ""
"The top fields for a new payslip all filled out for a February payslip."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:95
msgid ""
"Typically, after making a selection in the :guilabel:`Employee` field, Odoo "
"auto-populates all other required fields (besides the :guilabel:`Period` "
"field), but **only** if that information is already on that employee's form "
"in the *Employees* app."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:100
msgid ""
"If modifications to auto-populated fields are made, it is recommended to "
"check with the accounting department to ensure every entry that affects the "
"*Accounting* application is correct."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:106
msgid "Worked days & inputs tab"
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:108
msgid ""
":guilabel:`Worked Days`: the entries under :guilabel:`Worked Days` "
"(including the :guilabel:`Type`, :guilabel:`Description`, :guilabel:`Number "
"of Days`, :guilabel:`Number of Hours`, and :guilabel:`Amount`) are "
"automatically filled in, based on what was entered for the "
":guilabel:`Period`, :guilabel:`Contract`, and :guilabel:`Structure` fields "
"of the payslip form."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:112
msgid ""
":guilabel:`Other Inputs`: additional inputs affecting the payslip can be "
"entered in this section, such as deductions, reimbursements, and expenses."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:115
msgid ""
"Click :guilabel:`Add a line` to create an entry in the :guilabel:`Other "
"Inputs` section."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:117
msgid ""
"Using the drop-down menu in the :guilabel:`Type` column, select a "
":guilabel:`Type` for the input. Next, enter a :guilabel:`Description`, if "
"desired. Lastly, enter the amount in the :guilabel:`Count` field."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst-1
msgid "The fields filled out in the worked days and inputs tab."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:126
msgid "Salary computation tab"
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:128
msgid ""
":guilabel:`Salary Computation`: the :guilabel:`Salary Computation` tab is "
"automatically filled in after the :guilabel:`Compute Sheet` button is "
"clicked. Doing so displays the wages, deductions, taxes, etc. for the entry."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:131
msgid ""
":guilabel:`Has Negative Net To Report`: click the checkbox if the employee "
"has a negative net amount for this payslip. This **only** appears if the "
"employee's payslip has a negative balance."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst-1
msgid "The fields filled out in the salary computation tab."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:139
msgid "Other info tab"
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:141
msgid ""
":guilabel:`Payslip Name`: type in a name for the payslip in this field. The "
"name should be short and descriptive, such as `(Employee Name) April 2023`. "
"This field is **required**."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:143
msgid ""
":guilabel:`Company`: select the company the payslip applies to using the "
"drop-down menu in this field. This field is **required**."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:145
msgid ""
":guilabel:`Close Date`: enter the date that the payment is made to the "
"employee in this field."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:147
msgid ""
"Click in the field to reveal a calendar pop-up window. Using the "
":guilabel:`< > (less-than/greater-than)` icons, navigate to the desired "
"month and year."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:150
msgid "Then, click on the desired date to select it."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:151
msgid ""
":guilabel:`Date Account`: enter the date on which the payslip should be "
"posted in this field."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:152
msgid ""
":guilabel:`Salary Journal`: this field auto-populates after selecting an "
"existing :guilabel:`Employee`. This field **cannot** be edited, as it is "
"linked to the *Accounting* application. This field is **required**."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:155
msgid ""
":guilabel:`Accounting Entry`: if applicable, this field is automatically "
"populated once the payslip is confirmed. This field **cannot** be modified."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:157
msgid ""
":guilabel:`Add an Internal Note...`: any note or reference message for the "
"new entry can be typed in this field."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst-1
msgid "The fields filled out in the other info tab."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:165
msgid "Process the new payslip"
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:167
msgid ""
"When all the necessary information on the payslip is entered, click the "
":guilabel:`Compute Sheet` button. Upon doing so, all the information on the "
"payslip is saved, and the :guilabel:`Salary Computation` tab auto-populates,"
" based on the information on the employee's contract or attendance records."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:172
msgid ""
"If any modifications need to be made, first click the :guilabel:`Cancel` "
"button, then click the :guilabel:`Set to Draft` button. Make any desired "
"changes, then click the :guilabel:`Compute Sheet` button once again, and the"
" changes are reflected in the :guilabel:`Worked Days` and :guilabel:`Salary "
"Computation` tabs."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:177
msgid ""
"Once everything on the payslip form is correct, click the :guilabel:`Create "
"Draft Entry` button to create the payslip."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:180
msgid ""
"Then, a confirmation pop-up window appears, asking :guilabel:`Are you sure "
"you want to proceed?`. Click :guilabel:`OK` to confirm."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:183
msgid ""
"The chatter is automatically updated to show the email sent to the employee,"
" along with a PDF copy of the payslip."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:187
msgid ""
"The database may need to be refreshed for the payslip and email to appear."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:189
msgid ""
"To print the payslip, click the :guilabel:`Print` button. To cancel the "
"payslip, click the :guilabel:`Cancel` button."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst-1
msgid ""
"The new payslip is emailed to the employee and the email appears in the "
"chatter."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:196
msgid ""
"Next, the payment must be sent to the employee. To do this, click the "
":guilabel:`Register Payment` button. Doing so reveals a pop-up form, in "
"which the desired :guilabel:`Bank Journal` that the payment should be made "
"against must be selected from a drop-down menu. Then, click the "
":guilabel:`Confirm` button to confirm the journal, and return to the "
"payslip."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:202
msgid ""
"In order for a payslip to be paid, the employee *must* have a bank account "
"entered in their contact information. If there is no bank information, a "
"payslip cannot be paid, and an error appears when the :guilabel:`Make "
"Payment` button is clicked. Banking information can be found in the "
":ref:`Private Information <employees/private-info>` tab on the employee's "
"card in the *Employees* app. Edit the employee card, and add banking "
"information, if it is missing."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:0
msgid "Banking information can be entered in an employee's card."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:212
msgid ""
"Odoo automatically checks bank account information. If there is an error "
"with the employee's listed bank account, an error appears in a pop-up "
"window, stating, *The employee bank account is untrusted.* If this error "
"appears, update the employee's bank account information on their "
":ref:`Employee Form <employees/private-info>`."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:217
msgid ""
"If a payment needs to be canceled or refunded, click the corresponding "
":guilabel:`Cancel` or :guilabel:`Refund` button, located at the top-left of "
"the screen."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:221
msgid ""
"Before processing payslips, it is best practice to check the *Warnings* "
"section of the *Payroll* app dashboard. Here, all possible issues concerning"
" payroll appear."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:224
msgid ""
"To view the warnings, navigate to :menuselection:`Payroll app --> "
"Dashboard`. The warnings appear in the top-left corner of the dashboard."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:0
msgid ""
"The dashboard view of the Payroll app, with the warnings box highlighted."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:231
msgid ""
"Warnings are grouped by type, such as `Employees Without Running Contracts` "
"or `Employees Without Bank account Number`. Click on a warning to view all "
"entries associated with that specific issue."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:234
msgid ""
"If the warnings are not resolved, at any point in the payslip processing "
"process, an error may occur. Errors appear in a pop-up window, and provide "
"details for the error, and how to resolve them."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:238
msgid ""
"Payslips **cannot** be completed if there are any warnings or issues "
"associated with the payslip."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:243
msgid "All payslips"
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:245
msgid ""
"To view all payslips, regardless of status, go to :menuselection:`Payroll "
"app --> Payslips --> All Payslips`. The :guilabel:`Employee Payslips` page "
"loads, displaying all payslips, organized by batch, in a default nested list"
" view."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:249
msgid ""
"Click on the :guilabel:`▶ (right arrow)` next to an individual batch name to"
" view all the payslips in that particular batch, along with all the payslip "
"details."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:252
msgid ""
"The number of payslips in the batch is written in parenthesis after the "
"batch name. The :guilabel:`Status` for each individual payslip appears on "
"the far-right side, indicating one of the following status options:"
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:256
msgid ""
":guilabel:`Draft`: the payslip is created, and there is still time to make "
"edits, since the amounts are not calculated."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:258
msgid ""
":guilabel:`Waiting`: the payslip has been calculated, and the salary details"
" can be found in the *Salary Computation* tab."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:260
msgid ":guilabel:`Done`: the payslip is calculated and ready to be paid."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:261
msgid ":guilabel:`Paid`: the employee has been paid."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst-1
msgid ""
"View all payslips organized by batches. Click on the arrow to expand each "
"batch."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:267
msgid ""
"Click on an individual payslip to view the details for that payslip on a "
"separate page. Using the breadcrumb menu, click :guilabel:`Employee "
"Payslips` to go back to the list view of all payslips."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:270
msgid ""
"A new payslip can be created from the :guilabel:`Employee Payslips` page, by"
" clicking the :guilabel:`New` button in the upper-left corner. Doing so "
"reveals a separate blank payslip form page. On that blank payslip form page,"
" enter all the necessary information, as described in the :ref:`Create new "
"payslips <payroll/new-payslip>` section."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:275
msgid ""
"To print PDF versions of payslips from the *Payslips to Pay* or "
":guilabel:`Employee Payslips` pages, first select the desired payslips by "
"clicking on the individual checkbox to the left of each payslip to be "
"printed. Or, click the box to the left of the :guilabel:`Reference` column "
"title, which selects all visible payslips on the page. Then, click the "
":guilabel:`Print` button to print the payslips."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:281
msgid ""
"Payslips can also be exported to an Excel spreadsheet. To export **all** "
"payslips, click on the :guilabel:`⚙️ (gear)` icon at the end of the words "
":guilabel:`Employee Payslips` in the top-left corner. This reveals a drop-"
"down menu. Click :guilabel:`Export All` to export all payslips to a "
"spreadsheet."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst-1
msgid ""
"Click on the Export All smart button to export all payslips to an Excel "
"payslip."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:290
msgid ""
"To export only select payslips, first select the payslips to be exported "
"from the list. Then, click the checkbox to the left of each individual "
"payslip to select it. As payslips are selected, a smart button appears in "
"the top-center of the page, indicating the number of selected payslips. "
"Then, click the :guilabel:`⚙️ (gear) Actions` icon in the top-center of the "
"page, and click :guilabel:`Export`."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst-1
msgid ""
"The individual list of employee ayslips with three selected to be exported."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:301
msgid ""
"Both *To Pay* and *All Payslips* display all the detailed information for "
"each payslip."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:304
msgid "Batches"
msgstr "אצוות"

#: ../../content/applications/hr/payroll/payslips.rst:306
msgid ""
"To view payslips in batches, navigate to :menuselection:`Payroll app --> "
"Payslips --> Batches` to display all the payslip batches that have been "
"created. These payslip batches are displayed in a list view, by default."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:310
msgid ""
"Each batch displays the :guilabel:`Name`, :guilabel:`Date From` and "
":guilabel:`Date To` dates, its :guilabel:`Status`, the number of payslips in"
" the batch (:guilabel:`Payslips Count`), and the :guilabel:`Company`."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst-1
msgid "View displaying all batches created."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:319
msgid "Create a new batch"
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:321
msgid ""
"To create a new batch of payslips from the :guilabel:`Payslips Batches` page"
" (:menuselection:`Payroll app --> Payslips --> Batches`), click the "
":guilabel:`New` button in the top-left corner. Doing so reveals a blank "
"payslip batch form on a separate page."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:325
msgid "On the new payslip batch form, enter the :guilabel:`Batch Name`."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:327
msgid ""
"Next, select the date range to which the batch applies. Click into one of "
"the :guilabel:`Period` fields, and a calendar pop-up window appears. From "
"this calendar pop-up window, navigate to the correct month, and click on the"
" corresponding day for both the start and end dates of the batch."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:331
msgid ""
"The current company populates the :guilabel:`Company` field. If operating in"
" a multi-company environment, it is **not** possible to modify the "
":guilabel:`Company` from the form. The batch **must** be created while in "
"the database for the desired company."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst-1
msgid "Enter the details for the new batch."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:342
msgid "Process a batch"
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:344
msgid ""
"Click on an individual batch to view the details for that batch on a "
"separate page. On this batch detail page, different options (buttons) appear"
" at the top, depending on the status of the batch:"
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:347
msgid ""
":guilabel:`New` status: batches without any payslips added to them have a "
"status of :guilabel:`New`. The following button options appear for these "
"batches:"
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:0
msgid "A batch with a status of new, with the available buttons highlighted."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:354
msgid ""
":guilabel:`Add Payslips`: click the :guilabel:`Add Payslips` button to add "
"payslips to the batch, and an :guilabel:`Add Payslips` pop-up window "
"appears. Only payslips that can be added to the batch (payslips not "
"currently part of a batch) appear on the list."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:358
msgid ""
"Select the desired payslips by clicking the checkbox to the left of each "
"payslip name, then click the :guilabel:`Select` button to add them to the "
"batch. Once payslips are selected and added to the batch, the status changes"
" to :guilabel:`Confirmed`."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:362
msgid ""
":guilabel:`Generate Payslips`: after payslips have been added to the batch, "
"click the :guilabel:`Generate Payslips` button to process the payslips and "
"create individual payslips in the database."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:366
msgid ""
"A :guilabel:`Generate Payslips` pop-up window appears. If only a specific "
":guilabel:`Salary Structure` and/or specific :guilabel:`Department` is "
"desired to make payslips for, select them from the corresponding drop-down "
"menus. If no selections are made, then all payslips listed in the pop-up "
"window are processed as usual."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:371
msgid ""
"Click the :guilabel:`Generate` button to create the payslips. The "
":guilabel:`Generate Payslips` button changes to a :guilabel:`Create Draft "
"Entry` button, and the status changes to :guilabel:`Confirmed`."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:375
msgid ""
":guilabel:`Confirmed` status: batches that have been created and have "
"payslips in them, but the payslips have *not* been processed, have a status "
"of :guilabel:`Confirmed`. The following two button options appear for these "
"batches:"
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:0
msgid ""
"A batch with a status of confirmed, with the available buttons highlighted."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:383
msgid ""
":guilabel:`Create Draft Entry`: click the :guilabel:`Create Draft Entry` "
"button to confirm the individual payslips (and the batch), and create a "
"draft of the payslips. The batch now has a status of :guilabel:`Done`."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:386
#: ../../content/applications/hr/payroll/payslips.rst:408
msgid ""
":guilabel:`Set to Draft`: if at any point the batch needs to be reverted "
"back to a status of :guilabel:`New`, click the :guilabel:`Set to Draft` "
"button. This action does **not** remove any payslips that have already been "
"added to the batch."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:390
msgid ""
":guilabel:`Done` status: batches with confirmed payslips in them have a "
"status of :guilabel:`Done`. The following button options appear for these "
"batches:"
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:0
msgid "A batch with a status of done, with the available buttons highlighted."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:397
msgid ""
":guilabel:`Create Payment Report`: click the :guilabel:`Create Payment "
"Report` button, and a :guilabel:`Select a bank journal` pop-up window "
"appears. Select the correct bank journal from the drop-down menu."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:401
msgid ""
"The batch name appears in the :guilabel:`File name` field, but this can be "
"modified, if desired. Finally, click :guilabel:`Confirm` to process the "
"payslips, and pay the employees."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:403
msgid ""
":guilabel:`Mark as paid`: after the payments have been created via the "
":guilabel:`Create Payment Report` button, the payslips need to be marked as "
"paid in the database."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:406
msgid ""
"Click the :guilabel:`Mark as paid` button, and the status of the batch "
"changes to :guilabel:`Paid`."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:412
msgid ""
":guilabel:`Paid` status: batches that have been completed have a status of "
":guilabel:`Paid`. No other button options appear for this status."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:0
msgid "A batch with a status of paid, with the available buttons highlighted."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:419
msgid ""
"On the batch detail page, the individual payslips in the batch are "
"accessible, via the :guilabel:`Payslips` smart button, located above the "
"batch information, in the center. Click the :guilabel:`Payslips` smart "
"button to view a list of all the individual payslips."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:423
msgid ""
"Use the breadcrumb menu to navigate back to the individual batch detail "
"page, or back to the list of all batches."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:427
msgid "Generate warrant payslips"
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:429
msgid "Commissions are paid to employees in Odoo using *warrant payslips*."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:431
msgid ""
"Warrant payslips can be generated directly from the :guilabel:`Payslips "
"Batches` page (:menuselection:`Payroll app --> Payslips --> Batches`)."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:434
msgid ""
"First, select the desired batches by clicking the box to the left of each "
"batch for which commission payslips should be created. Next, click the "
":guilabel:`Generate Warrant Payslips` button at the top of the page."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:438
msgid ""
"Doing so reveals a :guilabel:`Generate Warrant Payslips` pop-up window, in "
"which the necessary information **must** be filled out."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst-1
msgid "Enter the commission details."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:445
msgid ""
"In this pop-up window, click on the drop-down menus, located beside the "
":guilabel:`Period` field, to reveal calendar pop-up windows. On these "
"calendar pop-up windows, select the desired period for which the payslips "
"are being generated. Using the :guilabel:`< (left)` and :guilabel:`> "
"(right)` arrow icons, navigate to the correct month, and click on the date "
"to select it."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:450
msgid ""
"In the :guilabel:`Department` field, select the desired department from the "
"drop-down menu."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:452
msgid ""
"When a department is selected, the employees listed for that department "
"appear in the :guilabel:`Employee` section."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:455
msgid ""
"Under the :guilabel:`Employee` section, enter the :guilabel:`Commission "
"Amount` for each employee in the far-right column. To remove an employee, "
"click the :guilabel:`🗑️ (trash)` icon to remove the line."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:459
msgid ""
"Add a new entry by clicking :guilabel:`Add a Line`, and entering the "
":guilabel:`Employee` and the appropriate :guilabel:`Commission Amount`."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:462
msgid ""
"Click the :guilabel:`Upload your file` button to add a file, if necessary. "
"Any file type is accepted."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:465
msgid ""
"Once all the commissions are properly entered, click the :guilabel:`Generate"
" Payslips` button to create the warrant payslips in a batch."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:468
msgid ""
":ref:`Process the batch <payroll/batch-process>` in the same way as a "
"typical batch to complete the payment process."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:5
msgid ""
"The *Reporting* section of the *Payroll* app offers a variety of reports to "
"choose from, organized by location."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:8
msgid ""
"The *Payroll* report, *Work Entry Analysis* report, and *Salary Attachment "
"Report* are default reports in the *Payroll* app, and are available for all "
"companies, regardless of location."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:11
msgid ""
"Beneath the three default reports are all localization-based reports, "
"organized by country, in alphabetical order. These reports contain all the "
"various information for the offered benefits and local tax laws."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:15
msgid ""
"To view all the available reports for the database, including all the "
"localization-specific ones, navigate to :menuselection:`Payroll app --> "
"Reporting` to view the available reports in a drop-down menu. Click on a "
"specific report to view it."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst-1
msgid "Report dashboard view showing extra reports for Belgium databases."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:23
msgid ""
"If a report is unavailable to a user, an :guilabel:`Invalid Operation` pop-"
"up window appears, stating: :guilabel:`You must be logged in to a (country) "
"company to use this feature`, where \"(country)\" is the specific country "
"the company is configured for."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:28
msgid "Default reports"
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:33
msgid ""
"Click on :menuselection:`Payroll app --> Reporting --> Payroll` to display "
"the :guilabel:`Payroll Analysis` report. This report shows all the payslips "
"generated in the last 365 days, due to the default :ref:`filter "
"<payroll/filters>`: `Last 365 Days Payslip`."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst-1
msgid "Payroll overview report showing payroll for the last 365 days."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:41
msgid ""
"The report can display metrics for a variety of parameters. Click the "
":guilabel:`Measures` box to view a drop-down menu with the various metric "
"options to display. The default options available include:"
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:45
msgid ":guilabel:`# Payslip`"
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:46
msgid ":guilabel:`Basic Wage`"
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:47
msgid ":guilabel:`Basic Wage for Time Off`"
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:48
msgid ":guilabel:`Days of Paid Time Off`"
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:49
msgid ":guilabel:`Days of Unforeseen Absence`"
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:50
msgid ":guilabel:`Days of Unpaid Time Off`"
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:51
msgid ":guilabel:`Gross Wage`"
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:52
msgid ":guilabel:`Net Wage`"
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:53
msgid ":guilabel:`Number of Days`"
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:54
msgid ":guilabel:`Number of Hours`"
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:55
msgid ":guilabel:`Work Days`"
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:56
msgid ":guilabel:`Work Hours`"
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:57
msgid ":guilabel:`Count`"
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:59
msgid ""
":guilabel:`Net Wage` is the default metric for the :guilabel:`Payroll` "
"report."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst-1
msgid ""
"The various measures available to display for the Payroll Analysis report."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:66
msgid "Line chart"
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:68
msgid ""
"A line chart is the default view for the *Payroll* report. If a different "
"view is selected, click the :guilabel:`Line Chart` button (represented by a "
":guilabel:`📈 (chart increasing)` icon) in the menu bar to change the view "
"back to a line chart."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:72
msgid ""
"Several options are available for the line chart. Click the corresponding "
"button to activate the selection, and change the way the data is presented. "
"These icons appear at the end of the chart options. The various options are:"
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:78
msgid ""
":guilabel:`Stacked`: data is presented with each metric in its own line, "
"\"stacked\" on top of each other. This helps visualize the distribution and "
"variances between different categories."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:83
msgid ""
":guilabel:`Cumulative`: data is presented with each metric on an individual "
"line, with the total amount calculated by combining all the lines. This "
"provides a comprehensive view of the cumulative data."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:89
msgid ""
":guilabel:`Descending`: data is shown with the largest values on the left "
"side of the chart, gradually decreasing towards the smallest values on the "
"right side, along the x-axis. This arrangement helps emphasize trends or "
"outliers at the extremes."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:95
msgid ""
":guilabel:`Ascending`: data is presented with the smallest values on the "
"left side of the chart, increasing towards the largest values on the right "
"side, along the x-axis. This arrangement can be useful for highlighting "
"progressive growth or trends."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:100
msgid "These options can be combined to create a variety of views."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst-1
msgid ""
"Menu buttons with the line chart called out, along with the other option "
"buttons."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:107
msgid "Bar chart"
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:109
msgid ""
"To display the data in a bar chart, click on the :guilabel:`Bar Chart` "
"button (represented by a :guilabel:`📊 (bar chart)` icon) in the menu bar."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:112
msgid ""
"Click the :ref:`Stacked <payroll/stacked>` icon to view the bar chart in a "
"stacked format (where multiple values appear in each column). "
":ref:`Cumulative <payroll/cumulative>` bar charts are useful for visualizing"
" the progression over time or other categories."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:116
msgid ""
"An option to display the columns in :ref:`Descending <payroll/descending>` "
"or :ref:`Ascending <payroll/ascending>` order appears at the end of the "
"options."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst-1
msgid ""
"Menu buttons with the bar chart called out, along with the other option "
"buttons."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:124
msgid ""
"Clicking an option enables it. To turn off the option, click it again. When "
"the option is enabled the icon appears lighter, with a turquoise outline. "
"When it is inactive, it appears gray, with no outline."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:129
msgid "Pie chart"
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:131
msgid ""
"To display the data in a pie chart, click on the :guilabel:`Pie Chart` "
"button (represented by a :guilabel:`(pie chart)` icon) in the menu bar. "
"There are no additional options available in this view."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst-1
msgid "Menu buttons with the pie chart called out."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:140
msgid "Pivot table"
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:142
msgid ""
"To display the data in a pivot table, click on the :guilabel:`Pivot` button "
"(represented by a :guilabel:`(pivot)` icon) located in the far-right side of"
" the top menu bar."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:145
msgid ""
"The default information displayed includes the number of payslips "
"(:guilabel:`# Payslip`), the :guilabel:`Net Wage`, the :guilabel:`Gross "
"Wage`, the number of :guilabel:`Days of Paid Time Off`, and the number of "
":guilabel:`Days of Unpaid Time Off`. The information is organized by "
"department."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:149
msgid ""
"To display more information on the report, click the :guilabel:`Measures` "
"button to reveal a drop-down menu. Then, click on any other metric to "
"display it on the pivot table."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst-1
msgid "Pivot table view with the various metrics called out."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:156
msgid ""
"To sort the entries by a specific column, such as :guilabel:`Net Wage`, "
"click on the column name twice. The first click selects the column, and the "
"second click sorts the information in descending order."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:160
msgid ""
"To export the data in an XLSX format, click the :guilabel:`Download xlsx` "
"button, represented by a :guilabel:`⬇️ (down arrow above a horizontal bar)` "
"icon, located at the far-right of the available icons. The information is "
"then downloaded into a spreadsheet."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst-1
msgid "The menu options with the download button highlighted."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:168
msgid ""
"Any report can be inserted into a spreadsheet by clicking the "
":guilabel:`Insert in Spreadsheet` button. A :guilabel:`Select a spreadsheet "
"to insert your (type of report)` pop-up window appears, asking which "
"spreadsheet to place the information in. Select an existing spreadsheet or "
"dashboard, or select a new :guilabel:`Blank spreadsheet`. Click the "
":guilabel:`Confirm` button to move to a spreadsheet view with the report "
"added to it."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst-1
msgid "The view of data sent to a spreadsheet."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:181
msgid ""
"If the **Documents** app is **not** installed, the :guilabel:`Insert in "
"Spreadsheet` option places the newly-created spreadsheet in the "
"**Dashboards** app."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:184
msgid ""
"If the **Documents** application *is* installed, the spreadsheet has the "
"option to be stored in either the **Dashboards** app or **Documents** app."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:192
msgid ""
"At the top of each report, the default filters are shown inside the "
":guilabel:`Search...` box."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:194
msgid ""
"Click the :guilabel:`⬇️ (down arrow)` icon in the search bar to display the "
"available :guilabel:`Filters`. Filters show information that match the "
"specific filter parameters."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:198
msgid ""
"The :guilabel:`Work Entries Analysis` report has two default filters, the "
"`Current month:(Month) (Year)` filter, and the `Validated` filter."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst-1
msgid "Filters enabled for the Work Entries Analysis report."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:205
msgid ""
"The :guilabel:`Payroll` report has only one default filter, the `Last 365 "
"Days Payslip` filter."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:207
msgid ""
"The :guilabel:`Salary Attachment Report` has only one default filter, the "
"`Payslip End Date: (Year)` filter."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:210
msgid ""
"All reports can include custom filters, or group information, by different "
"metrics (employee, department, company, etc.)."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:213
msgid ""
"Some reports have the option to compare the current report to the previous "
"time period or year (a :guilabel:`Comparison` option)."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:216
msgid ""
"Click on a parameter to select it and activate it. The report is immediately"
" updated with the new parameters."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:219
msgid ""
"The updated report can be set as a *favorite* report, meaning the parameters"
" are stored for quick access in the future. To do that, click "
":guilabel:`Save the current search`, under the :guilabel:`Favorites` "
"section, located in the search bar drop-down mega menu of filter options. "
"Doing so reveals two options and a :guilabel:`Save` button."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:224
msgid ""
"To set the current report as the default configuration when the report is "
"accessed, check the box next to :guilabel:`Default filter`. If the current "
"report should be accessible to everyone in the database, check the box next "
"to :guilabel:`Share`."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:228
msgid ""
"Finally, click :guilabel:`Save`, which saves the currently configured "
"report. Then, it appears beneath the :guilabel:`Favorites` in the search bar"
" drop-down mega menu of filter options."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachment.rst:3
msgid "Salary attachment report"
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachment.rst:5
msgid ""
"*Salary attachments* in Odoo refer to a portion of an employee's earnings "
"that are designated for a specific purpose, both voluntary and involuntary. "
"These can include contributions to a retirement plan, repayment of a loan, "
"wage garnishments, or child support."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachment.rst:9
msgid ""
"Voluntary salary attachments, such as repaying a loan, or contributing to a "
"charity on a monthly basis, are considered *Assignments of Salary* in Odoo. "
"Salary attachments that are required, such as a lawsuit settlement "
"repayment, or repaying a tax lien, are considered *Attachments of Salary* in"
" Odoo. Child support payments have their own category, and are simply "
"referred to as *Child Support* in Odoo."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachment.rst:15
msgid ""
"To view this report, navigate to :menuselection:`Payroll app --> Reporting "
"--> Salary Attachment Report`. The :guilabel:`Salary Attachment Report` "
"shows all deductions or allocations per employee, organized by payslip, in a"
" default pivot table. The default filter is the end of the current year "
"(:guilabel:`Payslip End Date: (year)`). The employees populate the rows, "
"while the various deductions populate the columns, organized by type of "
"deduction, and further grouped by individual payslip."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachment.rst:22
msgid ""
"The default report contains **all** payslips for the current year, so the "
"report typically contains a large number of columns. This could make it "
"difficult to view all the data at once, as the report may be very wide and "
"require scrolling to view all the data."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachment.rst:26
msgid ""
"To view a condensed version of salary attachments, and have all the salary "
"attachment columns visible on one page, click the :icon:`fa-minus-square-o` "
":guilabel:`Total` icon at the top of the report, above the various payslips."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachment.rst:30
msgid ""
"This presents the salary attachments for the current year, and only displays"
" three columns, :guilabel:`Attachment of Salary`, :guilabel:`Assignment of "
"Salary`, and :guilabel:`Child Support.`"
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachment.rst:33
msgid ""
"Each entry displays the total amount paid for each specific type of salary "
"attachment, for each employee."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachment.rst-1
msgid ""
"The Attachment of Salary report that shows all salary garnishments in a "
"condensed view."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachment.rst:39
msgid ""
"The report can be downloaded as an XLSX file, or :doc:`inserted into a "
"spreadsheet <../../productivity/spreadsheet/insert>` using the corresponding"
" buttons at the top."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachment.rst:42
msgid ""
"Click the :guilabel:`Measures` button to reveal the options of what data is "
"displayed. :guilabel:`Assignment of salary`, :guilabel:`Attachment of "
"salary`, and :guilabel:`Child support` are all selected and visible, by "
"default, while the :guilabel:`Count` option is not."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachment.rst:46
msgid ""
"Click an option to either show or hide that particular metric. A :icon:`fa-"
"check` :guilabel:`(checkmark)` icon indicates the data is visible."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachment.rst:50
msgid "Compare to previous year"
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachment.rst:52
msgid ""
"The :guilabel:`Salary Attachment Report` can be compared to the report for "
"the previous time period or the previous year."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachment.rst:55
msgid ""
"To view these comparisons, click the :icon:`fa-caret-down` :guilabel:`(down "
"arrow)` icon in the search bar, then click either :guilabel:`Payslip End "
"Date: Previous Period` or :guilabel:`Payslip End Date: Previous Year`, "
"beneath the :icon:`fa-adjust` :guilabel:`Comparison` column."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachment.rst:59
msgid ""
"The report updates and displays the current time period values, and the "
"previous time period values, as well as the :guilabel:`Variation` between "
"the two, in a percentage."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachment.rst-1
msgid "The salary attachment report modified to compare to the previous year."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachments.rst:5
msgid ""
"Salary attachments are portions of earnings taken directly out of a payslip "
"for a specific purpose, whether voluntary or required."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachments.rst:8
msgid ""
"When the deduction is voluntary, they are typically considered *deductions*."
" When the deduction is court-ordered, or involuntary, it is sometimes "
"referred to as a *wage garnishment*. In Odoo, these are all universally "
"called, *salary attachments*."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachments.rst:15
msgid "Salary attachment types"
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachments.rst:17
msgid ""
"To view the currently configured salary attachment types, navigate to "
":menuselection:`Payroll app --> Configuration --> Salary Attachment Types`. "
"The default salary attachment types are: :guilabel:`Attachment of Salary`, "
":guilabel:`Assignment of Salary`, and :guilabel:`Child Support`."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachments.rst:21
msgid ""
"Each salary attachment type displays the :guilabel:`Name` of the attachment "
"type, the :guilabel:`Code` used when calculating payslips, a checkbox to "
"indicate if there is :guilabel:`No End Date`, and whether it is "
":guilabel:`Country` specific (or universal)."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachments.rst-1
msgid "The default salary attachment types."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachments.rst:29
msgid "Create new salary attachment types"
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachments.rst:32
msgid ""
"Upon installation of the **Payroll** application, the pre-configured default"
" salary attachment types are linked to a variety of rules that are linked to"
" various salary structures, as well as the installed :ref:`localization "
"package <fiscal_localizations/packages>`."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachments.rst:36
msgid ""
"It is **not** recommended to alter or modify **any** of the preconfigured "
"salary attachment types, especially if they have been previously used on "
"payslips in the database. Doing so may affect various salary rules, and can "
"prevent the creation of payslips."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachments.rst:40
msgid ""
"A new salary attachment type *can* be created, but this should only be done "
"when absolutely necessary. All salary attachments can be associated with one"
" of the three default salary attachment types."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachments.rst:44
msgid ""
"To make a new type of salary attachment, click the :guilabel:`New` button, "
"and a blank :guilabel:`Salary Attachment Types` form loads. Enter the "
":guilabel:`Name` for the new salary attachment type in the corresponding "
"field. Next, enter the :guilabel:`Code` used in the salary rules to compute "
"payslips. Last, tick the :guilabel:`No End Date` checkbox if this salary "
"attachment never expires."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachments.rst:50
msgid ""
"If in a multi-company database, with locations in multiple countries, a "
":guilabel:`Country` field also appears on the :guilabel:`Salary Attachment "
"Types` form. Select the country the attachment applies to, or leave blank if"
" it is universal."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachments.rst:57
msgid "Create a salary attachment"
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachments.rst:59
msgid ""
"All salary attachments must be configured separately for each employee, for "
"each type of salary attachment. To view the currently configured salary "
"attachments, navigate to :menuselection:`Payroll app --> Contracts --> "
"Salary Attachments`."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachments.rst:63
msgid ""
"All salary attachments appear in a default list view, and displays the name "
"of the :guilabel:`Employees`, :guilabel:`Description`, the salary attachment"
" :guilabel:`Type`, the :guilabel:`Monthly Amount`, :guilabel:`Start Date`, "
"and current :guilabel:`Status`."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachments.rst:67
msgid ""
"To create a new salary attachment, click the :guilabel:`New` button in the "
"top-left corner, and a blank :guilabel:`Salary Attachment` form loads. Enter"
" the following information on the form:"
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachments.rst:70
msgid ""
":guilabel:`Employees`: Using the drop-down menu, select the desired "
"employees. Multiple employees can be listed in this field."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachments.rst:72
msgid ""
":guilabel:`Description`: Enter a short description of the salary attachment."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachments.rst:73
msgid ""
":guilabel:`Type`: Using the drop-down menu, select the specific :ref:`salary"
" attachment type <payroll/salary-attachment/types>`."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachments.rst:75
msgid ""
":guilabel:`Start Date`: Using the calendar selector, select the date the "
"salary attachment goes into effect."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachments.rst:77
msgid ""
":guilabel:`Estimated End Date`: This field is **not** modifiable, and "
"**only** appears after the :guilabel:`Monthly Amount` field is populated. "
"This field is the estimated date when the salary attachment will be "
"completed. Today's date populates the field by default. Then, when the "
":guilabel:`Total Amount` field is populated, this date is updated."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachments.rst:81
msgid ""
":guilabel:`Document`: If any documentation is needed, such as a court order,"
" click the :guilabel:`Upload your file` button, and a file explorer window "
"loads. Select the desired document to attach it to the record. Only **one** "
"document can be attached to a salary attachment."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachments.rst:84
msgid ""
":guilabel:`Monthly Amount`: Enter the amount taken out of each paycheck "
"every month in this field."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachments.rst:85
msgid ""
":guilabel:`Total Amount`: This field **only** appears if the :ref:`salary "
"attachment type <payroll/salary-attachment/types>` has no end date (the "
":guilabel:`No End Date` option is **not** ticked.)"
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachments.rst-1
msgid "The salary attachment form with all fields filled out."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachments.rst:92
msgid ""
"Since the salary attachment form auto saves as the fields are populated, "
"after making a salary attachment for an individual employee, there is no "
"further action required."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachments.rst:95
msgid ""
"If creating salary attachments for multiple employees on a single salary "
"attachment form, after the form is filled out, click the :guilabel:`Create "
"Individual Attachments` button. This creates separate salary attachments for"
" each of the employees listed in the :guilabel:`Employees` field."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachments.rst:99
msgid ""
"After the separate salary attachments have been created, the screen returns "
"to the :guilabel:`Salary Attachment` dashboard, but with a "
":guilabel:`Description` filter, populated with the description filled in on "
"the salary attachment form. All the salary attachments have a status of "
":guilabel:`Running`, since they are currently active. Clear the filter in "
"the search box to view the default :guilabel:`Salary Attachment` dashboard "
"in its entirety."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachments.rst:106
msgid "Manage salary attachments"
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachments.rst:108
msgid ""
"Salary attachments can have one of three statuses: *Running*, *Completed*, "
"or *Canceled*. To view the current status of all salary attachments, "
"navigate to :menuselection:`Payroll app --> Contracts --> Salary "
"Attachments`."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachments.rst:112
msgid ""
"All salary attachments appear in the order they were configured. To view the"
" salary attachments by a particular metric, such as the :guilabel:`Status`, "
"or :guilabel:`Type`, click on the column title to sort by that specific "
"column."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachments.rst:117
msgid "Completed salary attachments"
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachments.rst:119
msgid ""
"When a salary attachment is created, it has a status of :guilabel:`Running`."
" Once the salary attachment is finished (the *Total Amount* entered on the "
":ref:`salary attachment form <payroll/salary-attachment/create>` has been "
"paid in full), the status automatically changes to *Completed*, and the "
"employee no longer has the money taken out of future paychecks."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachments.rst:124
msgid ""
"If a salary attachment has been fulfilled, but has not automatically changed"
" to *Completed*, the record can be manually updated. To change the status, "
"open the *Salary Attachment* dashboard by navigating to "
":menuselection:`Payroll app --> Contracts --> Salary Attachments`."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachments.rst:128
msgid ""
"Click on the record to update, and the detailed :guilabel:`Salary "
"Attachment` form loads. On the individual :guilabel:`Salary Attachment` "
"record, click the :guilabel:`Mark as Completed` button in the upper-left "
"corner, and the status changes to :guilabel:`Completed`."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachments.rst:133
msgid ""
"The following is an example of when a payroll manager may need to manually "
"change a salary attachment from :guilabel:`Active` to :guilabel:`Cancelled`."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachments.rst:136
msgid ""
"Rose Smith has a salary attachment for a lawsuit settlement, where she is "
"required to pay $3,000.00. A salary attachment is created that takes $250.00"
" a month out of Rose's paycheck, to go towards this settlement payment."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachments.rst:140
msgid ""
"After six months, Rose has paid $1,500.00 from her salary. She received a "
"tax refund, and uses the money to pay off the remainder of the lawsuit "
"settlement. After sending the relevant documentation to the payroll manager,"
" showing the settlement has been paid in full, the payroll manager manually "
"changes the status of her salary attachment to :guilabel:`Completed`."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachments.rst:146
msgid "Cancel salary attachments"
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachments.rst:148
msgid ""
"Any salary attachment can be cancelled at any time. To cancel a salary "
"attachment, click on the individual attachment record from the main "
":guilabel:`Salary Attachment` dashboard to open the record. From the "
":guilabel:`Salary Attachment` record, click the :guilabel:`Cancel` button to"
" cancel the salary attachment, and stop having the designated money taken "
"out of future paychecks."
msgstr ""

#: ../../content/applications/hr/payroll/salary_attachments.rst:154
msgid ":doc:`salary_attachment`"
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:5
msgid ""
"Work entries are created automatically in the *Payroll* app, based on the "
"employee's :ref:`salary structure type <payroll/structure-types>`, and from "
"the *Planning*, *Attendances*, and *Time Off* applications."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:9
msgid ""
"The *Work Entries* dashboard of the *Payroll* application provides a visual "
"overview of the individual work entries for every employee."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:12
msgid ""
"To open the dashboard, navigate to :menuselection:`Payroll app --> Work "
"Entries --> Work Entries`."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:14
msgid ""
"On the :guilabel:`Work Entry` dashboard, work entries appear in alphabetical"
" order, based on the first name of the employees. The entire month is "
"displayed, with the current day highlighted in pale yellow."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:18
msgid ""
"If any entries have :ref:`conflicts <payroll/conflicts>` that need to be "
"resolved, the dashboard defaults to filter only the :guilabel:`Conflicting` "
"entries."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:21
msgid ""
"To remove the filter from the :guilabel:`Search...` bar to view all work "
"entries, click the :guilabel:`✖️ (remove)` icon on the "
":guilabel:`Conflicting` filter in the :guilabel:`Search...` bar, and all "
"work entries appear in the list."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst-1
msgid ""
"Conflicts dashboard view showing all employee's conflicts in work entries."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:31
msgid ""
"To change the view, so only the entries for a single day, week, or month are"
" shown, click on :guilabel:`Month`. A drop-down menu appears with the "
"options of :guilabel:`Day`, :guilabel:`Week`, or :guilabel:`Month`. Click on"
" one of the options to only display data for that specific selection."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:35
msgid ""
"Use the :guilabel:`⬅️ (left arrow)` and :guilabel:`➡️ (right arrow)` icons "
"on the left and right side of the :guilabel:`Month` button to adjust the "
"displayed dates. The arrows adjust the date based on the type of time "
"selected."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:39
msgid ""
"For example, if :guilabel:`Month` is selected, the arrows move one month "
"with each click of the arrow. If :guilabel:`Week` or :guilabel:`Day` is "
"selected, the time moves by either a week or a day for each click of the "
"arrow, respectively."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:43
msgid ""
"At any point, to return to a view containing the current day, click the "
":guilabel:`Today` button."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:48
msgid "Add a new work entry"
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:50
msgid ""
"If a work entry is missing and needs to be added, such as sick time, or if "
"an employee forgot to clock in and out for a shift, click :guilabel:`New` on"
" the :guilabel:`Work Entry` dashboard, to create a new work entry."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:54
msgid "A :guilabel:`Create` work entry pop-up form appears."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:58
msgid ""
":guilabel:`Description`: enter a short description for the work entry, such "
"as `Sick Time`. If this field is left blank, it automatically populates once"
" an employee is selected. The default entry is `Attendance: (Employee)`."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:61
msgid ""
":guilabel:`Employee`: select the employee the work entry is for, using the "
"drop-down menu."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:62
msgid ""
":guilabel:`Work Entry Type`: select the :ref:`work entry type <payroll/work-"
"entries>` using the drop-down menu."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:64
msgid ""
":guilabel:`From` and :guilabel:`To`: enter the start (:guilabel:`From`) and "
"end (:guilabel:`To`) dates and times for the work entry."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:67
msgid ""
"First, click on either the :guilabel:`From` or :guilabel:`To` line to reveal"
" a calendar pop-up window. Select the date by navigating to the correct "
"month and year, using the :guilabel:`< (left arrow)` and :guilabel:`> (right"
" arrow)` icons, then click on the specific day."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:71
msgid ""
"Next, select the time, by clicking on either the hour or minute fields at "
"the bottom of the calendar, and select the desired time for both the hour "
"and minutes."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:74
msgid ""
"When the date and time are correct for the entry, click the "
":guilabel:`Apply` button."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:75
msgid ""
":guilabel:`Duration`: displays the hours based on the :guilabel:`To` and "
":guilabel:`From` entries. Modifying this field modifies the :guilabel:`To` "
"field (the :guilabel:`From` field does not change)."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:79
msgid ""
"Once the desired information is entered, click :guilabel:`Save & Close` to "
"save the entry, and close the pop-up form."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst-1
msgid "Filling in the work entry Create form in Odoo."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:89
msgid "Conflicts"
msgstr "מתנגש"

#: ../../content/applications/hr/payroll/work_entries.rst:91
msgid ""
"A conflict appears for any request that has not been approved, such as sick "
"time or vacation, or if there are any errors on the work entry, such as "
"required fields being left blank. Conflicts are required to be resolved "
"before payslips can be generated."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:95
msgid ""
"Any work entry that has a conflict to be resolved is indicated on the main "
":guilabel:`Work Entry` dashboard, which can be accessed by navigating to "
":menuselection:`Payroll app --> Work Entries --> Work Entries`. Only "
"conflicts needing resolution are shown by default."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:99
msgid ""
"Conflicts are indicated with an orange triangle in the top-left corner of "
"each individual work entry. Click on an individual work entry to see the "
"date and time for the specific work entry, then click :guilabel:`Edit` to "
"view the conflict details in a pop-up window."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst-1
msgid "A row of conflicts, with one entry showing details for the conflict."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:107
msgid ""
"The conflict is briefly explained in an orange text box in the "
":guilabel:`Open` pop-up window that appears."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:110
msgid ""
"The :guilabel:`Description`, :guilabel:`Employee`, and :guilabel:`Work Entry"
" Type` are listed on the left side of the pop-up window. The "
":guilabel:`From` and :guilabel:`To` date and time range, as well as the "
"total time (in hours) in the :guilabel:`Duration` field, appears on the "
"right side."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:114
msgid ""
"If the conflict is due to a time off request that has not been approved yet,"
" a :guilabel:`Time Off` field appears on the left side, with the type of "
"time off requested in the description."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst-1
msgid "The detailed conflict pop-up window that appears when Edit is clicked."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:122
msgid "Time off conflicts"
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:124
msgid ""
"The most common work entry conflicts are for time off requests that have "
"been submitted, but not yet approved, which results in duplicate work "
"entries for that employee (one for time off and another for regular work)."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:128
msgid ""
"If there is a conflict because a time off request is in the system for the "
"same time that a regular work entry already exists, the time off request is "
"entered in the :guilabel:`Time Off` field."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:131
msgid ""
"The time off conflict can be resolved either on the work entry pop-up "
"window, or on a detailed time off request pop-up window."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:135
msgid "Resolve on work entry"
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:137
msgid ""
"To resolve the time off conflict on this work entry pop-up window, click the"
" :guilabel:`Approve Time Off` button to approve the time off request, and "
"resolve the work entry conflict."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:140
msgid ""
"The :guilabel:`Approve Time Off` and :guilabel:`Refuse Time Off` buttons "
"disappear. Click the :guilabel:`Save & Close` button to close the pop-up "
"window. The conflict disappears from the :guilabel:`Work Entry` dashboard, "
"since the conflict is resolved."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:145
msgid "Resolve on time off request"
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:147
msgid ""
"To resolve the time off conflict on the detailed time off request pop-up "
"window, click the :guilabel:`Internal Link` button at the end of the "
":guilabel:`Time Off` entry line, and the time off request details appear in "
"a new pop-up window. The request can be modified, if needed."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:151
msgid ""
"Click the :guilabel:`Approve` button to approve the request, then click the "
":guilabel:`Save & Close` button to save the changes, and go back to the work"
" entry conflict pop-up window."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst-1
msgid "The detailed time off request form."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:158
msgid ""
"Now, the :guilabel:`Approve Time Off` button is hidden, only the "
":guilabel:`Refuse Time Off` button is visible."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:161
msgid ""
"If the approval was a mistake, the request can be refused here, by clicking "
"the :guilabel:`Refuse Time Off` button."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:164
msgid ""
"Since the time off was approved in the time off window, click the "
":guilabel:`X` in the top-right corner to close the window. The conflict "
"disappears from the :guilabel:`Work Entry` dashboard, since it has been "
"resolved."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:171
msgid "Regenerate work entries"
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:173
msgid ""
"When regenerating work entries, any manual changes, such as resolved "
"conflicts, are overwritten, and work entries are regenerated (or recreated) "
"from the applications that created them."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:176
msgid ""
"This method for correcting a large amount of conflicts is recommended to "
"keep all records correct. While :ref:`conflicts <payroll/conflicts>` *can* "
"be resolved individually, if the conflicts are caused from another "
"application, it is best practice to ensure the records in the other "
"applications are also correct. That is why it is recommended to resolve "
"these conflicts in the applications that created the conflict."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:182
msgid ""
"Another reason this method is recommended is because, when work entries are "
"regenerated, the conflicts reappear, if the issue in the related application"
" is **not** resolved."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:185
msgid ""
"First, ensure the issues are resolved in the specific applications that "
"caused the work entry conflicts."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:188
msgid ""
"Next, click the :guilabel:`Regenerate Work Entries` button at the top of the"
" :guilabel:`Work Entries` dashboard, and a :guilabel:`Work Entry "
"Regeneration` pop-up window appears."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:191
msgid ""
"Select the :guilabel:`Employees` to regenerate work entries for from the "
"drop-down menu, and adjust the :guilabel:`From` and :guilabel:`To` fields, "
"so the correct date range is displayed."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:194
msgid ""
"Click the :guilabel:`Regenerate Work Entries` button, and the work entries "
"are recreated. Once finished, the pop-up window closes."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst-1
msgid "Regenerate a work entry for a particular employee."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:202
msgid ""
"An employee has incorrect work entries generated from the *Planning* app "
"because they were incorrectly assigned to two work stations simultaneously. "
"This should be fixed in the *Planning* app, instead of the *Payroll* app."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:206
msgid ""
"To correct this issue, modify the employee's schedule in the *Planning* app,"
" so they are correctly assigned to only one work station. Then, in the "
"*Payroll* app, regenerate work entries for that employee, for that specific "
"time period."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:210
msgid ""
"The *Payroll* app then pulls the new, corrected data form the *Planning* "
"app, and recreates the correct work entries for that employee. All conflicts"
" for that employee are now resolved."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:214
msgid "Generating payslips"
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:216
msgid ""
"To generate payslips, :ref:`navigate to the time period <payroll/adjust-"
"view>` the payslips should be generated for. Ensure the "
":guilabel:`Conflicting` filter is removed. When the desired pay period is "
"displayed, click the :guilabel:`Generate Payslips` button."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:221
msgid ""
"If the :guilabel:`Generate Payslips` button is not active (appears pale "
"purple, instead of dark purple), that indicates there are conflicts, or the "
"date selected includes dates in the future. Resolve all conflicts before "
"generating payslips."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:225
msgid ""
"When the :guilabel:`Generate Payslips` button is clicked, a batch entry "
"appears on a separate page for the time period selected."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:228
msgid ""
"The batch name populates the :guilabel:`Batch Name` field in a default `From"
" (date) to (date)` format."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:231
msgid ""
"The date range to which the payslips apply appears in the :guilabel:`Period`"
" field, and the company appears in the :guilabel:`Company` field. It is "
"**not** possible to make changes to this form."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:234
msgid ""
"Click the :guilabel:`Create Draft Entry` button to create the payslips for "
"the batch."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:236
msgid ""
"Click the :guilabel:`Payslips` smart button at the top of the page to view "
"all the payslips for the batch."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst-1
msgid "Information that appears when generating payslips."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:244
msgid "Printing payslips"
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:246
msgid ""
"To print payslips, first view the individual payslips by clicking the "
":guilabel:`Payslips` smart button on the batch form."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:249
msgid ""
"Next, select the payslips to print from the :guilabel:`Payslips` list. Click"
" the box next to each payslip to print, or click the box to the left of the "
":guilabel:`Reference` column title, to select all the payslips in the list "
"at once."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:253
msgid ""
"Click the :guilabel:`Print` button, and a PDF file is created with all the "
"specified payslips."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst-1
msgid "Print button for printing the payslips."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:260
msgid ""
"The :guilabel:`Print` button does **not** appear until at least one payslip "
"is selected in the list."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:264
msgid "Time off to report"
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:266
msgid ""
"If a time off request is submitted for a time period that was already "
"processed on a payslip, the time off request appears in the *Time Off* page "
"in the *Payroll* app, which is accessible by navigating to "
":menuselection:`Payroll app --> Work Entries --> Time Off to Report`."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:270
msgid ""
"On the :guilabel:`Time Off` page, the request appears with a status of "
":guilabel:`To defer to next payslip`. This is because the employee was "
"already paid for that day, and it was logged as time spent at work, as a "
"typical work day."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:274
msgid ""
"In order to keep the employee's time off balances correct, the time off "
"request **must** be applied to the following pay period. This not only "
"ensures time off request balances are current, it also eliminates the need "
"to redo work entries, cancel paychecks, and reissue paychecks."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:278
msgid ""
"The most common scenario when this situation occurs, is when payslips are "
"processed a day or two before the pay period ends, and an employee is "
"unexpectedly sick on one of the last days of the pay period. The employee "
"puts in a time off request for a day that was already processed on a payslip"
" as a regular work day. Instead of canceling the payslip, modifying the work"
" entries, and reissuing the paycheck, Odoo allows for those time off "
"requests to be applied to the following pay period, instead."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:285
msgid ""
"To view all the time off requests that need to be deferred to the next "
"payslip, navigate to :menuselection:`Payroll app --> Work Entries --> Time "
"Off to Report`. The default filter for this report is :guilabel:`To Defer`."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:289
msgid ""
"All time off requests that need to be applied to the following pay period "
"appear with a :guilabel:`Payslip State` of :guilabel:`To defer to next "
"payslip`."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst-1
msgid ""
"A list of all time off requests that were not approved before payslips were "
"generated."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:297
msgid "Defer multiple time off entries"
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:299
msgid ""
"To select the work entries to defer, click the box to the left of the work "
"entry line. To select all work entries in the list, click the box to the "
"left of the :guilabel:`Employees` column title, at the top of the list."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:303
msgid ""
"Once any work entry is selected, two buttons appear at the top of the "
"report: a :guilabel:`(#) Selected` button, and an :guilabel:`Actions` "
"button. The :guilabel:`(#) Selected` button indicates how many entries are "
"currently selected."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:307
msgid ""
"When all the desired work entries are selected, click the "
":guilabel:`Actions` button, and a menu appears with several choices. Click "
":guilabel:`Defer to Next Month` in the list, and all selected entries are "
"deferred to the following month."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst-1
msgid ""
"The actions button and # Selected buttons that appear after any selections "
"are made."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:316
msgid "Defer individual time off entries"
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:318
msgid ""
"Time off requests appearing on the :guilabel:`Time Off to Report` list can "
"be deferred individually."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:320
msgid ""
"Click on an individual time off request, and the details for that request "
"load."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:322
msgid ""
"The specific details for the time off request appear on the left-hand side, "
"and all of the employee's submitted time off requests appear on the right-"
"hand side (including the request in the details on the left-hand side)."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:326
msgid ""
"To defer the time off request to the next payslip, click the "
":guilabel:`Report to Next Month` button at the top. Once processed, the "
":guilabel:`Report to Next Month` button disappears, and the "
":guilabel:`Payslip State` changes from :guilabel:`To defer to next payslip` "
"to :guilabel:`Computed in Current Payslip`."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:331
msgid ""
"To go back to the :guilabel:`Time Off to Report` list, click on "
":guilabel:`Time Off` in the breadcrumb menu."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst-1
msgid ""
"The time off details for an individual request that needs to be deferred."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:339
msgid ":ref:`Configure work entries <payroll/work-entries-config>`"
msgstr ""

#: ../../content/applications/hr/payroll/work_entry_analysis.rst:3
msgid "Work entry analysis"
msgstr ""

#: ../../content/applications/hr/payroll/work_entry_analysis.rst:5
msgid ""
"The default *Work Entries Analysis* report provides an overview of the "
"validated work entries for the current month. To view this report, navigate "
"to :menuselection:`Payroll app --> Reporting --> Work Entry Analysis`."
msgstr ""

#: ../../content/applications/hr/payroll/work_entry_analysis.rst:9
msgid ""
"The work entries appear in a pivot table, with the default filters of "
":guilabel:`Current month: (Month)(Year)` and :guilabel:`Validated`. The "
"various types of :doc:`work_entries` populate the rows, while the "
":guilabel:`Total` values populate the only visible column."
msgstr ""

#: ../../content/applications/hr/payroll/work_entry_analysis.rst:13
msgid ""
"To change the displayed information, click :icon:`fa-plus-square` "
":guilabel:`Total` above the main column, revealing a drop-down menu of "
"available metrics. Click on one of the available groupings, and the data is "
"further organized by that selected metric. The default options are "
":guilabel:`Work Entry Type`, :guilabel:`Employee`, and "
":guilabel:`Department`. If in a multi-company database, a "
":guilabel:`Company` option also appears."
msgstr ""

#: ../../content/applications/hr/payroll/work_entry_analysis.rst:20
msgid "Work entry analysis comparison"
msgstr ""

#: ../../content/applications/hr/payroll/work_entry_analysis.rst:22
msgid ""
"It is possible to compare the work entries from one time period to a "
"previous time period. To view this comparison, first navigate to "
":menuselection:`Payroll app --> Reporting --> Work Entry Analysis`."
msgstr ""

#: ../../content/applications/hr/payroll/work_entry_analysis.rst:26
msgid ""
"Next, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon in the "
"search bar, revealing a drop-down menu. Under the :icon:`fa-adjust` "
":guilabel:`Comparison` section, click on either :guilabel:`Current Month: "
"Previous Period` or :guilabel:`Current Month: Previous Year`."
msgstr ""

#: ../../content/applications/hr/payroll/work_entry_analysis.rst:30
msgid ""
"The report updates and displays the data for the current time period, data "
"for the selected previous time period, as well as the :guilabel:`Variation` "
"between the two, in a percentage."
msgstr ""

#: ../../content/applications/hr/payroll/work_entry_analysis.rst-1
msgid ""
"A pivot table comparing the work entries of the current month and the "
"previous month."
msgstr ""

#: ../../content/applications/hr/payroll/work_entry_analysis.rst:37
msgid ""
"If no work entries for a specific :ref:`work entry type <payroll/work-"
"entries>` are logged for the time period, it does **not** appear on the "
"report. That does **not** mean the work entry type does not exist, or is not"
" configured."
msgstr ""

#: ../../content/applications/hr/payroll/work_entry_analysis.rst:41
msgid ""
"Additionally, if the default :guilabel:`Current month: (Month)(Year)` filter"
" is removed from the search bar, the :guilabel:`Comparison` column does "
"**not** appear; there must be a time-frame selected to view the "
":guilabel:`Comparison` column."
msgstr ""

#: ../../content/applications/hr/payroll/work_entry_analysis.rst:46
msgid "Use case: overtime report comparison"
msgstr ""

#: ../../content/applications/hr/payroll/work_entry_analysis.rst:48
msgid ""
"It is possible to alter the *Work Entries Analysis* report to show a "
"comparison of only overtime work entries, grouped by employee, for a "
"specific time period. To view this data, first navigate to the default *Work"
" entry analysis* report by going to :menuselection:`Payroll app --> "
"Reporting --> Work Entry Analysis`."
msgstr ""

#: ../../content/applications/hr/payroll/work_entry_analysis.rst:53
msgid ""
"Next, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon in the "
"search bar, revealing a drop-down menu. Under the :icon:`fa-filter` "
":guilabel:`Filters` column, click :guilabel:`Add Custom Filter`, and a "
":guilabel:`Add Custom Filter` pop-up window appears."
msgstr ""

#: ../../content/applications/hr/payroll/work_entry_analysis.rst:57
msgid ""
"Using the drop-down menu, select :guilabel:`Work Entry Type` for the first "
"field, leave the middle field as-is (with :guilabel:`is in` populating the "
"field), and select :guilabel:`Overtime Hours` for the last field. Click "
":guilabel:`Add`, and all other work entry types disappear, and "
":guilabel:`Overtime Hours` appear in the sole row."
msgstr ""

#: ../../content/applications/hr/payroll/work_entry_analysis.rst:62
msgid ""
"To compare overtime from the current month to the previous month, to see "
"which month had more overtime logged, click the :icon:`fa-caret-down` "
":guilabel:`(down arrow)` icon again in the search bar. Under the :icon:`fa-"
"adjust` :guilabel:`Comparison` section, click :guilabel:`Current Month: "
"Previous Period`. Click away from the drop-down menu to close it."
msgstr ""

#: ../../content/applications/hr/payroll/work_entry_analysis.rst:67
msgid ""
"Now, the report displays the :guilabel:`Overtime Hours` for the current "
"month and the previous month, along with the :guilabel:`Variation`, in a "
"percentage."
msgstr ""

#: ../../content/applications/hr/payroll/work_entry_analysis.rst:70
msgid ""
"To view which employees received the most overtime, click :icon:`fa-plus-"
"square` :guilabel:`Overtime Hours`, revealing a drop-down menu of options. "
"Click :guilabel:`Employee`, and all employees with overtime work entries for"
" either the current or previous month appears."
msgstr ""

#: ../../content/applications/hr/payroll/work_entry_analysis.rst:74
msgid ""
"In this example, it can be determined that :guilabel:`Marc Demo` worked the "
"most overtime in :guilabel:`August 2024`, whereas :guilabel:`Beth Evans` "
"worked the most overtime hours in :guilabel:`September 2024`. Additionally, "
":guilabel:`Mitchell Admin` had the largest variation change, with a "
":guilabel:`-100%` change from :guilabel:`August 2024` to "
":guilabel:`September 2024`."
msgstr ""

#: ../../content/applications/hr/payroll/work_entry_analysis.rst-1
msgid ""
"A pivot table comparing the overtime from September 2024 with August 2024."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:5
msgid "Recruitment"
msgstr "גיוס"

#: ../../content/applications/hr/recruitment.rst:7
msgid ""
"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.'"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:12
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:16
msgid ""
":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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:20
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:25
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:36
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:42
msgid "Job posting"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:44
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:49
msgid ""
"The :guilabel:`Online Posting` is only available if the *Website* "
"application is also installed."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:52
msgid "Recruitment process"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:54
msgid ""
"The :guilabel:`Recruitment process` section of the settings page specifies "
"what the database can and cannot do during the recruitment process."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:58
msgid "Send interview survey"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:60
msgid ""
"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"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:64
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:69
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:75
msgid ""
"For more detailed information about surveys, refer to the :doc:`survey "
"essentials <../marketing/surveys/create>` documentation."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:79
msgid ""
"Enabling the :guilabel:`Send Interview Survey` option will install the "
"*Surveys* application once the settings are saved, if it is not installed "
"already."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:83
msgid "Send SMS"
msgstr "שלח SMS"

#: ../../content/applications/hr/recruitment.rst:85
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:91
msgid ""
"For more information, refer to the :doc:`SMS pricing and FAQs "
"<../marketing/sms_marketing/pricing_and_faq>` documentation."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:97
msgid "CV display"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:99
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:103
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:108
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:113
msgid ""
"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)."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:116
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst-1
msgid "The resumé on an applicant's card, appearing on the right side."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:127
msgid "CV digitization (OCR)"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:129
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:135
msgid ""
"When enabled, additional options appear. Click on the corresponding radio "
"button to select one of the following options:"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:138
msgid ""
":guilabel:`Do not digitize`: this option turns off resumé digitization."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:139
msgid ""
":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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:142
msgid ""
":guilabel:`Digitize automatically`: this option automatically digitizes all "
"resumés when they are submitted."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:145
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:150
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:154
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:158
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:161
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:169
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:176
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst-1
msgid ""
"Main dashboard view of job position card, showing new applications button."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:185
msgid ""
"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:"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:189
msgid ":ref:`New <recruitment/new>`"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:190
msgid ":ref:`Initial Qualification <recruitment/initial-qualification>`"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:191
msgid ":ref:`First Interview <recruitment/first-interview>`"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:192
msgid ":ref:`Second Interview <recruitment/second-interview>`"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:193
msgid ":doc:`Contract Proposal <recruitment/offer_job_positions>`"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:194
msgid ""
":ref:`Contract Signed <recruitment/offer_job_positions/contract-signed>`"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:196
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst-1
msgid "Expand a folded column by clicking on it in the Kanban view."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:205
msgid ""
"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:"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:208
msgid ":guilabel:`Green`: the applicant is ready to move to the next stage."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:209
msgid ""
":guilabel:`Red`: the applicant is blocked from moving to the next stage."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:210
msgid ""
":guilabel:`Gray`: the applicant is still in progress in the current stage "
"and is neither ready nor blocked from the next stage."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:213
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst-1
msgid "The applicant card statuses, and status bar."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:222
msgid ""
"The names for the three status colors (`In Progress`, `Blocked`, and `Ready "
"for Next Stage`) :ref:`can be modified <recruitment/modify-stages>`, if "
"desired."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:228
msgid "Customize stages"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:230
msgid ""
"Stages can be modified, added, or deleted to best meet the needs of the "
"particular hiring steps of a business."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:234
msgid "New stage"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:236
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst-1
msgid "The plus sign to click to add a new column to the Kanban stages."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:248
#: ../../content/applications/hr/recruitment/schedule_interviews.rst:223
msgid "Modify stage"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:250
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst-1
msgid ""
"The gear icon that appears when a column name is moused over, and the drop-down menu it\n"
"displays when clicked."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:264
msgid "Edit stage form"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:266
msgid ""
"The :guilabel:`Edit: (Stage)` form is where the stage's settings are "
"configured. The only required field is the :guilabel:`Stage Name`."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:269
msgid "The fields to be populated or modified are:"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:271
msgid ":guilabel:`Stage Name`: type in a name for the stage."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:272
msgid ""
":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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:275
msgid ""
":guilabel:`Folded in Kanban`: check the box to have the stage appear folded "
"(hidden) at all times in the default view."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:277
msgid ""
":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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:281
msgid ""
":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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:283
msgid ""
":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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:288
msgid ""
":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)."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:293
msgid ""
":guilabel:`Requirements`: enter any internal notes for this stage explaining"
" any requirements of the stage."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:297
msgid "Delete stage"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:299
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:306
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:311
msgid "Email templates"
msgstr "תבניות דוא\"ל"

#: ../../content/applications/hr/recruitment.rst:313
msgid ""
"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:"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:316
msgid ""
":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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:319
msgid ""
":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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:322
msgid ""
":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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:326
msgid ""
":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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:329
msgid ""
":guilabel:`Recruitment: Refuse`: this template is used when an applicant is "
"no longer being considered for the position."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:333
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:336
msgid ""
"To manually send an email, click :guilabel:`Send message` in the chatter. A "
"text box appears, as well as the applicant's email address."
msgstr ""

#: ../../content/applications/hr/recruitment.rst-1
msgid "Send an email from the chatter."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:343
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:349
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:352
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:358
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:362
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:366
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst-1
#: ../../content/applications/hr/recruitment/recruitment-flow.rst-1
msgid ""
"Send a custom survey, also referred to as an interview form, to an applicant using a\n"
"pre-configured template."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:377
msgid ":doc:`recruitment/new_job`"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:378
msgid ":doc:`recruitment/add-new-applicants`"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:379
msgid ":doc:`recruitment/schedule_interviews`"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:380
msgid ":doc:`recruitment/offer_job_positions`"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:381
msgid ":doc:`recruitment/refuse_applicant`"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:382
msgid ":doc:`recruitment/source_analysis`"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:383
msgid ":doc:`recruitment/recruitment_analysis`"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:384
msgid ":doc:`recruitment/time_in_stage`"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:385
msgid ":doc:`recruitment/team_performance`"
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:3
msgid "Add new applicants"
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:5
msgid ""
"Once an applicant submits an application, either using the online "
"application, or emailing a job position alias, an applicant card is "
"automatically created in the *Recruitment* application."
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:8
msgid ""
"However, in some instances, applicants may need to be created manually in "
"the database. This could be necessary if, for example, a company accepts "
"paper applications in the mail, or is meeting prospective applicants at an "
"in-person job fair."
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:12
msgid ""
"To view current applicants, navigate to the :menuselection:`Recruitment` "
"app, then click the desired job position card. Doing so reveals the "
":guilabel:`Applications` page, which displays all applicants for that "
"specific role, in a default Kanban view, organized by stage."
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:16
msgid ""
"Add new applicants from a job position's :guilabel:`Applications` page by "
"using either: the :ref:`New <recruitment/create-new-applicant>` button or "
"the :ref:`quick add <recruitment/quick-add-applicant>` button."
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:23
msgid "Quick add"
msgstr "הוספה מהירה"

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:25
msgid ""
"On the :guilabel:`Applications` page, click the on the quick add button, "
"represented by a small :icon:`fa-plus` :guilabel:`(plus)` icon in the top-"
"right corner of each stage to quickly add a new applicant to that stage."
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:29
msgid "Enter the following information on the card:"
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:31
msgid ""
":guilabel:`Subject/Application`: enter the title for the card. Typically, "
"this is the applicant's name, and job position being applied to. For "
"example: `Laura Smith - HR Manager`. The text entered in this field is "
"**not** visible in the Kanban view of the :guilabel:`Applications` page, "
"unless the :guilabel:`Applicant's Name` field is left blank."
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:35
msgid ""
":guilabel:`Applicant's Name`: enter the applicant's name. Displays as the "
"card title in the Kanban view of the :guilabel:`Applications` page."
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:37
#: ../../content/applications/hr/recruitment/add-new-applicants.rst:87
msgid ":guilabel:`Email`: enter the applicant's email address."
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:38
msgid ""
":guilabel:`Applied Job`: the current job position populates this field. If "
"needed, the job position can be changed by selecting a different position "
"from the drop-down menu. If a different job position is selected, after the "
"card is created, the card appears on the :guilabel:`Applications` page for "
"that newly-selected job position."
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:43
msgid ""
"After the information is entered, click :guilabel:`Add`. The applicant "
"appears in the list, and a new blank applicant card appears."
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:46
msgid ""
"If preferred, after entering the :guilabel:`Applicant's Name` in the Kanban "
"card that appears, click :guilabel:`Edit`, and a detailed applicant form "
"loads. Refer to the :ref:`New applicant form <recruitment/applicant-"
"details>` section for details about filling out the form."
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:50
msgid ""
"When doing a quick add, clicking away from an empty card, or clicking the "
":icon:`fa-trash-o` (:guilabel:`trash`) icon, discards the applicant."
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst-1
msgid ""
"All the fields for a new applicant form entered when using the Quick Add "
"option."
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:60
msgid "New applicant form"
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:62
msgid ""
"On the new applicant form, the :guilabel:`Subject / Application` field is "
"populated with the pre-selected job position, by default. Certain fields on "
"the applicant card may also be pre-populated, depending on how the job "
"position is configured. Typically, the :guilabel:`Job` section, as well as "
"the :guilabel:`Recruiter` field, are pre-populated."
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:67
msgid ""
"Complete the fields in the following sections on the new applicant form."
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:70
msgid ""
"Depending on installed applications and configurations, some fields may "
"**not** be displayed."
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst-1
msgid "All the fields for a new applicant form entered."
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:79
msgid "Applicant section"
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:81
msgid ""
":guilabel:`Subject/Application Name`: this is the **only** required field. "
"Enter the title for the card in this field. Typically, this is the "
"applicant's name, and the job position being applied to. For example: `John "
"Smith - Experienced Developer`. This field is **not** visible in the Kanban "
"view of the :guilabel:`Applications` page, unless the :guilabel:`Applicant's"
" Name` is left blank."
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:85
msgid ""
":guilabel:`Applicant's Name`: enter the applicant's name. This field is "
"displayed as the card title in the Kanban view of the "
":guilabel:`Applications` page."
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:88
msgid ":guilabel:`Phone`: enter the applicant's phone number."
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:89
msgid ":guilabel:`Mobile`: enter the applicant's mobile number."
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:90
msgid ""
":guilabel:`LinkedIn Profile`: enter the web address for the applicant's "
"personal profile on LinkedIn."
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:92
msgid ""
":guilabel:`Degree`: select the applicant's highest level of education from "
"the drop-down menu. Options are: :guilabel:`Graduate`, :guilabel:`Bachelor "
"Degree`, :guilabel:`Master Degree`, or :guilabel:`Doctoral Degree`. The "
":guilabel:`Graduate` option indicates the applicant graduated at the highest"
" level of school before a Bachelor's degree, such as a high school or "
"secondary school diploma, depending on the country."
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:97
msgid ""
":guilabel:`Interviewers`: using the drop-down menu, select the people to "
"conduct the interviews. The selected people **must** have either *recruiter*"
" or *officer* rights configured for the *Recruitment* application to appear "
"in the drop-down list. Refer to the :doc:`Access rights "
"<../../general/users/access_rights>` documentation for more information."
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:101
msgid ""
":guilabel:`Recruiter`: select the user responsible for the entire "
"recruitment process for the job position."
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:103
msgid ""
":guilabel:`Evaluation`: represents a rating for the applicant: one star "
"(:icon:`fa-star` :icon:`fa-star-o` :icon:`fa-star-o`) is :guilabel:`Good`, "
"two stars (:icon:`fa-star` :icon:`fa-star` :icon:`fa-star-o`) is "
":guilabel:`Very Good`, and three stars (:icon:`fa-star` :icon:`fa-star` "
":icon:`fa-star`)is :guilabel:`Excellent.`"
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:107
msgid ""
":guilabel:`Source`: using the drop-down menu, select where the applicant "
"learned about the job position. The following options come pre-configured in"
" Odoo: :guilabel:`Search engine`, :guilabel:`Lead Recall`, "
":guilabel:`Newsletter`, :guilabel:`Facebook`, :guilabel:`Twitter`, "
":guilabel:`LinkedIn`, :guilabel:`Monster`, :guilabel:`Glassdoor`, and "
":guilabel:`Craigslist`. To add a new :guilabel:`Source`, type in the source,"
" then click :guilabel:`Create \"(new source)\"`."
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:112
msgid ""
":guilabel:`Medium`: using the drop-down menu, specify how the job listing "
"was found. The pre-configured options are: :guilabel:`Banner`, "
":guilabel:`Direct`, :guilabel:`Email`, :guilabel:`Facebook`, "
":guilabel:`Google Adwords`, :guilabel:`LinkedIn`, :guilabel:`Phone`, "
":guilabel:`Television`, :guilabel:`Twitter` (now known as \"X\"), or "
":guilabel:`Website`. To add a new :guilabel:`Medium`, type in the medium, "
"then click :guilabel:`Create \"(new medium)\"`."
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:117
msgid ""
":guilabel:`Referred By User`: if referral points are to be earned for this "
"job position in the *Referrals* application, select the user who referred "
"the applicant from the drop-down menu. The *Referrals* application **must** "
"be installed for this field to appear."
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:120
msgid ""
":guilabel:`Availability`: select the available start date for the applicant."
" To select a date, click on the field to reveal a popover calendar. Use the "
":icon:`fa-angle-left` :guilabel:`(left)` and :icon:`fa-angle-right` "
":guilabel:`(right)` arrows on either side of the month to navigate to the "
"desired month, then click the desired date. Leaving this field blank "
"indicates the applicant can start immediately."
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:125
msgid ""
":guilabel:`Tags`: select as many tags as desired from the drop-down menu. To"
" add a tag that does not exist, type in the tag name, then click "
":guilabel:`Create \"new tag\"` from the resulting drop-down menu."
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:130
msgid "Job section"
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:132
msgid ""
"The following fields are pre-populated when creating a new applicant, as "
"long as these field are specified on the job position form. Editing the "
"fields is possible, if desired."
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:135
msgid ""
":guilabel:`Applied Job`: select the job position the applicant is applying "
"to from the drop-down menu."
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:137
msgid ""
":guilabel:`Department`: select the department the job position falls under "
"from the drop-down menu."
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:139
msgid ""
":guilabel:`Company`: select the company the job position is for using the "
"drop-down menu. This field **only** appears when in a multi-company "
"database."
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:143
msgid "Contract section"
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:145
msgid ""
":guilabel:`Expected Salary`: enter the amount the applicant is requesting in"
" this field. The number should be in a `XX,XXX.XX` format. The currency is "
"determined by the localization setting for the company."
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:149
msgid ""
":guilabel:`Extra advantages...`: if any extra advantages are requested by "
"the applicant, enter it in the :guilabel:`Extra advantages...` field to the "
"right of the :guilabel:`Expected Salary` field. This should be short and "
"descriptive, such as `1 week extra vacation` or `dental plan`."
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:153
msgid ""
":guilabel:`Proposed Salary`: enter the amount to be offered to the applicant"
" for the role in this field. The number should be in a `XX,XXX.XX` format."
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:156
msgid ""
":guilabel:`Extra advantages...`: if any extra advantages are offered to the "
"applicant, enter it in the :guilabel:`Extra advantages...` field to the "
"right of the :guilabel:`Proposed Salary` field. This should be short and "
"descriptive, such as `unlimited sick time` or `retirement plan`."
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:161
msgid "Application Summary tab"
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:163
msgid ""
"Any additional details or notes that should be added to the applicant's card"
" can be typed into this field."
msgstr ""

#: ../../content/applications/hr/recruitment/add-new-applicants.rst:169
msgid ""
"Skills can be added to the applicant's card. For details on adding skills, "
"refer to the :ref:`Create new employees <employees/skills>` document."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:5
msgid ""
"In Odoo *Recruitment*, all job positions are shown on the default dashboard "
"in the *Recruitment* app. This includes positions that are being actively "
"recruited for, as well as inactive positions."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:8
msgid ""
"Each job position is shown in an individual Kanban card. If the job position"
" is active, and candidates can apply, a :guilabel:`Published` banner appears"
" in the top-right corner of the card."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:11
msgid ""
"View submitted applications by clicking anywhere on a job position card."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst-1
msgid "Main dashboard view of Recruitment app showing all job positions."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:18
msgid "Create a new job position"
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:20
msgid ""
"To create a new job position from the main dashboard in the *Recruitment* "
"app, click the :guilabel:`New` button in the top-left corner, and a "
":guilabel:`Create a Job Position` modal appears."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:24
msgid ""
"First, enter the name of the :guilabel:`Job Position` (such as `Sales "
"Manager`, `Mechanical Engineer`, etc.) in the field."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:27
msgid ""
"Next, enter an :guilabel:`Application email` by typing in the first half of "
"the email address in the first field, then select the second half of the "
"email using the drop-down menu in the second field. Applicants can send a "
"resumé to this specific email address, and Odoo creates an application for "
"them automatically."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:32
msgid ""
"When complete, click the :guilabel:`Create` button to save the entry, or the"
" :guilabel:`Discard` button to delete it."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst-1
msgid "Create a new job position."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:39
msgid ""
"Once the job position has been created, it appears as a card in the Kanban "
"view on the main *Recruitment* app dashboard."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:45
msgid "Edit a new job position"
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:47
msgid ""
"After the job position is created, it's time to enter the details for the "
"position. Click on the :guilabel:`⋮ (three dots)` icon in the upper-right "
"corner of the relevant card to reveal several options, and then click "
":guilabel:`Configuration` to edit the details."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst-1
msgid "Edit the job position card."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:55
msgid ""
"All the basic information about the job position is listed under the "
":guilabel:`Recruitment` tab."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:57
msgid ""
"None of the fields are required, but it is important to configure and "
"populate the :guilabel:`Department`, :guilabel:`Location`, "
":guilabel:`Employment Type`, and :guilabel:`Job Summary` fields, as they are"
" all visible to prospective applicants on the website."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:61
msgid "The fields can be filled out as follows:"
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:63
msgid ""
":guilabel:`Department`: select the relevant department for the job position."
" This is visible on the website."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:65
msgid ""
":guilabel:`Job Location`: select the physical address for the job. If the "
"job position is remote, leave this field blank. This is visible on the "
"website."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:67
msgid ""
":guilabel:`Email Alias`: enter an email address to which applicants can send"
" a resumé. Once emailed, Odoo automatically creates an application for them."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:69
msgid ""
":guilabel:`Employment Type`: select what type of position the job is, using "
"the drop-down menu. The default options are :guilabel:`Permanent`, "
":guilabel:`Temporary`, :guilabel:`Seasonal`, :guilabel:`Interim`, "
":guilabel:`Full-Time`, and :guilabel:`Part-Time`. This is visible on the "
"website."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:73
msgid ""
":guilabel:`Company`: select the company the job is for. This field only "
"appears if using a multi-company database."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:75
msgid ""
":guilabel:`Target`: enter the number of employees to be hired for this "
"position."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:76
msgid ""
":guilabel:`Is Published`: activate this option to publish the job online."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:77
msgid ":guilabel:`Website`: select the website the job is published on."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:78
msgid ""
":guilabel:`Recruiter`: select the person responsible for recruiting this "
"role."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:79
msgid ""
":guilabel:`Interviewers`: select who should perform the interviews. Multiple"
" people can be selected."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:81
msgid ""
":guilabel:`Interview Form`: select an :ref:`Interview form "
"<recruitment/interview>` that applicants fill out prior to their interview."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:83
msgid ""
":guilabel:`Contract Template`: select a contract template to be used when "
"offering the job to a candidate."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:85
msgid ""
":guilabel:`Process Details` section: this section contains information that "
"is displayed online for the job position. This informs the applicants of the"
" timeline and steps for the recruitment process, so they know when to expect"
" a reply."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:89
msgid ""
":guilabel:`Time to Answer`: enter the number of days before the applicant is"
" contacted."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:90
msgid ""
":guilabel:`Process`: enter the various stages the candidate goes through "
"during the recruitment process."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:92
msgid ""
":guilabel:`Days to get an Offer`: enter the number of days before the "
"applicant should expect an offer after the recruitment process has ended."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:96
msgid ""
"The :guilabel:`Process Details` section is a text field. All answers are "
"typed in rather than selected from a drop-down menu. The text is displayed "
"on the website exactly as it appears in this tab."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:100
msgid "Finally, enter the job description in the :guilabel:`Job Summary` tab."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst-1
msgid "Enter job information details in the recruitment tab."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:109
msgid "Create interview form"
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:111
msgid ""
"An *Interview Form* is used to determine if a candidate is a good fit for a "
"job position. Interview forms can be as specific or general as desired, and "
"can take the form of a certification, an exam, or a general questionnaire. "
"Interview forms are determined by the recruitment team."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:115
msgid ""
"Before creating an interview form, ensure the proper settings are enabled. "
"Navigate to :menuselection:`Recruitment app --> Configuration --> Settings`,"
" and under the :guilabel:`Recruitment Process` section, ensure the "
":guilabel:`Send Interview Survey` option is enabled."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:120
msgid ""
"Since there are no pre-configured forms in Odoo, all interview forms must be"
" created. To create an interview form, start from the "
":guilabel:`Recruitment` tab of the :guilabel:`Job Position` form. In the "
":guilabel:`Interview Form` field, enter a name for the new interview form. "
"As the name is typed, several options populate beneath the entry: "
":guilabel:`Create (interview form name)`, :guilabel:`Search More...`, and "
":guilabel:`Create and edit...`. Click :guilabel:`Create and edit...` and a "
":guilabel:`Create Interview Form` modal appears."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst-1
msgid "The blank interview form modal."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:132
msgid ""
"The option :guilabel:`Search More...` only appears if there are any "
"interview forms already created. If no interview forms exist, the only "
"options available are :guilabel:`Create (interview form name)`, and "
":guilabel:`Create and edit...`."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:136
msgid ""
"Proceed to fill out the modal interview form as a typical survey. For "
"specific directions on how to create a survey, refer to the :doc:`survey "
"essentials <../../marketing/surveys/create>` document, which provides step-"
"by-step instructions on how to create and configure a survey."
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:3
msgid "Offer job positions"
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:5
msgid ""
"Once an applicant has successfully passed the various interview stages, the "
"recruitment team is ready to send an offer for employment. The next step is "
"to send the applicant a contract."
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:9
msgid ""
"Refer to the :doc:`recruitment <../recruitment>` documentation for details "
"on the various stages of the recruitment process."
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:13
msgid "Contract proposal"
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:15
msgid ""
"When an offer is ready to be sent, first open the applicant's card by "
"navigating to the :menuselection:`Recruitment app`, and clicking on the "
"desired job position card."
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:18
msgid ""
"From the resulting :guilabel:`Job Positions` Kanban view, the corresponding "
"applicant card can be dragged-and-dropped to the :guilabel:`Contract "
"Proposal` stage. Or, click into the desired applicant's card, and click the "
":guilabel:`Contract Proposal` stage, located in the status bar in the top-"
"right of the applicant's form."
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:23
msgid ""
"The next step is to send an offer to the applicant. Start by selecting the "
"desired applicant's card to open their applicant form."
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:26
msgid ""
"On the applicant's form, click the :guilabel:`Generate Offer` button. A "
":guilabel:`Generate a Simulation Link` pop-up window appears."
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:29
msgid ""
"Most fields are pre-populated with information from the job position. If any"
" necessary fields are blank, or if any information needs to be updated, "
"enter, or update, the relevant information in the corresponding fields."
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:34
msgid ""
"Depending on the localization setting for the company, and which "
"applications are installed, some fields may not appear in the "
":guilabel:`Generate a Simulation Link` pop-up window."
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:37
msgid ""
"For example, if the *Fleet* application is **not** installed, any fields "
"related to vehicles do **not** appear."
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:41
msgid "Universal fields"
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:43
msgid ""
"The following fields appear in the :guilabel:`Generate a Simulation Link` "
"pop-up window, regardless of the localization."
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:46
msgid ""
":guilabel:`Contract Template`: the template currently being used to populate"
" the :guilabel:`Generate a Simulation Link` pop-up window. Use the drop-down"
" menu to select a different :guilabel:`Contract Template`, if desired."
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:51
msgid ""
"To modify the template, hover over the current template name, and click the "
":icon:`oi-launch` :guilabel:`Internal link` icon that appears to the right "
"of the field. Make any desired changes, then click :guilabel:`Save & Close`."
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:55
msgid ""
":guilabel:`Job Position`: the name of the :guilabel:`Job Position` being "
"offered to the applicant. The selections available in the drop-down menu "
"correspond to the job position configured on the main *Recruitment* "
"dashboard."
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:58
msgid ""
":guilabel:`Job Title`: the selected :guilabel:`Job Position` populates this "
"field, by default. The title can be modified to suit the specific "
"applicant's position and provide more details."
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:62
msgid ""
"An applicant is offered a marketing manager job at a shoe company, "
"specifically for the children's line."
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:65
msgid ""
"The :guilabel:`Job Position` selected from the drop-down menu is `Marketing "
"Manager`, and the :guilabel:`Job Title` is modified for their specific "
"responsibilities, `Marketing Manager: Children's Shoes`."
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:69
msgid ":guilabel:`Department`: the department the job position falls under."
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:70
msgid ""
":guilabel:`Contract Start Date`: the date the contract takes effect. The "
"default date is the current date. To modify the date, click on the displayed"
" date to reveal a calendar popover window. Navigate to the desired month, "
"then click the day to select the date."
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:73
msgid ":guilabel:`Yearly Cost`: the annual salary being offered."
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:74
msgid ""
":guilabel:`Link Expiration Date`: the number of days the job offer is valid."
" The default expiration date is `30` days. Modify the expiration date, if "
"desired."
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:78
msgid "Send offer"
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:80
msgid ""
"Once the :guilabel:`Generate a Simulation Link` pop-up window is complete, "
"click :guilabel:`Send By Email` to reveal an email pop-up window."
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:84
msgid ""
"If the applicant does not have an email address listed on their applicant "
"card, a warning appears in a red box at the bottom of the "
":guilabel:`Generate a Simulation Link` pop-up window, stating: "
":guilabel:`The applicant does not have a valid email set. The Offer Link "
"won't be able to be completed.` Click :guilabel:`Discard`, then enter an "
"email on the applicant's card. Once an email is entered, click the "
":guilabel:`Generate Offer` button, and the email pop-up window loads again."
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:90
msgid ""
"The default :guilabel:`Recruitment: Your Salary Package` email template is "
"used (set in the :guilabel:`Load template` field), and the "
":guilabel:`Recipients`, :guilabel:`Subject`, and email body are pre-"
"populated based on the email template."
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:94
msgid ""
"If any attachments need to be added, click the :icon:`fa-paperclip` "
":guilabel:`Attachments` button, and a file explorer window appears. Navigate"
" to the desired file, then click :guilabel:`Open` to attach it to the email."
" The attachment loads, and is listed above the :icon:`fa-paperclip` "
":guilabel:`Attachments` button."
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:99
msgid ""
"Once the email is ready to send, click :guilabel:`Send`. The email pop-up "
"window closes, and an :guilabel:`Offers` smart button appears at the top of "
"the applicant's card."
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:103
msgid ""
"To send an offer, ensure the *Sign* application is installed. This is "
"necessary, so the offer can be sent to the applicant by the recruiter, and "
"they can actually sign the offer. The applicant does **not** need any "
"software installed to sign the offer."
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst-1
msgid "Send an email to the applicant with a link to the offered salary."
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:112
msgid "Configure your package"
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:114
msgid ""
"If applicable, the applicant can modify their salary package. This option is"
" not available for all localizations. Depending on where the company is "
"located, this option may not be available."
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:117
msgid ""
"The email template includes a :guilabel:`Configure your package` button. "
"This link takes the applicant to a webpage, where they can modify the "
"proposed salary package, and enter their personal information."
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:121
msgid ""
"Once the applicant is hired, the personal information entered on the webpage"
" is imported to their employee record, when created."
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:124
msgid ""
"Once all the information is completed, the applicant can then accept the "
"offer by clicking the :guilabel:`Review Contract & Sign` button to accept "
"the contract, and sign it using the *Sign* application."
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:131
msgid "Contract signed"
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:133
msgid ""
"Once the applicant has accepted the offer and signed the contract, the next "
"step is to move the applicant to the :guilabel:`Contract Signed` stage. This"
" stage is folded in the Kanban view, by default."
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:137
msgid ""
"To move the applicant to that stage, drag-and-drop the applicant's card to "
"the :guilabel:`Contract Signed` stage. If the stage is not visible, click "
"the :icon:`fa-ellipsis-h` :guilabel:`(ellipsis)` button to the right of "
":guilabel:`Contract Proposal` on the applicant's form, and click "
":guilabel:`Contract Signed` from the resulting drop-down menu."
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:142
msgid ""
"Once the applicant is moved to the :guilabel:`Contract Signed` stage, a "
"green :guilabel:`HIRED` banner appears in the top-right of the applicant's "
"card and form."
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst-1
msgid "Hired banner in the top right corner of applicant card."
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:152
msgid "Create employee"
msgstr "צור עובד"

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:154
msgid ""
"Once the applicant has been hired, the next step is to create their employee"
" record. Click the :guilabel:`Create Employee` button in the top-left corner"
" of the hired applicant's form."
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:157
msgid ""
"An employee form appears, with information from the applicant's card, and "
"the employee contract."
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:159
msgid ""
"Fill out the rest of the employee form. For detailed information on the "
"fields, refer to the :doc:`../employees/new_employee` documentation."
msgstr ""

#: ../../content/applications/hr/recruitment/offer_job_positions.rst:162
msgid "Once completed, the employee record is saved in the *Employees* app."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:3
msgid "Recruitment flow"
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:5
msgid ""
"When a prospective employee applies for a job in Odoo, there is a "
"preconfigured process from the :ref:`initial inquiry <recruitment/new>` to "
"the :ref:`creating of a new employee <recruitment/new-employee>` once hired."
" The following outlines the default recruitment process for Odoo's "
"*Recruitment* application."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:11
msgid ""
"The following is based on Odoo's default recruitment pipeline. Be advised "
"that if :ref:`modifications are made <recruitment/customize-stages>` to the "
"pipeline, the process differs."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:20
msgid ""
"At the start of the process, all applicants appear in the :guilabel:`New` "
"stage on the :guilabel:`Applications` page, whether submitted online or if "
"the applicant is :doc:`manually entered by a recruiter <add-new-"
"applicants>`."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:24
msgid ""
"When the applicant's card is created, Odoo automatically populates the "
":guilabel:`Subject/Application`, the :guilabel:`Applicant's Name`, "
":guilabel:`Email`, and :guilabel:`Mobile` number, on the applicant's card. "
"This information is required when applying for a job position, by default."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:30
msgid ""
"If the website application form is modified, different fields may be "
"populated, based on what information is requested on the website."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:33
msgid ""
"If the applicant entered any information in the *Short Introduction* section"
" of the online application, it populates the :guilabel:`Application Summary`"
" tab at the bottom of the applicant's card."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:40
msgid ""
"If a resumé was attached to the online application, it appears in the "
":guilabel:`Files` section of the chatter, and is also stored in the "
"*Documents* application."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:43
msgid ""
"To find the recruitment documents, navigate to the main "
":menuselection:`Documents app` dashboard, and click the "
":guilabel:`Recruitment` folder on the left-hand side. All recruitment "
"documents are stored within that folder."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:47
msgid ""
"If the :ref:`CV Display <recruitment/cv-display>` option was enabled in the "
":ref:`Settings <recruitment/settings>` of the *Recruitment* app, the resumé "
"appears on the applicant's card, on the right-hand side."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:52
msgid ""
"Depending on the browser zoom level, or size of the browser screen, the "
"resumé may appear below the main applicant card information as a PDF link."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:56
msgid "Send interview"
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:58
msgid ""
"At any point in the hiring process, an interview can be sent to the "
"applicant to obtain more information. These interviews are custom-made, and "
"can be formatted in a variety of ways."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:61
msgid ""
"The *Surveys* application is **required** to send interviews to an "
"applicant, so it **must** be installed."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:64
msgid ""
"Odoo uses the term *interview*, but these can be thought of as "
"questionnaires, surveys, tests, certifications, etc. Custom interviews can "
"be formatted to suit each individual job position's needs. For more "
"information on creating and editing interviews, refer to the "
":doc:`../../hr/recruitment/new_job` documentation."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:70
msgid ""
"A job position for a computer programmer could have an interview in the form"
" of a programming quiz to determine the skill level of the applicant. A job "
"position for a restaurant server could have a questionnaire inquiring about "
"the applicant's availability, if the desired applicant needs to be available"
" on weekend evenings."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:75
msgid ""
"To send an interview to an applicant, first click the applicant's card from "
"the :guilabel:`Applications` page, to view the detailed applicant "
"information. At the top-left of the applicant's card, click the "
":guilabel:`Send Interview` button."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:79
msgid ""
"If the applicant's card has an email address on file, a :guilabel:`Send an "
"interview` pop-up window appears, with the :guilabel:`Recipients`, "
":guilabel:`Subject`, and email body populated."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:83
msgid ""
"To send an email to an applicant, there **must** be an :guilabel:`Email` "
"address on the applicant's card."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:86
msgid ""
"If an email address is not entered on the applicant's card, when the "
":guilabel:`Send Interview` button is clicked, an :guilabel:`Edit: "
"(Applicant's Name)` pop-up window appears, *on top of* the :guilabel:`Send "
"an interview` pop-up window."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:90
msgid ""
"Enter the email address in the :guilabel:`Email` field, then click "
":guilabel:`Save & Close`."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:92
msgid ""
"Once the applicant's information is saved, the :guilabel:`Edit: (Applicant's"
" Name)` pop-up window closes, and the :guilabel:`Send an interview` pop-up "
"window remains."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:95
msgid ""
"Sometimes, preconfigured email templates in Odoo use dynamic placeholders, "
"which are automatically filled with specific data when the email is sent. "
"For example, if a placeholder for the applicant's name is used, it is "
"replaced with the actual name of the applicant in the email. For more "
"detailed information on email templates, refer to the "
":doc:`../../general/companies/email_template` documentation."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:101
msgid ""
"Add the email addresses of any additional recipients for the survey in the "
":guilabel:`Additional emails` field, if more people should receive the "
"email. If an email address is in the database as a contact, add that contact"
" in the :guilabel:`Recipients` field. If an email should be sent to someone "
"who is not in the database as a contact, and they should **not** be added as"
" a contact, add their email address in the :guilabel:`Additional emails` "
"field."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:107
msgid ""
"If any attachments need to be added, click the :icon:`fa-paperclip` "
":guilabel:`Attachments` button, and a file explorer window appears. Navigate"
" to the desired file, and click :guilabel:`Open` to attach it to the email. "
"The attachment loads, and is listed above the :icon:`fa-paperclip` "
":guilabel:`Attachments` button."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:112
msgid ""
"If the emailed interview must be completed by a specific date, enter that "
"date in the :guilabel:`Answer deadline` field, located in the lower-right "
"area of the pop-up window."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:115
msgid ""
"To do so, click the empty field next to :guilabel:`Answer deadline`, and a "
"calendar selector appears. Use the :icon:`fa-chevron-left` "
":guilabel:`(left)` and :icon:`fa-chevron-right` :guilabel:`(right)` arrows, "
"on either side of the month, to navigate to the desired month. Then, click "
"on the desired day to select the date."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:120
msgid ""
"The :guilabel:`Mail Template` field is pre-populated, based on the "
"configuration for the interview. A different template can be chosen from the"
" drop-down menu, if desired. If a new template is selected, the new email "
"template loads in the email body."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:124
msgid ""
"To send the email with the interview link to the applicant, click "
":guilabel:`Send` at the bottom of the email pop-up window."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:135
msgid "Initial qualification"
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:137
msgid ""
"If an applicant seems to be a good potential candidate, they are moved to "
"the :guilabel:`Initial Qualification` stage."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:140
msgid ""
"This stage exists to quickly sort candidates that have potential, from those"
" that do not meet the requirements. No automatic actions, such as emails, "
"are set for this stage. This stage simply informs the recruitment team to "
"potentially set up a phone call or an interview with the candidate."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:145
msgid ""
"In order to move an applicant's card from one stage to another, the "
"applicant's card can either be dragged and dropped in the Kanban view of the"
" :guilabel:`Applications` page to the desired stage, or the stage can be "
"modified on the applicant's card."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:149
msgid ""
"To change the stage on the applicant's card, first click the desired "
"applicant's card from the :guilabel:`Applications` page. The current stage "
"for the card is highlighted at the top on a status bar, above the card."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:153
msgid ""
"Click the desired stage for the card, and the stage changes. A log note "
"indicating the stage change appears in the chatter, as well."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:0
msgid ""
"Change the stage of an applicant by clicking on the desired stage at the top of the\n"
"applicant's card."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:164
msgid "First interview"
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:166
msgid ""
"After an applicant has passed the :guilabel:`Initial Qualification` stage, "
"they can be manually moved to the :guilabel:`First Interview` stage on the "
":guilabel:`Applications` page, while in Kanban view."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:170
msgid ""
"To move the applicant to the next stage, drag-and-drop the applicant's card "
"to the :guilabel:`First Interview` stage."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:173
msgid ""
"Alternatively, open the desired applicant's card from the "
":guilabel:`Applications` page, and click the :guilabel:`First Interview` "
"stage on the status bar at the top of the individual applicant's card."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst-1
msgid ""
"An applicant's card moves from one stage to another by using the click and "
"drag method."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:182
msgid ""
"The :guilabel:`First Interview` stage can be modified, so when the "
"applicant's card moves to the :guilabel:`First Interview` stage, an email "
"can be automatically sent to the applicant, stating an interview is "
"requested. In this pre-configured email template, a link to the recruiting "
"team's calendar appears, allowing the applicant to schedule their interview."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:187
msgid ""
":ref:`Edit <recruitment/edit-stage>` the :guilabel:`First Interview` stage, "
"and select the :guilabel:`Recruitment: Schedule Interview` option in the "
":guilabel:`Email Template` field, to automate this action."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:194
msgid "Second interview"
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:196
msgid ""
"After an applicant has passed the :guilabel:`First Interview` stage, they "
"can be moved to the :guilabel:`Second Interview` stage. To move the "
"applicant to the next stage, drag-and-drop the applicant's card to the "
":guilabel:`Second Interview` stage from the Kanban view of the "
":guilabel:`Applications` page, or click on the :guilabel:`Second Interview` "
"stage at the top of the individual applicant's card."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:202
msgid ""
"When the applicant's card moves to the :guilabel:`Second Interview` stage, "
"there are no automatic activities or emails configured for this stage, by "
"default. The recruiter can now :ref:`schedule a second interview "
"<recruitment/schedule_interviews/recruitment-scheduled>` with the applicant,"
" following the same process as the first interview."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:210
msgid "Contract Proposal"
msgstr "הצעת חוזה"

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:212
msgid ""
"After the applicant has completed the various interview processes, the next "
"step is to :doc:`send the job offer <offer_job_positions>`."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:215
msgid ""
"Once the offer has been sent, drag-and-drop the applicant's card to the "
":guilabel:`Contract Proposal` stage from the Kanban view of the "
":guilabel:`Applications` page, or click on the :guilabel:`Contract Proposal`"
" stage at the top of the individual applicant's card."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:220
msgid "Contract Signed"
msgstr "חוזה חתום"

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:222
msgid ""
"Once the contract has been signed, and the applicant has been hired, the "
"applicant's card moves to the :guilabel:`Contract Signed` stage."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:225
msgid ""
"Drag-and-drop the applicant's card to the :guilabel:`Contract Signed` stage "
"from the Kanban view of the :guilabel:`Applications` page, or click the "
":icon:`fa-ellipsis-h` :guilabel:`(ellipsis)` icon at the top of the "
"individual applicant's card, then click :guilabel:`Contract Signed` on the "
"status bar."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:231
msgid "Refuse applicant"
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment-flow.rst:233
msgid ""
"At any point in the recruitment process, a candidate can be :doc:`refused "
"<refuse_applicant>`."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:3
msgid "Recruitment analysis"
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:5
msgid ""
"The *Recruitment Analysis* report allows recruiting departments to see which"
" job positions have the most applicants, which have the most referrals, and "
"how long it takes for applicants to move through the pipeline."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:9
msgid ""
"Knowing how many applicants each specific job position has, along with "
"statistics about how many are hired and refused, can provide valuable "
"insights. This information can assist the recruiting team to pivot their "
"strategies to acquire the most desirable candidates."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:14
msgid "Recruitment analysis report"
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:16
msgid ""
"Start by navigating to :menuselection:`Recruitment app --> Reporting --> "
"Recruitment Analysis`. This presents a line chart of all applicants for the "
"last year."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:19
msgid ""
"Three separate color-coded metrics are presented: :guilabel:`In Progress`, "
":guilabel:`Hired`, and :guilabel:`Refused`."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:22
msgid ""
"Hover the cursor over a month of the chart, and a pop-up window appears, "
"displaying the specific numbers for that month."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment_analysis.rst-1
msgid "The default Recruitment Analysis report."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:30
#: ../../content/applications/hr/recruitment/team_performance.rst:31
msgid "Pivot table view"
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:32
msgid ""
"For a more detailed view of the information in the :guilabel:`Recruitment "
"Analysis` report, click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` icon "
"in the top-right corner. This displays all the information in a pivot table."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:36
msgid ""
"In this view, the job positions are displayed in the rows, and the columns "
"display the total numbers of applicants, including how many of those "
"applicants were hired or refused. The displayed information can be modified,"
" if desired."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:40
msgid ""
"In this example, there are 17 total applicants. Out of that, three have been"
" hired, and four refused. The :guilabel:`Experienced Developer` position has"
" eight total applicants, two of which were hired, and two were refused."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment_analysis.rst-1
#: ../../content/applications/hr/recruitment/team_performance.rst-1
msgid "The detailed pivot table view."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:49
msgid "Use case: applicants with referrals"
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:51
msgid ""
"To get a better understanding of how effective the company's :doc:`referral "
"program <../referrals>` is, the :guilabel:`Recruitment Analysis` report can "
"be modified to show how many applicants were referred by current employees."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:55
msgid ""
"From the :icon:`oi-view-pivot` :guilabel:`(Pivot)` view of the "
":guilabel:`Recruitment Analysis` report, first click the "
":guilabel:`Measures` button to reveal a drop-down menu of options."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:58
msgid ""
"Click both :guilabel:`Has Referrer` and :guilabel:`Count`, to activate those"
" two measures. Then, click :guilabel:`# Applicant`, :guilabel:`# Hired`, and"
" :guilabel:`# Refused` to deactivate those default measures."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:62
msgid ""
"Now, the column displays the number of applicants that came from a referral "
"in the :guilabel:`Has Referrer` column, and the total number of applicants "
"in the :guilabel:`Count` column."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment_analysis.rst-1
msgid ""
"The detailed pivot table view displaying the number of referrals and the "
"total applicants."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:69
msgid ""
"In this example, the :guilabel:`Experienced Developer` job position has the "
"most applicants from referrals. Out of the eight applicants, six have "
"applied through a referral from a current employee. Meanwhile, the "
":guilabel:`Marketing and Community Manager` job position has the least "
"amount of referrals out of the total applicants, only one out of six."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:75
msgid "Hired through referrals"
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:77
msgid ""
"It is possible to modify this report even further to see how many referred "
"applicants end up being hired."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:80
msgid ""
"To view this data, click on a :icon:`fa-plus-square` :guilabel:`[job "
"position]` row, which reveals a drop-down menu. Then, click "
":guilabel:`State` to show the various states applicants are currently in."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:85
msgid ""
"Only states that have applicants in them are shown for each job position. If"
" a state does **not** have any applicants, it does not appear in the list."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:88
msgid ""
"To expand the other rows, and display the various states, click on the "
":icon:`fa-plus-square` :guilabel:`[job position]` button."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment_analysis.rst-1
msgid ""
"The detailed pivot table view displaying applicants hired through referrals."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:95
msgid ""
"In this example, the :guilabel:`Experienced Developer` job position is the "
"most successful in terms of referrals. Both of the hired employees came from"
" internal referrals. Meanwhile, there have been no hired employees for the "
":guilabel:`Chief Executive Officer` position, and the only hired employee "
"for the :guilabel:`Marketing and Community Manager` was not referred by an "
"employee."
msgstr ""

#: ../../content/applications/hr/recruitment/recruitment_analysis.rst:100
msgid ""
"In this scenario, it is possible to determine that the current software "
"developers are providing the most referrals, with the highest success rate."
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:3
msgid "Refuse applicants"
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:5
msgid ""
"At any point in the recruitment process, an applicant can be refused for a "
"job position."
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:7
msgid ""
"To refuse an applicant, start by navigating to the applicant's card in the "
"*Recruitment* app. This is done in one of two ways:"
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:10
msgid ""
"Navigate to :menuselection:`Recruitment app --> Applications --> All "
"Applications`. In the :guilabel:`Applications` list, click anywhere on the "
"desired applicant's line to open that specific applicant's card."
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:13
msgid ""
"Navigate to the main *ob Positions* dashboard by navigating to "
":menuselection:`Recruitment app --> Applications --> By Job Position`. Next,"
" click on the desired job position card, then click on the individual "
"applicant card from the :guilabel:`Applications` page."
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:17
msgid ""
"At the top of the applicant's card, there are several buttons. Click the one"
" labeled :guilabel:`Refuse`."
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:23
msgid "Refuse reasons"
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:25
msgid ""
"*Refuse reasons* allow recruiters to document why an applicant was not a "
"good fit, and send specific refusal reason email templates to the applicant."
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:28
msgid ""
"Clicking :guilabel:`Refuse` on an applicant's form makes the "
":guilabel:`Refuse Reason` pop-up window appear."
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:31
msgid ""
"The default refuse reasons in Odoo, and their corresponding email templates,"
" are:"
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:37
msgid "Email Template"
msgstr "תבנית דוא\"ל"

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:38
msgid "Refusal Reason"
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:39
msgid ":guilabel:`Recruitment: Refuse`"
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0
msgid ":guilabel:`Doesn't fit the job requirements`"
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0
msgid ":guilabel:`Language issues`"
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0
msgid ":guilabel:`Role already fulfilled`"
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0
msgid ":guilabel:`Duplicate`"
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0
msgid ":guilabel:`Spam`"
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:45
msgid ":guilabel:`Recruitment: Not interested anymore`"
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0
msgid ":guilabel:`Refused by Applicant: don't like job`"
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0
msgid ":guilabel:`Refused by Applicant: better offer`"
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0
msgid ":guilabel:`Refused by Applicant: salary`"
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:50
msgid ""
"Additional refusal reasons :ref:`can be created, and existing ones can be "
"modified (or deleted) <recruitment/new-refuse>`."
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:53
msgid ""
"Select a refusal reason to :ref:`send a refusal email <recruitment/send-"
"refusal-email>`."
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:58
msgid "Create or modify refuse reasons"
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:60
msgid ""
"To view and configure refuse reasons, navigate to "
":menuselection:`Recruitment app --> Configuration --> Applications: Refuse "
"Reasons`. Doing so reveals the :guilabel:`Refuse Reasons` page, where all "
"the existing refuse reasons are listed."
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:64
msgid ""
"To create a new refuse reason from the :guilabel:`Refuse Reasons` page, "
"click the :guilabel:`New` button in the top-left corner. A blank line "
"appears at the bottom of the list, with an empty field present in the "
":guilabel:`Description` column."
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:68
msgid ""
"Type in the new refuse reason in the field. It is recommended to enter a "
"reason that is short and concise, such as `Offer expired` or `Withdrew "
"application`."
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:71
msgid ""
"Then, in the :guilabel:`Email Template` field, click on the field to reveal "
"a drop-down menu. Select an :guilabel:`Email Template` from the list to be "
"used when this refuse reason is selected."
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:74
msgid ""
"If a new :guilabel:`Email Template` is desired, type in the name for the new"
" template in the field. Then, click :guilabel:`Create and edit...`, and a "
":guilabel:`Create Email Template` form pop-up window appears."
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:78
msgid ""
"In the :guilabel:`Create Email Template` pop-up window, enter a "
":guilabel:`Name` for the form, and an email :guilabel:`Subject` in the "
"corresponding fields."
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:81
msgid ""
"Enter the desired email content in the :guilabel:`Content` tab. Proceed to "
"make any other modifications to the template in the :guilabel:`Email "
"Configuration` and :guilabel:`Settings` tabs, then click :guilabel:`Save & "
"Close` to save the template. Upon clicking that, Odoo returns to the "
":guilabel:`Refuse Reasons` list."
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:86
msgid ""
"The new template appears in the new refuse reason :guilabel:`Email Template`"
" field."
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:89
msgid ""
"Pre-configured recruitment refusal email templates in Odoo use dynamic "
"placeholders, which are personalized placeholders that populate data from "
"the applicant's record in the email body."
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:92
msgid ""
"For example, if the applicant's name is a used in a dynamic placeholder, the"
" applicant's name appears anytime that dynamic placeholder appears on the "
"email template."
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:95
msgid ""
"For more detailed information on email templates, refer to the "
":doc:`../../general/companies/email_template` documentation."
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:101
msgid "Send refusal email"
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:103
msgid ""
"After clicking the :guilabel:`Refuse` button on an applicant form, a "
":ref:`Refuse Reason <recruitment/refuse-reasons>` can be selected from the "
":guilabel:`refuse reason` pop-up window. Then, two fields appear below the "
"selected refusal reason: :guilabel:`Send Email` and :guilabel:`Email "
"Template`."
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst-1
msgid ""
"The Refuse Reason pop-up window that appears when refusing an applicant."
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:112
msgid ""
"The applicant's email address automatically populates the :guilabel:`Send "
"Email` field; additional email recipients **cannot** be added."
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:115
msgid ""
"If an email should **not** be sent to the applicant, uncheck the "
":guilabel:`Send Email` checkbox."
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:117
msgid ""
"The email template associated with the refusal reason populates the "
":guilabel:`Email Template` field. If a different email template is desired, "
"select a different template from the :guilabel:`Email Template` drop-down "
"menu."
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:121
msgid ""
"To send the refusal email to the applicant, ensure the :guilabel:`Send "
"Email` checkbox is ticked, then click :guilabel:`Refuse` at the bottom of "
"the :guilabel:`Refuse Reason` pop-up window. The refusal email is sent to "
"the applicant, and a red :guilabel:`Refused` banner appears on the "
"applicant's card in the top-right corner."
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst-1
msgid ""
"An applicant's card with the refused banner appearing in the top-right "
"corner in red."
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:131
msgid "View refused applicants"
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:133
msgid ""
"After refusal, the applicant's card is no longer visible in the job "
"position's Kanban view. However, it is still possible to view applicants who"
" have been refused."
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:136
msgid ""
"To view only the refused applicants, go to :menuselection:`Recruitment app "
"--> Applications --> By Job Positions`, or :menuselection:`Recruitment app "
"--> Applications --> All Applications`."
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:139
msgid ""
"On the :guilabel:`Applications` page, click the :icon:`fa-caret-down` "
":guilabel:`(caret down)` button in the :guilabel:`Search...` bar, then click"
" :guilabel:`Refused`, located under the :guilabel:`Filters` section."
msgstr ""

#: ../../content/applications/hr/recruitment/refuse_applicant.rst:143
msgid ""
"All applicants that have been refused for the job position appear on the "
":guilabel:`Applications` page for that position, organized by the stage they"
" were in when they were refused."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:3
msgid "Schedule interviews"
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:5
msgid ""
"Schedule in-person, virtual, and phone interviews with Odoo through the "
"*Recruitment* app."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:7
msgid ""
"An interview can be scheduled in one of two ways: either by the "
":ref:`recruitment team <recruitment/schedule_interviews/recruitment-"
"scheduled>`, or by the :ref:`applicant "
"<recruitment/schedule_interviews/applicant-scheduled>`."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:14
msgid "Recruitment team scheduled interviews"
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:16
msgid ""
"When an applicant reaches the interview stage, the recruitment team should "
"schedule the interview, by first coordinating a suitable date and time with "
"the applicant and interviewers."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:19
msgid ""
"To schedule the interview, navigate to the applicant's card, by first going "
"to the :menuselection:`Recruitment app`, and clicking the relevant job card."
" This opens the :guilabel:`Applications` page for that job position. Then, "
"click the desired applicant's card to view their detailed applicant form."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:24
msgid ""
"To schedule an phone, virtual, or in-person interview, click the "
":guilabel:`No Meeting` smart button at the top of the applicant's record."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:28
msgid ""
"The *Meetings* smart button displays :guilabel:`No Meeting` if no meetings "
"are currently scheduled. For applicants who are new to the :guilabel:`First "
"Interview` stage, this is the default."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:32
msgid ""
"If there is one meeting already scheduled, the smart button displays *1 "
"Meeting*, with the date of the upcoming meeting beneath it. If more than one"
" meeting is scheduled, the button displays *Next Meeting*, with the date of "
"the first upcoming meeting beneath it."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:36
msgid ""
"Clicking the *Meetings* smart button loads a calendar, showing the scheduled"
" meetings and events for the currently signed-in user, as well as the "
"employees who are listed under the :guilabel:`Attendees` section, located to"
" the right of the calendar."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:40
msgid ""
"To change the currently loaded meetings and events being displayed, uncheck "
"an attendee whose calendar events are to be hidden. Only the checked "
"attendees are visible on the calendar."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst-1
msgid "The calendar view, highlighting how to change the displayed meetings."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:47
msgid ""
"To add a meeting to the calendar when in the *Day* or *Week* view, click on "
"the start time of the meeting and drag down to the end time. Doing so "
"selects the date, time, and the length of the meeting."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:51
msgid ""
"A meeting can also be added in this view by clicking on the desired day "
"*and* time slot."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:53
msgid ""
"Both methods cause a :ref:`New Event <recruitment/schedule_interviews/event-"
"card>` pop-up window to appear."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:59
msgid "New event pop-up window"
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:61
msgid ""
"Clicking a grid, corresponding with the time and date, opens the "
":guilabel:`New Event` pop-up window to schedule a meeting."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:64
msgid ""
"Enter the information on the form. The only required fields to enter are a "
"title for the meeting, along with the :guilabel:`Start` (and end date/time) "
"fields."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:67
msgid ""
"Once the card details are entered, click :guilabel:`Save & Close` to save "
"the changes and create the interview."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:70
msgid ""
"After entering in a required name for the meeting, the fields available to "
"modify on the :guilabel:`New Event` card are as follows:"
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:73
msgid ""
":guilabel:`Meeting Title`: enter the subject for the meeting. This should "
"clearly indicate the purpose of the meeting. The default subject is the "
":guilabel:`Subject/Application Name` on the applicant's card."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:76
msgid ""
":guilabel:`Start`: start and end date and times for the meeting. Clicking "
"either of these fields opens a calendar pop-up window. Click "
":guilabel:`Apply` to close the window."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:78
msgid ""
":guilabel:`All Day`: tick the box to schedule an all-day interview. If this "
"box is ticked, the :guilabel:`Start` field changes to :guilabel:`Start "
"Date`."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:80
msgid ""
":guilabel:`Attendees`: select the people who should attend the meeting. The "
"default employee listed is the person who created the meeting. Add as many "
"other people as desired."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:82
msgid ""
":guilabel:`Videocall URL`: if the meeting is virtual, or if there is a "
"virtual option available, click :icon:`fa-plus` :guilabel:`Odoo meeting`, "
"and a URL is automatically created for the meeting, which populates the "
"field."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:85
msgid ""
":guilabel:`Description`: enter a brief description in this field. There is "
"an option to enter formatted text, such as numbered lists, headings, tables,"
" links, photos, and more. Use the powerbox feature, by typing a `/` to "
"reveal a list of options."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:89
msgid ""
"Scroll through the options and click on the desired item. The item appears "
"in the field, and can be modified. Each command presents a different pop-up "
"window. Follow the instructions for each command to complete the entry."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:94
msgid "More options"
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:96
msgid ""
"To add additional information to the meeting, click the :guilabel:`More "
"Options` button in the lower-right corner of the :ref:`New Event "
"<recruitment/schedule_interviews/event-card>` pop-up window. Enter any of "
"the following additional fields:"
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:100
msgid ""
":guilabel:`Duration`: this field auto populates based on the "
":guilabel:`Start` (and end) date and time. If the meeting time is adjusted, "
"this field automatically adjusts to the correct duration length. The default"
" length of a meeting is one hour."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:103
msgid ""
":guilabel:`Recurrent`: if the meeting should repeat at a selected interval "
"(not typical for a first interview), tick the checkbox next to "
":guilabel:`Recurrent`. Several additional fields appear when this is "
"enabled:"
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:107
msgid ""
":guilabel:`Timezone`: using the drop-down menu, select the "
":guilabel:`Timezone` for the recurrent meetings."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:109
msgid ""
":guilabel:`Repeat`: choose :guilabel:`Daily`, :guilabel:`Weekly`, "
":guilabel:`Monthly`, :guilabel:`Yearly`, or :guilabel:`Custom` recurring "
"meetings. If :guilabel:`Custom` is selected, a :guilabel:`Repeat Every` "
"field appears beneath it, along with another time frequency parameter "
"(:guilabel:`Days`, :guilabel:`Weeks`, :guilabel:`Months`, or "
":guilabel:`Years`). Enter a number in the blank field, then select the time "
"period using the drop-down menu."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:114
msgid ""
":guilabel:`Repeat on`: enabled when the :guilabel:`Weekly` option is "
"selected in the :guilabel:`Repeat` field. Choose the day the weekly meeting "
"falls on."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:116
msgid ""
":guilabel:`Day of Month`: configure the two drop-down menu options to select"
" a specific day of the month, irrespective of the date (e.g. the first "
"Tuesday of every month). To set a specific calendar date, choose "
":guilabel:`Date of Month` and enter the calendar date in the field (e.g. "
"`15` to set the meeting to occur on the fifteenth of every month)."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:120
msgid ""
":guilabel:`Until`: using the drop-down menu, select when the meetings stop "
"repeating. The available options are :guilabel:`Number of repetitions`, "
":guilabel:`End date`, and :guilabel:`Forever`. If :guilabel:`Number of "
"repetitions` is selected, enter the number of total meetings to occur in the"
" blank field to the right. If :guilabel:`End date` is selected, specify the "
"date using the calendar pop-up window, or type in a date in a XX/XX/XXXX "
"format. :guilabel:`Forever` schedules meetings indefinitely."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:127
msgid ":guilabel:`Location`: enter the location for the meeting."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:128
msgid ""
":guilabel:`Tags`: select any tags for the meeting using the drop-down menu, "
"or add a new tag by typing in the tag and clicking :guilabel:`Create "
"\"tag\"`. There is no limit to the number of tags that can be used."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:131
msgid ""
":guilabel:`Appointment`: if an appointment is associated with this meeting, "
"select it from the drop-down menu, or create a new appointment by typing in "
"the appointment name, then clicking :guilabel:`Create & Edit...` from the "
"resulting drop-down men. A :guilabel:`Create Appointment` form loads. Enter "
"the information on the form, then click :guilabel:`Save & Close`."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:135
msgid ""
":guilabel:`Privacy`: select if the organizer appears either "
":guilabel:`Available` or :guilabel:`Busy` for the duration of the meeting. "
"Next, select the visibility of this meeting, using the drop-down menu to the"
" right of the first selection. Options are :guilabel:`Public`, "
":guilabel:`Private`, and :guilabel:`Only internal users`. :guilabel:`Public`"
" allows for everyone to see the meeting, :guilabel:`Private` allows only the"
" attendees listed on the meeting to see the meeting, and :guilabel:`Only "
"internal users` allows anyone logged into the company database to see the "
"meeting."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:142
msgid ""
":guilabel:`Organizer`: the employee who created the meeting is populated in "
"this field. Use the drop-down menu to change the selected employee."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:144
msgid ""
":guilabel:`Reminders`: select a reminder from the drop-down menu. Default "
"options include :guilabel:`Notification`, :guilabel:`Email`, and "
":guilabel:`SMS Text Message`, each with a specific time period before the "
"event (hours, days, etc). The chosen reminder chosen alerts the meeting "
"participants of the meeting, via the selected option at the specified time. "
"Multiple reminders can be selected in this field."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst-1
msgid "A new meeting card with all the details populated, and ready to save."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:155
msgid "Send meeting to attendees"
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:157
msgid ""
"Once changes have been entered on the :ref:`New Event "
"<recruitment/schedule_interviews/event-card>` pop-up window, and the meeting"
" details are correct, the meeting can be sent to the attendees, via email or"
" text message, from the expanded event form (what is seen when the "
":guilabel:`More Options` button is clicked on in the :guilabel:`New Event` "
"pop-up window)."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:162
msgid ""
"To send the meeting via email, click the :icon:`fa-envelope` "
":guilabel:`Email` button next to the :guilabel:`Attendees` field on the "
"expanded meeting form."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:165
msgid ""
"A :guilabel:`Contact Attendees` email configurator pop-up window appears. A "
"pre-formatted email, using the default :guilabel:`Calendar: Event Update` "
"email template, populates the email body field."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:168
msgid ""
"The followers of the job application, as well as the user who created the "
"meeting, are added as :guilabel:`Recipients` by default. If needed, add the "
"applicant's email address to the list to send the email to the applicant, as"
" well. Make any other desired changes to the email. If an attachment is "
"needed, click the :guilabel:`Attachments` button, navigate to the file, then"
" click :guilabel:`Open`. Once the email is ready to be sent, click "
":guilabel:`Send`."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst-1
msgid "Enter the information to send the event via email."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:178
msgid ""
"To send the meeting via text message, click the :icon:`fa-mobile` "
":guilabel:`SMS` button next to the :guilabel:`Attendees` field on the "
"expanded meeting form. A :guilabel:`Send SMS Text Message` pop-up window "
"appears."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:182
msgid ""
"At the top, a blue banner appears if any attendees do not have valid mobile "
"numbers, and lists how many records are invalid. If a contact does not have "
"a valid mobile number listed, click :guilabel:`Close`, and edit the "
"attendee's record, then redo these steps."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:186
msgid ""
"When no warning message appears, type in the message to be sent to the "
"attendees in the :guilabel:`Message` field. To add any emojis to the "
"message, click the :icon:`oi-smile-add` :guilabel:`(smile add)` icon on the "
"right-side of the pop-up window."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:190
msgid ""
"The number of characters, and amount of text messages required to send the "
"message (according to GSM7 criteria) appears beneath the :guilabel:`Message`"
" field. Click :guilabel:`Put In Queue` to have the text sent later, after "
"any other messages are scheduled, or click :guilabel:`Send Now` to send the "
"message immediately."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst-1
msgid "Send a text message to the attendees of the meeting."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:200
msgid ""
"Sending text messages is **not** a default capability with Odoo. To send "
"text messages, credits are required, which need to be purchased. For more "
"information on IAP credits and plans, refer to the "
":doc:`../../essentials/in_app_purchase` documentation."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:207
msgid "Applicant scheduled interviews"
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:209
msgid ""
"By default, the recruitment interview stages are **not** set up for "
"applicants to schedule their own interviews."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:212
msgid ""
"However, if the :guilabel:`First Interview` or :guilabel:`Second Interview` "
"stages are modified to send the :guilabel:`Recruitment: Schedule Interview` "
"email template when an applicant reaches that stage, the applicant receives "
"a link to the recruitment team's calendar, and can schedule the interview on"
" their own. The recruitment team's availability is reflected in the "
"calendar."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:217
msgid ""
"In order for applicants to be able to schedule their own interviews, a "
":ref:`stage must first be modified <recruitment/schedule_interviews/modify-"
"stage>` in the *Recruitment* app."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:225
msgid ""
"To modify either the :guilabel:`First Interview` or :guilabel:`Second "
"Interview` stage, first navigate to the main :menuselection:`Recruitment` "
"app dashboard. Next, click on the desired job card to navigate to the "
":guilabel:`Applications` page for that job position."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:229
msgid ""
"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 name. Click the "
":icon:`fa-cog` :guilabel:`(gear)` icon, and a drop-down menu appears. Then, "
"click on the :guilabel:`Edit` option, and an :guilabel:`Edit: (Stage)` form "
"appears."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst-1
msgid "The drop-down that appears after clicking the cog."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:238
msgid ""
"The :guilabel:`Email Template` field is blank, by default. Using the drop-"
"down menu, select :guilabel:`Recruitment: Schedule interview` for the "
":guilabel:`Email Template` field, then click :guilabel:`Save & Close` when "
"done."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst-1
msgid ""
"The Recruitment: Schedule Interview email template populating the Email "
"Template field."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:247
msgid "Send email"
msgstr "שלח דוא\"ל"

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:249
msgid ""
"After either the :guilabel:`First Interview` or :guilabel:`Second Interview`"
" stages are :ref:`modified to send the "
"<recruitment/schedule_interviews/modify-stage>` :guilabel:`Recruitment: "
"Schedule interview` email to the applicant upon moving their applicant card "
"to one of those stages, the following email is received by the applicant:"
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:254
msgid ""
"`Subject: Can we plan an interview together for your (Job Position) "
"application?`"
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:256
msgid ""
"`Congratulations! Your application is really interesting and we'd like to "
"plan an interview with you. Can you please use the button below to schedule "
"it with one of our recruiters?`"
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:260
msgid "`Plan my interview`"
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:263
msgid "Schedule interview"
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:265
msgid ""
"When the applicant received the email, they click the :guilabel:`Plan my "
"interview` button at the bottom of the email. This navigates the applicant "
"to a private online scheduling page, which is **only** accessible through "
"the emailed link."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:269
msgid ""
"This page displays the :guilabel:`MEETING DETAILS` on the right side of the "
"screen. This includes the format and length of the meeting. In this example."
" the interview is virtual (:icon:`fa-video-camera` :guilabel:`Online`) and "
"the duration is a half hour (:icon:`fa-clock-o` :guilabel:`30 minutes`)."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:274
msgid ""
"First, if there is an option of who to meet with, the user selects who they "
"are scheduling their meeting with, by clicking on their icon and name. If "
"only one person is available to interview the applicant, this step is not "
"available. If the applicant does not wish to chose an interviewer, they can "
"just click :guilabel:`See all availabilities` :icon:`fa-arrow-right`."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst-1
msgid ""
"The first screen seen after clicking 'Plan my interview', where the applicant selects their\n"
"interviewer."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:285
msgid ""
"If the applicant selects an interviewer, the applicant is shown a "
":guilabel:`Select a date & time` page, and **only** sees the dates and times"
" that specific person is available. In addition, that interviewer's "
"information (name, email, and phone number) appears on the right-side of the"
" screen, under the heading :guilabel:`OPERATOR`, located beneath the "
":guilabel:`MEETING DETAILS`."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:290
msgid ""
"If the applicant clicks :guilabel:`See all availabilities` :icon:`fa-arrow-"
"right` instead, or if there are no interviewer options available, the user "
"is navigated to the same :guilabel:`Select a date & time` page, but there is"
" no :guilabel:`OPERATOR` section visible."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:294
msgid ""
"Then the applicant clicks on an available day on the calendar, signified by "
"a square around the date. Once a day is selected, they click on one of the "
"available times to select that date and time."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst-1
msgid "The calendar screen with dates and times to schedule an interview."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:302
msgid ""
"Be sure to check the :guilabel:`Timezone` field, beneath the calendar, to "
"ensure it is set to the correct time zone. Changing the time zone may alter "
"the available times presented."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:305
msgid ""
"Once the date and time are selected, the applicant is navigated to an "
":guilabel:`Add more details about you` page. This page asks the applicant to"
" enter their :guilabel:`Full name`, :guilabel:`Email`, and :guilabel:`Phone "
"number`. The contact information entered on this form is how the applicant "
"is contacted to remind them about the scheduled interview."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:310
msgid ""
"When everything is entered on the :guilabel:`Add more details about you` "
"page, the applicant clicks the :guilabel:`Confirm Appointment` button, and "
"the interview is scheduled."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst-1
msgid ""
"The confirmation page with all the details for the interview displayed."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:317
msgid ""
"After confirming the interview, the applicant is taken to a confirmation "
"page, where all the details of the interview are displayed. The option to "
"add the meeting to the applicant's personal calendars is available, through "
"the :guilabel:`Add to iCal/Outlook` and :guilabel:`Add to Google Agenda` "
"buttons, beneath the interview details."
msgstr ""

#: ../../content/applications/hr/recruitment/schedule_interviews.rst:322
msgid ""
"The applicant is also able to cancel or reschedule the interview, if "
"necessary, with the :guilabel:`Cancel/Reschedule` button."
msgstr ""

#: ../../content/applications/hr/recruitment/source_analysis.rst:3
msgid "Source analysis reporting"
msgstr ""

#: ../../content/applications/hr/recruitment/source_analysis.rst:5
msgid ""
"Reporting is a critical tool used by recruiting departments to gain insights"
" into the entire recruitment process."
msgstr ""

#: ../../content/applications/hr/recruitment/source_analysis.rst:8
msgid ""
"Determining where applicants come from can provide information about which "
"sources have the best results. This information is determined by the *Source"
" Analysis* report. With this data, recruitment teams can better pivot their "
"recruiting strategies to gain better applicants, in both quantity and "
"quality."
msgstr ""

#: ../../content/applications/hr/recruitment/source_analysis.rst:14
#: ../../content/applications/hr/recruitment/team_performance.rst:12
msgid "Open report"
msgstr ""

#: ../../content/applications/hr/recruitment/source_analysis.rst:16
msgid ""
"To access the *Source Analysis* report, navigate to "
":menuselection:`Recruitment app --> Reporting --> Source Analysis`."
msgstr ""

#: ../../content/applications/hr/recruitment/source_analysis.rst:19
msgid ""
"This presents the data for the :icon:`fa-filter` :guilabel:`Last 365 Days "
"Applicant`, in a default :icon:`fa-area-chart` :guilabel:`(Graph)` view, "
"showing the amount of applicants by :guilabel:`Source`, and further "
"separated by stage (:guilabel:`In Progress` and :guilabel:`Hired`)"
msgstr ""

#: ../../content/applications/hr/recruitment/source_analysis.rst:23
msgid ""
"Hover the cursor over any column to view the specific numbers fort that "
"column."
msgstr ""

#: ../../content/applications/hr/recruitment/source_analysis.rst-1
msgid "The default bar chart of the source analysis information."
msgstr ""

#: ../../content/applications/hr/recruitment/source_analysis.rst:29
msgid ""
"To view more details, view the :guilabel:`Source Analysis` report in a pivot"
" table. To do so, click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` icon "
"in the top-right corner. The data is presented in a pivot table, with rows "
"populated by job positions, and columns populated stages."
msgstr ""

#: ../../content/applications/hr/recruitment/source_analysis.rst:34
msgid "Source effectiveness report"
msgstr ""

#: ../../content/applications/hr/recruitment/source_analysis.rst:36
msgid ""
"To identify which sources (e.g., job boards, social media, employee "
"referrals, company website) produce the most hires, the pivot table view of "
"the :guilabel:`Source Analysis` report can be configured to display further "
"details."
msgstr ""

#: ../../content/applications/hr/recruitment/source_analysis.rst:40
msgid ""
"To expand this chart to show what specific sources the applicants came from,"
" click the :icon:`fa-plus-square` :guilabel:`Total` box above the columns, "
"to reveal a drop-down menu, and click :guilabel:`Source`."
msgstr ""

#: ../../content/applications/hr/recruitment/source_analysis.rst:44
msgid ""
"Each column is then grouped by the source, such as: :guilabel:`Search "
"engine`, :guilabel:`Facebook`, :guilabel:`Newsletter`, etc. Each source "
"displays a separate count for :guilabel:`Applicant`, :guilabel:`Hired`, and "
":guilabel:`Refused`."
msgstr ""

#: ../../content/applications/hr/recruitment/source_analysis.rst:48
msgid ""
"This information, as presented, makes it difficult to view the specific "
"numbers for each source. Click the :icon:`fa-exchange` :guilabel:`(Flip "
"axis)` icon, to swap the information. After that, the rows represent the "
"source, and the columns represent the job positions, further divided by "
"stage."
msgstr ""

#: ../../content/applications/hr/recruitment/source_analysis.rst-1
msgid "The axes flipped in the source analysis report, in pivot table view."
msgstr ""

#: ../../content/applications/hr/recruitment/source_analysis.rst:56
msgid ""
"In this view, the total number of applicants, hired employees, and refused "
"applicants, are displayed for each source, as well as for each stage by job "
"position."
msgstr ""

#: ../../content/applications/hr/recruitment/source_analysis.rst:60
msgid "Medium"
msgstr "אמצעי תקשורת"

#: ../../content/applications/hr/recruitment/source_analysis.rst:62
msgid ""
"Viewing the medium for the applicants can be beneficial to see which "
"specific medium is more successful."
msgstr ""

#: ../../content/applications/hr/recruitment/source_analysis.rst:65
msgid ""
"*Mediums* are the specific methods the applicant used to discover and then "
"apply for job positions, such as organic search, paid search, social media "
"ad, email, etc."
msgstr ""

#: ../../content/applications/hr/recruitment/source_analysis.rst:68
msgid ""
"To further group the results by medium, click into one of the :icon:`fa-"
"plus-square` :guilabel:`[Source]` rows. Click :guilabel:`Medium` in the "
"resulting drop-down menu. The row presents the specific mediums, relevant to"
" that specific source."
msgstr ""

#: ../../content/applications/hr/recruitment/source_analysis.rst:72
msgid ""
"Once :guilabel:`Medium` is selected for one source, clicking into another "
"row automatically reveals the specific metrics for the mediums for that "
"source."
msgstr ""

#: ../../content/applications/hr/recruitment/source_analysis.rst-1
msgid "The sources rows, expanded to also show the medium for each source."
msgstr ""

#: ../../content/applications/hr/recruitment/source_analysis.rst:80
msgid ""
"The only mediums that appear for a source, are mediums that have been set on"
" an applicant's form. If a medium has **not** been set for any applicants, "
"the medium does not appear in the drop-down rows beneath the source."
msgstr ""

#: ../../content/applications/hr/recruitment/source_analysis.rst:84
msgid ""
"For example, if no applicants applied with the medium *Google Adwords*, that"
" medium does **not** appear beneath the *Search engine* source row."
msgstr ""

#: ../../content/applications/hr/recruitment/team_performance.rst:3
msgid "Team performance reporting"
msgstr ""

#: ../../content/applications/hr/recruitment/team_performance.rst:5
msgid ""
"The *Team Performance* report in the **Recruitment** app shows how many "
"applicants each recruiter is managing."
msgstr ""

#: ../../content/applications/hr/recruitment/team_performance.rst:8
msgid ""
"This information is determined by the individuals populating the "
":ref:`Recruiter <recruitment/applicant-details>` field on each applicant "
"form."
msgstr ""

#: ../../content/applications/hr/recruitment/team_performance.rst:14
msgid ""
"To access the *Team Performance* report, navigate to "
":menuselection:`Recruitment app --> Reporting --> Team Performance`."
msgstr ""

#: ../../content/applications/hr/recruitment/team_performance.rst:17
msgid ""
"The number of :guilabel:`In Progress`, :guilabel:`Hired`, and "
":guilabel:`Refused` applicants for each recruiter is displayed in the "
":icon:`fa-area-chart` :guilabel:`(Graph)` view."
msgstr ""

#: ../../content/applications/hr/recruitment/team_performance.rst:20
msgid ""
"The information shown is for the :icon:`fa-filter` :guilabel:`Last 365 Days "
"Applicant` default filter, as displayed in the search bar."
msgstr ""

#: ../../content/applications/hr/recruitment/team_performance.rst:23
msgid ""
"Hover the cursor over any column to view a popover window, displaying the "
"specific details for that column."
msgstr ""

#: ../../content/applications/hr/recruitment/team_performance.rst-1
msgid "The default bar chart of the team performance report."
msgstr ""

#: ../../content/applications/hr/recruitment/team_performance.rst:33
msgid ""
"For a more detailed view of the information in the :guilabel:`Team "
"Performance` report, click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` "
"icon in the top-right corner. This displays all the information in a pivot "
"table."
msgstr ""

#: ../../content/applications/hr/recruitment/team_performance.rst:37
msgid ""
"In this view, the job positions are displayed in the rows, while the columns"
" display the total number of applicants. The applicants are further "
"organized by :guilabel:`# Applicant` (in process), :guilabel:`# Hired`, and "
":guilabel:`# Refused`."
msgstr ""

#: ../../content/applications/hr/recruitment/team_performance.rst:41
msgid "The displayed information can be modified, if desired."
msgstr ""

#: ../../content/applications/hr/recruitment/team_performance.rst:43
msgid ""
"In this example, there are 19 total applicants. Out of those 19, eight have "
"been hired, and three refused."
msgstr ""

#: ../../content/applications/hr/recruitment/team_performance.rst:46
msgid ""
"From the data presented, the :guilabel:`Experienced Developer` job position "
"is the most successful. This job position has the highest number of total "
"applicants, as well as the most hires. In addition, the "
":guilabel:`Experienced Developer` has the least amount of refused "
"applicants."
msgstr ""

#: ../../content/applications/hr/recruitment/team_performance.rst:50
msgid ""
"This pivot table also shows that the :guilabel:`Chief Executive Officer` "
"position is the hardest to fill, as it has the fewest total applicants."
msgstr ""

#: ../../content/applications/hr/recruitment/team_performance.rst:58
msgid "Use case: recruiter performance over time"
msgstr ""

#: ../../content/applications/hr/recruitment/team_performance.rst:60
msgid ""
"One way to modify this report is to show how recruiters are performing over "
"time. To show this information, begin with the :guilabel:`Team Performance` "
"report in the :icon:`oi-view-pivot` :guilabel:`(Pivot)` view."
msgstr ""

#: ../../content/applications/hr/recruitment/team_performance.rst:64
msgid ""
"Next, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` in the search"
" bar, revealing a drop-down menu. Click :guilabel:`Add Custom Group` "
":icon:`oi-caret-down` at the bottom of the :icon:`oi-group` :guilabel:`Group"
" By` column, then click :guilabel:`Recruiter`. Click away from the drop-down"
" menu to close it. Now, each row on the table represents a recruiter."
msgstr ""

#: ../../content/applications/hr/recruitment/team_performance.rst-1
msgid "The pivot table now displaying the recruiters in the rows."
msgstr ""

#: ../../content/applications/hr/recruitment/team_performance.rst:73
msgid ""
"To compare the team's performance over different time periods, click the "
":icon:`fa-caret-down` :guilabel:`(down arrow)` in the search bar. Click "
":guilabel:`Start Date` :icon:`fa-caret-down` in the :icon:`fa-filter` "
":guilabel:`Filters` column, revealing various time periods to select."
msgstr ""

#: ../../content/applications/hr/recruitment/team_performance.rst:77
msgid ""
"In this example, the desired data is the comparison between the team's "
"performance in the third quarter (June - August) and the second quarter "
"(April - July). To do so, click :guilabel:`Q3`. Once clicked, the current "
"year is also ticked. In this example, it is :guilabel:`2024`."
msgstr ""

#: ../../content/applications/hr/recruitment/team_performance.rst:81
msgid ""
"After making this selection, a :icon:`fa-adjust` :guilabel:`Comparison` "
"column appears. Click :guilabel:`Start Date: Previous Period` to compare the"
" third quarter with the second quarter, for the various recruiters."
msgstr ""

#: ../../content/applications/hr/recruitment/team_performance.rst-1
msgid "A comparison table of recruiter totals of Q2 and Q3."
msgstr ""

#: ../../content/applications/hr/recruitment/team_performance.rst:89
msgid ""
"From this report, several things can be extrapolated: the total number of "
"applicants increased, the number of hired applicants remained the same, "
"while the number of refused applicants decreased."
msgstr ""

#: ../../content/applications/hr/recruitment/team_performance.rst:92
msgid ""
"Additionally, :guilabel:`Jane Jobs` had the highest increase in number of "
"applicants during the third quarter, but her number of hired applicants went"
" down :guilabel:`67%`. The recruiter with the best overall numbers was "
":guilabel:`Rose Recruiter`, who had both their active applicants and hired "
"applicants, increase in the third quarter, while their refused applicants "
"went down."
msgstr ""

#: ../../content/applications/hr/recruitment/time_in_stage.rst:3
msgid "Time in stage analysis"
msgstr ""

#: ../../content/applications/hr/recruitment/time_in_stage.rst:5
msgid ""
"The *Time In Stage Analysis* report provides information on how long "
"applicants stay in each stage of the recruitment process. This is important,"
" as every job position has specific :ref:`process details "
"<recruitment/new_job_position/edit>` that state the length of time "
"applicants should expect to wait between specific stages."
msgstr ""

#: ../../content/applications/hr/recruitment/time_in_stage.rst:10
msgid ""
"Knowing how long applicants remain in each stage can help highlight possible"
" bottlenecks. Analyzing this data allows the recruitment team to assess each"
" stage, identify any issues, and pivot their strategies to move applicants "
"through each stage, within the expected time interval."
msgstr ""

#: ../../content/applications/hr/recruitment/time_in_stage.rst:15
msgid "Time in stage analysis report"
msgstr ""

#: ../../content/applications/hr/recruitment/time_in_stage.rst:17
msgid ""
"To access the report, navigate to :menuselection:`Recruitment app --> "
"Reporting --> Time in Stage Analysis`. By default, the report displays data "
"from all job positions, with the stages populating the x-axis, and the "
"number of days populating the y-axis, in a :icon:`fa-line-chart` "
":guilabel:`(Line Chart)`."
msgstr ""

#: ../../content/applications/hr/recruitment/time_in_stage.rst:22
msgid ""
"The default filter is :guilabel:`Last 365 Days Applicant`, showing "
"information for the last 365 days."
msgstr ""

#: ../../content/applications/hr/recruitment/time_in_stage.rst:25
msgid ""
"Hover over a stage in the line chart to reveal a popover window listing all "
"the job positions within it, and the average number of days each job "
"position sits in each stage."
msgstr ""

#: ../../content/applications/hr/recruitment/time_in_stage.rst:28
msgid ""
"For a more visually digestible view of the information in the "
":guilabel:`Time In Stage Analysis` report, click the :icon:`fa-bar-chart` "
":guilabel:`(Bar Chart)` icon in the upper-left corner. This displays all the"
" information in a bar chart."
msgstr ""

#: ../../content/applications/hr/recruitment/time_in_stage.rst:32
msgid ""
"In this view, it is easier to visualize the differences between the job "
"positions, regarding how long applicants stay in each stage. From this view,"
" recruiters can more easily determine which job positions have delays or "
"bottlenecks at certain stages."
msgstr ""

#: ../../content/applications/hr/recruitment/time_in_stage.rst-1
msgid "The bar chart view of the Time In Stage Analysis report."
msgstr ""

#: ../../content/applications/hr/recruitment/time_in_stage.rst:41
msgid "Use case: comparing times by month"
msgstr ""

#: ../../content/applications/hr/recruitment/time_in_stage.rst:43
msgid ""
"With the :guilabel:`Time In Stage Analysis` report, it is possible to see if"
" there are certain months where applicants take longer to be moved through "
"the pipeline. To view this data, switch to the :icon:`oi-view-pivot` "
":guilabel:`(Pivot)` view in the upper-right corner."
msgstr ""

#: ../../content/applications/hr/recruitment/time_in_stage.rst:47
msgid ""
"This presents the data in a detailed pivot table, with the rows representing"
" the different job positions, and the columns representing the stages. The "
"average :guilabel:`Days in Stage` populates the various boxes."
msgstr ""

#: ../../content/applications/hr/recruitment/time_in_stage.rst:52
msgid ""
"If a field is empty, it indicates no applicant has been in that stage. "
"Instead, all applicants moved from a previous stage without being placed in "
"the stage with an empty field."
msgstr ""

#: ../../content/applications/hr/recruitment/time_in_stage.rst-1
msgid "The pivot table view of the Time In Stage Analysis report."
msgstr ""

#: ../../content/applications/hr/recruitment/time_in_stage.rst:59
msgid ""
"Click :icon:`fa-minus-square-o` :guilabel:`Total` above the job position "
"rows to collapse the information. Next, click :icon:`fa-plus-square` "
":guilabel:`Total` again, revealing a drop-down menu. Click :guilabel:`Add "
"Custom Group` :icon:`fa-caret-down` at the bottom of the list, revealing "
"further grouping options. Click :guilabel:`Start Date` from the expanded "
"list."
msgstr ""

#: ../../content/applications/hr/recruitment/time_in_stage.rst:64
msgid ""
"After doing so, the data presented is grouped with the various months from "
"the previous 365 days for the rows, leaving the :guilabel:`Days In Stage` as"
" the columns."
msgstr ""

#: ../../content/applications/hr/recruitment/time_in_stage.rst-1
msgid "The pivot table showing the months averages for times in stage."
msgstr ""

#: ../../content/applications/hr/recruitment/time_in_stage.rst:71
msgid ""
"In this example, :guilabel:`July 2024` had the longest time that applicants "
"spent in each stage, on average. In addition, the :guilabel:`Contract "
"Proposal` stage had the longest wait time in July, with an average of "
":guilabel:`31.62` days in that stage."
msgstr ""

#: ../../content/applications/hr/recruitment/time_in_stage.rst:75
msgid ""
"While this report does not display the reasons applicants stayed in the "
"various stages for these lengths of time, it can be helpful to know when "
"delays occur."
msgstr ""

#: ../../content/applications/hr/recruitment/time_in_stage.rst:79
msgid ":doc:`Essentials reporting documentation <../../essentials/reporting>`"
msgstr ""

#: ../../content/applications/hr/referrals.rst:5
msgid "Referrals"
msgstr "הפניות"

#: ../../content/applications/hr/referrals.rst:7
msgid ""
"Odoo's *Referrals* application is a centralized place where all information "
"regarding referrals is housed - from points earned, coworkers hired, and "
"rewards selected. Users can recommend people they know for job positions, "
"and then earn referral points as those people progress through the "
"recruitment pipeline. Once enough referral points are earned, they can be "
"exchanged for prizes. The *Referrals* application integrates with the "
"*Employees*, *Recruitment*, and *Website* applications, all of which must be"
" installed in order for the *Referrals* application to function."
msgstr ""

#: ../../content/applications/hr/referrals.rst:14
msgid ""
"The only configurations needed for the *Referrals* application *after* it "
"has been installed, are related to the :doc:`rewards <referrals/rewards>`; "
"everything else is pre-configured when Odoo *Referrals* is installed."
msgstr ""

#: ../../content/applications/hr/referrals.rst:18
msgid ""
"Users with either :guilabel:`Referral User`, :guilabel:`Officer`, or "
":guilabel:`Administrator` access rights for the *Recruitment* application "
"have access to the *Referrals* application. Only users with "
":guilabel:`Administrator` access rights for the *Recruitment* application "
"have access to the :doc:`reporting <referrals/reporting>` and configurations"
" menus. For more information on users and access rights, refer to these "
"documents: :doc:`../general/users` and "
":doc:`../general/users/access_rights`."
msgstr ""

#: ../../content/applications/hr/referrals.rst:28
msgid "Onboarding"
msgstr "קליטה לעבודה"

#: ../../content/applications/hr/referrals.rst:30
msgid ""
"When opening the *Referrals* application for the first time, a pre-"
"configured onboarding script appears. This is in the form of four slides, "
"each explaining the different parts of the *Referrals* application. At the "
"top of the dashboard, the following message is displayed throughout all the "
"onboarding slides: :guilabel:`GATHER YOUR TEAM! Job Referral Program`. "
"Behind this main message is an image, and beneath it some more explanatory "
"text."
msgstr ""

#: ../../content/applications/hr/referrals.rst:36
msgid ""
"Each of the onboarding slides has a corresponding image and message that is "
"displayed. After reading each message, click the :guilabel:`Next` button to "
"advance to the next slide."
msgstr ""

#: ../../content/applications/hr/referrals.rst:39
msgid "The text that appears on each slide is as follows:"
msgstr ""

#: ../../content/applications/hr/referrals.rst:41
msgid ""
":guilabel:`Oh no! Villains are lurking the city! Help us recruit a team of "
"superheroes to save the day!`"
msgstr ""

#: ../../content/applications/hr/referrals.rst:43
msgid ""
":guilabel:`Browse through open job positions, promote them on social media, "
"or refer friends.`"
msgstr ""

#: ../../content/applications/hr/referrals.rst:44
msgid ""
":guilabel:`Collect points and exchange them for awesome gifts in the shop.`"
msgstr ""

#: ../../content/applications/hr/referrals.rst:45
msgid ""
":guilabel:`Compete against your colleagues to build the best justice "
"league!`"
msgstr ""

#: ../../content/applications/hr/referrals.rst:48
msgid ""
"The onboarding slides will appear every time the *Referrals* application is "
"opened, until all the slides have been viewed and the :guilabel:`Start Now` "
"button has been clicked. If the onboarding is exited at any point, or if the"
" :guilabel:`Start Now` button has *not* been clicked, the onboarding slides "
"will begin again when the *Referrals* application is opened. Once the "
":guilabel:`Start Now` button has been clicked, the onboarding slides will "
"not be seen again, and the main dashboard will load when the *Referrals* "
"application is opened from that point on."
msgstr ""

#: ../../content/applications/hr/referrals.rst:55
msgid ""
"At any point during onboarding, the :guilabel:`Skip` button may be clicked. "
"This exits the onboarding, and the main *Referrals* dashboard loads. If "
":guilabel:`Skip` is clicked, onboarding slides will not load anymore when "
"opening the *Referrals* application."
msgstr ""

#: ../../content/applications/hr/referrals.rst-1
msgid ""
"An onboarding slide with the skip and next buttons visible at the bottom."
msgstr ""

#: ../../content/applications/hr/referrals.rst:64
msgid ""
"If there are any candidates hired that the user had referred prior to "
"opening the Referrals app (meaning the onboarding slides have not appeared "
"before), when :guilabel:`Start Now` is clicked at the end of onboarding, "
"instead of going to the main dashboard, a :ref:`hired <referrals/hired>` "
"screen appears instead."
msgstr ""

#: ../../content/applications/hr/referrals.rst:70
msgid "Modifying onboarding slides"
msgstr ""

#: ../../content/applications/hr/referrals.rst:72
msgid ""
"Onboarding slides can be modified if desired. Only users with "
":guilabel:`Administrator` rights for the *Recruitment* application can "
"modify onboarding slides. To edit a slide, navigate to "
":menuselection:`Referrals app --> Configuration --> Onboarding.` Each line "
"displays the text for the individual onboarding slide. To edit an onboarding"
" slide, click on an individual slide line to open the slide's onboarding "
"form."
msgstr ""

#: ../../content/applications/hr/referrals.rst:78
msgid ""
"Make any changes to the message in the :guilabel:`Text` field. A "
":guilabel:`Company` may be selected, as well. However, if this field is "
"populated, that slide is *only* displayed for that particular company."
msgstr ""

#: ../../content/applications/hr/referrals.rst:83
msgid ""
"The :guilabel:`Company` field only appears when in a multi-company database."
msgstr ""

#: ../../content/applications/hr/referrals.rst:85
msgid ""
"The image can be modified, as well. Hover over the image thumbnail in the "
"top-right corner of the form. A :guilabel:`✏️ (pencil)` icon and "
":guilabel:`🗑️ (garbage can)` icon appear. Click the :guilabel:`✏️ (pencil)` "
"icon to change the image. A file navigator window loads. Navigate to the "
"desired image, select it, then click :guilabel:`Open`. The new image appears"
" in the thumbnail. To delete an image, click the :guilabel:`🗑️ (garbage "
"can)` icon, then select a new image using the :guilabel:`✏️ (pencil)` icon."
msgstr ""

#: ../../content/applications/hr/referrals.rst-1
msgid "An onboarding slide in edit mode, with the main fields highlighted."
msgstr ""

#: ../../content/applications/hr/referrals.rst:96
msgid ""
"The sequence in which the slides appear can be changed from the *Onboarding*"
" dashboard. Click the :guilabel:`(six small gray boxes)` icon to the left of"
" the the slide text, and drag the slide to the desired position."
msgstr ""

#: ../../content/applications/hr/referrals.rst-1
msgid ""
"The onboarding slides in a list, with the drag and drop arrows highlighted."
msgstr ""

#: ../../content/applications/hr/referrals.rst:107
msgid "Hired referrals"
msgstr ""

#: ../../content/applications/hr/referrals.rst:109
msgid ""
"When a candidate that has been referred by a user is hired, the user \"grows"
" their superhero team\" and adds superhero avatars to their Referrals "
"dashboard."
msgstr ""

#: ../../content/applications/hr/referrals.rst:112
msgid ""
"After a referral has been hired, when the user next opens the Referrals app,"
" instead of the main dashboard, a hired page loads. The text "
":guilabel:`(Referral Name) has been hired! Choose an avatar for your new "
"friend!` appears."
msgstr ""

#: ../../content/applications/hr/referrals.rst:116
msgid ""
"Below this message are five avatar thumbnails to choose from. If an avatar "
"has already been assigned to a referral, the thumbnail is grayed out, and "
"the name that the avatar has been chosen for appears beneath the avatar. "
"Click on an available avatar to select it."
msgstr ""

#: ../../content/applications/hr/referrals.rst:120
msgid ""
"If more than one referral was hired since opening the *Referrals* "
"application, after selecting the first avatar, the user is prompted to "
"select another avatar for the subsequent hired referral. Once all avatars "
"have been selected, the dashboard loads and all the avatars are now visible."
" Mouse over each avatar and their name is displayed above them."
msgstr ""

#: ../../content/applications/hr/referrals.rst-1
msgid ""
"The hired screen. A selection of avatars are presented to chose from, with any already\n"
"chosen are greyed out."
msgstr ""

#: ../../content/applications/hr/referrals.rst:131
msgid "Modify friends"
msgstr ""

#: ../../content/applications/hr/referrals.rst:133
msgid ""
"Friend avatars are able to be modified in the same manner that :ref:`levels "
"<referrals/levels>` are modified. Only users with :guilabel:`Administrator` "
"rights for the *Recruitment* application can make modifications to friends. "
"The pre-configured friends can be seen and modified by navigating to "
":menuselection:`Referrals app --> Configuration --> Friends`. Each friend "
"avatar appears in the :guilabel:`Dashboard Image` column, and the "
"corresponding name appears in the :guilabel:`Friend Name` column. The "
"default images are a motley group of hero characters, ranging from robots to"
" dogs."
msgstr ""

#: ../../content/applications/hr/referrals.rst:140
msgid ""
"To modify a friend's dashboard image, thumbnail, name, or position, click on"
" an individual friend to open the referral friend form. Click "
":guilabel:`Edit` to make modifications. Type the name in the "
":guilabel:`Friend Name` field. The name is solely to differentiate the "
"friends in the configuration menu; the friend's name is not visible anywhere"
" else in the *Referrals* application."
msgstr ""

#: ../../content/applications/hr/referrals.rst:145
msgid ""
"The :guilabel:`Position` can be set to either :guilabel:`Front` or "
":guilabel:`Back`. This determines the position of the friend in relation to "
"the user's super hero avatar. Click the radio button next to the desired "
"selection, and the friend will appear either in front of or behind the "
"user's avatar when activated."
msgstr ""

#: ../../content/applications/hr/referrals.rst:150
msgid ""
"If desired, both the thumbnail :guilabel:`Image` and the "
":guilabel:`Dashboard Image` can be modified. Hover over the image being "
"replaced to reveal a :guilabel:`✏️ (pencil)` icon and :guilabel:`🗑️ (garbage"
" can)` icon. Click the :guilabel:`✏️ (pencil)` icon, and a file explorer "
"window appears. Navigate to the desired image file, then click "
":guilabel:`Open` to select it."
msgstr ""

#: ../../content/applications/hr/referrals.rst:155
msgid ""
"The referral friend form automatically saves, but can be saved manually at "
"any time by clicking the *Save manually* option, represented by a "
":guilabel:`(cloud upload)` icon, located in the top-left corner. To cancel "
"any changes made, click the :guilabel:`✖️ (Discard all changes)` icon to "
"delete any changes, and revert to the original content."
msgstr ""

#: ../../content/applications/hr/referrals.rst-1
msgid "A friend form in edit mode."
msgstr ""

#: ../../content/applications/hr/referrals.rst:165
#: ../../content/applications/hr/referrals.rst:225
msgid ""
"It is not advised to edit the images. An image file must have a transparent "
"background in order for it to render properly. Only users with knowledge "
"about transparent images should attempt adjusting any images in the "
"*Referrals* application."
msgstr ""

#: ../../content/applications/hr/referrals.rst:169
msgid ""
"Once an image is changed and the friend is saved, it is **not possible** to "
"revert to the original image. To revert to the original image, the "
"*Referrals* application must be *uninstalled then reinstalled.*"
msgstr ""

#: ../../content/applications/hr/referrals.rst:176
msgid "Levels"
msgstr "רמות"

#: ../../content/applications/hr/referrals.rst:178
msgid ""
"The *Referrals* application has pre-configured levels that are reflected in "
"the user's avatar on the Referrals dashboard. As a user refers potential "
"employees and earns points, they can *level up*, much like in a video game."
msgstr ""

#: ../../content/applications/hr/referrals.rst:182
msgid ""
"Levels have no functional impact on the performance of the application. They"
" are solely used for the purpose of adding achievement tiers for "
"participants to aim for, gamifying referrals for the user."
msgstr ""

#: ../../content/applications/hr/referrals.rst:185
msgid ""
"The user's current level is displayed at the top of the main *Referrals* "
"application dashboard, directly beneath their photo, in a :guilabel:`Level: "
"X` format. In addition, a colored ring appears around the user's photo, "
"indicating how many points the user currently has, and how many additional "
"points they need to level up. The cyan colored portion of the ring "
"represents points earned, while the white colored portion represents the "
"points still needed before they can level up."
msgstr ""

#: ../../content/applications/hr/referrals.rst:192
msgid "Modify levels"
msgstr ""

#: ../../content/applications/hr/referrals.rst:194
msgid ""
"Only users with :guilabel:`Administrator` rights for the *Recruitment* "
"application can modify levels. The pre-configured levels can be seen and "
"modified by navigating to :menuselection:`Referrals app --> Configuration "
"--> Levels`. Each avatar appears in the :guilabel:`Image` column, and the "
"corresponding level number appears in the :guilabel:`Level Name` column. The"
" default images are of Odoo superheroes, and each level adds an additional "
"element to their avatar, such as capes and shields."
msgstr ""

#: ../../content/applications/hr/referrals.rst:201
msgid ""
"To modify a level's image, name, or points required to reach the level, "
"click on an individual level in the list to open the level form, then make "
"modifications."
msgstr ""

#: ../../content/applications/hr/referrals.rst:204
msgid ""
"Type in the name (or number) of the level in the :guilabel:`Level Name` "
"field. What is entered is displayed beneath the user's photo on the main "
"dashboard when they reach that level. Enter the number of referral points "
"needed to reach that level in the :guilabel:`Requirements` field. The points"
" needed to level up are the total accumulated points earned over the "
"lifetime of the employee, not additional points from the previous level that"
" must be earned."
msgstr ""

#: ../../content/applications/hr/referrals.rst:210
msgid ""
"If desired, the :guilabel:`Image` can also be modified. Hover over the image"
" to reveal a :guilabel:`✏️ (pencil)` icon and :guilabel:`🗑️ (garbage can)` "
"icon. Click the :guilabel:`✏️ (pencil)` icon, and a file explorer window "
"appears. Navigate to the desired image file, then click :guilabel:`Open` to "
"select it."
msgstr ""

#: ../../content/applications/hr/referrals.rst:215
msgid ""
"The level form saves automatically, but can be saved manually at any time by"
" clicking the *save manually* option, represented by a :guilabel:`(cloud "
"upload)` icon, located in the top-left corner. To cancel any changes made, "
"click the :guilabel:`✖️ (Discard all changes)` icon to delete any changes, "
"and revert to the original content."
msgstr ""

#: ../../content/applications/hr/referrals.rst-1
msgid "A level form in edit mode."
msgstr ""

#: ../../content/applications/hr/referrals.rst:229
msgid ""
"Once an image is changed and the level is saved, it is **not possible** to "
"revert to the original image. To revert to the original image, the "
"*Referrals* application must be *uninstalled then reinstalled.*"
msgstr ""

#: ../../content/applications/hr/referrals.rst:234
msgid "Level up"
msgstr ""

#: ../../content/applications/hr/referrals.rst:236
msgid ""
"Once enough points have been accumulated to level up, the circle around the "
"user's photo is completely filled in with a cyan color, a large image "
"stating :guilabel:`Level up!` appears above the photo, and the phrase "
":guilabel:`Click to level up!` appears beneath the user's photo and current "
"level."
msgstr ""

#: ../../content/applications/hr/referrals.rst:241
msgid ""
"Click on either the :guilabel:`LEVEL UP!` graphic, the user's photo, or the "
"text :guilabel:`Click to level up!` beneath the user's photo to level up the"
" user. The user's avatar changes to the current level, and the ring around "
"the photo is updated to indicate the current amount of points."
msgstr ""

#: ../../content/applications/hr/referrals.rst:245
msgid ""
"Leveling up does not cost the user any points, the user simply needs to earn"
" the specified amount of points required."
msgstr ""

#: ../../content/applications/hr/referrals.rst-1
msgid ""
"A 'Click to level up!' appears beneath the user's image, and a large 'Level up!' appears\n"
"above their image."
msgstr ""

#: ../../content/applications/hr/referrals.rst:254
msgid ""
"Once a user has reached the highest configured level, they will continue to "
"accrue points that can be redeemed for rewards, but they are no longer able "
"to level up. The ring around their photo remains solid cyan."
msgstr ""

#: ../../content/applications/hr/referrals.rst:259
msgid ":doc:`referrals/share_jobs`"
msgstr ""

#: ../../content/applications/hr/referrals.rst:260
msgid ":doc:`referrals/points`"
msgstr ""

#: ../../content/applications/hr/referrals.rst:261
msgid ":doc:`referrals/rewards`"
msgstr ""

#: ../../content/applications/hr/referrals.rst:262
msgid ":doc:`referrals/alerts`"
msgstr ""

#: ../../content/applications/hr/referrals.rst:263
msgid ":doc:`referrals/reporting`"
msgstr ""

#: ../../content/applications/hr/referrals/alerts.rst:5
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/referrals/alerts.rst:8
msgid ""
"Alerts remain on the main *Referrals* dashboard for the specified amount of "
"time configured on the individual alert."
msgstr ""

#: ../../content/applications/hr/referrals/alerts.rst-1
msgid "Two alert banners appear above the user's photo."
msgstr ""

#: ../../content/applications/hr/referrals/alerts.rst:16
msgid "Create an alert"
msgstr ""

#: ../../content/applications/hr/referrals/alerts.rst:18
msgid ""
"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`."
msgstr ""

#: ../../content/applications/hr/referrals/alerts.rst:21
msgid ""
"Click :guilabel:`New` to open a blank alert form. Enter the following "
"information on the form:"
msgstr ""

#: ../../content/applications/hr/referrals/alerts.rst:23
msgid ""
":guilabel:`Date From`: the date the alert starts. On this date, the alert is"
" visible on the dashboard."
msgstr ""

#: ../../content/applications/hr/referrals/alerts.rst:25
msgid ""
":guilabel:`Date To`: the date the alert ends. After this date, the alert is "
"hidden from view."
msgstr ""

#: ../../content/applications/hr/referrals/alerts.rst:26
msgid ""
":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."
msgstr ""

#: ../../content/applications/hr/referrals/alerts.rst:30
msgid ""
"If this field remains blank, the alert is visible to everyone with access to"
" the *Referrals* application."
msgstr ""

#: ../../content/applications/hr/referrals/alerts.rst:33
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/referrals/alerts.rst:35
msgid ""
":guilabel:`Alert`: enter the text for the alert. This message appears inside"
" the alert banner on the main *Referrals* dashboard."
msgstr ""

#: ../../content/applications/hr/referrals/alerts.rst:37
msgid ""
":guilabel:`On Click`: there are three options for the alert. Click the radio"
" button next to the desired selection. The options are:"
msgstr ""

#: ../../content/applications/hr/referrals/alerts.rst:40
msgid ""
":guilabel:`Not Clickable`: the alert only displays text, there is no link to"
" click."
msgstr ""

#: ../../content/applications/hr/referrals/alerts.rst:41
msgid ""
":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."
msgstr ""

#: ../../content/applications/hr/referrals/alerts.rst:43
msgid ""
":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."
msgstr ""

#: ../../content/applications/hr/referrals/alerts.rst-1
msgid "An alert form completely filled in with all selections entered."
msgstr ""

#: ../../content/applications/hr/referrals/alerts.rst:52
msgid "Dismiss an alert"
msgstr ""

#: ../../content/applications/hr/referrals/alerts.rst:54
msgid ""
"It is possible to dismiss an alert, if a user does not wish to see a "
"specific alert again."
msgstr ""

#: ../../content/applications/hr/referrals/alerts.rst:56
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/referrals/alerts.rst:59
msgid ""
"This prevents the alert from appearing again, even when opening the "
"*Referrals* application for the first time in a new session."
msgstr ""

#: ../../content/applications/hr/referrals/points.rst:3
msgid "Referral points"
msgstr ""

#: ../../content/applications/hr/referrals/points.rst:5
msgid ""
"The *Referrals* application allows employees to earn points that are then "
"exchanged for :doc:`rewards <rewards>`."
msgstr ""

#: ../../content/applications/hr/referrals/points.rst:8
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/referrals/points.rst:12
msgid ""
"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`."
msgstr ""

#: ../../content/applications/hr/referrals/points.rst:16
msgid ""
"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`."
msgstr ""

#: ../../content/applications/hr/referrals/points.rst:20
msgid ""
"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`."
msgstr ""

#: ../../content/applications/hr/referrals/points.rst:26
msgid "My referrals"
msgstr ""

#: ../../content/applications/hr/referrals/points.rst:28
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/referrals/points.rst:32
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/referrals/points.rst:36
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/referrals/points.rst:40
msgid ""
"For referrals that have been hired, the selected avatar also appears on the "
"card."
msgstr ""

#: ../../content/applications/hr/referrals/points.rst-1
msgid "Two referral cards, one hired and one in-progress."
msgstr ""

#: ../../content/applications/hr/referrals/points.rst:47
msgid "Points"
msgstr "נקודות"

#: ../../content/applications/hr/referrals/points.rst:49
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/referrals/points.rst:53
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/referrals/points.rst:57
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/referrals/points.rst:62
msgid "The preconfigured point structure for referrals is as follows:"
msgstr ""

#: ../../content/applications/hr/referrals/points.rst:64
msgid ":guilabel:`Initial Qualification`: 1 point"
msgstr ""

#: ../../content/applications/hr/referrals/points.rst:65
msgid ":guilabel:`First Interview`: 20 points"
msgstr ""

#: ../../content/applications/hr/referrals/points.rst:66
msgid ":guilabel:`Second Interview`: 9 points"
msgstr ""

#: ../../content/applications/hr/referrals/points.rst:67
msgid ":guilabel:`Contract Proposal`: 5 points"
msgstr ""

#: ../../content/applications/hr/referrals/points.rst:68
msgid ":guilabel:`Contract Signed`: 50 points"
msgstr ""

#: ../../content/applications/hr/referrals/points.rst:70
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/referrals/reporting.rst:5
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/referrals/reporting.rst:10
msgid ""
"Only users with *Administrator* rights for the **Recruitment** app have "
"access to the reporting feature in the **Referrals** app."
msgstr ""

#: ../../content/applications/hr/referrals/reporting.rst:14
msgid "Employees referral analysis report"
msgstr ""

#: ../../content/applications/hr/referrals/reporting.rst:16
msgid ""
"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`."
msgstr ""

#: ../../content/applications/hr/referrals/reporting.rst:20
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/referrals/reporting.rst:25
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/referrals/reporting.rst:28
msgid ""
"Hover over any bar to view a popover containing specific data for that "
"particular bar."
msgstr ""

#: ../../content/applications/hr/referrals/reporting.rst:30
msgid ""
"In this view, it is easy to see which :guilabel:`Medium` is the most "
"successful."
msgstr ""

#: ../../content/applications/hr/referrals/reporting.rst:33
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/referrals/reporting.rst:0
msgid "The default report in the Referrals app."
msgstr ""

#: ../../content/applications/hr/referrals/reporting.rst:41
msgid "Use case: hired referrals"
msgstr ""

#: ../../content/applications/hr/referrals/reporting.rst:43
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/referrals/reporting.rst:46
msgid ""
"In this example, data is examined to determined which employee has the "
"highest number of hired referrals for the current year."
msgstr ""

#: ../../content/applications/hr/referrals/reporting.rst:49
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/referrals/reporting.rst:52
msgid ""
"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`)."
msgstr ""

#: ../../content/applications/hr/referrals/reporting.rst:57
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/referrals/reporting.rst:61
msgid ""
"The information displayed shows how many total applicants each employee "
"referred, and how many of those applicants were hired, for the current year."
msgstr ""

#: ../../content/applications/hr/referrals/reporting.rst:64
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/referrals/reporting.rst:68
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/referrals/reporting.rst-1
msgid ""
"The customized report showing which employees have the most referrals and "
"hires."
msgstr ""

#: ../../content/applications/hr/referrals/reporting.rst:76
msgid ""
"The pivot table can be inserted into a new or existing :doc:`spreadsheet "
"<../../productivity/spreadsheet/insert>`, if desired."
msgstr ""

#: ../../content/applications/hr/referrals/reporting.rst:79
msgid ""
"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."
msgstr ""

#: ../../content/applications/hr/referrals/reporting.rst:84
msgid ""
"Click :guilabel:`Confirm`, and the selected spreadsheet loads, with the new "
"table in it."
msgstr ""

#: ../../content/applications/hr/referrals/reporting.rst:86
msgid ""
"The spreadsheet is stored in the *Documents* application. This application "
"**must** be installed to use the :guilabel:`Insert in Spreadsheet` option."
msgstr ""

#: ../../content/applications/hr/referrals/rewards.rst:3
msgid "Rewards"
msgstr "הטבות"

#: ../../content/applications/hr/referrals/rewards.rst:5
msgid ""
"After employees have successfully earned referral points, they can exchange "
"their points by purchasing rewards in Odoo's *Referrals* application. "
"Rewards **must** be :ref:`created and configured <referrals/create>` before "
"employees can :ref:`redeem points for rewards <referrals/redeem>`."
msgstr ""

#: ../../content/applications/hr/referrals/rewards.rst:13
msgid "Create rewards"
msgstr ""

#: ../../content/applications/hr/referrals/rewards.rst:15
msgid ""
"Rewards are the only configurations needed when setting up the *Referrals* "
"application."
msgstr ""

#: ../../content/applications/hr/referrals/rewards.rst:17
msgid ""
"Only users with :guilabel:`Administrator` rights for the *Recruitment* "
"application can create or modify rewards."
msgstr ""

#: ../../content/applications/hr/referrals/rewards.rst:20
msgid ""
"To add rewards, navigate to :menuselection:`Referrals app --> Configuration "
"--> Rewards`. Click :guilabel:`New`, and a reward form loads. Enter the "
"following information on the form:"
msgstr ""

#: ../../content/applications/hr/referrals/rewards.rst:23
msgid ""
":guilabel:`Product Name`: enter the name as it should appear for the reward."
" This field is required."
msgstr ""

#: ../../content/applications/hr/referrals/rewards.rst:25
msgid ""
":guilabel:`Cost`: enter the amount of points required to redeem the reward."
msgstr ""

#: ../../content/applications/hr/referrals/rewards.rst:26
msgid ""
":guilabel:`Company`: using the drop-down menu, select the company the reward"
" is configured for. If a reward is available for multiple companies, each "
"company **must** configure a reward for their specific company. This field "
"**only** appears if in a multi-company environment; if this field appears, "
"it is required."
msgstr ""

#: ../../content/applications/hr/referrals/rewards.rst:32
msgid ""
"A corporation with three different companies offers a gift card as a reward."
" In the database, there are three separate rewards listed for a gift card, "
"one for each of the three companies."
msgstr ""

#: ../../content/applications/hr/referrals/rewards.rst:35
msgid ""
":guilabel:`Gift Responsible`: using the drop-down menu, select the person "
"responsible for procuring and delivering the reward to the recipient. This "
"person is alerted when the reward is bought in the *Referrals* application, "
"so they know when to deliver the reward to the recipient."
msgstr ""

#: ../../content/applications/hr/referrals/rewards.rst:38
msgid ""
":guilabel:`Photo`: add a photo of the reward, which appears on the rewards "
"page. Hover over the image box in the top-right corner (a square with a "
"camera and plus sign inside it), and a :icon:`fa-pencil` "
":guilabel:`(pencil)` icon appears. Click the :icon:`fa-pencil` "
":guilabel:`(pencil)` icon to select and add a photo to the reward form. Once"
" a photo is added, hovering over the image reveals two icons instead of one:"
" a :icon:`fa-pencil` :guilabel:`(pencil)` icon and a :icon:`fa-trash-o` "
":guilabel:`(trash can)` icon. Click the :icon:`fa-trash-o` :guilabel:`(trash"
" can)` icon to delete the currently selected image."
msgstr ""

#: ../../content/applications/hr/referrals/rewards.rst:45
msgid ""
":guilabel:`Description` tab: type in the description for the reward. This is"
" visible on the reward card, beneath the title. This field is required."
msgstr ""

#: ../../content/applications/hr/referrals/rewards.rst-1
msgid "A filled out reward form with all details entered."
msgstr ""

#: ../../content/applications/hr/referrals/rewards.rst:53
msgid ""
"It is advised to enter a :guilabel:`Cost` and add a :guilabel:`Photo`. If a "
"cost is not entered, the default cost is listed as zero, which would list "
"the reward as free in the reward shop. If a photo is not selected, a "
"placeholder icon is displayed on the rewards page."
msgstr ""

#: ../../content/applications/hr/referrals/rewards.rst:60
msgid "Redeem rewards"
msgstr ""

#: ../../content/applications/hr/referrals/rewards.rst:62
msgid ""
"In order to redeem a reward, points must be earned. These points can then be"
" used to purchase a reward."
msgstr ""

#: ../../content/applications/hr/referrals/rewards.rst:65
msgid ""
"To purchase a reward, click the :guilabel:`Rewards` button on the main "
":guilabel:`Referrals` dashboard. All the configured rewards are listed in "
"individual reward cards."
msgstr ""

#: ../../content/applications/hr/referrals/rewards.rst:68
msgid ""
"The required point amount needed to purchase a reward is listed in the top-"
"right corner of the card."
msgstr ""

#: ../../content/applications/hr/referrals/rewards.rst:70
msgid ""
"If the user has enough points to purchase a reward, a :icon:`fa-shopping-"
"basket` :guilabel:`Buy` button appears at the bottom of the reward card. If "
"they do not have enough points for a reward, the reward card displays "
":guilabel:`You need another (x) points to buy this`, instead of a :icon:`fa-"
"shopping-basket` :guilabel:`Buy` button."
msgstr ""

#: ../../content/applications/hr/referrals/rewards.rst:75
msgid ""
"Click the :icon:`fa-shopping-basket` :guilabel:`Buy` button on a reward to "
"purchase it. A :guilabel:`Confirmation` pop-up window appears, asking if the"
" user is sure they want to purchase the reward. Click :guilabel:`OK` to "
"purchase the item, or :guilabel:`Cancel` to close the window, and cancel the"
" purchase."
msgstr ""

#: ../../content/applications/hr/referrals/rewards.rst:80
msgid ""
"After :guilabel:`OK` is clicked, the pop-up window closes, and the points "
"used to purchase the reward are subtracted from the user's available points."
" The rewards presented are now updated to reflect the user's current "
"available points."
msgstr ""

#: ../../content/applications/hr/referrals/rewards.rst-1
msgid ""
"Buy button appears below a mug and backpack reward, while the bicycle reward states how\n"
"many more reward points are needed to redeem."
msgstr ""

#: ../../content/applications/hr/referrals/share_jobs.rst:3
msgid "Share job positions"
msgstr ""

#: ../../content/applications/hr/referrals/share_jobs.rst:5
msgid ""
"In Odoo *Referrals*, users can earn referral points by sharing job positions"
" with potential applicants. Job positions can be shared in several ways, "
"through the :ref:`View Jobs <referrals/view-jobs>` button and the "
":ref:`Email A Friend <referrals/email-jobs>` button, located at the bottom "
"of the *Referrals* app dashboard."
msgstr ""

#: ../../content/applications/hr/referrals/share_jobs.rst:11
msgid ""
"Sharing jobs can **only** occur after onboarding slides have been viewed or "
"skipped."
msgstr ""

#: ../../content/applications/hr/referrals/share_jobs.rst:16
msgid "View Jobs"
msgstr "צפה במשרות"

#: ../../content/applications/hr/referrals/share_jobs.rst:18
msgid ""
"To see all job positions that are actively recruiting candidates, click the "
":guilabel:`View Jobs` button on the main *Referrals* dashboard. This "
"presents all job positions, with each individual job presented with its own "
"card."
msgstr ""

#: ../../content/applications/hr/referrals/share_jobs.rst-1
msgid ""
"The 'View Jobs' screen, displaying all current open job positions. All information is\n"
"displayed on the card."
msgstr ""

#: ../../content/applications/hr/referrals/share_jobs.rst:27
msgid "Each job position card contains the following information:"
msgstr ""

#: ../../content/applications/hr/referrals/share_jobs.rst:29
msgid ""
"The title of the job position. This information is taken from the *Job "
"Position* field of the job form."
msgstr ""

#: ../../content/applications/hr/referrals/share_jobs.rst:31
msgid ""
"The number of :guilabel:`Open Positions` being recruited. This information "
"is taken from the *Expected New Employees* field of the *Recruitment* tab of"
" the job form."
msgstr ""

#: ../../content/applications/hr/referrals/share_jobs.rst:33
msgid "The points a user earns when an applicant applies for the position."
msgstr ""

#: ../../content/applications/hr/referrals/share_jobs.rst:34
msgid ""
"The job description detailing the job position. This information is taken "
"from the *Job Position* tab of the job form."
msgstr ""

#: ../../content/applications/hr/referrals/share_jobs.rst:37
msgid ""
"To see all the details for a job position, click the :guilabel:`More Info` "
"button on the specific card. This opens the job position webpage in a new "
"browser tab. This is what an applicant sees before applying for a position."
msgstr ""

#: ../../content/applications/hr/referrals/share_jobs.rst:42
msgid ""
"Only published job positions are visible in the *Referrals* app. To check "
"which job positions are published or not, refer to the "
":doc:`../recruitment/new_job` documentation."
msgstr ""

#: ../../content/applications/hr/referrals/share_jobs.rst:46
msgid "Refer friends"
msgstr ""

#: ../../content/applications/hr/referrals/share_jobs.rst:48
msgid ""
"To share a job position with someone, click the :guilabel:`Refer Friend` "
"button on the specific job position card. A pre-configured :guilabel:`Send "
"Job Offer by Mail` pop-up window appears. Enter the recipient's email "
"address in the :guilabel:`Email` field."
msgstr ""

#: ../../content/applications/hr/referrals/share_jobs.rst:52
msgid ""
"The :guilabel:`Subject` and :guilabel:`Body` are populated using a default "
"template. The :guilabel:`Subject` `Job for you` is present, by default, but "
"can be modified, if desired."
msgstr ""

#: ../../content/applications/hr/referrals/share_jobs.rst:55
msgid ""
"The specific title of the job position populates the *Job Position* "
"placeholder in the email body. The `See Job Offer` text in the email body is"
" an individualized tracking link to the specific job position listed on the "
"website."
msgstr ""

#: ../../content/applications/hr/referrals/share_jobs.rst:59
msgid ""
"When the prospective employee receives the email, the link sends them to the"
" job position page, where they can apply for the position, and the person "
"who referred them is tracked in the *Referrals* application."
msgstr ""

#: ../../content/applications/hr/referrals/share_jobs.rst:63
msgid ""
"If desired, add any text or closing salutation to the email body. When all "
"edits have been made, click :guilabel:`Send Mail` to send the email, or "
"click :guilabel:`Cancel` to close the pop-up window."
msgstr ""

#: ../../content/applications/hr/referrals/share_jobs.rst-1
msgid "Referral email pop-up window with the email message inside it."
msgstr ""

#: ../../content/applications/hr/referrals/share_jobs.rst:72
msgid "Share a job"
msgstr ""

#: ../../content/applications/hr/referrals/share_jobs.rst:74
msgid ""
"Other than sending an email, job positions can be shared, via social media "
"platforms, and by tracking links to the job position. At the bottom of each "
"job position card are four icons, and corresponding tracking links, that can"
" be used to share the job position, keeping track of applicants in the "
"*Referrals* application."
msgstr ""

#: ../../content/applications/hr/referrals/share_jobs.rst-1
msgid "The various sharing icons that appear for each job."
msgstr ""

#: ../../content/applications/hr/referrals/share_jobs.rst:84
msgid "Link"
msgstr "קישור"

#: ../../content/applications/hr/referrals/share_jobs.rst:86
msgid ""
"To share the job position with a customized tracking link, click the "
":guilabel:`Share Now` button with the :icon:`fa-chain` :guilabel:`(link)` "
"icon above it. A :guilabel:`Link to Share` pop-up window appears with the "
"tracking link. Click :guilabel:`Copy` to copy the link. After the link is "
"copied, click the :guilabel:`Close` button to close the pop-up window. Next,"
" share the link with the prospective employee."
msgstr ""

#: ../../content/applications/hr/referrals/share_jobs.rst:93
msgid "Facebook"
msgstr "פייסבוק"

#: ../../content/applications/hr/referrals/share_jobs.rst:95
msgid ""
"To share the job position using Facebook, click the :guilabel:`Share Now` "
"button with the :icon:`fa-facebook` :guilabel:`(Facebook)` icon above it."
msgstr ""

#: ../../content/applications/hr/referrals/share_jobs.rst:98
msgid ""
"If the user is already logged into Facebook, when the the :guilabel:`Share "
"Now` button is clicked, a :guilabel:`Share on Facebook` page loads in a new "
"tab, with the link populated in the main body of the new post in a pop-up "
"window. If the user is *not* already logged in, a log-in screen loads, "
"instead, prompting the user to log-in to Facebook first."
msgstr ""

#: ../../content/applications/hr/referrals/share_jobs.rst:103
msgid ""
"Type in any additional information to add to the post, then share the job "
"position using the available options in Facebook."
msgstr ""

#: ../../content/applications/hr/referrals/share_jobs.rst:107
msgid "X (formerly Twitter)"
msgstr ""

#: ../../content/applications/hr/referrals/share_jobs.rst:109
msgid ""
"A job position can also be shared on X. Click the :guilabel:`Share Now` "
"button with the :guilabel:`(X)` icon above it."
msgstr ""

#: ../../content/applications/hr/referrals/share_jobs.rst:112
msgid ""
"If the user is already signed-in to X, when the :guilabel:`Share Now` button"
" is clicked, an X page loads in a new tab with a pre-populated message ready"
" to post, in a draft pop-up window. If the user is *not* already signed-in, "
"a sign-in screen loads instead, prompting the user to first sign-in to X."
msgstr ""

#: ../../content/applications/hr/referrals/share_jobs.rst:117
msgid "The default message is:"
msgstr ""

#: ../../content/applications/hr/referrals/share_jobs.rst:119
msgid ""
"`Amazing job offer for (Job Position)! Check it live: (link to Job "
"Position)`"
msgstr ""

#: ../../content/applications/hr/referrals/share_jobs.rst:121
msgid ""
"Type in any additional information, or make any edits to the message, then "
"share using the available options in X."
msgstr ""

#: ../../content/applications/hr/referrals/share_jobs.rst:125
msgid "LinkedIn"
msgstr "לינקדאין"

#: ../../content/applications/hr/referrals/share_jobs.rst:127
msgid ""
"To share a job position on LinkedIn, click the :guilabel:`Share Now` button "
"with the :icon:`fa-linkedin` :guilabel:`(LinkedIn)` icon above it."
msgstr ""

#: ../../content/applications/hr/referrals/share_jobs.rst:130
msgid ""
"If the user is already logged into LinkedIn, when the :guilabel:`Share Now` "
"button is clicked, a new tab loads in LinkedIn, with a link to the job "
"position at the top. If the user is *not* already logged in, a log-in screen"
" loads instead, prompting the user to log-in to LinkedIn first."
msgstr ""

#: ../../content/applications/hr/referrals/share_jobs.rst:134
msgid ""
"The job position can be shared either in a public post, or in a private "
"message to an individual (or group of individuals)."
msgstr ""

#: ../../content/applications/hr/referrals/share_jobs.rst:137
msgid ""
"Type in any additional information, or make any edits to the message or "
"post, then share using the available options in LinkedIn."
msgstr ""

#: ../../content/applications/hr/referrals/share_jobs.rst:143
msgid "Email a friend"
msgstr "שלח דוא\"ל לחבר"

#: ../../content/applications/hr/referrals/share_jobs.rst:145
msgid ""
"Another way to share job opportunities is to share the entire current list "
"of open job positions, instead of one job position at a time. To do this, "
"navigate to the :menuselection:`Referrals` main dashboard. Click the "
":guilabel:`Email a friend` button at the bottom of the screen. A "
":guilabel:`Send Job Offer by Mail` pop-up window appears."
msgstr ""

#: ../../content/applications/hr/referrals/share_jobs.rst:150
msgid ""
"Enter the email address in the :guilabel:`Email` field. The email can be "
"sent to multiple recipients by separating each email address with a comma "
"followed by a single space. The :guilabel:`Subject` is pre-configured with "
":guilabel:`Job for you`, but can be edited."
msgstr ""

#: ../../content/applications/hr/referrals/share_jobs.rst:154
msgid ""
"The email :guilabel:`Body` is also populated with pre-configured text. The "
"text that appears is:"
msgstr ""

#: ../../content/applications/hr/referrals/share_jobs.rst:156
msgid "`Hello,`"
msgstr ""

#: ../../content/applications/hr/referrals/share_jobs.rst:158
msgid ""
"`There are some amazing job offers in my company! Have a look, they can be "
"interesting for you\\:`"
msgstr ""

#: ../../content/applications/hr/referrals/share_jobs.rst:160
msgid "`See Job Offers`"
msgstr ""

#: ../../content/applications/hr/referrals/share_jobs.rst:162
msgid ""
"The :guilabel:`See Job Offers` text is a tracking link to a complete list of"
" all job positions currently being recruited for. Add any additional text "
"and make any edits to the message body, if necessary. Then, click "
":guilabel:`Send Mail` to send the email. This sends the message, and closes "
"the window."
msgstr ""

#: ../../content/applications/hr/time_off.rst:5
msgid "Time Off"
msgstr "מאשר חופשות"

#: ../../content/applications/hr/time_off.rst:7
msgid ""
"Odoo's **Time Off** application serves as a centralized hub for all time-"
"off-related information. This application manages requests, balances, "
"allocations, approvals, and reports."
msgstr ""

#: ../../content/applications/hr/time_off.rst:10
msgid ""
"Users can :doc:`request time off <../hr/time_off/request_time_off>`, and see"
" an overview of their requests and time off balances. Managers can "
":doc:`allocate time off <time_off/allocations>` to individuals, teams, or "
"the whole company, and :ref:`approve time off requests <time_off/manage-"
"time-off>`."
msgstr ""

#: ../../content/applications/hr/time_off.rst:15
msgid ""
"Detailed :ref:`reports <time_off/reporting>` can be run to see how much time"
" off (and what kinds of time off) are being used, :ref:`accrual plans "
"<time_off/accrual-plans>` can be created, and :ref:`public holidays "
"<time_off/public-holidays>` can be set."
msgstr ""

#: ../../content/applications/hr/time_off.rst:20
msgid ""
"Be advised, only users with specific access rights can see all aspects of "
"the **Time Off** app."
msgstr ""

#: ../../content/applications/hr/time_off.rst:22
msgid ""
"All users can access the *My Time Off* and *Overview* sections of the **Time"
" Off** app. All other sections require specific access rights."
msgstr ""

#: ../../content/applications/hr/time_off.rst:25
msgid ""
"To better understand how access rights affect the **Time Off** app, refer to"
" the :doc:`employees/new_employee` document, specifically the section about "
"configuring the work information tab."
msgstr ""

#: ../../content/applications/hr/time_off.rst:32
msgid ""
"In order to allocate time off to employees, and for employees to request and"
" use their time off, the various time off types must be configured first, "
"then allocated to employees (if allocation is required)."
msgstr ""

#: ../../content/applications/hr/time_off.rst:39
msgid "Time off types"
msgstr ""

#: ../../content/applications/hr/time_off.rst:41
msgid ""
"To view the currently configured time off types, navigate to "
":menuselection:`Time Off app --> Configuration --> Time Off Types`. The time"
" off types are presented in a list view."
msgstr ""

#: ../../content/applications/hr/time_off.rst:44
msgid ""
"The **Time Off** app comes with four preconfigured time off types: "
":guilabel:`Paid Time Off`, :guilabel:`Sick Time Off`, :guilabel:`Unpaid`, "
"and :guilabel:`Compensatory Days`. These can be modified to suit business "
"needs, or used as-is."
msgstr ""

#: ../../content/applications/hr/time_off.rst:49
msgid "Create time off type"
msgstr ""

#: ../../content/applications/hr/time_off.rst:51
msgid ""
"To create a new time off type, navigate to :menuselection:`Time Off app --> "
"Configuration --> Time Off Types`. From here, click the :guilabel:`New` "
"button to reveal a blank time off type form."
msgstr ""

#: ../../content/applications/hr/time_off.rst:54
msgid ""
"Enter the name for the particular type of time off in the blank line at the "
"top of the form, such as `Sick Time` or `Vacation`. Then, enter the "
"following information on the form."
msgstr ""

#: ../../content/applications/hr/time_off.rst:58
msgid ""
"The only **required** fields on the time off type form are the name of the "
":guilabel:`Time Off Type`, the :guilabel:`Take Time Off In`, and the "
":guilabel:`Kind of Time Off`. In addition, the :guilabel:`Time Off Requests`"
" and :guilabel:`Allocation Requests` sections **must** be configured."
msgstr ""

#: ../../content/applications/hr/time_off.rst:64
msgid "Time Off Requests section"
msgstr ""

#: ../../content/applications/hr/time_off.rst:66
msgid ""
":guilabel:`Approval`: select what specific kind of approval is required for "
"the time off type. The options are:"
msgstr ""

#: ../../content/applications/hr/time_off.rst:69
msgid ""
":guilabel:`No Validation`: No approvals are required when requesting this "
"type of time off. The time off request is automatically approved."
msgstr ""

#: ../../content/applications/hr/time_off.rst:71
msgid ""
":guilabel:`By Time Off Officer`: Only the specified :ref:`Time Off Officer "
"<time_off/time-off-officer>`, set on this form in the :guilabel:`Notified "
"Time Off Officer` field, is required to approve the time off request. This "
"option is selected, by default."
msgstr ""

#: ../../content/applications/hr/time_off.rst:74
msgid ""
":guilabel:`By Employee's Approver`: Only the employee's specified approver "
"for time off, which is set on the *Work Information* tab on the "
":ref:`employee's form <employees/work-info-tab>`, is required to approve the"
" time off request."
msgstr ""

#: ../../content/applications/hr/time_off.rst:77
msgid ""
":guilabel:`By Employee's Approver and Time Off Officer`: Both the employee's"
" :ref:`specified time off approver<employees/work-info-tab>` and the "
":ref:`Time Off Officer <time_off/time-off-officer>` are required to approve "
"the time off request."
msgstr ""

#: ../../content/applications/hr/time_off.rst:82
msgid "Allocation Requests section"
msgstr ""

#: ../../content/applications/hr/time_off.rst:84
msgid ""
":guilabel:`Requires allocation`: If the time off must be allocated to "
"employees, select :guilabel:`Yes`. If the time off can be requested without "
"time off being previously allocated, select :guilabel:`No Limit`. If "
":guilabel:`No Limit` is selected, the following options do not appear on the"
" form."
msgstr ""

#: ../../content/applications/hr/time_off.rst:88
msgid ""
":guilabel:`Employee Requests`: Select :guilabel:`Extra Days Requests "
"Allowed` if the employee is able to request more time off than was "
"allocated."
msgstr ""

#: ../../content/applications/hr/time_off.rst:91
msgid ""
"If employees should **not** be able to make requests for more time off than "
"what was allocated, select the :guilabel:`Not Allowed` option."
msgstr ""

#: ../../content/applications/hr/time_off.rst:95
msgid ""
"Ten days are allocated to the employee for this particular type of time off,"
" and the :guilabel:`Extra Days Requests Allowed` option is enabled. The "
"employee wants to take a vacation for twelve days. They may submit a request"
" for two additional days, since the :guilabel:`Extra Days Requests Allowed` "
"option is enabled."
msgstr ""

#: ../../content/applications/hr/time_off.rst:101
msgid ""
"It is important to note that requesting additional time off does **not** "
"guarantee that time off is granted."
msgstr ""

#: ../../content/applications/hr/time_off.rst:104
msgid ""
":guilabel:`Approval`: Select the type of approvals required for the "
"allocation of this particular time off type."
msgstr ""

#: ../../content/applications/hr/time_off.rst:107
msgid ""
":guilabel:`Approved by Time Off Officer` indicates the :ref:`Time Off "
"Officer <time_off/time-off-officer>` set on this form must approve the "
"allocation."
msgstr ""

#: ../../content/applications/hr/time_off.rst:109
msgid ""
":guilabel:`No validation needed` indicates that no approvals are required."
msgstr ""

#: ../../content/applications/hr/time_off.rst:112
msgid "Configuration section"
msgstr ""

#: ../../content/applications/hr/time_off.rst:116
msgid ""
":guilabel:`Notified Time Off Officer`: Select the person who is notified and"
" responsible for approving requests and allocations for this specific type "
"of time off."
msgstr ""

#: ../../content/applications/hr/time_off.rst:118
msgid ""
":guilabel:`Take Time Off in`: Select the format the time off is requested in"
" from the drop-down menu."
msgstr ""

#: ../../content/applications/hr/time_off.rst:121
msgid "The options are:"
msgstr ""

#: ../../content/applications/hr/time_off.rst:123
msgid ""
":guilabel:`Day`: if time off can only be requested in full day increments (8"
" hours)."
msgstr ""

#: ../../content/applications/hr/time_off.rst:124
msgid ""
":guilabel:`Half Day`: if time off can only be requested in half day "
"increments (4 hours)."
msgstr ""

#: ../../content/applications/hr/time_off.rst:125
msgid ":guilabel:`Hours`: if the time off can be taken in hourly increments."
msgstr ""

#: ../../content/applications/hr/time_off.rst:129
msgid ""
":guilabel:`Deduct Extra Hours`: Enable this option if the time off request "
"should factor in any extra time accrued by the employee."
msgstr ""

#: ../../content/applications/hr/time_off.rst:133
msgid ""
"If an employee works two extra hours for the week, and requests five hours "
"of time off, the request would be for three hours, since the two extra "
"worked hours are used first, and deducted from the request."
msgstr ""

#: ../../content/applications/hr/time_off.rst:137
msgid ""
":guilabel:`Allow To Attach Supporting Document`: Enable this option to allow"
" the employee to attach documents to the time off request. This is useful in"
" situations where documentation is required, such as long-term medical "
"leave."
msgstr ""

#: ../../content/applications/hr/time_off.rst:140
msgid ""
":guilabel:`Kind of Time Off`: From the drop-down menu, select the type of "
"time off, either :guilabel:`Worked Time` or :guilabel:`Absence`. "
":guilabel:`Worked Time` indicates the time off taken counts toward worked "
"time for any type of accrual the employee is working towards, whereas "
":guilabel:`Absence` does not count toward any type of accrual."
msgstr ""

#: ../../content/applications/hr/time_off.rst:144
msgid ""
":guilabel:`Company`: If multiple companies are created in the database, and "
"this time off type only applies to one company, select the company from the "
"drop-down menu. If this field is left blank, the time off type applies to "
"all companies in the database. This field **only** appears in a multi-"
"company database."
msgstr ""

#: ../../content/applications/hr/time_off.rst:150
msgid "Negative Cap section"
msgstr ""

#: ../../content/applications/hr/time_off.rst:152
msgid ""
"Enable the :guilabel:`Allow Negative Cap` option if employees are able to "
"request more time off than they currently have, allowing a negative balance."
" If enabled, an :guilabel:`Amount in Negative` field appears. In this field,"
" enter the maximum amount of negative time allowed, in days."
msgstr ""

#: ../../content/applications/hr/time_off.rst:157
msgid ""
"Sara currently has three days of the time off type `Vacation`. She is "
"planning a trip that requires five days of time off."
msgstr ""

#: ../../content/applications/hr/time_off.rst:160
msgid ""
"The `Vacation` time off type has the :guilabel:`Allow Negative Cap` option "
"enabled, and the :guilabel:`Amount in Negative` is set to five."
msgstr ""

#: ../../content/applications/hr/time_off.rst:163
msgid ""
"These settings allow Sara to submit a request for five days of the "
"`Vacation` time off type. If approved, her `Vacation` time off balance will "
"be negative two (-2) days."
msgstr ""

#: ../../content/applications/hr/time_off.rst-1
msgid ""
"The top half of the time off type form, with all the information filled out for sick time\n"
"off."
msgstr ""

#: ../../content/applications/hr/time_off.rst:172
msgid "Payroll section"
msgstr ""

#: ../../content/applications/hr/time_off.rst:174
msgid ""
"If the time off type should create :doc:`../hr/payroll/work_entries` in the "
"**Payroll** app, select the :guilabel:`Work Entry Type` from the drop-down "
"list."
msgstr ""

#: ../../content/applications/hr/time_off.rst:178
msgid "Timesheets section"
msgstr ""

#: ../../content/applications/hr/time_off.rst:181
msgid ""
"The :guilabel:`Timesheets` section only appears if the user is in developer "
"mode. Refer to the :ref:`developer-mode` document for details on how to "
"access the developer mode."
msgstr ""

#: ../../content/applications/hr/time_off.rst:184
msgid ""
"When an employee takes time off, and is also using timesheets, Odoo creates "
"entries in the **Timesheets** app for the time off. This section defines how"
" they are entered."
msgstr ""

#: ../../content/applications/hr/time_off.rst:187
msgid ""
":guilabel:`Project`: Select the project the time off type entries appear in."
msgstr ""

#: ../../content/applications/hr/time_off.rst:188
msgid ""
":guilabel:`Task`: Select the task that appears in the timesheet for this "
"time off type. The default options are: :guilabel:`Time Off`, "
":guilabel:`Meeting`, or :guilabel:`Training`."
msgstr ""

#: ../../content/applications/hr/time_off.rst:192
msgid "Display Option section"
msgstr ""

#: ../../content/applications/hr/time_off.rst:194
msgid ""
":guilabel:`Color`: Select a color to be used in the **Time Off** app "
"dashboard."
msgstr ""

#: ../../content/applications/hr/time_off.rst:195
msgid ""
":guilabel:`Cover Image`: Select an icon to be used in the **Time Off** app "
"dashboard."
msgstr ""

#: ../../content/applications/hr/time_off.rst-1
msgid ""
"The lower half of the time off type form, with all the information filled out for sick time\n"
"off."
msgstr ""

#: ../../content/applications/hr/time_off.rst:205
msgid "Accrual plans"
msgstr ""

#: ../../content/applications/hr/time_off.rst:207
msgid ""
"Some time off is earned through an accrual plan, meaning that for every "
"specified amount of time an employee works (hour, day, week, etc), they earn"
" or *accrue* a specified amount of time off."
msgstr ""

#: ../../content/applications/hr/time_off.rst:211
msgid ""
"If an employee accrues a vacation day for every week they work, they would "
"earn 0.2 vacation days for each hour they work. At the end of a forty hour "
"work week, they would earn one whole vacation day (8 hours)."
msgstr ""

#: ../../content/applications/hr/time_off.rst:216
msgid "Create accrual plan"
msgstr ""

#: ../../content/applications/hr/time_off.rst:218
msgid ""
"To create a new accrual plan, navigate to :menuselection:`Time Off app --> "
"Configuration --> Accrual Plans`. Then, click the :guilabel:`New` button, "
"which reveals a blank accrual plan form."
msgstr ""

#: ../../content/applications/hr/time_off.rst:223
msgid ":guilabel:`Name`: Enter the accrual plan name."
msgstr ""

#: ../../content/applications/hr/time_off.rst:224
msgid ""
":guilabel:`Accrued Gain Time`: Select when the employee begins to accrue "
"time off, either :guilabel:`At the start of the accrual period` or "
":guilabel:`At the end of the accrual period`."
msgstr ""

#: ../../content/applications/hr/time_off.rst:226
msgid ""
":guilabel:`Carry-Over Time`: Select when the employee received previously "
"earned time. The options are:"
msgstr ""

#: ../../content/applications/hr/time_off.rst:229
msgid ""
":guilabel:`At the start of the year`: Select this if the accrual rolls over "
"on January 1 of the upcoming year."
msgstr ""

#: ../../content/applications/hr/time_off.rst:231
msgid ""
":guilabel:`At the allocation date`: Select this if the accrual rolls over as"
" soon as time is allocated to the employee."
msgstr ""

#: ../../content/applications/hr/time_off.rst:233
msgid ""
":guilabel:`Other`: Select this option if neither of the other two options "
"are applicable. When selected, a :guilabel:`Carry-Over Date` field appears. "
"Select the date using the two drop-down menus, one for the day and one for "
"the month."
msgstr ""

#: ../../content/applications/hr/time_off.rst:237
msgid ""
":guilabel:`Based on worked time`: Enable this option if time off accrual is "
"determined by the employee's worked hours. Days **not** considered as worked"
" time do **not** contribute to the accrual plan in Odoo."
msgstr ""

#: ../../content/applications/hr/time_off.rst:242
msgid ""
"An employee is granted time off from an accrual plan configured to accrue "
"one day of vacation for every five days worked. The accrual plan is based on"
" the employee's worked time (the :guilabel:`Based on worked time` checkbox "
"is ticked)."
msgstr ""

#: ../../content/applications/hr/time_off.rst:246
msgid ""
"The employee works standard 40-hour weeks. According to the accrual plan, "
"they should earn four vacation days per month."
msgstr ""

#: ../../content/applications/hr/time_off.rst:249
msgid ""
"The employee takes five days off. The :ref:`time off type <time_off/time-"
"off-types>` the employee has taken has the :guilabel:`Kind of Time Off` "
"configured as an :guilabel:`Absence`."
msgstr ""

#: ../../content/applications/hr/time_off.rst:252
msgid ""
"Since the accrual plan only grants time off based on the worked time, the "
"employee does **not** accrue a vacation day for the five days of time off "
"that is considered an absence."
msgstr ""

#: ../../content/applications/hr/time_off.rst:255
msgid ""
"At the end of the month, the employee accrues only three days, instead of "
"four."
msgstr ""

#: ../../content/applications/hr/time_off.rst:257
msgid ""
":guilabel:`Milestone Transition`: This field is **only** visible after a "
"minimum of two :ref:`rules <time_off/rules>` have been configured on the "
"accrual plan. This selection determines when employees move up to a new "
"milestone. If they qualify to change milestones in the middle of a pay "
"period, decide whether the employee changes milestones "
":guilabel:`Immediately` or :guilabel:`After this accrual's period` (after "
"the current pay period)."
msgstr ""

#: ../../content/applications/hr/time_off.rst:262
msgid ""
":guilabel:`Company`: This field **only** appears in a multi-company "
"database. Using the drop-down menu, select the company the accrual plan "
"applies to. If left blank, the accrual plan can be used for all companies."
msgstr ""

#: ../../content/applications/hr/time_off.rst-1
msgid "An accrual plan form with all the entries filled out."
msgstr ""

#: ../../content/applications/hr/time_off.rst:275
msgid ""
"Rules must be created in order for employees to accrue time off from the "
"accrual plan."
msgstr ""

#: ../../content/applications/hr/time_off.rst:277
msgid ""
"To create a new rule, click the :guilabel:`New Milestone` button in the gray"
" :guilabel:`Rules` section, and a :guilabel:`Create Milestone` modal form "
"appears."
msgstr ""

#: ../../content/applications/hr/time_off.rst:282
msgid ""
":guilabel:`Employee accrue`: Select the parameters for earned time off in "
"this section."
msgstr ""

#: ../../content/applications/hr/time_off.rst:284
msgid ""
"First, select either :guilabel:`Days` or :guilabel:`Hours` for the increment"
" of accrued time using the drop-down menu."
msgstr ""

#: ../../content/applications/hr/time_off.rst:287
msgid ""
"Next, enter the numerical amount of the selected parameter that is accrued. "
"The numerical format is `X.XXXX`, so that partial days or hours can also be "
"configured."
msgstr ""

#: ../../content/applications/hr/time_off.rst:290
msgid ""
"Last, select how often the time is accrued using the drop-down menu. The "
"default options are :guilabel:`Hourly`, :guilabel:`Daily`, "
":guilabel:`Weekly`, :guilabel:`Twice a month`, :guilabel:`Monthly`, "
":guilabel:`Twice a year`, and :guilabel:`Yearly`."
msgstr ""

#: ../../content/applications/hr/time_off.rst:294
msgid ""
"Depending on which option is selected, additional fields may appear. For "
"example, if :guilabel:`Twice a month` is selected, two additional fields "
"appear, to specify the two days of each month the milestone occurs."
msgstr ""

#: ../../content/applications/hr/time_off.rst:297
msgid ""
":guilabel:`Cap accrued time`: If there is a maximum amount of days the "
"employee can accrue with this plan, enable this option."
msgstr ""

#: ../../content/applications/hr/time_off.rst:300
msgid ""
"When enabled, two additional fields appear beneath it. Select the type of "
"time period from the drop-down menu, either :guilabel:`Days` or "
":guilabel:`Hours`."
msgstr ""

#: ../../content/applications/hr/time_off.rst:303
msgid ""
"Then, enter a numerical value in the field to specify the maximum amount of "
"time that can be accrued."
msgstr ""

#: ../../content/applications/hr/time_off.rst:305
msgid ""
":guilabel:`Milestone reached`: Enter the number and value of the time period"
" that must pass before the employee starts to accumulate time off. The first"
" value is numerical; enter a number in the first field."
msgstr ""

#: ../../content/applications/hr/time_off.rst:309
msgid ""
"Then, select the type of time period using the drop-down menu in the second "
"field. The options are: :guilabel:`Days`, :guilabel:`Months`, or "
":guilabel:`Years`."
msgstr ""

#: ../../content/applications/hr/time_off.rst:311
msgid ""
":guilabel:`Carry over`: select how any unused time off is handled. The "
"options are either:"
msgstr ""

#: ../../content/applications/hr/time_off.rst:313
msgid ""
":guilabel:`None. Accrued time reset to 0`: Any unused time off is gone."
msgstr ""

#: ../../content/applications/hr/time_off.rst:314
msgid ""
":guilabel:`All accrued time carried over`: All unused time off is rolled "
"over to the next calendar year."
msgstr ""

#: ../../content/applications/hr/time_off.rst:316
msgid ""
":guilabel:`Carry over with a maximum`: Unused time off is rolled over to the"
" next calendar year, but there is a cap. An :guilabel:`Up to` field appears "
"if this is selected. Enter the maximum number of :guilabel:`Days` that can "
"roll over to the following year. Any time off beyond this parameter is lost."
msgstr ""

#: ../../content/applications/hr/time_off.rst:322
msgid ""
"If the :guilabel:`Carry over` field is set to :guilabel:`None. Accrued time "
"reset to 0`, that rule *overrides* the :guilabel:`Carry-Over Time` set on "
"the accrual plan."
msgstr ""

#: ../../content/applications/hr/time_off.rst:325
msgid ""
"If a company creates an accrual plan, granting employees time off "
":guilabel:`At the start of the accrual period` (i.e., the beginning of the "
"year), and sets the :guilabel:`Carry-Over Time` on the *accrual plan* to "
":guilabel:`At the start of the year`, it allows unused vacation time to "
"rollover to the following year."
msgstr ""

#: ../../content/applications/hr/time_off.rst:330
msgid ""
"Then, the company adds rules to the accrual plan, allocating five days of "
"vacation, annually, on the first of the year (one week of vacation allocated"
" on January 1st)."
msgstr ""

#: ../../content/applications/hr/time_off.rst:333
msgid ""
"If the :guilabel:`Carry over` field is set to :guilabel:`None. Accrual time "
"reset to 0` on the :guilabel:`Create Milestone` pop-up for, any unused "
"vacation time *does not* carry over, even though on the :guilabel:`Accrual "
"Plan` form, the :guilabel:`Carry-Over Time` is set to :guilabel:`At the "
"start of the year`."
msgstr ""

#: ../../content/applications/hr/time_off.rst:338
msgid ""
"The carry over set on the *rule* takes precedence over the carry over set on"
" the *accrual plan form*."
msgstr ""

#: ../../content/applications/hr/time_off.rst:341
msgid ""
"Once the form is completed, click :guilabel:`Save & Close` to save the "
":guilabel:`Create Milestone` form, and close the modal, or click "
":guilabel:`Save & New` to save the form and create another milestone. Add as"
" many milestones as desired."
msgstr ""

#: ../../content/applications/hr/time_off.rst-1
msgid "A milestone form with all the entries filled out."
msgstr ""

#: ../../content/applications/hr/time_off.rst:352
msgid "Public holidays"
msgstr ""

#: ../../content/applications/hr/time_off.rst:354
msgid ""
"To observe public or national holidays, and provide extra days off as "
"holidays to employees, configure the observed *public holidays* in Odoo."
msgstr ""

#: ../../content/applications/hr/time_off.rst:357
msgid ""
"It is important to configure these days in Odoo, so employees are aware of "
"the days they have off, and do not request time off on days that are already"
" set as a public holiday (non-working days)."
msgstr ""

#: ../../content/applications/hr/time_off.rst:360
msgid ""
"Additionally, all public holidays configured in the **Time Off** app are "
"also reflected in any app that uses working schedules, such as **Calendar**,"
" **Planning**, **Manufacturing**, and more."
msgstr ""

#: ../../content/applications/hr/time_off.rst:363
msgid ""
"Due to Odoo's integration with other apps that use working schedules, it is "
"considered best practice to ensure *all* public holidays are configured."
msgstr ""

#: ../../content/applications/hr/time_off.rst:367
msgid "Create public holiday"
msgstr ""

#: ../../content/applications/hr/time_off.rst:369
msgid ""
"To create a public holiday, navigate to :menuselection:`Time Off app --> "
"Configuration --> Public Holidays`."
msgstr ""

#: ../../content/applications/hr/time_off.rst:372
msgid "All currently configured public holidays appear in a list view."
msgstr ""

#: ../../content/applications/hr/time_off.rst:374
msgid ""
"Click the :guilabel:`New` button, and a new line appears at the bottom of "
"the list."
msgstr ""

#: ../../content/applications/hr/time_off.rst:376
#: ../../content/applications/hr/time_off.rst:439
msgid "Enter the following information on that new line:"
msgstr ""

#: ../../content/applications/hr/time_off.rst:378
msgid ":guilabel:`Name`: Enter the name of the holiday."
msgstr ""

#: ../../content/applications/hr/time_off.rst:379
msgid ""
":guilabel:`Company`: If in a multi-company database, the current company "
"populates this field by default. It is **not** possible to edit this field."
msgstr ""

#: ../../content/applications/hr/time_off.rst:383
msgid ""
"The :guilabel:`Company` field is hidden, by default. To view this field, "
"click the :icon:`oi-settings-adjust` :guilabel:`(additional options)` icon "
"in the top-right corner of the list, to the far-right of the column titles, "
"and activate the :guilabel:`Company` selection from the drop-down menu that "
"appears."
msgstr ""

#: ../../content/applications/hr/time_off.rst:388
msgid ""
":guilabel:`Start Date`: Using the date and time picker, select the date and "
"time the holiday starts, then click :icon:`fa-check` :guilabel:`Apply`. By "
"default, this field is configured for the current date. The start time is "
"set according to the start time for the company (according to the "
":ref:`working schedules <payroll/working-times>`). If the user's computer is"
" set to a different time zone, the start time is adjusted according, "
"compared to the company's time zone."
msgstr ""

#: ../../content/applications/hr/time_off.rst:393
msgid ""
":guilabel:`End Date`: Using the date and time picker, select the date and "
"time the holiday ends, then click :icon:`fa-check` :guilabel:`Apply`. By "
"default, this field is configured for the current date, and the time is set "
"to the end time for the company (according to the :ref:`working schedules "
"<payroll/working-times>`). If the user's computer is set to a different time"
" zone, the start time is adjusted accordingly, compared to the company's "
"time zone."
msgstr ""

#: ../../content/applications/hr/time_off.rst:400
msgid ""
"A company located in San Francisco operates from 9:00 AM - 6:00 PM, with an "
"eight hour work day and one hour lunch break."
msgstr ""

#: ../../content/applications/hr/time_off.rst:403
msgid ""
"For a user in New York, with a computer time zone set to Eastern Standard "
"Time, a created public holiday displays a start time of 12:00 PM - 9:00 PM, "
"accounting for the three hour time zone difference."
msgstr ""

#: ../../content/applications/hr/time_off.rst:407
msgid ""
"Similarly, a user located in Los Angeles, with a computer time zone set to "
"Pacific Standard Time, sees a public holiday time as 9:00 AM - 6:00 PM."
msgstr ""

#: ../../content/applications/hr/time_off.rst:410
msgid ""
":guilabel:`Working Hours`: If the holiday should only apply to employees who"
" have a specific set of working hours, select the working hours from the "
"drop-down menu. If left blank, the holiday applies to all employees."
msgstr ""

#: ../../content/applications/hr/time_off.rst:413
msgid ""
":guilabel:`Work Entry Type`: If using the **Payroll** app, this field "
"defines how the :ref:`work entries <payroll/work-entries>` for the holiday "
"appear. Select the work entry type from the drop-down menu."
msgstr ""

#: ../../content/applications/hr/time_off.rst-1
msgid "The list of public holidays in the configuration menu."
msgstr ""

#: ../../content/applications/hr/time_off.rst:422
msgid "Mandatory days"
msgstr ""

#: ../../content/applications/hr/time_off.rst:424
msgid ""
"Some companies have special days where specific departments, or the entire "
"staff, is required to be present, and time off is not allowed on those "
"specific days."
msgstr ""

#: ../../content/applications/hr/time_off.rst:427
msgid ""
"These types of days are called *mandatory days* in Odoo. These can be "
"configured to be company-wide, or department specific. When configured, "
"employees in the specified department or company are unable to submit time "
"off requests for these mandatory days."
msgstr ""

#: ../../content/applications/hr/time_off.rst:432
msgid "Create mandatory days"
msgstr ""

#: ../../content/applications/hr/time_off.rst:434
msgid ""
"No mandatory days are configured in Odoo by default. To create a mandatory "
"day, navigate to :menuselection:`Time Off app --> Configuration --> "
"Mandatory Days`."
msgstr ""

#: ../../content/applications/hr/time_off.rst:437
msgid ""
"Click the :guilabel:`New` button in the top-left corner, and a blank line "
"appears in the list."
msgstr ""

#: ../../content/applications/hr/time_off.rst:441
msgid ":guilabel:`Name`: Enter the name of the mandatory day."
msgstr ""

#: ../../content/applications/hr/time_off.rst:442
msgid ""
":guilabel:`Company`: If in a multi-company database, this field is visible, "
"and the current company populates this field, by default. Using the drop-"
"down menu, select the company the mandatory day is for."
msgstr ""

#: ../../content/applications/hr/time_off.rst:445
msgid ""
":guilabel:`Departments`: This column is hidden by default. First, click the "
":icon:`oi-settings-adjust` :guilabel:`(additional options)` icon in the top-"
"right corner, next to :guilabel:`Color`, and then tick the checkbox next to "
":guilabel:`Departments` to reveal that column."
msgstr ""

#: ../../content/applications/hr/time_off.rst:450
msgid ""
"Next, select the desired departments from the drop-down menu. Multiple "
"departments can be selected, and there is no limit to the amount of "
"departments that can be added."
msgstr ""

#: ../../content/applications/hr/time_off.rst:453
msgid ""
"If this field is left blank, the mandatory day applies to the entire "
"company."
msgstr ""

#: ../../content/applications/hr/time_off.rst:454
msgid ""
":guilabel:`Start Date`: Using the calendar picker, select the date the "
"mandatory day starts."
msgstr ""

#: ../../content/applications/hr/time_off.rst:455
msgid ""
":guilabel:`End Date`: Using the calendar picker, select the date the "
"mandatory day ends. If creating a single mandatory day, the end date should "
"be the same as the start date."
msgstr ""

#: ../../content/applications/hr/time_off.rst:457
msgid ""
":guilabel:`Color`: If desired, select a color from the available presented "
"options. If no color is desired, select the `No color` option, represented "
"by a white box with a red line diagonally across it. The selected color "
"appears on the main **Time Off** app dashboard, in both the calendar and in "
"the legend."
msgstr ""

#: ../../content/applications/hr/time_off.rst-1
msgid "The Mandatory Days section with three configured days."
msgstr ""

#: ../../content/applications/hr/time_off.rst:469
msgid ""
"To view a color-coded schedule of the user's time off, and/or of the team "
"managed by them, navigate to :menuselection:`Time Off app --> Overview`. "
"This presents a calendar with the default filter of `My Team`, in a month "
"view."
msgstr ""

#: ../../content/applications/hr/time_off.rst:473
msgid ""
"To change the time period displayed, click on the :guilabel:`Month` button "
"to reveal a drop-down menu. Then, select either :guilabel:`Day`, "
":guilabel:`Week`, or :guilabel:`Year` to present the calendar in that "
"corresponding view."
msgstr ""

#: ../../content/applications/hr/time_off.rst:477
msgid ""
"To navigate forward or backward in time, in the selected increment "
"(:guilabel:`Month`, :guilabel:`Week`, etc.), click the :guilabel:`← (left "
"arrow)` or :guilabel:`→ (right arrow)` to move either forward or backward in"
" that specified amount of time."
msgstr ""

#: ../../content/applications/hr/time_off.rst:481
msgid ""
"For example, if :guilabel:`Month` is selected, the arrows adjust the view by"
" one month."
msgstr ""

#: ../../content/applications/hr/time_off.rst:483
msgid ""
"To return to a view containing the current day, click the :guilabel:`Today` "
"button at any time."
msgstr ""

#: ../../content/applications/hr/time_off.rst:485
msgid ""
"Team members are listed alphabetically on individual lines, and their "
"requested time off, regardless of the status (*validated* or *to approve*), "
"is visible on the calendar."
msgstr ""

#: ../../content/applications/hr/time_off.rst:488
msgid ""
"Each employee is color-coded. The employee's color is selected at random, "
"and does *not* correspond to the type of time off they requested."
msgstr ""

#: ../../content/applications/hr/time_off.rst:491
msgid ""
"The status of the time off is represented by the color detail of the "
"request, either appearing solid (*validated*) or striped (*to approve*)."
msgstr ""

#: ../../content/applications/hr/time_off.rst:494
msgid ""
"The number of days or hours requested is written on the request (if there is"
" enough space)."
msgstr ""

#: ../../content/applications/hr/time_off.rst:496
msgid ""
"At the bottom of the calendar, in the :guilabel:`Total` line, a bar graph "
"shows how many people are projected to be out on any given day. The number "
"on each individual bar represents the number of employees out for those "
"highlighted days."
msgstr ""

#: ../../content/applications/hr/time_off.rst:500
msgid ""
"Click on a time off entry to view the details for the specific time off "
"entry. The total number of hours or days are listed, along with the start "
"and end time of the time off. To view the details of the time off request in"
" a modal, click the :guilabel:`View` button."
msgstr ""

#: ../../content/applications/hr/time_off.rst-1
msgid "Overview of the user's team, with time off requests shown."
msgstr ""

#: ../../content/applications/hr/time_off.rst:513
msgid ""
"The reporting feature allows users to view time off for their team, either "
"by employee or type of time off. This allows users to see which employees "
"are taking time off, how much time off they are taking, and what time off "
"types are being used."
msgstr ""

#: ../../content/applications/hr/time_off.rst:517
msgid ""
"Any report can be added to a spreadsheet, when in either the :icon:`fa-area-"
"chart` :guilabel:`(Graph)` or :icon:`oi-view-pivot` :guilabel:`(Pivot)` "
"view, through the *Insert in Spreadsheet* button that appears in the top-"
"left of the report."
msgstr ""

#: ../../content/applications/hr/time_off.rst:522
msgid ""
"If the **Documents** app is installed, an option to add the report to a "
"spreadsheet appears. If not, the report can be added to a *Dashboard*."
msgstr ""

#: ../../content/applications/hr/time_off.rst:526
msgid "By employee"
msgstr ""

#: ../../content/applications/hr/time_off.rst:528
msgid ""
"To view a report of employee time off requests, navigate to "
":menuselection:`Time Off app --> Reporting --> by Employee`."
msgstr ""

#: ../../content/applications/hr/time_off.rst:531
msgid ""
"The default report presents the current year's data in a list view, "
"displaying all the employees in alphabetical order. Each employee's line is "
"collapsed by default. To expand a line, click anywhere on the line."
msgstr ""

#: ../../content/applications/hr/time_off.rst:535
msgid ""
"The view expands, and has the time off requests organized by time off type. "
"Click anywhere on a time off type line to expand it, and view all the "
"individual time off requests that fall under that type."
msgstr ""

#: ../../content/applications/hr/time_off.rst:538
msgid ""
"The information shown in the list includes: the :guilabel:`Employee` name, "
":guilabel:`Number of Days` off requested, the :guilabel:`Start Date`, "
":guilabel:`End Date`, :guilabel:`Status`, and :guilabel:`Description`."
msgstr ""

#: ../../content/applications/hr/time_off.rst-1
msgid "Report of time off, shown by each employee in a list view."
msgstr ""

#: ../../content/applications/hr/time_off.rst:546
msgid ""
"The report can be displayed in other ways, as well. Click the corresponding "
"button option in the top-right corner of the page to view the data in that "
"specific way. The various options are a :icon:`oi-view-list` "
":guilabel:`(List)`, or default view, :icon:`fa-area-chart` "
":guilabel:`(Graph)`, :icon:`oi-view-pivot` :guilabel:`(Pivot)` table, or "
":icon:`fa-calendar` :guilabel:`(Calendar)` view."
msgstr ""

#: ../../content/applications/hr/time_off.rst:551
msgid ""
"When a selection has been made, additional options appear for that "
"particular selection. For more detailed information on the reports and their"
" various options, refer to the :doc:`reporting <../essentials/reporting>` "
"documentation."
msgstr ""

#: ../../content/applications/hr/time_off.rst:556
msgid "By type"
msgstr "לפי סוג"

#: ../../content/applications/hr/time_off.rst:558
msgid ""
"To view a list of all time off, organized by time off type, navigate to "
":menuselection:`Time Off app --> Reporting --> by Type`. This shows all time"
" off requests in a default bar chart."
msgstr ""

#: ../../content/applications/hr/time_off.rst:561
msgid ""
"Hover over a bar to view the :guilabel:`Duration (Days)` of that specific "
"time off type."
msgstr ""

#: ../../content/applications/hr/time_off.rst-1
msgid ""
"The various time off types, and how many days requested, in a bar chart. Details are\n"
"highlighted in a red box."
msgstr ""

#: ../../content/applications/hr/time_off.rst:568
msgid ""
"Click on a bar to go to a detailed list view of all the time off requests "
"for that time off type."
msgstr ""

#: ../../content/applications/hr/time_off.rst:570
msgid ""
"Each request is listed, with the following information displayed: the "
":guilabel:`Employee`, :guilabel:`Number of Days`, :guilabel:`Request Type`, "
":guilabel:`Start Date`, :guilabel:`End Date`, :guilabel:`Status`, and the "
":guilabel:`Description`."
msgstr ""

#: ../../content/applications/hr/time_off.rst:574
msgid ""
"The report can be displayed in other ways, as well. Click the corresponding "
"button option in the top-right corner of the page to view the data in that "
"way. The various options are a :icon:`fa-area-chart` :guilabel:`(Graph)` "
"(the default view), :icon:`oi-view-list` :guilabel:`(List)`, or :icon:`oi-"
"view-pivot` :guilabel:`(Pivot)` table."
msgstr ""

#: ../../content/applications/hr/time_off.rst:579
msgid ""
"When a selection has been made, additional options appear for that "
"particular selection. For more detailed information on the reports, and "
"their various options, refer to the :doc:`reporting "
"<../essentials/reporting>` documentation."
msgstr ""

#: ../../content/applications/hr/time_off.rst:584
msgid ":doc:`time_off/allocations`"
msgstr ""

#: ../../content/applications/hr/time_off.rst:585
msgid ":doc:`time_off/request_time_off`"
msgstr ""

#: ../../content/applications/hr/time_off.rst:586
msgid ":doc:`time_off/my_time`"
msgstr ""

#: ../../content/applications/hr/time_off.rst:587
msgid ":doc:`time_off/management`"
msgstr ""

#: ../../content/applications/hr/time_off/allocations.rst:3
msgid "Allocations"
msgstr "הקצאות"

#: ../../content/applications/hr/time_off/allocations.rst:5
msgid ""
"Once :ref:`time off types <time_off/time-off-types>` and :ref:`accrual plans"
" <time_off/accrual-plans>` have been configured, the next step is to "
"*allocate*, or give, time off to employees."
msgstr ""

#: ../../content/applications/hr/time_off/allocations.rst:9
msgid ""
"The *Allocations* page of the **Time Off** app is **only** visible to users "
"who have either *Time Off Officer* or *Administrator* access rights for the "
"**Time Off** application. For more information on access rights, refer to "
"the :doc:`access rights <../../general/users/access_rights/>` documentation."
msgstr ""

#: ../../content/applications/hr/time_off/allocations.rst:15
msgid "Allocate time off"
msgstr ""

#: ../../content/applications/hr/time_off/allocations.rst:17
msgid ""
"To create a new allocation, navigate to :menuselection:`Time Off app --> "
"Management --> Allocations`."
msgstr ""

#: ../../content/applications/hr/time_off/allocations.rst:20
msgid ""
"This presents a list of all current allocations, including their respective "
"statuses."
msgstr ""

#: ../../content/applications/hr/time_off/allocations.rst:22
msgid ""
"Click :guilabel:`New` to allocate time off, and a blank allocation form "
"appears."
msgstr ""

#: ../../content/applications/hr/time_off/allocations.rst:24
msgid ""
"After entering a name for the allocation on the first blank field of the "
"form, enter the following information:"
msgstr ""

#: ../../content/applications/hr/time_off/allocations.rst:27
msgid ""
":guilabel:`Time Off Type`: Using the drop-down menu, select the type of time"
" off that is being allocated to the employees."
msgstr ""

#: ../../content/applications/hr/time_off/allocations.rst:29
msgid ""
":guilabel:`Allocation Type`: Select either :guilabel:`Regular Allocation` or"
" :guilabel:`Accrual Allocation`. If the allocation is **not** based on an "
":ref:`accrual plan <time_off/accrual-plans>`, select :guilabel:`Regular "
"Allocation`."
msgstr ""

#: ../../content/applications/hr/time_off/allocations.rst:32
msgid ""
":guilabel:`Accrual Plan`: If :guilabel:`Accrual Allocation` is selected for "
"the :guilabel:`Allocation Type`, the :guilabel:`Accrual Plan` field appears."
" Using the drop-down menu, select the accrual plan with which the allocation"
" is associated. An accrual plan **must** be selected for an "
":guilabel:`Accrual Allocation`."
msgstr ""

#: ../../content/applications/hr/time_off/allocations.rst:36
msgid ""
":guilabel:`Validity Period/Start Date`: If :guilabel:`Regular Allocation` is"
" selected for the :guilabel:`Allocation Type`, this field is labeled "
":guilabel:`Validity Period`. If :guilabel:`Accrual Allocation` is selected "
"for the :guilabel:`Allocation Type`, this field is labeled :guilabel:`Start "
"Date`."
msgstr ""

#: ../../content/applications/hr/time_off/allocations.rst:41
msgid ""
"The current date populates the first date field, by default. To select "
"another date, click on the pre-populated date to reveal a popover calendar "
"window. Navigate to the desired start date for the allocation, and click on "
"the date to select it."
msgstr ""

#: ../../content/applications/hr/time_off/allocations.rst:45
msgid ""
"If the allocation expires, select the expiration date in the next date "
"field. If the time off does *not* expire, leave the second date field blank."
" :guilabel:`No Limit` appears in the field if no date is selected."
msgstr ""

#: ../../content/applications/hr/time_off/allocations.rst:49
msgid ""
"If :guilabel:`Accrual Allocation` is selected for the :guilabel:`Allocation "
"Type`, this second field is labeled :guilabel:`Run until`."
msgstr ""

#: ../../content/applications/hr/time_off/allocations.rst:53
msgid ""
"If the :guilabel:`Start Date` entered is in the middle of a period of time, "
"such as the middle of the month, Odoo applies the allocation to the "
"beginning or end of the period, depending on the *Accrued Gain Time* entered"
" on the :ref:`accrual plan <time_off/accrual-plans>` (either *At the start "
"of the accrual period*, or *At the end of the accrual period*) instead of "
"the specific date entered."
msgstr ""

#: ../../content/applications/hr/time_off/allocations.rst:59
msgid ""
"For example, an allocation is created, and references an accrual plan that "
"grants time *At the start of the accrual period*, monthly, on the first of "
"the month."
msgstr ""

#: ../../content/applications/hr/time_off/allocations.rst:62
msgid ""
"On the allocation form, the :guilabel:`Allocation Type` is set to "
":guilabel:`Accrual Allocation`, and the :guilabel:`Start Date` entered is "
"`06/16/24`."
msgstr ""

#: ../../content/applications/hr/time_off/allocations.rst:65
msgid ""
"Odoo's **Time Off** app retroactively applies the allocation to the "
"beginning of the time period entered in the :guilabel:`Start Date`."
msgstr ""

#: ../../content/applications/hr/time_off/allocations.rst:68
msgid ""
"Therefore, this allocation accrues time from `06/01/24`, rather than "
"`06/16/24`."
msgstr ""

#: ../../content/applications/hr/time_off/allocations.rst:70
msgid ""
"Additionally, if on the accrual form, the allocation references an accrual "
"plan that grants time *`At the end of the accrual period*, the allocation "
"accrues time from `7/01/24` rather than `6/18/24`."
msgstr ""

#: ../../content/applications/hr/time_off/allocations.rst:74
msgid ""
":guilabel:`Allocation`: Enter the amount of time that is being allocated to "
"the employees. This field displays the time in either :guilabel:`Hours` or "
":guilabel:`Days`, depending on how the selected :ref:`Time Off Type "
"<time_off/time-off-types>` is configured."
msgstr ""

#: ../../content/applications/hr/time_off/allocations.rst:77
msgid ""
":guilabel:`Mode`: Using the drop-down menu, select how the allocation is "
"assigned. This selection determines who receives the time off allocation. "
"The options are :guilabel:`By Employee`, :guilabel:`By Company`, "
":guilabel:`By Department`, or :guilabel:`By Employee Tag`."
msgstr ""

#: ../../content/applications/hr/time_off/allocations.rst:81
msgid ""
"Depending on what is selected for the :guilabel:`Mode`, the field beneath "
":guilabel:`Mode` is labeled either: :guilabel:`Employees`, "
":guilabel:`Company`, :guilabel:`Department`, or :guilabel:`Employee Tag`."
msgstr ""

#: ../../content/applications/hr/time_off/allocations.rst:85
msgid ""
"Using the drop-down menu, indicate the specific employees, company, "
"department, or employee tags receiving this time off."
msgstr ""

#: ../../content/applications/hr/time_off/allocations.rst:88
msgid ""
"Multiple selections can be made for either :guilabel:`Employees` or "
":guilabel:`Employee Tag`."
msgstr ""

#: ../../content/applications/hr/time_off/allocations.rst:90
msgid ""
"Only one selection can be made for the :guilabel:`Company` or "
":guilabel:`Department`."
msgstr ""

#: ../../content/applications/hr/time_off/allocations.rst:91
msgid ""
":guilabel:`Add a reason...`: If any description or note is necessary to "
"explain the time off allocation, enter it in this field at the bottom of the"
" form."
msgstr ""

#: ../../content/applications/hr/time_off/allocations.rst-1
msgid ""
"A new allocation form with all the fields filled out for the annual two week vacation\n"
"granted to all employees."
msgstr ""

#: ../../content/applications/hr/time_off/allocations.rst:102
msgid "Request allocation"
msgstr ""

#: ../../content/applications/hr/time_off/allocations.rst:104
msgid ""
"If an employee has used all their time off, or will run out of time off, "
"they can request an allocation for additional time. Allocations can be "
"requested in one of two ways, either from the :ref:`Dashboard "
"<time_off/dashboard>` or the :ref:`My Allocations <time_off/my-allocations>`"
" view."
msgstr ""

#: ../../content/applications/hr/time_off/allocations.rst:108
msgid ""
"To create a new allocation request, click either the :guilabel:`New "
"Allocation Request` button on the main **Time Off** dashboard, or the "
":guilabel:`New` button in the :guilabel:`My Allocations` list view. Both "
"buttons open a new allocation request form."
msgstr ""

#: ../../content/applications/hr/time_off/allocations.rst:113
msgid ""
"Both options open a new allocation request form, but when requested from the"
" :guilabel:`Dashboard`, the form appears in a pop-up window, and the "
"*Validity Period* field does **not** appear. When requested from the "
":guilabel:`My Allocations` list view, the screen navigates to a new "
"allocation request page, instead of presenting a pop-up window."
msgstr ""

#: ../../content/applications/hr/time_off/allocations.rst:118
msgid "Enter the following information on the new allocation request form:"
msgstr ""

#: ../../content/applications/hr/time_off/allocations.rst:120
msgid ""
":guilabel:`Time Off Type`: Select the type of time off being requested for "
"the allocation from the drop-down menu. After a selection is made, the title"
" updates with the time off type."
msgstr ""

#: ../../content/applications/hr/time_off/allocations.rst:122
msgid ""
":guilabel:`Validity Period`: By default, the current date populates this "
"field, and it is **not** able to be modified. This field **only** appears "
"when requesting an allocatoin from the :guilabel:`My Allocations` view "
"(:menuselection:`Time Off --> My Time --> My Allocations`)."
msgstr ""

#: ../../content/applications/hr/time_off/allocations.rst:125
msgid ""
":guilabel:`Allocation`: Enter the amount of time being requested in this "
"field. The format is presented in either :guilabel:`Days` or "
":guilabel:`Hours`, depending on how the :guilabel:`Time Off Type` is "
"configured. Once this field is populated, the name of the allocation request"
" is updated to include the amount of time being requested."
msgstr ""

#: ../../content/applications/hr/time_off/allocations.rst:129
msgid ""
":guilabel:`Add a reason...`: Enter a description for the allocation request "
"in this field. This should include any details that approvers may need to "
"approve the request."
msgstr ""

#: ../../content/applications/hr/time_off/allocations.rst:132
msgid ""
"If the request was created from the :guilabel:`Dashboard`, click the "
":guilabel:`Save & Close` button on the :guilabel:`New Allocation` pop-up "
"window to save the information and submit the request."
msgstr ""

#: ../../content/applications/hr/time_off/allocations.rst:135
msgid ""
"If the form was completed from the :guilabel:`My Allocations` list view, the"
" information is automatically saved as it is entered. However, the form can "
"be saved manually at any time by clicking the :icon:`fa-cloud-upload` "
":guilabel:`(cloud upload)` icon."
msgstr ""

#: ../../content/applications/hr/time_off/allocations.rst-1
msgid ""
"An allocation request form filled out for an employee requesting an additional week of\n"
"sick time."
msgstr ""

#: ../../content/applications/hr/time_off/management.rst:3
msgid "Management"
msgstr "ניהול"

#: ../../content/applications/hr/time_off/management.rst:7
msgid ""
"Time off and allocation requests undergo an approval process before being "
"granted. Requests either need one or two approvals, if any, depending on how"
" the specific type of time off is configured. All these configurations can "
"be found under the *Management* section of the *Time Off* application."
msgstr ""

#: ../../content/applications/hr/time_off/management.rst:11
msgid ""
"Only people who can approve allocation and time off requests have the "
":guilabel:`Management` section visible in the *Time Off* application."
msgstr ""

#: ../../content/applications/hr/time_off/management.rst:17
msgid "Manage time off"
msgstr ""

#: ../../content/applications/hr/time_off/management.rst:19
msgid ""
"To view time off requests that need approval, navigate to "
":menuselection:`Time Off app --> Management --> Time Off`. Doing so reveals "
"the :guilabel:`All Time Off` page."
msgstr ""

#: ../../content/applications/hr/time_off/management.rst:22
msgid ""
"The only time off requests that are visible on this page belong to employees"
" the user either has :guilabel:`Time Off Officer` or "
":guilabel:`Administrator` access rights for in the *Time Off* application."
msgstr ""

#: ../../content/applications/hr/time_off/management.rst:26
msgid ""
"The default filter on the :guilabel:`All Time Off` page is `Waiting For Me`."
msgstr ""

#: ../../content/applications/hr/time_off/management.rst:28
msgid ""
"This filter only presents time off requests that need to be approved for "
"current employees on the user's team, with a status of either :guilabel:`To "
"Approve` or :guilabel:`Second Approval`."
msgstr ""

#: ../../content/applications/hr/time_off/management.rst:31
msgid ""
"On the left side of the :guilabel:`All Time Off` page, there are various "
"grouping options that can be used to narrow down the presented time off "
"requests, located beneath the :guilabel:`Status` and :guilabel:`Department` "
"headings."
msgstr ""

#: ../../content/applications/hr/time_off/management.rst:35
msgid ""
"Since only time off requests that need to be approved are shown, the only "
":guilabel:`Status` options are :guilabel:`All`, :guilabel:`To Approve`, and "
":guilabel:`Second Approval`."
msgstr ""

#: ../../content/applications/hr/time_off/management.rst:38
msgid ""
"The various departments the user is a member of, and manages employees "
"under, also appear on the left side of the page, under "
":guilabel:`Departments`."
msgstr ""

#: ../../content/applications/hr/time_off/management.rst:42
msgid ""
"If there are no requests that fall under one of the status options or "
"departments, that status or department is **not** visible on the left-side "
"menu."
msgstr ""

#: ../../content/applications/hr/time_off/management.rst:45
msgid ""
"To only display time off requests for specific departments, click on the "
":guilabel:`Department` on the left-hand side of the page. Only requests "
"within the selected department are then presented."
msgstr ""

#: ../../content/applications/hr/time_off/management.rst:48
#: ../../content/applications/hr/time_off/management.rst:127
msgid ""
"The status column displays the status of each request, with the status "
"highlighted in a specific color."
msgstr ""

#: ../../content/applications/hr/time_off/management.rst:51
msgid ""
"The :guilabel:`To Approve` and :guilabel:`Second Approval` requests are "
"highlighted in yellow, and are the only ones that appear in the list by "
"default."
msgstr ""

#: ../../content/applications/hr/time_off/management.rst:54
msgid "If the `Waiting For Me` filter is removed, all statuses appear."
msgstr ""

#: ../../content/applications/hr/time_off/management.rst:56
msgid ""
":guilabel:`Approved` requests are highlighted in green, :guilabel:`To "
"Submit` (drafts) requests are highlighted in blue, and the "
":guilabel:`Refused` requests are highlighted in gray."
msgstr ""

#: ../../content/applications/hr/time_off/management.rst:59
msgid ""
"To approve a time off request, click the :icon:`fa-thumbs-up` "
":guilabel:`Approve` button at the end of the line."
msgstr ""

#: ../../content/applications/hr/time_off/management.rst:62
msgid ""
"To validate a time off request that has already been approved, and is "
"waiting on a second approval, click the :icon:`fa-check` "
":guilabel:`Validate` button at the end of the line."
msgstr ""

#: ../../content/applications/hr/time_off/management.rst:65
msgid ""
"To refuse a request, click the :icon:`fa-times` :guilabel:`Refuse` button at"
" the far end of the line."
msgstr ""

#: ../../content/applications/hr/time_off/management.rst-1
msgid ""
"Time off requests with the filter, groupings, and status sections "
"highlighted."
msgstr ""

#: ../../content/applications/hr/time_off/management.rst:72
msgid ""
"For more details, click anywhere on the time off request line (except for "
"the :icon:`fa-thumbs-up` :guilabel:`Approve`, :icon:`fa-check` "
":guilabel:`Validate` icon, and :icon:`fa-times` :guilabel:`Refuse` buttons)."
" Doing so loads that specific time off request form. Depending on the rights"
" of the user, changes can be made."
msgstr ""

#: ../../content/applications/hr/time_off/management.rst:77
msgid ""
"To modify the request, make any desired changes to the form. All changes are"
" automatically saved."
msgstr ""

#: ../../content/applications/hr/time_off/management.rst:79
msgid ""
"It is also possible to approve, validate, or refuse the request from this "
"form. Click the :guilabel:`Approve` button to approve, the "
":guilabel:`Validate` button to validate, or the :guilabel:`Refuse` button to"
" refuse the request."
msgstr ""

#: ../../content/applications/hr/time_off/management.rst:86
msgid "Manage allocations"
msgstr ""

#: ../../content/applications/hr/time_off/management.rst:88
msgid ""
"To view allocations that need approval, navigate to :menuselection:`Time Off"
" app --> Management --> Allocations`. Doing so reveals the "
":guilabel:`Allocations` page."
msgstr ""

#: ../../content/applications/hr/time_off/management.rst:91
msgid ""
"The user is only presented with allocations for employees they have either "
":guilabel:`Time Off Officer` or :guilabel:`Administrator` access rights for "
"in the *Time Off* application."
msgstr ""

#: ../../content/applications/hr/time_off/management.rst:94
msgid ""
"The default filters configured on the :guilabel:`Allocations` page are "
":guilabel:`My Team` and :guilabel:`Active Employee`. These default filters "
"*only* present employees on the user's team (who they manage) and active "
"employees. Inactive records are not shown."
msgstr ""

#: ../../content/applications/hr/time_off/management.rst:98
msgid ""
"The left side of the :guilabel:`Allocations` page has various grouping "
"options to narrow down the presented allocation requests."
msgstr ""

#: ../../content/applications/hr/time_off/management.rst:101
msgid ""
"The :guilabel:`Status` options are: :guilabel:`All`, :guilabel:`To Approve`,"
" :guilabel:`Refused`, and :guilabel:`Approved`. Click on a specific "
":guilabel:`Status` to view only requests with that specific status."
msgstr ""

#: ../../content/applications/hr/time_off/management.rst:105
msgid ""
"To view all allocation requests, regardless of status, click :guilabel:`All`"
" under the :guilabel:`Status` heading."
msgstr ""

#: ../../content/applications/hr/time_off/management.rst:108
msgid ""
"It is also possible to display allocation requests by department. Click on "
"the desired :guilabel:`Department` on the left side of the "
":guilabel:`Allocations` page, to only present allocations for that specific "
"department."
msgstr ""

#: ../../content/applications/hr/time_off/management.rst:113
msgid ""
"The groupings on the left side **only** present allocation requests that "
"fall under the default filters of :guilabel:`My Team` and :guilabel:`Active "
"Employee`, if those default filters are not removed from the "
":guilabel:`Search...` bar. Only the statuses for allocation requests that "
"fall under those filters are presented on the left side."
msgstr ""

#: ../../content/applications/hr/time_off/management.rst:118
msgid ""
"For example, if there are no requests with a status of :guilabel:`To "
"Submit`, that status option does not appear in the left-hand side of the "
":guilabel:`Allocations` page."
msgstr ""

#: ../../content/applications/hr/time_off/management.rst:121
msgid ""
"All departments for the user's employees appear in the list. If there are no"
" allocation requests that fall under that department matching the "
"preconfigured filters, the list is blank."
msgstr ""

#: ../../content/applications/hr/time_off/management.rst:124
msgid ""
"It is always possible to remove any of the preconfigured filters, by "
"clicking the :icon:`fa-times` :guilabel:`(remove)` icon on the specific "
"filter to remove it."
msgstr ""

#: ../../content/applications/hr/time_off/management.rst:130
msgid ""
"The :guilabel:`To Approve` requests are highlighted in yellow, "
":guilabel:`Approved` requests are highlighted in green, and the "
":guilabel:`Refused` requests are highlighted in gray."
msgstr ""

#: ../../content/applications/hr/time_off/management.rst:133
msgid ""
"To approve an allocation request, click the :icon:`fa-check` "
":guilabel:`Validate` button at the end of the line. To refuse a request, "
"click the :icon:`fa-times` :guilabel:`Refuse` button."
msgstr ""

#: ../../content/applications/hr/time_off/management.rst-1
msgid ""
"Allocations with the filter, groupings, and status sections highlighted."
msgstr ""

#: ../../content/applications/hr/time_off/management.rst:140
msgid ""
"If more details are needed, click anywhere on the allocation request line "
"(except for the :icon:`fa-check` :guilabel:`Validate` or :icon:`fa-times` "
":guilabel:`Refuse` buttons) to view the specific request in detail, via the "
"allocation request form."
msgstr ""

#: ../../content/applications/hr/time_off/management.rst:144
msgid ""
"Depending on the rights of the user, changes can be made to the allocation "
"request form that appears. To modify the request, make any desired changes "
"to the form. All changes are automatically saved."
msgstr ""

#: ../../content/applications/hr/time_off/management.rst:148
msgid ""
"It is also possible to approve or refuse the request from this form. Click "
"the :guilabel:`Validate` button to approve, or the :guilabel:`Refuse` button"
" to refuse the request."
msgstr ""

#: ../../content/applications/hr/time_off/my_time.rst:3
msgid "My time"
msgstr ""

#: ../../content/applications/hr/time_off/my_time.rst:5
msgid ""
"The *My Time* menu of the *Time Off* application houses all the various time"
" off information for the signed-in user."
msgstr ""

#: ../../content/applications/hr/time_off/my_time.rst:8
msgid ""
"This includes the main *Time Off* dashboard, which displays an overview of "
"the various time off balances, as well as time-off requests and allocations."
msgstr ""

#: ../../content/applications/hr/time_off/my_time.rst:14
msgid "Dashboard"
msgstr "לוח בקרה"

#: ../../content/applications/hr/time_off/my_time.rst:16
msgid ""
"All users have access to the *Time Off* :guilabel:`Dashboard`, which is the "
"first page that appears when the *Time Off* application is opened. The "
":guilabel:`Dashboard` can also be accessed at any point in the application, "
"by navigating to :menuselection:`Time Off app --> My Time --> Dashboard`."
msgstr ""

#: ../../content/applications/hr/time_off/my_time.rst:20
msgid ""
"The current year is displayed, and the current day is highlighted in a red "
"circle."
msgstr ""

#: ../../content/applications/hr/time_off/my_time.rst:22
msgid ""
"To change the view, click on the :guilabel:`Year` button to reveal a drop-"
"down menu. Then, select either :guilabel:`Day`, :guilabel:`Week`, or "
":guilabel:`Month` to present the calendar in that corresponding view."
msgstr ""

#: ../../content/applications/hr/time_off/my_time.rst:27
msgid ""
"To change the displayed dates, click the :icon:`fa-arrow-left` "
":guilabel:`(left arrow)` or :icon:`fa-arrow-right` :guilabel:`(right arrow)`"
" icons to the left of the :guilabel:`Year` button. The calendar view adjusts"
" in increments of the selected view."
msgstr ""

#: ../../content/applications/hr/time_off/my_time.rst:31
msgid ""
"For example, if :guilabel:`Year` is selected, the arrows adjust the view by "
"one year."
msgstr ""

#: ../../content/applications/hr/time_off/my_time.rst:33
msgid ""
"To reset the view, so it includes the current date, click the "
":guilabel:`Today` button."
msgstr ""

#: ../../content/applications/hr/time_off/my_time.rst:35
msgid ""
"Above the calendar view is a summary of the user's time off balances. Every "
"time off type that has been allocated appears in its own summary box. Each "
"summary lists the type of time off, the corresponding icon, the current "
"available balance (in hours or days), and an expiration date (if "
"applicable)."
msgstr ""

#: ../../content/applications/hr/time_off/my_time.rst:40
msgid ""
"To view the full details of a time off balance, click the :icon:`fa-"
"question-circle-o` :guilabel:`(question mark)` icon at the end of the "
":guilabel:`(DAYS/HOURS) AVAILABLE` on the time off summary. The complete "
"details are presented in a popover window, including the "
":guilabel:`Allocated` time, :guilabel:`Accrual (Future)` time, "
":guilabel:`Approved` time off scheduled, :guilabel:`Planned` time off, and "
"the currently :guilabel:`Available` time off."
msgstr ""

#: ../../content/applications/hr/time_off/my_time.rst-1
msgid "A view of the complete time off balance details in the popover window."
msgstr ""

#: ../../content/applications/hr/time_off/my_time.rst:50
msgid ""
"A user can also select a future date to see an estimate of how much time "
"they should accrue by that point. On the right side of the time off summary "
"blocks, there is a :guilabel:`Balance at the (date)` field. Click on the "
"date, and a calendar selector popover appears."
msgstr ""

#: ../../content/applications/hr/time_off/my_time.rst:55
msgid ""
"The :guilabel:`Balance at the (date)` field **only** appears if the user is "
"accruing time off through an :ref:`accrual plan <time_off/accrual-plans>`."
msgstr ""

#: ../../content/applications/hr/time_off/my_time.rst:58
msgid ""
"The current date is the default date selected. Navigate to the desired date,"
" and Odoo displays the time off balances the user should have on that date. "
"This takes into account all time off currently planned and approved. To "
"return to the current date, click the :guilabel:`Today` button to the right "
"of the date field."
msgstr ""

#: ../../content/applications/hr/time_off/my_time.rst:63
msgid ""
"On the right side of the calendar, the various time off types are displayed,"
" each with their own corresponding color. The :guilabel:`Legend` explains "
"how the various statuses for time off requests are presented."
msgstr ""

#: ../../content/applications/hr/time_off/my_time.rst:67
msgid ""
"Time off that has been validated appears in a solid color. Time off requests"
" that still are still in the :guilabel:`To Approve` stage, appear with white"
" stripes in the color. :guilabel:`Refused` time off requests have a line "
"through the dates."
msgstr ""

#: ../../content/applications/hr/time_off/my_time.rst:71
msgid ""
"The color for each request corresponds to the specified color set with the "
"various time off types, listed in the section above the :guilabel:`Legend`."
msgstr ""

#: ../../content/applications/hr/time_off/my_time.rst:74
msgid ""
"New time off requests can be made from the :guilabel:`Dashboard`. Click the "
":guilabel:`New` button in the upper-left corner, and a :doc:`New Time Off "
"<request_time_off>` pop-up window appears."
msgstr ""

#: ../../content/applications/hr/time_off/my_time.rst:77
msgid ""
"New allocation requests can also be made from the :guilabel:`Dashboard`. "
"Click the :guilabel:`New Allocation Request` button to request more time "
"off, and a :ref:`New Allocation <time_off/request-allocation>` pop-up window"
" appears."
msgstr ""

#: ../../content/applications/hr/time_off/my_time.rst-1
msgid ""
"Time off dashboard view with the legend, time off summaries, and view "
"buttons highlighted."
msgstr ""

#: ../../content/applications/hr/time_off/my_time.rst:88
msgid "My time off"
msgstr ""

#: ../../content/applications/hr/time_off/my_time.rst:90
msgid ""
"To view a list of all the time off requests, navigate to "
":menuselection:`Time Off app --> My Time --> My Time Off`. Here, all time "
"off requests, both past and present, appear in a list view."
msgstr ""

#: ../../content/applications/hr/time_off/my_time.rst:93
msgid ""
"The list includes the following information for each request: the "
":guilabel:`Time Off Type`, :guilabel:`Description`, :guilabel:`Start Date`, "
":guilabel:`End Date`, :guilabel:`Duration`, and :guilabel:`Status`."
msgstr ""

#: ../../content/applications/hr/time_off/my_time.rst:97
msgid ""
"A new time off request can be made from this view. Click the :guilabel:`New`"
" button to :doc:`request_time_off`."
msgstr ""

#: ../../content/applications/hr/time_off/my_time.rst:103
msgid "My allocations"
msgstr ""

#: ../../content/applications/hr/time_off/my_time.rst:105
msgid ""
"To view a list of all allocations, navigate to :menuselection:`Time Off app "
"--> My Time --> My Allocations`. All allocations and requested allocations "
"appear in a list view."
msgstr ""

#: ../../content/applications/hr/time_off/my_time.rst:108
msgid ""
"The information presented on the :guilabel:`My Allocations` page includes: "
":guilabel:`Time Off Type`, :guilabel:`Description`, :guilabel:`Amount`, "
":guilabel:`Allocation Type`, and :guilabel:`Status`."
msgstr ""

#: ../../content/applications/hr/time_off/my_time.rst:112
msgid ""
"A new allocation request can be made from this view, as well. Click the "
":guilabel:`New` button to :ref:`request an allocation <time_off/request-"
"allocation>`."
msgstr ""

#: ../../content/applications/hr/time_off/request_time_off.rst:3
msgid "Request time off"
msgstr ""

#: ../../content/applications/hr/time_off/request_time_off.rst:5
msgid ""
"Once time off has been allocated to an employee, a request to use it can be "
"submitted."
msgstr ""

#: ../../content/applications/hr/time_off/request_time_off.rst:7
msgid ""
"Time off can be requested in one of two ways: either from the main *Time "
"Off* application :guilabel:`Dashboard` (:menuselection:`Time Off app --> My "
"Time --> Dashboard`), or from the :guilabel:`My Time Off` dashboard view "
"(:menuselection:`Time Off app --> My Time --> My Time Off`)."
msgstr ""

#: ../../content/applications/hr/time_off/request_time_off.rst:11
msgid ""
"To create a new request for time off, click the :guilabel:`New` button on "
"either the main *Time Off* :guilabel:`Dashboard` or the :guilabel:`My Time "
"Off` dashboard, in the default list view."
msgstr ""

#: ../../content/applications/hr/time_off/request_time_off.rst:15
msgid ""
"Both :guilabel:`New` buttons allow the user to request time off, but when "
"requested from the :guilabel:`Dashboard`, a :guilabel:`New Time Off` request"
" form appears in a pop-up window. When requested from the :guilabel:`My Time"
" Off` list view, the screen navigates to a new time off request page, "
"instead."
msgstr ""

#: ../../content/applications/hr/time_off/request_time_off.rst:20
msgid ""
"Enter the following information on the :guilabel:`New Time Off` request "
"form:"
msgstr ""

#: ../../content/applications/hr/time_off/request_time_off.rst:22
msgid ""
":guilabel:`Time Off Type`: select the type of time off being requested from "
"the drop-down menu."
msgstr ""

#: ../../content/applications/hr/time_off/request_time_off.rst:23
msgid ""
":guilabel:`Dates`: enter the dates that the time off falls under. There are "
"two fields to populate: the start and end dates. Click on either date field "
"and a popover calendar appears."
msgstr ""

#: ../../content/applications/hr/time_off/request_time_off.rst:26
msgid ""
"Click on the start date, then click on the end date. The selected start and "
"end dates are circled, and the dates between them are highlighted (if "
"applicable)."
msgstr ""

#: ../../content/applications/hr/time_off/request_time_off.rst:29
msgid ""
"If only requesting time off for a single day, click on the start date, then "
"click the same date again for the end date."
msgstr ""

#: ../../content/applications/hr/time_off/request_time_off.rst:32
msgid ""
"When the correct dates are selected, click the :guilabel:`Apply` button."
msgstr ""

#: ../../content/applications/hr/time_off/request_time_off.rst:34
msgid ""
"The selected dates now populate the two portions of the :guilabel:`Dates` "
"field."
msgstr ""

#: ../../content/applications/hr/time_off/request_time_off.rst:36
msgid ""
"If the selected :guilabel:`Time Off Type` is configured to have the time off"
" taken in hours, the following two fields also appear:"
msgstr ""

#: ../../content/applications/hr/time_off/request_time_off.rst:39
msgid ""
":guilabel:`Half Day`: if the time off request is for a half day, tick this "
"checkbox. When this is selected, the second date field disappears, and is "
"replaced with a drop-down menu. From that drop-down menu, select either "
":guilabel:`Morning` or :guilabel:`Afternoon` to indicate which half of the "
"day is being requested."
msgstr ""

#: ../../content/applications/hr/time_off/request_time_off.rst:43
msgid ""
":guilabel:`Custom Hours`: if the time off requested is not a whole or half "
"day, tick this checkbox. If selected, a :guilabel:`From` and :guilabel:`To` "
"field appears beneath this option. Using the drop-down menu, select the "
"start and end time for the time off request."
msgstr ""

#: ../../content/applications/hr/time_off/request_time_off.rst:47
msgid ""
":guilabel:`Duration`: this field updates automatically once the "
":guilabel:`Date` section is completed. If the :guilabel:`Date` section is "
"modified, this section automatically updates to reflect the total time off "
"requested. This field is in either hours or days, depending on how the "
"selected :guilabel:`Time Off Type` is configured."
msgstr ""

#: ../../content/applications/hr/time_off/request_time_off.rst:51
msgid ""
":guilabel:`Description`: enter a description for the time off request. This "
"should include any details that managers and approvers may need to approve "
"the request."
msgstr ""

#: ../../content/applications/hr/time_off/request_time_off.rst:53
msgid ""
":guilabel:`Supporting Document`: this field only appears if the "
":guilabel:`Time Off Type` selected allows for the attachment of documents. "
"Click the :guilabel:`Attach File` button, and a file explorer window "
"appears."
msgstr ""

#: ../../content/applications/hr/time_off/request_time_off.rst:57
msgid ""
"Navigate to the desired files that should be attached, select them, then "
"click The :guilabel:`Open` button. The files then appear on the time off "
"request form. Multiple documents can be attached, if necessary."
msgstr ""

#: ../../content/applications/hr/time_off/request_time_off.rst:61
msgid ""
"If the request was created from the :guilabel:`Dashboard`, click the "
":guilabel:`Save & Close` button to save the information, and submit the "
"request."
msgstr ""

#: ../../content/applications/hr/time_off/request_time_off.rst:64
msgid ""
"If the form was completed from the :guilabel:`My Time Off` list view, the "
"information is automatically saved as it is entered. However, the form can "
"be saved manually at any time by clicking the :icon:`fa-cloud-upload` "
":guilabel:`(cloud upload)` icon."
msgstr ""

#: ../../content/applications/hr/time_off/request_time_off.rst-1
msgid ""
"A time off request form filled out for an employee home sick for two days "
"with the flu."
msgstr ""