documentation/locale/pl/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.
# 
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-03-25 16:01+0000\n"
"PO-Revision-Date: 2024-03-30 23:40+0000\n"
"Language-Team: Polish (https://app.transifex.com/odoo/teams/41243/pl/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: pl\n"
"Plural-Forms: nplurals=4; plural=(n==1 ? 0 : (n%10>=2 && n%10<=4) && (n%100<12 || n%100>14) ? 1 : n!=1 && (n%10>=0 && n%10<=1) || (n%10>=5 && n%10<=9) || (n%100>=12 && n%100<=14) ? 2 : 3);\n"

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

#: ../../content/applications/hr/appraisals.rst:3
#: ../../content/applications/hr/appraisals.rst:50
#: ../../content/applications/hr/appraisals.rst:195
msgid "Appraisals"
msgstr ""

#: ../../content/applications/hr/appraisals.rst:5
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:10
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:14
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:18
#: ../../content/applications/hr/attendances.rst:66
#: ../../content/applications/hr/frontdesk.rst:13
#: ../../content/applications/hr/time_off.rst:27
msgid "Configuration"
msgstr ""

#: ../../content/applications/hr/appraisals.rst:20
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:25
#: ../../content/applications/hr/fleet/configuration.rst:13
#: ../../content/applications/hr/payroll.rst:15
msgid "Settings"
msgstr ""

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

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

#: ../../content/applications/hr/appraisals.rst:33
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:36
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:40
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:43
msgid ""
"The :guilabel:`Manager Feedback Template` has the following sections: "
":guilabel:`Feedback`, :guilabel:`Evaluation`, and :guilabel:`Improvements`."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:46
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:52
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:62
msgid "Appraisals plans"
msgstr ""

#: ../../content/applications/hr/appraisals.rst:64
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:67
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:70
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:74
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:78
#: ../../content/applications/hr/appraisals.rst:120
msgid "360 feedback"
msgstr ""

#: ../../content/applications/hr/appraisals.rst:80
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:83
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:86
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:90
msgid ""
"For more information on how to edit a survey, refer to the "
":doc:`../marketing/surveys/create` document."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:94
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:99
msgid "Evaluation scale"
msgstr ""

#: ../../content/applications/hr/appraisals.rst:101
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:105
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:109
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:112
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:122
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:130
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:133
msgid "Each appraisal includes the following information:"
msgstr ""

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

#: ../../content/applications/hr/appraisals.rst:136
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:138
msgid ""
":guilabel:`Questions`: the number of questions in that particular survey."
msgstr ""

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

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

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

#: ../../content/applications/hr/appraisals.rst:143
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:146
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:150
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:153
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:158
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:161
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:165
msgid ""
"For more information on how to create a survey, refer to the "
":doc:`../marketing/surveys/create` document."
msgstr ""

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

#: ../../content/applications/hr/appraisals.rst:172
msgid "Tags"
msgstr ""

#: ../../content/applications/hr/appraisals.rst:174
msgid ""
"An additional feature of the *Appraisals* application is the ability to set "
":ref:`goals <appraisals/goals>` for employees. On each goal form, there is a"
" field to add tags. The available tags are pulled from a list that is "
"configured from the settings."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:178
msgid ""
"To view a list of all existing goal tags, and to create new tags, go to the "
":guilabel:`Goal Tags` page, by navigating to :menuselection:`Appraisals "
"application --> Configuration --> Tags`."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:181
msgid "All currently configured tags are presented in a list view."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:183
msgid ""
"The *Appraisals* application does **not** have any pre-configured tags, so "
"all tags need to be added from this list, or directly from the goal form."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:186
msgid ""
"To create a new tag from the :guilabel:`Goal Tags` page, click the "
":guilabel:`New` button, and a blank line appears."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:189
msgid ""
"Enter the name of the tag on the line. Then, press the enter key to save the"
" tag, and create a new blank line. Repeat this for all tags that need to be "
"added."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:192
msgid "The list of tags is automatically arranged in alphabetical order."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:197
msgid ""
"Navigate to the main *Appraisals* dashboard by opening the "
":guilabel:`Appraisals` application. The :guilabel:`Appraisals` dashboard is "
"the default view."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:200
msgid ""
"To view the dashboard at any point in the application, navigate to "
":menuselection:`Appraisals application --> Appraisals`."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:203
msgid ""
"All appraisals are displayed on the dashboard in a Kanban view, by default, "
"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.rst:207
msgid ""
"Click any grouping option to view appraisals for **only** the chosen "
"selection."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:210
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.rst:214
msgid "Each appraisal card displays the following information:"
msgstr ""

#: ../../content/applications/hr/appraisals.rst:216
msgid ":guilabel:`Name`: the employee's name."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:217
msgid ""
":guilabel:`Department`: the department the employee is associated with."
msgstr ""

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

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

#: ../../content/applications/hr/appraisals.rst:221
msgid ""
":guilabel:`Activities`: any activities that are scheduled for the appraisal,"
" such as :guilabel:`Meetings` or :guilabel:`Phone Calls.` If no activities "
"are scheduled, an activity can be scheduled from the :guilabel:`🕘 (clock)` "
"icon, located in the bottom-left corner of an appraisal card."
msgstr ""

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

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

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

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

#: ../../content/applications/hr/appraisals.rst:238
msgid "New appraisal"
msgstr ""

#: ../../content/applications/hr/appraisals.rst:240
msgid ""
"To create a new appraisal, click the :guilabel:`New` button at the top of "
"the :guilabel:`Appraisals` dashboard to load a blank appraisal form. Then, "
"enter the following information on the form:"
msgstr ""

#: ../../content/applications/hr/appraisals.rst:243
msgid ":guilabel:`Name`: enter the employee's name."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:244
msgid ""
":guilabel:`Manager`: select the employee's manager from the drop-down menu. "
"The manager is responsible for completing the :guilabel:`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.rst:248
msgid ""
":guilabel:`Appraisal Date`: the current date is automatically entered in "
"this field. This field is automatically updated once the appraisal is "
"completed or canceled, with the corresponding date of completion or "
"cancellation."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:251
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.rst:254
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.rst:259
msgid ""
"The only required fields for the appraisal form are the employee's "
":guilabel:`Name`, the :guilabel:`Manager`, and the :guilabel:`Company`."
msgstr ""

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

#: ../../content/applications/hr/appraisals.rst:264
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.rst:267
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.rst:272
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.rst:276
msgid "Ask for feedback"
msgstr ""

#: ../../content/applications/hr/appraisals.rst:278
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.rst:283
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.rst:286
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.rst:290
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.rst:293
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.rst:296
msgid "If required, an :guilabel:`Answer Deadline` can be added, as well."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:298
msgid ""
"If any attachments are needed, click the :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.rst:301
msgid "When the email is ready to send, click :guilabel:`Send.`"
msgstr ""

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

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

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

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

#: ../../content/applications/hr/appraisals.rst:318
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.rst:322
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.rst:325
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.rst-1
msgid ""
"The feedback section for the employee with the toggle button highlighted."
msgstr ""

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

#: ../../content/applications/hr/appraisals.rst:337
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.rst:341
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.rst:344
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.rst-1
msgid ""
"The feedback section for both employees and managers. The toggle buttons are"
" highlighted."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:353
msgid "Skills tab"
msgstr ""

#: ../../content/applications/hr/appraisals.rst:355
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 :doc:`employee form "
"<../hr/employees/new_employee>`, once an appraisal is confirmed."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:359
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.rst:362
msgid ""
"Update any skills, or add any new skills to the :guilabel:`Skills` tab."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:364
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.rst:368
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.rst:371
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.rst-1
msgid "The skills tab of an appraisal form, all filled out."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:379
msgid "Private note tab"
msgstr ""

#: ../../content/applications/hr/appraisals.rst:381
msgid ""
"If managers want to leave notes that are only visible to other managers, "
"they can be entered in the :guilabel:`Private Note` tab. 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.rst:386
#: ../../content/applications/hr/recruitment.rst:520
msgid "Schedule a meeting"
msgstr ""

#: ../../content/applications/hr/appraisals.rst:388
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.rst:392
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.rst:395
msgid ""
"To schedule an appraisal from the dashboard of the *Appraisals* application,"
" first navigate to :menuselection:`Appraisals application --> Appraisals`."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:398
msgid ""
"Click the :guilabel:`🕘 (clock)` icon, beneath the appraisal date on the "
"desired appraisal card, and a :guilabel:`Schedule Activity` pop-up window "
"appears. Then, click :guilabel:`+ Schedule an activity` to create a blank "
"activity form."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:402
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.rst:406
msgid ""
"If scheduling an activity other than a meeting, such as a :guilabel:`Call` "
"or a :guilabel:`To-Do`, the fields that appear on the :guilabel:`Schedule "
"Activity` pop-up form change, accordingly."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:410
msgid ""
"The :guilabel:`🕘 (clock)` icon may appear as a number of different icons, "
"depending on what, if any, scheduled activities are in place, and the color "
"represents their corresponding due dates."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:413
msgid ""
"If no activities are scheduled, that is represented by a gray :guilabel:`🕘 "
"(clock)` icon."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:415
msgid ""
"However, if a specific activity is scheduled, the icon may appear as a "
":guilabel:`📞 (phone)` icon for a phone call, a :guilabel:`👥 (group of "
"people)` icon for a meeting, and so on."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:418
msgid ""
"The color of the icon indicates the status; a green icon means an activity "
"is scheduled in the future, and a red icon means the activity is past due."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:421
msgid ""
"For more details on activities, refer to the :doc:`../essentials/activities`"
" document."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:0
msgid "The appraisal cards with the various activity icons highlighted."
msgstr ""

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

#: ../../content/applications/hr/appraisals.rst:430
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.rst:433
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 giving a :guilabel:`Name` to the meeting."
msgstr ""

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

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

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

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

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

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

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

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

#: ../../content/applications/hr/appraisals.rst:463
msgid "Goals"
msgstr ""

#: ../../content/applications/hr/appraisals.rst:465
msgid ""
"The ability to set goals for employees to work toward is an important "
"feature of Odoo *Appraisals*. Goals are typically set during an appraisal, "
"so the employee knows what they need to work toward before their next "
"appraisal."
msgstr ""

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

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

#: ../../content/applications/hr/appraisals.rst:474
msgid ":guilabel:`Skill`: the name of the goal."
msgstr ""

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

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

#: ../../content/applications/hr/appraisals.rst:477
msgid ":guilabel:`Progress`: the percentage of competency set for the goal."
msgstr ""

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

#: ../../content/applications/hr/appraisals.rst:480
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.rst-1
msgid "The goals Kanban view, with nine goal cards."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:487
msgid ""
"Every individual goal requires its own entry for each employee. If employees"
" have the same goal, a goal card for each employee appears on the list. For "
"example, if both 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.rst:493
msgid "New goal"
msgstr ""

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

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

#: ../../content/applications/hr/appraisals.rst:502
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.rst:505
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.rst-1
msgid "A goal form filled out for a Python skill, set to 50% proficiency."
msgstr ""

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

#: ../../content/applications/hr/appraisals.rst:515
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.rst:518
msgid ""
"To mark a goal as `Done` from the main :guilabel:`Goals` dashboard, click on"
" the :guilabel:`⋮ (three dots)` icon in the top-right of a goal card."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:522
msgid ""
"The :guilabel:`⋮ (three dots)` icon **only** appears when the mouse hovers "
"over the corner of a goal card."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:525
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.rst:528
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.rst:533
#: ../../content/applications/hr/attendances.rst:526
#: ../../content/applications/hr/frontdesk.rst:351
#: ../../content/applications/hr/payroll/reporting.rst:3
#: ../../content/applications/hr/referrals.rst:753
#: ../../content/applications/hr/time_off.rst:702
msgid "Reporting"
msgstr ""

#: ../../content/applications/hr/appraisals.rst:535
msgid ""
"The *Appraisals* application tracks two metrics across two different "
"reports: an :ref:`appraisal analysis <appraisals/analysis>`, and a "
":ref:`skills evolution <appraisals/skills-report>`."
msgstr ""

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

#: ../../content/applications/hr/appraisals.rst:543
msgid ""
"To access the *Appraisal Analysis* report, navigate to "
":menuselection:`Appraisals application --> Reporting --> Appraisal "
"Analysis`. This displays a report of all the appraisals in the database, "
"highlighted in different colors to represent their status."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:547
msgid ""
"Appraisals in yellow are completed, appraisals in orange are in-progress "
"(the appraisal is confirmed, but not completed), and appraisals in gray are "
"scheduled (according to the :ref:`appraisals/appraisal-plan`), but have not "
"been confirmed yet."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:551
msgid ""
"The report displays the whole current year, by default, grouped by "
"department."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:553
msgid ""
"To change the calendar view presented, change the date settings in the top-"
"left of the report. The options to display are :guilabel:`Day`, "
":guilabel:`Week`, :guilabel:`Month`, and :guilabel:`Year`. Use the arrows to"
" move forward or backward in time."
msgstr ""

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

#: ../../content/applications/hr/appraisals.rst:560
msgid ""
"The report can have other filters and groupings set in the "
":guilabel:`Search...` bar at the top."
msgstr ""

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

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

#: ../../content/applications/hr/appraisals.rst:571
msgid ""
"To access the *Skills Evolution* report, navigate to "
":menuselection:`Appraisals application --> Reporting --> Skills Evolution`. "
"This displays a report of all skills, grouped by employee."
msgstr ""

#: ../../content/applications/hr/appraisals.rst:574
msgid ""
"All the lines of the report are collapsed, by default. To view the details "
"of a line, click on a line to expand the data."
msgstr ""

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

#: ../../content/applications/hr/appraisals.rst:579
msgid ":guilabel:`Employee`: name of the employee."
msgstr ""

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

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

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

#: ../../content/applications/hr/appraisals.rst:583
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.rst:585
msgid ""
":guilabel:`Current Skill Level`: the current level the employee has achieved"
" for the skill."
msgstr ""

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

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

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

#: ../../content/applications/hr/attendances.rst:5
msgid "Attendances"
msgstr ""

#: ../../content/applications/hr/attendances.rst:12
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:21
msgid "Access rights"
msgstr ""

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

#: ../../content/applications/hr/attendances.rst:26
msgid ""
"Every user in the database is always able to access their own information on"
" the dashboard and can check in and out directly from the database. Access "
"to all the other features is determined by access rights."
msgstr ""

#: ../../content/applications/hr/attendances.rst:30
msgid ""
"To see what access rights a user has, navigate to the "
":menuselection:`Settings application --> 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:36
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 mode from the "
"application, access all reporting metrics, and make modifications to the "
"settings."
msgstr ""

#: ../../content/applications/hr/attendances.rst:41
msgid ""
"If left blank, the user can only view their own information on the "
"*Attendances* application dashboard and can view their own personal "
"attendance records under the reporting feature. All other attendance records"
" are hidden from view on the report. There is no access to either the kiosk "
"mode or the configuration menu."
msgstr ""

#: ../../content/applications/hr/attendances.rst:49
msgid "Approvers"
msgstr ""

#: ../../content/applications/hr/attendances.rst:51
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:59
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:68
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:74
msgid "Modes"
msgstr ""

#: ../../content/applications/hr/attendances.rst:78
msgid ""
":guilabel:`Kiosk Mode`: 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.rst:83
msgid ""
"The *Barcode* application **does not** need to be installed to use one of "
"the Barcode/RFID settings."
msgstr ""

#: ../../content/applications/hr/attendances.rst:86
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:93
msgid "Kiosk settings"
msgstr ""

#: ../../content/applications/hr/attendances.rst:95
msgid ""
"This section only needs to be configured if employees use kiosks for "
"checking in and out. If kiosks are **not** being used, modifying any of "
"these fields does **not** adversely affect the *Attendances* application."
msgstr ""

#: ../../content/applications/hr/attendances.rst:99
msgid ""
":guilabel:`Barcode Source`: this setting appears **only** if either of the "
"two Barcode/RFID selections were configured for the :ref:`Kiosk Mode "
"<attendances/kiosk-mode>` setting. Select how barcodes are scanned at the "
"kiosk, either with a dedicated barcode :guilabel:`Scanner`, or the device's "
":guilabel:`Front Camera`, or :guilabel:`Back Camera`."
msgstr ""

#: ../../content/applications/hr/attendances.rst:103
msgid ""
":guilabel:`Employee PIN Identification`: activate this option if employees "
"should use a unique PIN to check in. PINs are configured on each individual "
"employee record. Refer to the :doc:`../hr/employees/new_employee` "
"documentation for more information on setting up PINs."
msgstr ""

#: ../../content/applications/hr/attendances.rst:106
msgid ""
":guilabel:`Display Time`: set the duration (in seconds) the check in and "
"check out confirmation screen remains on the kiosk before going back to the "
"main check in screen."
msgstr ""

#: ../../content/applications/hr/attendances.rst:108
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 application kiosk."
msgstr ""

#: ../../content/applications/hr/attendances.rst:113
msgid ""
"These kiosk URLs are **not** secured with any type of access code. Anyone "
"who has the URL can access the Attendances application 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.rst:119
msgid "Extra hours"
msgstr ""

#: ../../content/applications/hr/attendances.rst:121
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:124
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:128
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:131
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:135
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:142
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:145
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:148
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:152
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:156
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:164
msgid "Check in and out via the database"
msgstr ""

#: ../../content/applications/hr/attendances.rst:166
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 some smaller companies, where every "
"employee is also a user, this feature may be useful."
msgstr ""

#: ../../content/applications/hr/attendances.rst:170
msgid ""
"A user can check in and out on the main database dashboard, as well as in "
"any application. In the upper right corner of the top main 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.rst-1
#: ../../content/applications/hr/attendances.rst-1
msgid "Top right main menu with check in button highlighted."
msgstr ""

#: ../../content/applications/hr/attendances.rst:180
msgid "Check in"
msgstr ""

#: ../../content/applications/hr/attendances.rst:182
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 ➡️` "
"button."
msgstr ""

#: ../../content/applications/hr/attendances.rst:190
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.rst:194
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.rst:197
msgid ""
"If the user has not checked in and out already 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 beneath that field, in an :guilabel:`HH:MM` (hours:minutes) format."
msgstr ""

#: ../../content/applications/hr/attendances.rst:202
msgid ""
"Click the :guilabel:`Check 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 ➡️` button to a yellow "
":guilabel:`Check out ➡️` button."
msgstr ""

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

#: ../../content/applications/hr/attendances.rst:210
msgid "Check out"
msgstr ""

#: ../../content/applications/hr/attendances.rst:212
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, :guilabel:`HH:MM` is "
"displayed, indicating the hours and minutes that have elapsed since checking"
" in. 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.rst:218
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 time displayed in both of "
"these fields are populated with the most recent check in time, and will "
"match. Beneath the :guilabel:`Before HH:MM (AM/PM)` field, the previously "
"logged hours are displayed, in an :guilabel:`HH:MM` (hours:minutes) format."
msgstr ""

#: ../../content/applications/hr/attendances.rst:224
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 will "
"be logged for the user, if they were to log out at that moment."
msgstr ""

#: ../../content/applications/hr/attendances.rst:228
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 ➡️` button. The attendance widget updates again,"
" displaying the :guilabel:`Total today` field with the logged time, and the "
"yellow :guilabel:`Check out ➡️` button changes to a green :guilabel:`Check "
"in ➡️` button."
msgstr ""

#: ../../content/applications/hr/attendances.rst:233
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.rst-1
msgid ""
"The pop-up that appears when an employee checks in inside the database."
msgstr ""

#: ../../content/applications/hr/attendances.rst:242
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 dashboard, including check ins and check outs with no time "
"value."
msgstr ""

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

#: ../../content/applications/hr/attendances.rst:252
msgid ""
"Some companies may opt to use a dedicated device (a laptop or desktop PC, a "
"tablet, or a mobile phone) for employees to check in and check out from. "
"Kiosk mode is used for these scenarios."
msgstr ""

#: ../../content/applications/hr/attendances.rst:256
msgid ""
"If users check in and out using either a badge or an RFID, then an "
"accessible device in kiosk mode **must** be available to check in and check "
"out using these two methods."
msgstr ""

#: ../../content/applications/hr/attendances.rst:259
msgid ""
"Entering kiosk mode is only available for users with specific :ref:`access "
"rights <attendances/access-rights>`."
msgstr ""

#: ../../content/applications/hr/attendances.rst:262
msgid "Kiosk mode can be activated in three different ways:"
msgstr ""

#: ../../content/applications/hr/attendances.rst:264
msgid ""
"Navigate to the :guilabel:`Attendances` application, and click "
":guilabel:`Kiosk Mode` in the top menu. The device then enters kiosk mode."
msgstr ""

#: ../../content/applications/hr/attendances.rst:266
msgid ""
"Navigate to the :menuselection:`Attendances application --> Configuration`. "
"In the :guilabel:`Kiosk Settings` section, click on the link in the "
":guilabel:`Attendance Kiosk Url` field. A new tab opens in kiosk mode. It is"
" recommended to close the database tab to keep the database secure."
msgstr ""

#: ../../content/applications/hr/attendances.rst:270
msgid ""
"Navigate to the :menuselection:`Attendances application --> Configuration`. "
"In the :guilabel:`Kiosk Settings` section, click :guilabel:`Copy` next to "
"the link beneath the :guilabel:`Attendance Kiosk Url` field. Paste this URL "
"into a web browser on the kiosk device and navigate to it."
msgstr ""

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

#: ../../content/applications/hr/attendances.rst:279
msgid ""
"As a security measure, once a device is in kiosk mode, it is not possible to"
" exit kiosk mode and go back into the database without signing back in. To "
"exit kiosk mode, click the back button in the web browser. This logs the "
"user out of the database, and returns to the main log in screen. This adds "
"an extra layer of security, preventing anyone from accessing the database."
msgstr ""

#: ../../content/applications/hr/attendances.rst:285
msgid "Badge"
msgstr ""

#: ../../content/applications/hr/attendances.rst:287
msgid ""
"To check in or out using a badge, tap the :guilabel:`📷 (camera) Tap to scan`"
" image in the center of the kiosk. Then, scan the barcode on the badge using"
" the method configured in the :ref:`kiosk settings <attendances/kiosk-"
"settings>` section of the configuration menu. Options are a dedicated "
"barcode scanning device, or the kiosk's front or back camera. Once the "
"barcode is scanned, the employee is checked in or out, and a "
":ref:`confirmation message <attendances/confirmation>` appears with all the "
"check in or check out information."
msgstr ""

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

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

#: ../../content/applications/hr/attendances.rst:301
msgid ""
"To check in or out using an RFID key fob, simply scan the fob with an RFID "
"reader. Once scanned, the employee is then either checked in or checked out,"
" and a :ref:`confirmation message <attendances/confirmation>` appears with "
"all the check in or check out information."
msgstr ""

#: ../../content/applications/hr/attendances.rst:306
msgid "Manually"
msgstr ""

#: ../../content/applications/hr/attendances.rst:308
msgid ""
"Users who do not have a scannable badge or an RFID fob can manually check in"
" and out at a kiosk. Tap the :guilabel:`Identify Manually` button on the "
"kiosk, and a screen with all the employees that can be checked in or out "
"appears. This is the same view as in the *Employees* application dashboard. "
"Tap on the person, and they are either checked in or checked out, and a "
":ref:`confirmation message <attendances/confirmation>` appears."
msgstr ""

#: ../../content/applications/hr/attendances.rst:314
msgid ""
"When a large number of employees appear in the list, making scrolling "
"inefficient, there are two ways to quickly find a specific person:"
msgstr ""

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

#: ../../content/applications/hr/attendances.rst:319
msgid ""
":guilabel:`Department`: to quickly filter the presented employees, tap on a "
"department to display only those employees that are part of that department."
" The :guilabel:`Departments` are listed on the left side of the screen, and "
"the number at the end of each department indicates how many employees are "
"part of the department, and is displayed when selected."
msgstr ""

#: ../../content/applications/hr/attendances.rst:325
msgid "PIN"
msgstr ""

#: ../../content/applications/hr/attendances.rst:327
msgid ""
"If the :guilabel:`Employee PIN Identification` option was activated 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.rst:331
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.rst:336
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.rst-1
msgid "The pop-up that appears when prompted to enter a pin."
msgstr ""

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

#: ../../content/applications/hr/attendances.rst:348
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. An :guilabel:`Hours "
"Previously Today: HH:MM` field also appears, displaying any time already "
"logged for that employee for the day. If no time has already been logged, "
"the value displayed is `00:00`. Beneath the message is an :guilabel:`OK` "
"button. To exit the screen before the preset time in the kiosk, tap the "
":guilabel:`OK` button."
msgstr ""

#: ../../content/applications/hr/attendances.rst:355
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.rst-1
msgid "The goodbye message with all the employee's check out information."
msgstr ""

#: ../../content/applications/hr/attendances.rst:364
#: ../../content/applications/hr/time_off.rst:309
msgid "Overview"
msgstr ""

#: ../../content/applications/hr/attendances.rst:366
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:373
msgid "Views"
msgstr ""

#: ../../content/applications/hr/attendances.rst:375
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:379
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:388
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:397
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:404
msgid "Filters and groups"
msgstr ""

#: ../../content/applications/hr/attendances.rst:406
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:413
#: ../../content/applications/hr/payroll/reporting.rst:276
msgid "Filters"
msgstr ""

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

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

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

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

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

#: ../../content/applications/hr/attendances.rst:422
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:424
msgid ""
":guilabel:`Last 7 days`: this filter presents the attendance data for the "
"last seven days."
msgstr ""

#: ../../content/applications/hr/attendances.rst:425
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:429
msgid "Groups"
msgstr ""

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

#: ../../content/applications/hr/attendances.rst:433
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:437
msgid ""
":guilabel:`Employee`: this group presents the attendance data organized by "
"employee."
msgstr ""

#: ../../content/applications/hr/attendances.rst:438
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:442
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:449
msgid "Attendance log details"
msgstr ""

#: ../../content/applications/hr/attendances.rst:451
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:454
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:457
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:460
msgid "The detailed attendance log contains the following information:"
msgstr ""

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

#: ../../content/applications/hr/attendances.rst:465
msgid ":guilabel:`Employee`: the name of the employee."
msgstr ""

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

#: ../../content/applications/hr/attendances.rst:467
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:469
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:472
msgid ""
":guilabel:`Extra Hours`: any extra hours the employee logged that is beyond "
"their expected working hours."
msgstr ""

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

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

#: ../../content/applications/hr/attendances.rst:481
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:485
msgid ""
":guilabel:`IP Address`: the IP address for the computer the employee used to"
" log in or out."
msgstr ""

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

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

#: ../../content/applications/hr/attendances.rst:488
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:498
msgid "Errors"
msgstr ""

#: ../../content/applications/hr/attendances.rst:500
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:504
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:507
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:519
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:522
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:528
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:531
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:535
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:538
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:542
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:545
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/hardware.rst:3
msgid "Hardware"
msgstr ""

#: ../../content/applications/hr/attendances/hardware.rst:6
msgid "Kiosk management"
msgstr ""

#: ../../content/applications/hr/attendances/hardware.rst:8
msgid ""
"A kiosk is a self-service station that allows employees to check in and "
"check out for work shifts."
msgstr ""

#: ../../content/applications/hr/attendances/hardware.rst:10
msgid "There are two ways to set up a kiosk:"
msgstr ""

#: ../../content/applications/hr/attendances/hardware.rst:12
msgid "**Laptop and desktop PC**"
msgstr ""

#: ../../content/applications/hr/attendances/hardware.rst:14
msgid ""
"Running a kiosk in a web browser is the cheapest and most flexible option. "
"You can print employee badges with any thermal or inkjet printer compatible "
"with your web browser."
msgstr ""

#: ../../content/applications/hr/attendances/hardware.rst:17
msgid "**Tablet and mobile phone (Android or iOS)**"
msgstr ""

#: ../../content/applications/hr/attendances/hardware.rst:19
msgid ""
"Tablets and mobile phones take up much less space, and their touchscreens "
"are easy to use. Consider putting them in a secure stand at the front desk "
"or mounting them securely on a wall."
msgstr ""

#: ../../content/applications/hr/attendances/hardware.rst:23
msgid ""
"We recommend using an iPad together with the `Heckler Design WindFall Stand "
"<https://hecklerdesign.com/products/windfall-stand-for-ipad>`_"
msgstr ""

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

#: ../../content/applications/hr/attendances/hardware.rst:29
msgid ""
"Employees can scan personal RFID key fobs with an RFID reader to manage "
"check-ins and check-outs quickly and easily."
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:38
msgid ""
"We recommend using 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:41
#: ../../content/applications/hr/attendances/hardware.rst:57
msgid "An IoT box is **not** required."
msgstr ""

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

#: ../../content/applications/hr/attendances/hardware.rst:46
msgid ""
"Employees can scan the barcode on their employee badges to manage check-ins "
"and check-outs quickly and easily. The kiosk mode works with most USB "
"barcode scanners connected directly to a computer. Bluetooth barcode "
"scanners are also supported natively."
msgstr ""

#: ../../content/applications/hr/attendances/hardware.rst:51
msgid ""
"We recommend using the `Honeywell product line "
"<https://sps.honeywell.com/us/en/products/productivity/barcode-scanners>`_. "
"If the barcode scanner is connected directly to a computer, it must be "
"configured to use the computer's keyboard layout."
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/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
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
#: ../../content/applications/hr/payroll/contracts.rst:39
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
#: ../../content/applications/hr/payroll/contracts.rst:66
#: ../../content/applications/hr/recruitment.rst:736
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:861
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/management/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/fleet.rst:7
msgid "Fleet"
msgstr ""

#: ../../content/applications/hr/fleet.rst:9
msgid ""
"Odoo *Fleet* organizes all the vehicles, contracts, and repairs of all the "
"vehicles."
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:3
msgid "Configuration menu"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:5
msgid ""
"This document outlines all of the configurations and settings for the "
"*Fleet* application, including :ref:`settings "
"<fleet/configuration/settings>`, :ref:`manufacturers "
"<fleet/configuration/manufacturers>`, vehicle :ref:`models "
"<fleet/configuration/models>`, and model :ref:`categories "
"<fleet/configuration/categories>`."
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:15
msgid ""
"To access the settings menu, go to :menuselection:`Fleet application --> "
"Configuration --> Settings`. There are two settings that need configuration,"
" the vehicle contract end date alert, and a new vehicle request limit."
msgstr ""

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

#: ../../content/applications/hr/fleet/configuration.rst:24
msgid "End date contract alert"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:26
msgid ""
"The :guilabel:`End Date Contract Alert` field defines when an alert is sent "
"to the persons responsible for the vehicle contracts. The responsible "
"persons receive an email informing them when a vehicle contract is expiring."
" How far in advance the email is sent is defined in this field."
msgstr ""

#: ../../content/applications/hr/fleet/configuration.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:`Information` section of the contract is the one who receives the "
"alert."
msgstr ""

#: ../../content/applications/hr/fleet/configuration.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/configuration.rst:38
msgid ""
"An individual contract can also be found by navigating to "
":menuselection:`Fleet app --> Fleet --> Fleet` and clicking on an individual"
" vehicle card. On the vehicle form, click the :guilabel:`Contracts` smart "
"button at the top of the page. The contracts associated only with this "
"vehicle appear 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/configuration.rst:45
msgid "New vehicle request"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:47
msgid ""
"The :guilabel:`New Vehicle Request` field sets a limit on how many new "
"vehicles are requested based on fleet availability. After being offered a "
"position, an employee filling out the online salary configurator form is "
"**not** 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/configuration.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/configuration.rst:61
#: ../../content/applications/hr/fleet/configuration.rst:102
msgid "Models"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:64
msgid "Manufacturers"
msgstr ""

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

#: ../../content/applications/hr/fleet/configuration.rst:70
msgid ""
"The manufacturers appear in a list view in alphabetical order. Each "
"manufacturer's card lists how many specific models are configured for each "
"particular manufacturer. Odoo comes with forty five pre-configured "
":ref:`models <fleet/configuration/models>` from four major auto "
"manufacturers: Audi, BMW, Mercedes, and Opel."
msgstr ""

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

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

#: ../../content/applications/hr/fleet/configuration.rst:84
msgid ""
"To add a new manufacturer to the database, click :guilabel:`New`, and a "
"blank manufacturer form loads."
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:87
msgid ""
"First, type the name of the manufacturer in the :guilabel:`Name` field. This"
" is the only required field."
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:90
msgid ""
"Next, if a photo is available, hover over the image box and click the "
":guilabel:`✏️ (Pencil)` icon that appears in the lower-left corner."
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:93
msgid ""
"A file explorer window pops up. Navigate to the file, then click "
":guilabel:`Open` to select it."
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:95
msgid ""
"The manufacturer 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/fleet/configuration.rst:104
msgid ""
"Many manufacturers have a variety of models that they produce. Odoo comes "
"with pre-configured car models from four major auto manufacturers: Audi, "
"BMW, Mercedes, and Opel."
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:107
msgid ""
"If a vehicle *other* than the pre-configured models from these manufacturers"
" is part of a fleet, the model (and/or manufacturer) **must** be added to "
"the database."
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:111
msgid "Pre-configured models"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:113
msgid ""
"The following models are pre-configured in Odoo and do not need to be added "
"to the database:"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:116
msgid "AUDI"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:116
msgid "BMW"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:116
msgid "Mercedes"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:116
msgid "Opel"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:118
msgid "A1"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:118
msgid "Serie 1"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:118
msgid "Class A"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:118
msgid "Agilia"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:120
msgid "A3"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:120
msgid "Serie 3"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:120
msgid "Class B"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:120
msgid "Ampera"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:122
msgid "A4"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:122
msgid "Serie 5"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:122
msgid "Class C"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:122
msgid "Antara"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:124
msgid "A5"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:124
msgid "Serie 6"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:124
msgid "Class CL"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:124
msgid "Astra"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:126
msgid "A6"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:126
msgid "Serie 7"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:126
msgid "Class CLS"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:126
msgid "AstraGTC"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:128
msgid "A7"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:128
msgid "Serie Hybrid"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:128
msgid "Class E"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:128
msgid "Combo Tour"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:130
msgid "A8"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:130
msgid "Serie M"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:130
msgid "Class GL"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:130
msgid "Corsa"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:132
msgid "Q3"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:132
msgid "Serie X"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:132
msgid "Class GLK"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:132
msgid "Insignia"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:134
msgid "Q5"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:134
msgid "Serie Z4"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:134
msgid "Class M"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:134
msgid "Meriva"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:136
msgid "Q7"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:136
msgid "Class R"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:136
msgid "Mokka"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:138
msgid "TT"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:138
msgid "Class S"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:138
msgid "Zafira"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:140
msgid "Class SLK"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:140
msgid "Zafira Tourer"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:142
msgid "Class SLS"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:148
msgid "Add a new model"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:150
msgid ""
"New vehicle models can easily be added to the database. To add a new model, "
"navigate to :menuselection:`Fleet app --> Configuration --> Models: Models`."
" Click the :guilabel:`New` button in the top-left corner and a blank vehicle"
" model form loads."
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:154
#: ../../content/applications/hr/frontdesk.rst:31
#: ../../content/applications/hr/payroll.rst:881
#: ../../content/applications/hr/payroll/work_entries.rst:54
#: ../../content/applications/hr/time_off.rst:416
msgid "Enter the following information on the form:"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:157
msgid ""
"Some fields or sections are based on the localization setting of the "
"company, therefore not all fields or sections may be visible."
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:160
msgid ":guilabel:`Model name`: enter the model name in the field."
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:161
msgid ""
":guilabel:`Manufacturer`: select the manufacturer from the drop-down menu. "
"If a logo is configured for the selected manufacturer, the logo "
"automatically loads in the image box in the top-right corner. If the "
"manufacturer is not already configured, type in the manufacturer name and "
"then click :guilabel:`Create` to add the manufacturer, or :guilabel:`Create "
"and edit...` to :ref:`add the manufacturer and the logo "
"<fleet/configuration/add-manufacturer>` in a :guilabel:`Create Manufacturer`"
" pop-up window."
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:167
msgid ""
":guilabel:`Vehicle Type`: select one of two pre-configured 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/configuration.rst:171
msgid ""
":guilabel:`Category`: select the category the vehicle is categorized under "
"from the drop-down menu. To create a new category, type in the category name"
" and then click :guilabel:`Create \"new category\"`."
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:176
msgid "Information tab"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:179
msgid "Model"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:181
msgid ""
":guilabel:`Seats Number`: enter how many passengers the vehicle can "
"accommodate."
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:182
msgid ":guilabel:`Doors Number`: enter the number of doors the vehicle has."
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:183
msgid ":guilabel:`Color`: enter the color of the vehicle."
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:184
msgid ":guilabel:`Model Year`: enter the year the vehicle was manufactured."
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:185
msgid ""
":guilabel:`Trailer Hitch`: check this box if the vehicle has a trailer hitch"
" installed."
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:188
#: ../../content/applications/hr/payroll.rst:390
msgid "Salary"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:191
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/configuration.rst:195
msgid ""
":guilabel:`Can be requested`: check this box if employees can request this "
"model for a new vehicle."
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:197
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/configuration.rst:199
msgid ""
":guilabel:`C02 fee`: this value is automatically calculated based on Belgian"
" laws and regulations, and cannot be modified. The value is based on the "
"value entered in the :guilabel:`CO2 Emissions` field in the "
":guilabel:`Engine` section of the vehicle form."
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:204
msgid ""
"Modifying the :guilabel:`CO2 Emissions` field adjusts the value in the "
":guilabel:`CO2 fee` field."
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:207
msgid ""
":guilabel:`Cost (Depreciated)`: enter the monthly cost for the vehicle, "
"which appears in the salary configurator that is available to a future "
"employee when they are offered a job position."
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:210
msgid ""
"This value impacts the gross and net salary of the employee who is assigned "
"to the vehicle. This figure is depreciated over time according to local tax "
"laws."
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:213
msgid ""
"The :guilabel:`Cost (Depreciated)` does **not** depreciate automatically on "
"the *vehicle model*, it **only** depreciates based on the *contract* linked "
"to a specific vehicle and not on the general model."
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:216
msgid ""
":guilabel:`Total Cost (Depreciated)`: this value is the :guilabel:`Cost "
"(Depreciated)` and the :guilabel:`C02 fee` fields combined, and is also "
"depreciated over time. This field is automatically calculated and cannot be "
"modified."
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:221
msgid "Engine"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:223
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:`Full Hybrid`, :guilabel:`Plug-in Hybrid Diesel`, :guilabel:`Plug-"
"in Hybrid Gasoline`, :guilabel:`CNG`, :guilabel:`LPG`, :guilabel:`Hydrogen`,"
" or :guilabel:`Electric`."
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:227
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/configuration.rst:229
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/configuration.rst:231
msgid ""
":guilabel:`Transmission`: select the transmission type from the drop-down "
"menu, either :guilabel:`Manual` or :guilabel:`Automatic`."
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:233
msgid ""
":guilabel:`Power`: if the vehicle is electric or hybrid, enter the power the"
" vehicle uses in kilowatts (kW)."
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:235
msgid ":guilabel:`Horsepower`: enter the vehicle's horsepower in this field."
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:236
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/configuration.rst:239
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/configuration.rst:243
msgid "Vendors tab"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:245
msgid ""
"Vehicle specific vendors, such as car dealerships, are not listed separately"
" from other vendors. The vendors that a vehicle can be purchased from also "
"appear in the list of vendors in the *Purchase* app."
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:249
msgid ""
"The vendors the specific vehicle model can be purchased from may be added in"
" this tab. To add a vendor, click the :guilabel:`Add` button. An "
":guilabel:`Add: Vendors` pop-up window loads with a list of all the vendors "
"currently in the database."
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:253
msgid ""
"Select the vendor to add by clicking the checkbox to the left of 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/configuration.rst:256
msgid ""
"If a vendor is not in the database, add a vendor by clicking the "
":guilabel:`New` button at the bottom of the :guilabel:`Add: Vendors` pop-up "
"window. A blank :guilabel:`Create Vendors` pop-up form loads."
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:260
msgid ""
"Enter the information on the :guilabel:`Create Vendors` form, including the "
"various tabs, then click :guilabel:`Save & Close` to add the vendor and "
"close the window, or :guilabel:`Save & New` to add the current vendor and "
"create another new vendor."
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst-1
msgid "Vendor form to fill out when adding a new vendor."
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:271
msgid "Categories"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:273
msgid ""
"To best organize a fleet, it is recommended to have vehicle models housed "
"under a specific category, to more easily see what kinds of vehicles are in "
"the fleet."
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:276
msgid ""
"Model categories are set on the :ref:`vehicle model form "
"<fleet/configuration/add-model>`."
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:278
msgid ""
"Unlike manufacturers and models, Odoo does not come with any categories pre-"
"configured; all categories must be added."
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:281
msgid ""
"To view all the currently configured categories, navigate to "
":menuselection:`Fleet application --> Configuration --> Models: Categories`."
" All currently configured categories are displayed in a list view."
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:286
msgid "Add a new category"
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:288
msgid ""
"To add a new category, click the :guilabel:`New` button in the top-left "
"corner. A new entry line appears at the bottom of the list. Type in the new "
"category, then either press the enter key on the keyboard, or click anywhere"
" on the screen, to save the entry."
msgstr ""

#: ../../content/applications/hr/fleet/configuration.rst:292
msgid ""
"To reorganize how the categories appear in the list, click the "
":guilabel:`(six small gray boxes)` to the left of the category to be moved, "
"and drag the line to the desired position. 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/configuration.rst-1
msgid "List view of the categories in the fleet."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:3
msgid "Create 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 driver's records."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:8
msgid ""
"All vehicles are organized on the main :guilabel:`Fleet` dashboard. Each "
"vehicle has its own *vehicle form*, which is displayed as a card in the "
"kanban view, according to it's status. Every vehicle form is displayed in "
"its current corresponding kanban stage. The default stages are "
":guilabel:`New Request`, :guilabel:`To Order`, :guilabel:`Ordered`, "
":guilabel:`Registered`, :guilabel:`Downgraded`, :guilabel:`Reserve`, and "
":guilabel:`Waiting List`."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:14
msgid ""
"To add a new vehicle to the fleet, click the :guilabel:`Create` button, and "
"a blank vehicle form loads. Enter the vehicle information in the vehicle "
"form, then click :guilabel:`Save`."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:18
msgid "Vehicle form fields"
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:20
msgid ""
":guilabel:`Model`: select the vehicle's model from the drop-down menu. If "
"the model is not listed, type in the model name and click either "
":guilabel:`Create` or :guilabel:`Create and Edit`."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:22
msgid ""
":guilabel:`License Plate`: enter the vehicle's license plate number in this "
"field."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:23
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:27
msgid ""
"The :guilabel:`Model` is the only required field on the new vehicle form. "
"When a model is selected, other fields will appear on the vehicle form, and "
"relevant information will auto-populate 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:33
msgid "Driver section"
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:35
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:38
msgid ""
":guilabel:`Driver`: select the driver from the drop-down menu, or type in a "
"new driver and click either :guilabel:`Create` or :guilabel:`Create and "
"Edit`."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:40
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 will appear in this field. If there is no mobility card listed and "
"one should be added, :ref:`edit the employee card <employees/hr-settings>` "
"in the *Employees* application."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:44
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` or :guilabel:`Create and Edit`."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:47
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 will be driving next, check this box. If the "
"current driver does not plan to change their vehicle and use this current "
"vehicle, do not check this box."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:52
msgid ""
":guilabel:`Assignment Date`: select the date the vehicle will be available "
"for another driver using the drop-down calendar. 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 blank, this indicates the vehicle is currently "
"available and can be reassigned to another driver. If it is populated, the "
"vehicle will not be available to assign to another driver until the date "
"entered."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:60
msgid ""
"A driver does **not** have to be an employee, but a driver must be listed in"
" the *Contacts* application. When creating a new driver, the driver is added"
" to the *Contacts* application, not the *Employees* application."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:65
msgid "Vehicle section"
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:67
msgid ""
"This section of the vehicle form relates to the physical vehicle, it's "
"various properties, when it was added, where it is located, and who is "
"managing it."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:70
msgid ""
":guilabel:`Immatriculation Date`: select the date the vehicle is acquired "
"using the drop-down calendar."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:72
msgid ""
":guilabel:`Cancellation Date`: select the date the vehicle lease will "
"expire, or when the vehicle will be no longer available, using the drop-down"
" calendar."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:74
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:76
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:79
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:81
msgid ""
":guilabel:`Location`: type in the location for the vehicle in the field. The"
" most common scenario for when this field would be populated is if a company"
" has several office locations. The typical office location where the vehicle"
" is located would be the location entered."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:84
msgid ""
":guilabel:`Company`: select the company that the vehicle will be used for "
"and associated with from the drop-down menu, or type in a new company and "
"click either :guilabel:`Create` or :guilabel:`Create and Edit`."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:89
msgid ""
"Creating a new company may cause a subscription price change depending on "
"the current plan. Refer to `Odoo's pricing plan "
"<https://www.odoo.com/pricing-plan>`_ for more details."
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:97
msgid "Tax Info tab"
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:100
msgid "Fiscality"
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:102
msgid ""
":guilabel:`Horsepower Taxation`: enter the amount that is taxed based on the"
" size of the vehicles 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:105
msgid ""
":guilabel:`Disallowed Expense Rate`: this is the amount of non-deductible "
"expenses for the vehicle. This amount is not counted towards any deductions "
"on a tax return or as an allowable expense when calculating taxable income. "
"It is recommended to check with the accounting department to ensure the "
"value(s) entered are correct."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:110
msgid ""
":guilabel:`Start Date`: enter the :guilabel:`Start Date` and :guilabel:`(%) "
"Percentage` for when the :guilabel:`Disallowed Expense Rate` value goes into"
" effect. Click :guilabel:`Add a line` to enter a date. Click on the blank "
"line to display a calendar. 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. Enter the percentage "
"that is disallowed in the :guilabel:`% (percent)` field to the right of the "
"date. The percentage should be entered in an XX.XX format. Repeat this for "
"all entries needed."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:119
msgid "Contract"
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:121
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:123
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:125
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:126
msgid ":guilabel:`Residual Value`: enter the current value of the vehicle."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:129
msgid ""
"The values listed above will 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:137
msgid "Model tab"
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:139
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/configuration/add-model>`."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:144
msgid ""
"Check the information in the :guilabel:`Model` tab to ensure it is accurate."
" For example, the color of the vehicle, or whether there is a trailer hitch "
"installed or not, are examples of information that may need updating."
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:153
msgid "Note tab"
msgstr ""

#: ../../content/applications/hr/fleet/new_vehicle.rst:155
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:10
msgid "Create a service record"
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:12
msgid ""
"To log a service, go to the main services dashboard by navigating to "
":menuselection:`Fleet app --> Fleet --> Services`. Click :guilabel:`Create` "
"and a service form appears. Fill in the information on the form and click "
":guilabel:`Save`. The only two fields that are required to be populated are "
":guilabel:`Service Type` and :guilabel:`Vehicle`."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:17
msgid "The fields are:"
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:19
msgid ":guilabel:`Description`: enter in a short description of the service."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:20
msgid ""
":guilabel:`Service Type`: select the type of service performed from the "
"drop-down menu, or type in a new type of service and click either "
":guilabel:`Create` or :guilabel:`Create & Edit...`. This list is not pre-"
"configured in Odoo. When creating a fleet and logging a service, the types "
"of service need to be created."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:24
msgid ""
":guilabel:`Date`: using the calendar module, select the date the service was"
" provided or is scheduled to be performed. Navigate to the desired month "
"using the left and right arrow icons, then click on the date to select it."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:27
msgid ":guilabel:`Cost`: enter the cost of the service."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:28
msgid ""
":guilabel:`Vendor`: select the vendor who performed the service 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` to add them, or "
":guilabel:`Create & Edit...` to create the vendor and edit the vendor form. "
"The vendor form allows for other details aside form the name to be entered, "
"such as contact information."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:33
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:`Mileage` field "
"appears."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:36
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:39
msgid ""
":guilabel:`Odometer Value`: enter the odometer reading when the service was "
"done. The units of measure will either be in kilometers (:guilabel:`km`) or "
"miles (:guilabel:`mi`). When the :guilabel:`Vehicle` is selected, the units "
"of measure is populated. This comes from the vehicle form. To change from "
"kilometers to miles, or vice versa, click the :guilabel:`External Link` "
"button next to the vehicle selected in the :guilabel:`Vehicle` field. Change"
" the unit of measure, then click :guilabel:`Save`. the unit of measure will "
"be updated in the :guilabel:`Odometer Value` field."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:46
msgid ""
":guilabel:`Notes`: enter any notes for the repair in the notes tab 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:54
msgid "List of services"
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:56
msgid ""
"To view all services logged in the database, including old and new requests,"
" go to :menuselection:`Fleet application --> Fleet --> Services`. All "
"services appear in a list view, including all the details for each service."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:60
msgid "Each service listed displays the following information:"
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:62
msgid ""
":guilabel:`Date`: the date service or repair was performed or is requested "
"to be performed."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:63
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:65
msgid ""
":guilabel:`Service Type`: the service or repair performed. This is selected "
"from a list of services that must be configured."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:67
msgid ""
":guilabel:`Vehicle`: the specific vehicle the service was performed on."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:68
msgid ":guilabel:`Driver`: who the current driver is for the vehicle."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:69
msgid ""
":guilabel:`Vendor`: the specific vendor who performed the service or repair."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:70
msgid ":guilabel:`Cost`: the total cost for the service or repair."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:71
msgid ""
":guilabel:`Notes`: any information associated with the service or repair "
"that is documented to add clarification."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:73
msgid ""
":guilabel:`Stage`: the status of the service or repair. Options are "
":guilabel:`New`, :guilabel:`Running`, :guilabel:`Canceled`, or "
":guilabel:`Done`."
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:81
msgid "View services"
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:83
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 cn be clicked to present the information in\n"
"different ways."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:93
msgid "List view"
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:95
msgid ""
"The default view of the services is the list view. This presents all the "
"services in chronological order, from oldest to newest, in a list."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:98
msgid ""
"The information can be sorted by any column. At the top of each column, "
"hover over the column name. An arrow appears to the right of the name. Click"
" the arrow to sort the data by that specific column."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:101
msgid ""
"The default sorting is descending alphabetical order (A to Z). Click the "
"arrow again to reverse the order, and go in reverse alphabetical order (Z to"
" A). The one exception to this sorting is the default :guilabel:`Date` "
"column, which sorts the information in chronological order (January to "
"December) instead of alphabetical order."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:107
#: ../../content/applications/hr/recruitment.rst:33
msgid "Kanban view"
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:109
msgid ""
"To view services by their stage, click on the :guilabel:`Kanban icon`, which"
" is the second icon in the top right, and appears as four black squares in a"
" cube."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:112
msgid ""
"All the services with the same status appear in the corresponding column, "
"from :guilabel:`Running` to :guilabel:`Cancelled`. To change the status of a"
" service, simply click and drag the service card to the desired stage."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:117
msgid "Graph view"
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:119
msgid ""
"Another way to view the data is in a graph. To view the graph, 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:122
msgid ""
"The graph displays the information in a graph where the X axis represents "
"the :guilabel:`Date` and the Y axis represents the :guilabel:`Cost`. Each "
"column represents a single month, and then is further organized by vehicle. "
"Each vehicle is represented by a different color, and each month's bar is "
"divided by each vehicle."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:128
msgid "Pivot view"
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:130
msgid ""
"The final way to view the service data is in a spreadsheet pivot table. "
"Click on the :guilabel:`Pivot icon`, which is the last icon in the top "
"right, and appears as a small spreadsheet."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:133
msgid ""
"The data presented in the table shows the cost of each service or repair. "
"The rows represent the vendors, and each vehicle that was serviced by them "
"appears beneath each vendor. The column represent the different service "
"types performed."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst:137
msgid ""
"The table can be inserted in a spreadsheet or downloaded. To add the pivot "
"table to a spreadsheet in Odoo, click :guilabel:`Insert In Spreadsheet` and "
"a pop-up appears. Select the spreadsheet the data should be added to from "
"the drop-down menu, and click :guilabel:`Confirm`. The spreadsheet then "
"loads on the screen. The spreadsheets are stored in Odoo's *Documents* "
"application. To download the table in an `xlsx` format, click the "
":guilabel:`Download` icon."
msgstr ""

#: ../../content/applications/hr/fleet/service.rst-1
msgid ""
"Download the pivot table to an xlsx file, or insert the data in a spreadsheet in Odoo's\n"
"Documents application."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:3
msgid "Frontdesk"
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:5
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:9
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:15
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:19
msgid "Stations"
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:21
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:25
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:28
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:33
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:36
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:39
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:43
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:46
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:50
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:53
#: ../../content/applications/hr/frontdesk.rst:166
#: ../../content/applications/hr/frontdesk.rst:182
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:56
msgid ""
"The image selected for the station photo appears as the background image for"
" the station kiosk."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:59
#: ../../content/applications/hr/recruitment.rst:608
msgid "Options tab"
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:63
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:66
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:69
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:71
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:73
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:76
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:79
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:82
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:88
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:91
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:95
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:98
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:100
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:104
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:107
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:110
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:114
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:118
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:123
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:126
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:134
msgid "Side Message tab"
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:136
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:143
msgid "Drinks"
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:145
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:149
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:152
msgid "Enter the following information on the drink form:"
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:154
msgid ""
":guilabel:`Drink Name`: type the name of the drink option in this field. "
"This field is required."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:155
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:157
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:163
#: ../../content/applications/hr/frontdesk.rst:179
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:169
#: ../../content/applications/hr/frontdesk.rst:185
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:176
msgid "Station dashboard"
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:191
msgid "Visitors"
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:193
msgid ""
"To access a complete list of visitors that are currently checked in, "
"navigate to :menuselection:`Frontdesk app --> Visitors`."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:196
msgid ""
"The visitors are listed in a list view, with the following details that were"
" entered when they checked in:"
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:200
msgid ""
"By default, the :guilabel:`Planned or Checked-In` and :guilabel:`Today` "
"filters appear in the :guilabel:`Search...` bar."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:203
msgid ":guilabel:`Name`: the guest's name."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:204
msgid ":guilabel:`Visitor Company`: the company the guest represents."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:205
msgid ":guilabel:`Phone`: the guest's phone number."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:206
msgid ":guilabel:`Drinks`: the drink the guest requested."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:207
msgid ":guilabel:`Host`: who the guest is waiting to see."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:208
msgid ":guilabel:`CheckIn`: the date and time the guest checked in."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:209
msgid ""
":guilabel:`Checkout`: the date and time the guest checked out. As mentioned,"
" 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.rst:212
msgid ""
":guilabel:`Duration`: the amount of time the guest has been checked in for."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:213
msgid ":guilabel:`Station`: the location of where the guest checked in."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:214
msgid ""
":guilabel:`Status`: the status of the guest. The options are "
":guilabel:`Checked-In`, :guilabel:`Planned`, :guilabel:`Checked-Out`, or "
":guilabel:`Canceled`. In the default view, only guests with a "
":guilabel:`Checked-In` or :guilabel:`Planned` status are visible."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:217
msgid ":guilabel:`Email`: the guest's email address."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:219
msgid ""
"To the far right of the titled columns on the :guilabel:`Visitors` page is "
"an untitled column, where a guest's status can be updated."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:222
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.rst:225
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.rst:229
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.rst:232
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.rst-1
msgid ""
"The full list of currently checked in visitors, with the drinks to be served"
" highlighted."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:239
msgid ""
"If any column is not visible, or if a visible column is preferred to be "
"hidden, click the :guilabel:`Additional Options (two horizontal lines with "
"dots)` icon, located at the end of the column name list."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:243
msgid ""
"Clicking that reveals a drop-down menu of column options to enable or "
"disable. A :guilabel:`✅ (checkmark)` icon indicates the column is visible."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:247
msgid "Planned visitors"
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:249
msgid ""
"If a guest is expected to arrive at a future date and time, it is possible "
"to enter their information into the *Frontdesk* application in advance."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:252
msgid ""
"To create a planned guest, navigate to :menuselection:`Frontdesk app --> "
"Visitors --> New`. Then, enter the same information as any other "
":ref:`visitor <frontdesk/visitors>`. 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.rst:258
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.rst:263
msgid ""
"Only when a planned guest is checked in inside the application's visitor "
"list, their :guilabel:`Planned` status changes to :guilabel:`Checked-In`."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:266
msgid ""
"If a guest does check in using a kiosk, ensure all records are current, and "
"the list of currently on-site guests 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.rst:270
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.rst:274
msgid "Frontdesk flow"
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:276
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:279
msgid "Navigate to the kiosk in one of two ways:"
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:281
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:283
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:288
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:292
msgid "Visitor flow"
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:294
msgid ""
"When a visitor arrives at a facility, they approach a frontdesk kiosk, and "
"enter their information. The information requested 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.rst:299
msgid ""
"Once all the information is entered, the visitor taps the :guilabel:`Check "
"In` button."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:301
msgid ""
"If drinks were configured for the station, after tapping :guilabel:`Check "
"In`, a registration confirmation screen loads, along with the question: `Do "
"you want something to drink?`"
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:304
msgid ""
"The visitor can tap either :guilabel:`Yes, please`, or :guilabel:`No, thank "
"you`."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:306
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.rst:310
msgid ""
"If a drink selection was made, a `Thank you for registering! Your drink is "
"on the way.` message appears."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:313
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.rst:316
msgid ""
"Once the visitor has checked in, the person they are visiting, and any other"
" users who were configured to be notified when checks 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.rst:320
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: `(Visitor Name) just "
"checked-in. They requested (Drink Name).`"
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:324
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.rst:327
msgid ""
"To mark a drink as delivered, navigate to :menuselection:`Frontdesk app --> "
"Stations --> (#) Drinks to serve` on the desired station card."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:330
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.rst:334
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.rst:337
msgid ""
"To check visitors out properly, navigate to :menuselection:`Frontdesk app "
"--> Stations --> (#) On Site`. Doing so opens a list of all the visitors who"
" are currently checked-in at that station."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:340
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.rst:344
msgid ""
"Visitors do **not** check themselves out when they leave. It is important to"
" check out visitors for accurate record keeping."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:347
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/frontdesk.rst:353
msgid ""
"The *Frontdesk* application has two reports available: :guilabel:`Visitors` "
"and :guilabel:`Drinks`."
msgstr ""

#: ../../content/applications/hr/frontdesk.rst:355
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:358
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:361
msgid ""
"As with all reports in Odoo, the filters and groups can be modified to show "
"other metrics, as well."
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:102
msgid "Templates"
msgstr ""

#: ../../content/applications/hr/payroll.rst:104
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:109
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:112
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:117
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:120
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:122
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:125
msgid ""
":guilabel:`Work Entry Source`: select how the work entries are generated. "
"Choices are either:"
msgstr ""

#: ../../content/applications/hr/payroll.rst:127
msgid ""
":guilabel:`Working Schedule`: work entries are generated based on the "
"selected working schedule."
msgstr ""

#: ../../content/applications/hr/payroll.rst:128
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:131
msgid ""
":guilabel:`Planning`: work entries are generated based on the employee's "
"planning in the *Planning* application."
msgstr ""

#: ../../content/applications/hr/payroll.rst:134
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:136
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:138
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:140
msgid ":guilabel:`Wage on Payroll`: enter the monthly wage in the field."
msgstr ""

#: ../../content/applications/hr/payroll.rst:141
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:143
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:145
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:147
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:155
msgid "Salary information tab"
msgstr ""

#: ../../content/applications/hr/payroll.rst:157
msgid ""
":guilabel:`Wage Type`: select either :guilabel:`Fixed Wage` or "
":guilabel:`Hourly Wage` from the drop-down menu."
msgstr ""

#: ../../content/applications/hr/payroll.rst:159
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:163
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:166
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:168
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:172
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:182
msgid "Pre-tax benefits and post-tax deductions"
msgstr ""

#: ../../content/applications/hr/payroll.rst:184
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:187
msgid ""
"For example, some entries may pertain to retirement accounts, health "
"insurance benefits, and commuter benefits."
msgstr ""

#: ../../content/applications/hr/payroll.rst:190
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:196
msgid "Employment types"
msgstr ""

#: ../../content/applications/hr/payroll.rst:198
msgid ""
"To view all the pre-configured employment types, navigate to "
":menuselection:`Payroll application --> Configuration --> Contracts: "
"Employment Types`."
msgstr ""

#: ../../content/applications/hr/payroll.rst:201
msgid ""
"The employment types are presented in a list view on the "
":guilabel:`Employment Types` page."
msgstr ""

#: ../../content/applications/hr/payroll.rst:203
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:206
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:209
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:214
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:223
#: ../../content/applications/hr/payroll/work_entries.rst:3
msgid "Work entries"
msgstr ""

#: ../../content/applications/hr/payroll.rst:225
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:230
msgid ":doc:`Manage work entries <payroll/work_entries>`"
msgstr ""

#: ../../content/applications/hr/payroll.rst:233
msgid "Work entry types"
msgstr ""

#: ../../content/applications/hr/payroll.rst:235
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:240
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:243
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:251
msgid "New work entry type"
msgstr ""

#: ../../content/applications/hr/payroll.rst:253
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:257
#: ../../content/applications/hr/payroll.rst:717
msgid "General information section"
msgstr ""

#: ../../content/applications/hr/payroll.rst:259
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:261
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:264
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:269
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:272
msgid ""
":guilabel:`SDWorx code`: this code is only for companies that use SDWorx, a "
"payroll service provider."
msgstr ""

#: ../../content/applications/hr/payroll.rst:274
msgid ":guilabel:`Color`: select a color for the particular work entry type."
msgstr ""

#: ../../content/applications/hr/payroll.rst:277
msgid "Display in payslip section"
msgstr ""

#: ../../content/applications/hr/payroll.rst:279
msgid ""
":guilabel:`Rounding`: the rounding method selected determines how quantities"
" on timesheet entries are displayed on the payslip."
msgstr ""

#: ../../content/applications/hr/payroll.rst:282
msgid ":guilabel:`No Rounding`: a timesheet entry is not modified."
msgstr ""

#: ../../content/applications/hr/payroll.rst:283
msgid ""
":guilabel:`Half Day`: a timesheet entry is rounded to the closest half day "
"amount."
msgstr ""

#: ../../content/applications/hr/payroll.rst:284
msgid ""
":guilabel:`Day`: a timesheet entry is rounded to the closest full day "
"amount."
msgstr ""

#: ../../content/applications/hr/payroll.rst:287
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:293
msgid "Unpaid section"
msgstr ""

#: ../../content/applications/hr/payroll.rst:295
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 would be logged on a "
"timesheet but no compensation given would be for unpaid internships, unpaid "
"training, or volunteer work."
msgstr ""

#: ../../content/applications/hr/payroll.rst:301
msgid "Valid for advantages section"
msgstr ""

#: ../../content/applications/hr/payroll.rst:303
msgid ""
":guilabel:`Meal Voucher`: if the work entry should count towards a meal "
"voucher, check the box."
msgstr ""

#: ../../content/applications/hr/payroll.rst:304
msgid ""
":guilabel:`Representation Fees`: if the work entry should count towards "
"representation fees, check the box."
msgstr ""

#: ../../content/applications/hr/payroll.rst:306
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:310
msgid "Time off options section"
msgstr ""

#: ../../content/applications/hr/payroll.rst:312
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:315
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:319
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:321
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:328
msgid "Reporting section"
msgstr ""

#: ../../content/applications/hr/payroll.rst:330
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:340
msgid "Working schedules"
msgstr ""

#: ../../content/applications/hr/payroll.rst:342
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:346
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:350
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:353
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:363
msgid "New working schedule"
msgstr ""

#: ../../content/applications/hr/payroll.rst:365
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:368
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:372
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:378
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:381
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:395
msgid "Structure types"
msgstr ""

#: ../../content/applications/hr/payroll.rst:397
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:403
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:409
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:412
msgid ""
"There are two default structure types configured in Odoo: "
":guilabel:`Employee` and :guilabel:`Worker`. 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:422
msgid "New structure type"
msgstr ""

#: ../../content/applications/hr/payroll.rst:424
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:427
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:430
msgid ""
":guilabel:`Structure Type`: enter the name for the new structure type, such "
"as `Employee` or `Worker`."
msgstr ""

#: ../../content/applications/hr/payroll.rst:432
msgid ""
":guilabel:`Country`: select the country that the new structure type applies "
"to from the drop-down menu."
msgstr ""

#: ../../content/applications/hr/payroll.rst:434
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:437
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:440
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:442
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:446
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:451
msgid ""
":guilabel:`Regular Pay Structure`: type in the name for the regular pay "
"structure."
msgstr ""

#: ../../content/applications/hr/payroll.rst:452
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:458
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:461
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:471
msgid "New default working hours"
msgstr ""

#: ../../content/applications/hr/payroll.rst:473
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:479
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:481
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:484
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:488
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:490
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:494
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:498
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:502
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:505
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:508
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:512
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:518
msgid "Structures"
msgstr ""

#: ../../content/applications/hr/payroll.rst:520
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:523
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:527
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:530
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:537
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:545
#: ../../content/applications/hr/time_off.rst:193
msgid "Rules"
msgstr ""

#: ../../content/applications/hr/payroll.rst:547
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:551
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:554
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:558
msgid "Top section"
msgstr ""

#: ../../content/applications/hr/payroll.rst:560
msgid ""
":guilabel:`Rule Name`: enter a name for the rule. This field is required."
msgstr ""

#: ../../content/applications/hr/payroll.rst:561
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:563
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:566
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:568
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:570
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:572
msgid ""
":guilabel:`Appears on payslip`: tick the checkbox to have the rule appear on"
" employee payslips."
msgstr ""

#: ../../content/applications/hr/payroll.rst:573
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:575
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:583
msgid "General tab"
msgstr ""

#: ../../content/applications/hr/payroll.rst:586
msgid "Conditions"
msgstr ""

#: ../../content/applications/hr/payroll.rst:588
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:594
msgid "Computation"
msgstr ""

#: ../../content/applications/hr/payroll.rst:596
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:602
msgid "Company contribution"
msgstr ""

#: ../../content/applications/hr/payroll.rst:604
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:608
#: ../../content/applications/hr/payroll.rst:802
msgid "Description tab"
msgstr ""

#: ../../content/applications/hr/payroll.rst:610
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:614
msgid "Accounting tab"
msgstr ""

#: ../../content/applications/hr/payroll.rst:616
msgid ""
":guilabel:`Debit Account`: select the debit account from the drop-down menu "
"the rule affects."
msgstr ""

#: ../../content/applications/hr/payroll.rst:617
msgid ""
":guilabel:`Credit Account`: select the credit account from the drop-down "
"menu the rule affects."
msgstr ""

#: ../../content/applications/hr/payroll.rst:618
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:622
msgid "Rule parameters"
msgstr ""

#: ../../content/applications/hr/payroll.rst:625
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:631
msgid "Other input types"
msgstr ""

#: ../../content/applications/hr/payroll.rst:633
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:642
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:647
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:656
msgid "Salary attachment types"
msgstr ""

#: ../../content/applications/hr/payroll.rst:658
msgid ""
"Salary attachments, also thought of as \"wage garnishments\", are portions "
"of earnings taken out of a payslip for something specific. Much like all "
"other aspects of payroll configurations, the types of salary attachments "
"**must** be defined."
msgstr ""

#: ../../content/applications/hr/payroll.rst:662
msgid ""
"To view the currently configured salary attachments, navigate to "
":menuselection:`Payroll app --> Configuration --> Salary --> 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.rst:666
msgid ""
"To make a new type of salary attachment, click the :guilabel:`New` button. "
"Then, enter the :guilabel:`Name`, the :guilabel:`Code` (used in the salary "
"rules to compute payslips), and decide if it should have :guilabel:`No End "
"Date`."
msgstr ""

#: ../../content/applications/hr/payroll.rst-1
msgid "A new salary attachment form filled in."
msgstr ""

#: ../../content/applications/hr/payroll.rst:675
msgid "Salary package configurator"
msgstr ""

#: ../../content/applications/hr/payroll.rst:677
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:682
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:688
msgid "Benefits"
msgstr ""

#: ../../content/applications/hr/payroll.rst:690
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:694
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:703
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:707
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:711
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:714
msgid "The various fields for creating a benefit are as follows:"
msgstr ""

#: ../../content/applications/hr/payroll.rst:719
msgid ""
":guilabel:`Benefits`: enter the name for the benefit. This field is "
"required."
msgstr ""

#: ../../content/applications/hr/payroll.rst:720
msgid ""
":guilabel:`Benefit Field`: select from the drop-down menu the type of "
"benefit this is."
msgstr ""

#: ../../content/applications/hr/payroll.rst:721
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:726
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:730
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:732
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:735
msgid ""
":guilabel:`Impacts Net Salary`: tick the checkbox if the benefit should "
"impact the employee's net salary."
msgstr ""

#: ../../content/applications/hr/payroll.rst:737
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:739
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:742
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:745
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:747
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:755
msgid "Display section"
msgstr ""

#: ../../content/applications/hr/payroll.rst:757
msgid ""
":guilabel:`Show Name`: tick the checkbox to have the benefit name appear in "
"the salary package configurator."
msgstr ""

#: ../../content/applications/hr/payroll.rst:759
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:764
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:766
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:769
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:771
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:774
msgid ""
":guilabel:`Fold Label`: enter a name for the folded section of the benefit."
msgstr ""

#: ../../content/applications/hr/payroll.rst:775
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:779
msgid "Activity section"
msgstr ""

#: ../../content/applications/hr/payroll.rst:781
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:783
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:786
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:789
msgid ""
":guilabel:`Assigned to`: select the user the activity is automatically "
"assigned to, using the drop-down menu."
msgstr ""

#: ../../content/applications/hr/payroll.rst:793
msgid "Sign section"
msgstr ""

#: ../../content/applications/hr/payroll.rst:795
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:798
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:804
msgid ""
"Provide any additional information in this tab to help clarify the benefit."
msgstr ""

#: ../../content/applications/hr/payroll.rst:807
msgid "Personal info"
msgstr ""

#: ../../content/applications/hr/payroll.rst:809
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:813
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:817
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:821
msgid "An employee card can be thought of as an employee personnel file."
msgstr ""

#: ../../content/applications/hr/payroll.rst:823
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:831
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:834
msgid "To create a new personal info entry, click the :guilabel:`New` button."
msgstr ""

#: ../../content/applications/hr/payroll.rst:836
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:839
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:843
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:848
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:851
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:863
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:866
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:869
msgid ""
"To configure this section, navigate to :menuselection:`Payroll app --> "
"Configuration --> Salary Package Configurator: Resumé`."
msgstr ""

#: ../../content/applications/hr/payroll.rst:872
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:875
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:878
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:883
msgid ":guilabel:`Information`: type in a name for this field."
msgstr ""

#: ../../content/applications/hr/payroll.rst:884
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:888
msgid "New categories can be made if needed."
msgstr ""

#: ../../content/applications/hr/payroll.rst:890
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:895
msgid "Finally, click :guilabel:`Save & Close`."
msgstr ""

#: ../../content/applications/hr/payroll.rst:896
msgid ""
":guilabel:`Impacts Monthly Total`: tick the checkbox if this value is added "
"in the monthly total calculation."
msgstr ""

#: ../../content/applications/hr/payroll.rst:898
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:901
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:904
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:906
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:909
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:916
msgid "Jobs"
msgstr ""

#: ../../content/applications/hr/payroll.rst:918
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:924
#: ../../content/applications/hr/recruitment/new_job.rst:3
msgid "Job positions"
msgstr ""

#: ../../content/applications/hr/payroll.rst:926
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:930
msgid ""
"To view the job positions, navigate to :menuselection:`Payroll app --> "
"Configuration --> Jobs: Job Positions`."
msgstr ""

#: ../../content/applications/hr/payroll.rst:933
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:940
msgid ""
"To create a new job description, click the :guilabel:`New` button and a job "
"form appears."
msgstr ""

#: ../../content/applications/hr/payroll.rst:942
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:945
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:949
msgid ":doc:`payroll/contracts`"
msgstr ""

#: ../../content/applications/hr/payroll.rst:950
msgid ":doc:`payroll/payslips`"
msgstr ""

#: ../../content/applications/hr/payroll.rst:951
msgid ":doc:`payroll/work_entries`"
msgstr ""

#: ../../content/applications/hr/payroll.rst:952
msgid ":doc:`payroll/reporting`"
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, "
"their 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 in order to send and sign contracts. Please refer"
" to the :doc:`/applications/productivity/documents` and "
":doc:`/applications/productivity/sign` documentation."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:15
msgid ""
"To view the employee contracts, go to the :menuselection:`Payroll app --> "
"Employees --> Contracts` from the top menu. All employee contracts, and "
"their current contract status, are displayed in a default kanban view. The "
"default view displays both running contracts and contracts that need action."
" Expired and canceled contracts are hidden in the default view."
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. The default contracts view in the "
"*Payroll* application displays running contracts and contracts needing "
"attention, while the default contracts view in the *Employees* application "
"displays all contracts in a kanban view, organized by their stage, "
"regardless of status. All contracts can be viewed by changing the filters."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:32
msgid "Create a new contract"
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:34
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 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-1
msgid "New contract form to be filled in when creating a new contract."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:45
msgid ""
":guilabel:`Contact Reference`: Type in the name or title for the contract, "
"such as `John Smith Contract`."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:47
msgid ""
":guilabel:`Company`: Select the company the contract applies to by clicking "
"on the drop-down menu. A new company can be created by typing the name in "
"the field, then clicking either :guilabel:`Create` to create the new "
"company, or :guilabel:`Create and Edit` to create the new company and edit "
"the company details."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:51
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."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:54
msgid ""
":guilabel:`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 :guilabel:`< > (arrow)` icons, then clicking on the "
":guilabel:`date`."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:57
msgid ""
":guilabel:`Working Schedule`: Select one of the working schedules from the "
"drop-down menu."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:60
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 --> Configuration --> Working Times` and "
"either :guilabel:`Create` a new working time or click on an existing working"
" time and edit it by clicking :guilabel:`Edit`."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:68
msgid ""
":guilabel:`Employee`: Name of the employee that the contract applies to."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:69
msgid ":guilabel:`Department`: The department the contract applies to."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:70
msgid ""
":guilabel:`Job Position`: The specific job position the contract applies to."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:71
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:74
msgid ""
":guilabel:`CDI` is an open-ended contract with only a start date but no end "
"date."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:75
msgid ":guilabel:`CDD` is a contract with both a start date and an end date."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:76
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:79
msgid ""
":guilabel:`End Date`: If the contract has a specific end date, click the "
"drop-down menu, navigate to the correct month and year using the arrow "
"icons, then click on the date."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:81
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."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:83
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:87
msgid "Contract details"
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:89
msgid ""
"The contract details section allows for the addition and editing of a "
"contract, and the ability to send the contract to the employee for approval "
"and signatures."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst-1
#: ../../content/applications/hr/payroll/contracts.rst-1
msgid "Contract details in optional tabs for a new contract."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:96
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:98
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:100
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:102
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:106
msgid "Modifying a contract"
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:108
msgid ""
"Click the :guilabel:`External Link` button at the end of each line to open "
"the corresponding contract template and make any changes."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:115
msgid ""
"A pop-up window appears with all the contract details. Modify the fields for"
" the contract as needed."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst-1
msgid "Edit the details for the contract."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:121
msgid ":guilabel:`Tags`: Select any tags associated with the contract."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:122
msgid ""
":guilabel:`Signed Document Workspace`: This is where the signatures are "
"stored. Choose a pre-configured workspace or create a new one."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:124
msgid ""
":guilabel:`Signed Document Tags`: Select or create any tags associated only "
"with the signed contract as opposed to the original unsigned contract."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:126
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, to the newly updated contract specifically written for them."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:129
msgid ""
":guilabel:`Who can Sign`: Select either :guilabel:`All Users` or "
":guilabel:`On Invitation`."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:131
msgid ""
":guilabel:`All Users`: Any user in the organization can sign the contract."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:132
msgid ""
":guilabel:`On Invitation`: Only users selected in this field can sign the "
"contract."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:134
msgid ""
":guilabel:`Invited Users`: Select the person(s) that can sign the document."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:135
msgid ""
":guilabel:`Document`: The attached document can be replaced by clicking the "
":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 :guilabel:`🗑️ (trash can)` icon."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:139
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:144
msgid "Salary information"
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst-1
msgid "Optional tabs for a new contract."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:150
msgid ""
"This section is where the specific salary details are defined. This section "
"is country-specific, so depending on where the company is located, these "
"fields may vary."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:153
msgid ""
"Enter the amount in the various fields, or check a box to apply a benefit. "
"Some options that can be entered here include :guilabel:`Meal Vouchers`, "
":guilabel:`Fuel Card`, :guilabel:`Internet`, :guilabel:`Paid Time Off`, etc."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:157
msgid ""
"Some fields may be automatically filled in based off of the contracts "
"selected in the :guilabel:`Contract Details` tab."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:161
msgid "Attachment of salary"
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:163
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:167
msgid ""
"To add a new deduction, click :guilabel:`Add a line`. Type in a description "
"for the allocation under :guilabel:`Description`."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst-1
msgid "Enter a new line for each type of garnishment."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:174
msgid ""
"Select the :guilabel:`Garnished Type` from the drop-down menu. Choose from:"
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:176
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:178
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:180
msgid ""
":guilabel:`Child Support`: Any payments taken out specifically for child "
"support."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:182
msgid ""
"Enter the start and end dates the entry applies to. Click on the drop-down "
"menu under :guilabel:`From` and :guilabel:`To`, navigate to the correct "
"month and year by using the :guilabel:`< > (arrow)` icons, then click on the"
" :guilabel:`date`."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:186
msgid ""
"Last, enter the :guilabel:`Amount` that each payslip pays towards the entry."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:188
msgid ""
"To delete a line, click the :guilabel:`🗑️ (trash can)` icon at the end of "
"the line."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:191
msgid "Save and send the contract"
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:193
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:196
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:202
msgid ""
":guilabel:`Generate Simulation Link`: This option is for Belgian companies "
"only. 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 Offer` to send an email to "
"the employee so they can sign the contract."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:0
msgid "Sends a link to the employee for the contract."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:212
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:215
msgid ""
":guilabel:`Signature Request`: Click this and a pop-up window appears 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:0
msgid "Request a signature for the contract via email."
msgstr ""

#: ../../content/applications/hr/payroll/contracts.rst:224
msgid ""
":guilabel:`Credit Time`: This option is for Belgian companies only. When "
"clicked, a pop-up window appears that allows for the changing of working "
"times, and can compute time off."
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:104
msgid "Worked days & inputs tab"
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:106
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:110
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:113
msgid ""
"Click :guilabel:`Add a line` to create an entry in the :guilabel:`Other "
"Inputs` section."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:115
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:124
msgid "Salary computation tab"
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:126
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:129
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:137
msgid "Other info tab"
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:139
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:141
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:143
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:145
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:148
msgid "Then, click on the desired date to select it."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:149
msgid ""
":guilabel:`Date Account`: enter the date on which the payslip should be "
"posted in this field."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:150
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:153
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:155
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:163
msgid "Process the new payslip"
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:165
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:170
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:175
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:178
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:181
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:185
msgid ""
"The database may need to be refreshed for the payslip and email to appear."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:187
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:194
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:200
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:210
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:215
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:219
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:222
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:229
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:232
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:236
msgid ""
"Payslips **cannot** be completed if there are any warnings or issues "
"associated with the payslip."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:241
msgid "All payslips"
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:243
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:247
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:250
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:254
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:256
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:258
msgid ":guilabel:`Done`: the payslip is calculated and ready to be paid."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:259
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:265
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:268
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:273
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:279
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:288
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:299
msgid ""
"Both *To Pay* and *All Payslips* display all the detailed information for "
"each payslip."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:302
msgid "Batches"
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:304
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:308
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:317
msgid "Create a new batch"
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:319
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:323
msgid "On the new payslip batch form, enter the :guilabel:`Batch Name`."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:325
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:329
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:340
msgid "Process a batch"
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:342
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:345
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:352
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:356
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:360
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:364
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:369
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:373
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:381
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:384
#: ../../content/applications/hr/payroll/payslips.rst:406
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:388
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:395
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:399
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:401
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:404
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:410
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:417
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:421
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:425
msgid "Generate warrant payslips"
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:427
msgid "Commissions are paid to employees in Odoo using *warrant payslips*."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:429
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:432
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:436
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:443
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:448
msgid ""
"In the :guilabel:`Department` field, select the desired department from the "
"drop-down menu."
msgstr ""

#: ../../content/applications/hr/payroll/payslips.rst:450
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:453
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:457
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:460
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:463
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:466
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
#: ../../content/applications/hr/payroll/reporting.rst:225
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:188
msgid "Work entry analysis"
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:190
msgid ""
"The default :guilabel:`Work entry 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/reporting.rst:194
msgid ""
"The work entries appear in a pivot table, with the default filters of "
"`Current month: (Month)(Year)` and `Validated`. The various types of "
":doc:`work_entries` are listed on the left-hand side (x-axis), while the "
":guilabel:`Total` values appear along the top (the y-axis)."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:198
msgid ""
"To change the displayed view, click the :guilabel:`➕ (plus)` icon next to "
"the word :guilabel:`Total`, then click on one of the grouping options. The "
"available 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/reporting.rst:203
msgid ""
"To add a new group to sort the data, click :guilabel:`Add Custom Group`, "
"then click one of the presented options."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:207
msgid ""
"Wherever a :guilabel:`➕ (plus)` icon appears on a pivot table, the "
"information can be further grouped. Click on a :guilabel:`➕ (plus)` icon to "
"reveal the available grouping options."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:210
msgid ""
"Click on a :guilabel:`➖ (minus)` icon anywhere on the pivot table to remove "
"that respective grouping."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:213
msgid ""
"It is possible to compare the current :guilabel:`Work entry analysis` report"
" to the previous month or the previous year. To view these comparisons, "
"click the :guilabel:`⬇️ (down arrow)` icon in the search bar to reveal the "
"various :ref:`filter <payroll/filters>` and grouping options."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:217
msgid ""
"In the section titled :guilabel:`Comparison`, click on either "
":guilabel:`Current Month: Previous Period` or :guilabel:`Current Month: "
"Previous Year`. The report updates and displays the previous time period "
"values, as well as the :guilabel:`Variation` between the two."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst-1
msgid ""
"A pivot table comparing the work entries of the current month and the "
"previous month."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:229
msgid ""
"The data can also be inserted into a spreadsheet. Click the "
":guilabel:`Insert in Spreadsheet` button and 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:236
msgid ""
"The work entry analysis spreadsheet is :ref:`stored in the same locations "
"<payroll/doc-storage>` as a pivot table."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:240
msgid "Salary attachment report"
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:242
msgid ""
"The :guilabel:`Salary Attachment Report` shows all deductions or allocations"
" per employee, such as child support payments and wage garnishments. To view"
" this report, navigate to :menuselection:`Payroll app --> Reporting --> "
"Salary Attachment Report`."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst-1
msgid ""
"View the Attachment of Salary report that shows all salary garnishments."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:250
msgid ""
"The employees are listed in the left-side column, while the different "
"deductions are listed in the top row, organized by deduction and monthly "
"individual payslips."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:253
msgid ""
"The report can be exported as an XLSX file, or inserted into a spreadsheet, "
"using the corresponding buttons at the top."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:256
msgid ""
"Click the :guilabel:`Measures` button to reveal the options of what data can"
" be displayed. :guilabel:`Assignment of salary`, :guilabel:`Attachment of "
"salary`, :guilabel:`Child support`, and :guilabel:`Count` can all be "
"selected or deselected by clicking on the item. If an item has a checkmark "
"next to it, that information is displayed."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst-1
msgid "Select the options to be displayed in the Salary Attachment Report."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:265
msgid ""
"The :guilabel:`Salary Attachment Report` can be compared to the report for "
"the previous time period or the previous year. To view these comparisons, "
"click the :guilabel:`⬇️ (down arrow)` icon in the search bar to reveal the "
"various :ref:`filter <payroll/filters>` and grouping options."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:269
msgid ""
"In the section titled :guilabel:`Comparison`, click on either "
":guilabel:`Payslip End Date: Previous Period` or :guilabel:`Payslip End "
"Date: Previous Year`. The report updates and displays the previous time "
"period values, as well as the :guilabel:`Variation` between the two."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:278
msgid ""
"At the top of each report, the default filters are shown inside the "
":guilabel:`Search...` box."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:280
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:284
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:291
msgid ""
"The :guilabel:`Payroll` report has only one default filter, the `Last 365 "
"Days Payslip` filter."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:293
msgid ""
"The :guilabel:`Salary Attachment Report` has only one default filter, the "
"`Payslip End Date: (Year)` filter."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:296
msgid ""
"All reports can include custom filters, or group information, by different "
"metrics (employee, department, company, etc.)."
msgstr ""

#: ../../content/applications/hr/payroll/reporting.rst:299
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:302
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:305
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:310
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:314
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/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:46
msgid "Add a new work entry"
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:48
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:52
msgid "A :guilabel:`Create` work entry pop-up form appears."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:56
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:59
msgid ""
":guilabel:`Employee`: select the employee the work entry is for, using the "
"drop-down menu."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:60
msgid ""
":guilabel:`Work Entry Type`: select the :ref:`work entry type <payroll/work-"
"entries-config>` using the drop-down menu."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:62
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:65
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:69
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:72
msgid ""
"When the date and time are correct for the entry, click the "
":guilabel:`Apply` button."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:73
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:77
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:87
msgid "Conflicts"
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:89
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:93
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:97
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:105
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:108
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:112
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:120
msgid "Time off conflicts"
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:122
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:126
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:129
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:133
msgid "Resolve on work entry"
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:135
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:138
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:143
msgid "Resolve on time off request"
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:145
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:149
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:156
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:159
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:162
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:169
msgid "Regenerate work entries"
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:171
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:174
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:180
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:183
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:186
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:189
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:192
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:200
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:204
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:208
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:212
msgid "Generating payslips"
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:214
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:219
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:223
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:226
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:229
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:232
msgid ""
"Click the :guilabel:`Create Draft Entry` button to create the payslips for "
"the batch."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:234
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:242
msgid "Printing payslips"
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:244
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:247
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:251
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:258
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:262
msgid "Time off to report"
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:264
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:268
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:272
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:276
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:283
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:287
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:295
msgid "Defer multiple time off entries"
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:297
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:301
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:305
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:314
msgid "Defer individual time off entries"
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:316
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:318
msgid ""
"Click on an individual time off request, and the details for that request "
"load."
msgstr ""

#: ../../content/applications/hr/payroll/work_entries.rst:320
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:324
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:329
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:337
msgid ":ref:`Configure work entries <payroll/work-entries-config>`"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:6
#: ../../content/applications/hr/recruitment/new_job.rst:51
msgid "Recruitment"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:8
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, to sending a job offer, just to name a few. This "
"process is referred to as the 'applicant flow'."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:13
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:17
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:21
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:26
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 will be "
"visible on all job positions."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:35
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:44
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 five default stages in Odoo:"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:48
msgid ":ref:`Initial Qualification <recruitment/initial-qualification>`"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:49
msgid ":ref:`First Interview <recruitment/first-interview>`"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:50
msgid ":ref:`Second Interview <recruitment/second-interview>`"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:51
msgid ":ref:`Contract Proposal <recruitment/contract-proposal>`"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:52
msgid ":ref:`Contract Signed <recruitment/contract-signed>`"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:54
msgid ""
"The last column, :guilabel:`Contract Signed`, is folded by default, meaning "
"that the column appears in 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:63
msgid ""
"Each stage has a color-coded bar beneath the stage name, giving information "
"about the applicant's status in the stage. The colors are:"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:66
msgid ""
":guilabel:`Green`: there are applicants in the stage with an activity that "
"is either already scheduled or needs to be scheduled in the future (such as "
"a phone call or interview), according to the parameters for that particular "
"stage."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:69
msgid ""
":guilabel:`Yellow`: there are applicants in the stage with an activity "
"either scheduled for today or due to be scheduled today."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:71
msgid ""
":guilabel:`Red`: there are applicants in the stage with overdue activities "
"which need to be scheduled."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:73
msgid ""
":guilabel:`Gray`: there are either no activities currently scheduled and no "
"future activities that are required to be scheduled, or there are no "
"applicants currently in the stage."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:79
msgid "Customize stages"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:81
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:85
msgid "New stage"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:87
msgid ""
"To create a new stage, click on :guilabel:`+ Add a Column` and a new column "
"appears. Enter the title for the new stage in the :guilabel:`Column 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 column creation."
msgstr ""

#: ../../content/applications/hr/recruitment.rst-1
msgid ""
"The plus sign to click in order to add a new column to the kanban stages."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:99
msgid "Modify stage"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:101
msgid ""
"To modify the settings of a stage, hover over the name of the stage, and a "
":guilabel:`⚙️ (gear)` icon appears in the upper right hand side of the "
"stage. Click on the :guilabel:`⚙️ (gear)` icon and a menu appears. Then "
"click on the :guilabel:`Edit Stage` option. An :guilabel:`Edit Column` form "
"appears. Make any modifications to the form, then click :guilabel:`Save` "
"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:112
msgid "Edit column form"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:114
msgid ""
"The :guilabel:`Edit Column` form is where the stage's settings are "
"configured. The only required fields are the :guilabel:`Stage Name`, and the"
" :guilabel:`Tooltips` section."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:117
msgid "The fields to be populated or modified are:"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:119
msgid ":guilabel:`Stage Name`: type in a name for the stage."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:120
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 will automatically be sent to the applicant using the "
"selected template."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:123
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:125
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:129
msgid ""
":guilabel:`Job Specific`: if the stage only applies to a specific job "
"position(s), select the job position(s) from the drop-down menu. Multiple "
"job positions can be selected."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:131
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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:135
msgid ""
":guilabel:`Tooltips` section: there are three pre-configured 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:140
msgid ""
":guilabel:`Requirements`: enter any internal notes for this stage explaining"
" any requirements of the stage."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:144
msgid "Delete stage"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:146
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 :guilabel:`⚙️ (gear)` icon appears."
" First, click on the :guilabel:`⚙️ (gear)` icon to reveal a drop-down menu, "
"then click :guilabel:`Delete`. A pop-up warning appears, asking "
":guilabel:`Are you sure you want to remove this column?`. Click "
":guilabel:`OK` to delete the column."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:152
msgid ""
"If there are applicants currently in the stage being deleted, an error pops "
"up when attempting to delete the stage, explaining that there are records in"
" the stage which need to be deleted, archived, or moved to a different stage"
" before deleting."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:157
msgid "Email templates"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:159
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:162
msgid ""
":guilabel:`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:`First "
"Interview` stage."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:165
msgid ""
":guilabel:`Applicant: Interest`: 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."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:168
msgid ""
":guilabel:`Applicant: 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:171
msgid ""
":guilabel:`Applicant: Refuse`: this template is used when an applicant is no"
" longer being considered for the position."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:173
msgid ""
":guilabel:`Applicant: Your Salary Package`: this template is used when "
"offering an applicant a position. This informs the applicant they can "
"configure their salary package."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:177
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:180
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. Click the "
":guilabel:`⤢ (double arrow)` full composer icon in the bottom right corner "
"of the :guilabel:`Send Message` tab in the chatter."
msgstr ""

#: ../../content/applications/hr/recruitment.rst-1
msgid "Send an email from the chatter."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:188
msgid ""
"An email composer pop-up loads, with the :guilabel:`Recipients` and "
":guilabel:`Subject` pre-populated. The applicant's email address is entered "
"on the :guilabel:`Recipients` line, and the :guilabel:`Subject` is `Re: "
"(Subject / Application Name)`. The email body is empty by default."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:192
msgid ""
"To use a pre-configured email template, click the drop-down next to the "
":guilabel:`Load template` field in the lower right section of the window. "
"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:199
msgid ""
"Only the email templates that are configured for the model will load. There "
"are other email templates pre-configured in Odoo, but if they are not "
"configured for the recruitment application, they will not appear in the list"
" of available templates."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:203
msgid ""
"If any attachments are to be added, click the :guilabel:`Attach A File` "
"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 "
":guilabel:`X (Delete)` icon to the right of the attachment. If any changes "
"need to be made to the email, edit the body of the email. If the edits "
"should be saved to be used in the future, the email can be saved as a new "
"template. Click the :guilabel:`Save As New Template` button in the bottom "
"right corner. To send the email, click :guilabel:`Send` and the email will "
"be sent to the applicant. The email then appears in the chatter."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:212
msgid "Stage flow"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:214
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 to the"
" desired stage, or the stage can be modified on the applicant's card."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:218
msgid ""
"To change the stage on the applicant's card, click on the applicant's card "
"in the kanban view to go to a detailed view of the card. The current stage "
"for the card is highlighted in purple at the top, above the card. Simply "
"click the desired stage for the card, and the stage changes. A log note "
"indicating the stage change appears in the chatter. Navigate back to the "
"kanban view by clicking on :guilabel:`Applications` in the breadcrumb menu "
"in the top left, and the applicant's card now appears in the new stage."
msgstr ""

#: ../../content/applications/hr/recruitment.rst-1
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.rst:233
msgid "Initial qualification"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:236
msgid ""
"The following information is based on Odoo's default recruitment pipeline "
"flow. Be advised that if modifications are made to create a customized "
"recruitment pipeline flow, it will vary from the following information."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:240
msgid ""
"All applicants appear in the :guilabel:`Initial Qualification` stage, "
"whether submitted online or if the applicant is manually entered by a "
"recruiter. When the applicant's card is created, Odoo automatically "
"populates the applicant's :guilabel:`Name`, :guilabel:`Email address`, and "
":guilabel:`Phone number` on the applicant's card. This information is "
"required when applying for a job position."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:246
msgid ""
"If the applicant entered any information in the :guilabel:`Short "
"Introduction` section of the online application, it is populated in the "
":guilabel:`Application Summary` tab at the bottom of the applicant's card. "
"If a resumé was attached to the online application, the resumé appears in "
"the attachments section of the chatter, and is also stored in the "
"*Documents* application. To find the recruitment documents stored in the "
"Documents application, navigate to the main :menuselection:`Documents` "
"dashboard, and click the folder labeled :guilabel:`Recruitment` on the right"
" side. All recruitment documents will be stored within that folder."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:255
msgid "Send interview"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:257
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.rst:260
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 example, 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. For more information on creating and editing interview"
" forms, refer to the :doc:`../hr/recruitment/new_job` documentation."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:269
msgid ""
"In order to send an email to an applicant, there must be an email address on"
" the applicant's card. If an email address is not entered on the applicant's"
" card, when :guilabel:`Send Interview` is clicked, the applicant's card "
"appears instead of the :guilabel:`Survey` pop-up window. Enter the email "
"address in the email field, then click :guilabel:`Save`. Once the "
"applicant's card is saved, the applicant's card closes and the "
":guilabel:`Survey` pop-up window appears."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:275
msgid ""
"To send an interview to an applicant, click on an applicant's card to "
"navigate to a detailed view of the applicant's card. At the top of the "
"applicant's card, click the button labeled :guilabel:`Send Interview`."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:279
msgid ""
"If the applicant's card has an email address on file, a :guilabel:`Survey` "
"pop-up window appears, with all the information populated. If an email is "
"not on the applicant's card, then a contact form appears. Enter the "
"applicants email address, then click :guilabel:`Save`. The card closes and "
"the :guilabel:`Survey` pop-up window appears."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:284
msgid ""
"Odoo refers to the interview forms as *surveys*. These email templates also "
"use dynamic placeholders to personalize the email to the applicant and the "
"job position. Add any additional recipients for the survey if more people "
"should receive the email. If an email is in the database as a contact, add "
"that contact on the :guilabel:`Recipients` line. 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 to the :guilabel:`Additional emails` "
"line."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:291
msgid ""
"If any attachments need to be added, click the :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 :guilabel:`Attachments` button."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:295
msgid ""
"If the emailed interview must be completed by a specific date, select a date"
" for the :guilabel:`Answer deadline` in the lower-right area of the pop-up "
"window. Click on the line next to :guilabel:`Answer deadline`, and a "
"calendar selector appears. Use the :guilabel:`< (left)` and :guilabel:`> "
"(right)` arrows on either side of the month to navigate to the desired "
"month, then click on the :guilabel:`day` to select the date."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:301
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.rst:305
msgid ""
"To send the email with the interview link to the applicant, click "
":guilabel:`Send` at the bottom of the email pop-up."
msgstr ""

#: ../../content/applications/hr/recruitment.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:314
msgid "Refuse"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:316
msgid ""
"At any point in the recruitment pipeline, an applicant can be refused from "
"the job application process. To refuse an applicant, click on an applicant's"
" card to navigate to a detailed view of the applicant's card. At the top of "
"the applicant's card, there are several buttons. Click the one labeled "
":guilabel:`Refuse`."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:321
msgid ""
"A :guilabel:`Refuse Reason` pop-up appears. Select the :guilabel:`Refuse "
"Reason` from the drop-down menu. The default refuse reasons in Odoo are: "
":guilabel:`Doesn't fit the job requirements`, :guilabel:`The applicant is "
"not interested anymore`, and :guilabel:`The applicant gets a better offer`. "
"These three refusal reasons have pre-configured email templates associated "
"with them. Additional refusal reasons can be created and existing ones can "
"be modified or deleted. To add a new refusal reason, type in the name of the"
" reason, then click :guilabel:`Create and Edit...`. A :guilabel:`Create: "
"Refuse Reason` pop-up window appears. Type in the name of the new email "
"template in the :guilabel:`Email Template` field, and click "
":guilabel:`Create and Edit...`. A :guilabel:`Create: Email Template` window "
"loads. Configure the new email template, then click :guilabel:`Save`."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:333
msgid ""
"Pre-configured email templates in Odoo sometimes use dynamic placeholders, "
"which are customized pieces of data that populate dynamic content. For "
"example, if the applicant's name is a piece of dynamic content, the "
"applicant's name will appear anytime that dynamic placeholder appears on the"
" email template. For more detailed information on email templates, refer to "
"the :doc:`../general/companies/email_template` documentation."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:339
msgid ""
"An email template populates the :guilabel:`Email Template` field after a "
"refusal reason is selected. If an email should not be sent to the applicant,"
" uncheck the :guilabel:`Send Email` checkbox. To view the email template, "
"click the :guilabel:`External Link` icon to the right of the email template "
"selected. The email template loads in the pop-up window, and can be modified"
" if needed. After making modifications, click :guilabel:`Save`. To close the"
" email template, click :guilabel:`Discard`."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:345
msgid ""
"To send the refusal email to the applicant, click :guilabel:`Send`. The "
"refusal email is sent to the applicant, and a :guilabel:`Refused` banner "
"appears on the applicant's card."
msgstr ""

#: ../../content/applications/hr/recruitment.rst-1
msgid ""
"An applicant's card with the refused banner appearing in the top right "
"corner in red."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:352
msgid ""
"After refusal, the applicant's card is no longer visible in the job "
"position's kanban view. To view refused applicants, navigate to the "
":menuselection:`Recruitment app --> Applications --> All Applications`. All "
"applications for all job positions are presented in a list view. To view the"
" refused applicants only, click :guilabel:`Filters`, then click "
":guilabel:`Archived/Refused`. All applicants that have been archived and/or "
"refused appear in the list. To further organize this list and view refusals "
"by job position, click :guilabel:`≣ Group By`, then click :guilabel:`Job`."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:360
msgid "New applicant"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:362
msgid ""
"An applicant card can be manually added if needed. If an applicant needs to "
"be added to the list of prospective candidates and an applicant card has not"
" been created yet (they have not applied for the job online yet) an "
"applicant card can be easily added from the job position kanban view in one "
"of two ways, using either the :ref:`Quick add <recruitment/quick-add-"
"applicant>` icon or the :ref:`Create <recruitment/create-new-applicant>` "
"button."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:371
msgid "Quick add"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:373
msgid ""
"Quickly add a new applicant using the :guilabel:`Quick add` icon. If not "
"already in the job position kanban view, navigate to the main recruitment "
"dashboard, and click the :guilabel:`New Applicants` button on the job "
"position card that the applicant should be added to. Then, click on the "
"small :guilabel:`+ (plus sign) Quick add` icon in the top right of the "
":guilabel:`Initial Qualification` stage to quickly add a new applicant."
msgstr ""

#: ../../content/applications/hr/recruitment.rst-1
msgid ""
"All the fields for a new applicant form entered when using the Quick Add "
"option."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:383
msgid "Enter the following information on the card:"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:385
msgid ""
":guilabel:`Subject/Application Name`: this is the only required field. Enter"
" the title for the card. Typically this is the applicant's name and job "
"position being applied to, for example: `Laura Smith - Experienced "
"Developer`. This field is not visible in the kanban view (unless in the "
"Developer mode), but is visible on the individual card."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:389
#: ../../content/applications/hr/recruitment.rst:434
msgid ":guilabel:`Applicant's Name`: enter the applicant's name."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:390
#: ../../content/applications/hr/recruitment.rst:435
msgid ":guilabel:`Email`: enter the applicant's email address."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:391
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 will appear in the selected job position."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:396
msgid ""
"After the information is entered, click :guilabel:`Add`. The applicant "
"appears in the list, and a new blank applicant card appears. Click either "
"the :guilabel:`🗑️ (delete)` icon or click anywhere on the screen to close "
"the card."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:400
msgid ""
"If preferred, after entering the applicant name, click :guilabel:`Edit` and "
"a detailed :guilabel:`Applicant Form` loads. :ref:`Enter the information on "
"the form <recruitment/applicant-details>`, then click :guilabel:`Save`"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:407
msgid "Create"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:409
msgid ""
"Add a new applicant including all the relevant information using the "
":guilabel:`Create` button. If not already in the kanban view for the job "
"position to add an applicant to, navigate to the main recruitment dashboard,"
" and click the :guilabel:`New Applicants` button on the job position card "
"that the applicant should be added to. Then, click the :guilabel:`Create` "
"button in the top left of the kanban view and an applicant form loads."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:415
msgid ""
"Certain fields on the applicant card may be pre-populated, depending on how "
"the job position is configured. Typically, the :guilabel:`Job` section, as "
"well as the :guilabel:`Recruiter` field, are all pre-populated."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:419
msgid ""
"Enter the following information on the new applicant form. Note that not all"
" fields listed below may be visible. Depending on installed applications and"
" configurations, some fields may not be displayed."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:426
msgid "Applicant section"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:428
msgid ""
":guilabel:`Subject/Application Name`: this is the only required field. Enter"
" the title for the card. Typically this is the applicant's name and job "
"position being applied to, for example: `Laura Smith - Experienced "
"Developer`. This field is not visible in the kanban view, unless the "
":guilabel:`Applicant's Name` is left blank. If there is no "
":guilabel:`Applicant's Name`, then the :guilabel:`Subject/Application Name` "
"is what is displayed on the applicant card in the kanban view."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:436
msgid ":guilabel:`Phone`: enter the applicant's phone number."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:437
msgid ":guilabel:`Mobile`: enter the applicant's mobile number."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:438
msgid ""
":guilabel:`Degree`: select the applicant's highest level of education earned"
" from the drop-down menu. Options are :guilabel:`Graduate`, "
":guilabel:`Bachelor Degree`, :guilabel:`Master Degree`, or "
":guilabel:`Doctoral Degree`. The :guilabel:`Graduate` option indicates "
"graduating 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.rst:443
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, the click "
":guilabel:`Create \"new tag\"`."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:445
msgid ""
":guilabel:`Interviewer`: select the person who will be conducting the "
"interview(s) from the drop-down menu. The person must have either "
"*recruiter* or *officer* rights configured for the Recruitment application "
"in order to appear on the drop-down."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:448
msgid ""
":guilabel:`Recruiter`: select the person responsible for the entire "
"recruitment process for the job position. Only *users* can be selected, and "
"all users are presented in the drop-down to select from."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:451
msgid ""
":guilabel:`Appreciation`: click on one of the stars to select a rating for "
"the applicant. One star indicates :guilabel:`Good`, two stars indicates "
":guilabel:`Very Good`, and three stars indicates :guilabel:`Excellent.`"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:454
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 to appear."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:459
msgid "Job section"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:461
msgid ""
"The following fields are pre-populated when creating a new applicant, as "
"long as these field are specified on the Job Position. Editing the fields is"
" possible, if desired."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:464
msgid ""
":guilabel:`Applied Job`: select the job position the applicant is applying "
"to from the drop-down menu."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:466
msgid ""
":guilabel:`Department`: select the department the job position falls under "
"from the drop-down menu."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:468
msgid ""
":guilabel:`Company`: select the company the job positions is for using the "
"drop-down menu."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:471
msgid "Contract section"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:473
msgid ""
":guilabel:`Expected Salary`: enter the amount the applicant is requesting "
"for the role 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.rst:476
msgid ""
":guilabel:`Expected Salary - Extra advantages...`: if any extra advantages "
"are requested by the applicant, enter it in this field. This should be short"
" and descriptive, such as `1 week extra vacation` or `dental plan`."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:479
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.rst:481
msgid ""
":guilabel:`Proposed Salary - Extra advantages...`: if any extra advantages "
"are offered to the applicant, enter it in this field. This should be short "
"and descriptive, such as `1 week extra vacation` or `dental plan`."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:484
msgid ""
":guilabel:`Availability`: using the calendar module in the drop-down menu, "
"select the available start date for the applicant."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:488
msgid "Application summary tab"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:490
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.rst-1
msgid "All the fields for a new applicant form entered."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:500
msgid "First interview"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:502
msgid ""
"After an applicant has passed the :guilabel:`Initial Qualification` stage, "
"they can be moved to the :guilabel:`First Interview` stage in the job "
"position kanban view. To move the applicant to the next stage, drag and drop"
" the applicant's card to the :guilabel:`First Interview` stage, or click on "
"the :guilabel:`First Interview` stage button at the top of the individual "
"applicant's card."
msgstr ""

#: ../../content/applications/hr/recruitment.rst-1
msgid ""
"An applicant's card moves from one stage t another by using the click and "
"drag method."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:511
msgid ""
"When the applicant's card moves to the :guilabel:`First Interview` stage, an"
" acknowledgement email is automatically sent to the applicant. The email is "
"created using an email template titled :guilabel:`Applicant: "
"Acknowledgement`. This email template is pre-configured in Odoo, and "
"contains dynamic placeholders for the job position, the recruiter's name, "
"and the company's information. Once the email is sent, the email appears in "
"the chatter."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:522
msgid ""
"When a date and time have been agreed upon for both the applicant and "
"interviewer, the interview can be scheduled. To schedule an interview, "
"whether a phone or in-person interview, click the :guilabel:`Meeting` smart "
"button at the top of the applicant's record."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:526
msgid ""
"The applicant's card can be found by navigating to the "
":menuselection:`Recruitment application` dashboard, click on a "
":guilabel:`New Applications` button in the job position card, then click on "
"the applicant's card."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:531
msgid ""
"The meeting smart button will display :guilabel:`No Meeting` if no meetings "
"are currently scheduled. For new applicants who are new to the "
":guilabel:`First Interview` stage, this will be the default. If there are "
"any meetings already scheduled, the smart button will display "
":guilabel:`Next Meeting` with the date of the upcoming meeting."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:536
msgid ""
"Doing so loads the *Calendar* application, showing the currently scheduled "
"meetings and events for the user. The meetings and events displayed are for "
"the employees who are listed under the :guilabel:`Attendees` section on the "
"right side of the calendar view. To change the currently loaded meetings and"
" events being displayed, uncheck the person who's calendar events are to be "
"hidden. Only the checked attendees will be visible on the calendar."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:542
msgid ""
"The default view is the week view. To change the calendar view, click on a "
"button to present the calendar in a different view, either :guilabel:`Day`, "
":guilabel:`Month`, or :guilabel:`Year`. To change the displayed date range "
"for the calendar, either use the :guilabel:`⬅️ (Left)`, :guilabel:`➡️ "
"(Right)`, or :guilabel:`Today` buttons above the calendar, or click on a "
"date in the calendar on the right side of the displayed calendar."
msgstr ""

#: ../../content/applications/hr/recruitment.rst-1
msgid "The calendar view, highlighting how to change the displayed meetings."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:552
msgid ""
"To add a meeting to the calendar, click on the day the meeting is to take "
"place, or click on the start time of the meeting and drag to the end time, "
"to select the date, time, and the length of the meeting. If the calendar is "
"displaying the day or week view, click on the day *and* the time slot the "
"meeting is to take place. A :guilabel:`New Event` pop up appears, with the "
":guilabel:`Meeting Subject` populated with the applicant card's "
":guilabel:`Subject/Application Name`. The default time slot is 30 minutes. "
"If the information is correct, click :guilabel:`Create` to add the meeting "
"to the calendar, or click :guilabel:`Edit` to modify the meeting."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:560
msgid ""
"If :guilabel:`Edit` is clicked, an expanded :guilabel:`New Event` card "
"loads. Make any changes needed to the form."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:564
msgid "New event card"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:566
msgid ""
"The fields available to populate or modify on the detailed :guilabel:`New "
"Event` card are as follows. The only required fields to enter are the "
":guilabel:`Meeting Subject`, :guilabel:`Starting At`, and :guilabel:`Ending "
"At` fields. Once the card details are entered, click :guilabel:`Save` to "
"save the changes and create the meeting."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:571
msgid ""
":guilabel:`Meeting Subject`: 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.rst:574
msgid ""
":guilabel:`Attendees`: select the people who should be in attendance. The "
"default employee listed is the person who is creating the meeting. Add as "
"many other people as desired."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:578
msgid "Meeting details tab"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:580
msgid ""
":guilabel:`Starting At`: using the drop-down calendar, select the date and "
"time for the meeting start time."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:582
msgid ""
":guilabel:`Ending At`: using the drop-down calendar, select the date and "
"time for the meeting end time."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:584
msgid ""
":guilabel:`Duration`: this field auto populates based on the "
":guilabel:`Starting At` and :guilabel:`Ending At` times entered. If the "
"meeting time is adjusted, this field automatically adjusts to the correct "
"duration length."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:587
msgid ""
":guilabel:`All Day`: if the meeting is an all day long event, check the box "
"next to :guilabel:`All Day`. After this box is checked, the "
":guilabel:`Duration` field is hidden from view, a well as the meeting start "
"and end times."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:590
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.rst:592
msgid ""
":guilabel:`Description`: enter a brief description in this field. There is "
"an option to enter formatted text, such as numbered lists, headings, tables,"
" as well as links, photos, and more. Use the powerbox feature, by typing a "
"`/`, and a list of options are presented. 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.rst:598
msgid ""
":guilabel:`Reminders`: select a reminder from the drop-down menu. Options "
"include :guilabel:`Notification`, :guilabel:`Email`, and :guilabel:`SMS Text"
" Message`, each with a specific time period before the event (hours, days, "
"etc). The reminder chosen will alert the meeting participants of the meeting"
" via the selected option."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:602
msgid ":guilabel:`Location`: enter the location for the meeting."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:603
msgid ""
":guilabel:`Meeting URL`: if the meeting is virtual, enter the meeting link "
"in this field."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:604
msgid ""
":guilabel:`Tags`: select any tag(s) for the meeting using the drop-down "
"menu. There is no limit to the number of tags that can be used."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:610
msgid ""
":guilabel:`Recurrent`: if the meeting should repeat at a selected interval "
"(not typical for a first interview), check the box next to "
":guilabel:`Recurrent`. This reveals a recurrence section. Enter the details "
"for how often the meeting should repeat, including an end time."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:613
msgid ""
":guilabel:`Privacy`: select the visibility of this meeting. 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.rst:618
msgid ""
":guilabel:`Show as`: select from the drop-down whether the meeting time "
"should appear as :guilabel:`Busy` or :guilabel:`Available` in the attendees'"
" schedules. Setting this field to :guilabel:`Available` allows other "
"meetings to be scheduled for the same time. It is recommended to set this "
"field to :guilabel:`Busy`, so no other meetings can be scheduled for the "
"attendees at the same time."
msgstr ""

#: ../../content/applications/hr/recruitment.rst-1
msgid "A new meeting card with all the details populated, and ready to save."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:629
msgid "Send meeting to attendees"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:631
msgid ""
"Once changes have been entered and the meeting details are correct, the "
"meeting can be sent to the attendees via email or text message."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:634
msgid ""
"To send the meeting via email, click the :guilabel:`Email` button next to "
"the list of attendees. A :guilabel:`Contact Attendees` email configurator "
"pop-up appears. A pre-formatted email using the default :guilabel:`Calendar:"
" Event Update` email template populates the email body field. The followers "
"of the document (job application), as well as the user who created the "
"meeting are added as :guilabel:`Recipients` by default. 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:`Attach A File` 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.rst-1
msgid "Enter the information to send the event via email."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:647
msgid ""
"To send the meeting via text message, click the :guilabel:`SMS` button next "
"to the list of attendees. A :guilabel:`Send SMS Text Message` pop-up "
"appears. At the top, in a blue box, information appears regarding the "
"message. The first line lists how many records (phone numbers) are selected."
" The second line lists the number of recipients and how many of them are "
"invalid. If a contact does not have a valid phone number listed, click "
":guilabel:`Close`, and edit the attendee's record, then redo these steps."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:655
msgid ""
"It is *not* recommended to check the box to send to all the records in the "
":guilabel:`Send SMS Text Message` pop-up. This would send a message to all "
"contacts with a valid phone number."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:658
msgid ""
"When the message reads :guilabel:`0 are invalid`, type in the message to be "
"sent in the :guilabel:`Message` field. Beneath the message field, the number"
" of characters, as well as the amount of text messages required to send the "
"message (according to GSM7 criteria) appears. 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.rst-1
msgid "Send a text message to the attendees of the meeting."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:669
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.rst:676
msgid "Second interview"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:678
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, or click on the :guilabel:`Second "
"Interview` stage button at the top of the individual applicant's card."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:683
msgid ""
"When the applicant's card moves to the :guilabel:`Second Interview` stage, "
"there are no automatic activities or emails configured for this stage, "
"unlike for the :guilabel:`First Interview` stage. The recruiter can now "
":ref:`schedule a second interview <recruitment/schedule-meetings>` with the "
"applicant, following the same process as for the first interview."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:691
msgid "Contract proposal"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:693
msgid ""
"When the applicant has passed the interview stages and an offer is ready to "
"be sent, they can be moved to the :guilabel:`Contract Proposal` stage. Drag "
"and drop the applicant's card to the :guilabel:`Contract Proposal` stage, or"
" click on the :guilabel:`Contract Proposal` stage button at the top right of"
" the individual applicant's card."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:698
msgid ""
"The next step is to send an offer to the applicant. On the applicant's card,"
" click the :guilabel:`Generate Offer` button. A :guilabel:`Generate a "
"Simulation Link` pop-up appears. All fields are pre-populated with "
"information from the job position, except for the :guilabel:`Force New Cars "
"List`, :guilabel:`Default Vehicle`, and the :guilabel:`Canteen Cost` (this "
"is set to `0.00`)."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:705
msgid ""
"Not all fields may appear on the :guilabel:`Generate a Simulation Link` pop-"
"up. Depending on the localization setting for the company and the "
"applications installed, some fields may not appear. For example if the "
"*Fleet* application is not installed, the fields related to vehicles will "
"not appear on the pop-up."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:711
msgid "Universal fields"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:713
msgid ""
"The following fields appear for all offers sent to applicants regardless of "
"localization settings."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:715
msgid ""
":guilabel:`Offer Template`: the template currently being used to populate "
"the :guilabel:`Generate a Simulation Link` pop-up. To modify the template, "
"click the :guilabel:`External link` icon to the right of the drop-down "
"arrow. Make any changes, then click :guilabel:`Save`."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:718
msgid ""
":guilabel:`Job Title`: the name of the position being offered to the "
"applicant."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:719
msgid ""
":guilabel:`Contract Start Date`: the date the contract takes effect. The "
"default date is the current date. To modify the date, click the drop-down to"
" reveal a calendar. Use the :guilabel:`< (left)` and :guilabel:`> (right)` "
"arrows on either side of the month to navigate to the desired month, then "
"click on the :guilabel:`day` to select the date."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:723
msgid ":guilabel:`Yearly Cost`: the annual salary being offered."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:724
msgid ""
":guilabel:`Offer Link`: this link takes the applicant to a webpage where "
"they can enter their personal information, which will be imported to their "
"employee record when created. If applicable, the applicant can modify their "
"salary package (this option is not available for all localizations). Lastly,"
" this is where the applicant accepts the offer by clicking :guilabel:`Review"
" Contract & Sign` to accept the contract and sign it using the *Sign* "
"application."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:732
msgid ""
"The *Sign* application must be installed in order for a document to be "
"signed. Ensure the *Sign* application is installed to use this feature."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:738
msgid ""
"The following fields will only appear if specific localization settings are "
"selected, and/or certain applications are installed. For example if the "
"*Fleet* application is not installed, none of the optional fields related to"
" vehicles will appear, such as :guilabel:`Force New Cars List` or "
":guilabel:`Default Vehicle`."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:743
msgid ""
":guilabel:`Job Position`: the official title of the job being offered to the"
" applicant, from the :guilabel:`Job Position` card. To modify the name, "
"click the :guilabel:`External link` icon to the right of the drop-down "
"arrow. Make any changes, then click :guilabel:`Save`."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:746
msgid ""
":guilabel:`Department`: the department the job position falls under. To "
"modify the department, click the :guilabel:`External link` icon to the right"
" of the drop-down arrow. Make any changes, then click :guilabel:`Save`."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:749
msgid ""
":guilabel:`Force New Cars List`: check this box to offer a new vehicle to "
"the applicant."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:750
msgid ""
":guilabel:`Default Vehicle`: using the drop-down menu, select the vehicle "
"that will be assigned to the applicant."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:752
msgid ""
":guilabel:`Canteen Cost`: enter the amount that is offered to the applicant "
"for the cafeteria."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:753
msgid ""
":guilabel:`Contract Type`: using the drop-down menu, select the type of "
"contract that is being offered."
msgstr ""

#: ../../content/applications/hr/recruitment.rst-1
msgid ""
"Format the offer to send to the applicant. Make any modifications before "
"sending."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:761
msgid "Send offer"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:763
msgid ""
"To send the offer to the applicant, click :guilabel:`Send`. If the applicant"
" does not have an email address listed on their applicant card, the "
"applicant form appears so their email can be configured. If there is already"
" an email configured on the applicant's card, the email pop-up appears "
"instead. If prompted with the applicant's card, enter the applicant's email "
"address in the :guilabel:`Email` field, then click :guilabel:`Save`. The "
"applicant form closes and the email pop-up appears."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:769
msgid ""
"The :guilabel:`Applicant: Your Salary Package` email template is used, and "
"the :guilabel:`Recipients`, :guilabel:`Subject`, and email body are pre-"
"populated based on the email template. If any attachments need to be added, "
"click the :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 "
":guilabel:`Attachments` button. Once the email is ready to send, click "
":guilabel:`Send`."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:777
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. The "
"applicant does not need any software installed."
msgstr ""

#: ../../content/applications/hr/recruitment.rst-1
msgid "Send an email to the applicant with a link to the offered salary."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:787
msgid "Contract signed"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:789
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. To "
"move the applicant to the next stage, drag and drop the applicant's card to "
"the :guilabel:`Contract Signed` stage, or click the :guilabel:`More` button "
"at the top of the applicant's card to reveal the :guilabel:`Contract Signed`"
" stage button at the top of the individual applicant's card, and click "
":guilabel:`Contract Signed`."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:796
msgid ""
"The :guilabel:`Contract Signed` stage is folded in the kanban view, but the "
"card may still be dragged and dropped into that stage."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:799
msgid ""
"Once the applicant's card moves to the :guilabel:`Contract Signed` stage, a "
"green :guilabel:`Hired` banner appears in the top right of the applicant's "
"card."
msgstr ""

#: ../../content/applications/hr/recruitment.rst-1
msgid "Hired banner in the top right corner of applicant card."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:807
msgid "Create employee"
msgstr ""

#: ../../content/applications/hr/recruitment.rst:809
msgid ""
"Once the applicant has been hired, the next step is to create an employee "
"record of them. On the applicant's card, click the :guilabel:`Create "
"Employee` button in the top left. An employee form appears, and any "
"information from the applicant's card that can be imported into the employee"
" card appears in the form."
msgstr ""

#: ../../content/applications/hr/recruitment.rst:814
msgid ""
"Fill out the rest of the form. For detailed information on the fields, refer"
" to the :doc:`employees/new_employee` documentation. When done, click "
":guilabel:`Save`. The employee record is now saved in the *Employees* app."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:5
msgid ""
"In the default :menuselection:`Recruitment` dashboard view, all job "
"positions are shown, regardless of status. Current published positions with "
"active applicants are shown, as well as job positions that have been created"
" but have not yet been published."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:9
msgid ""
"Each job position is shown in an individual kanban card. If the job position"
" is active and candidates can apply, then a :guilabel:`Published` banner "
"will appear in the top-right corner of the card."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:13
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 showing all job positions."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:20
msgid "Create a new job position"
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:22
msgid ""
"Create a new job position from the main Recruitment dashboard by clicking "
"the :guilabel:`New` button in the top-left corner."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:25
msgid ""
"Then, a :guilabel:`Create a Job Position` pop-up window will appear. From "
"here, enter the name of the position (such as `Sales Manager`, `Mechanical "
"Engineer`, etc.). 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:33
msgid ""
"Once the job position has been created, it will appear as a card in the "
"kanban view on the main :guilabel:`Recruitment` dashboard."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:37
msgid "Edit a new job position"
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:39
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:47
msgid ""
"Enter the job description in the :guilabel:`Job Summary` tab. This "
"information is what is visible to potential applicants when searching for "
"available jobs."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:53
msgid ""
"All the basic information about the job position is listed under the "
":guilabel:`Recruitment` tab. None of the fields are required, but it is a "
"good idea to provide at least a few details, such as where the job is "
"located."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:57
msgid "The fields can be filled out as follows:"
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:59
msgid ""
":guilabel:`Department`: select the relevant department for the job position."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:60
msgid ":guilabel:`Job Location`: select the physical address for the job."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:61
msgid ""
":guilabel:`Employment Type`: select what type of position the job is, such "
"as :guilabel:`Full-Time`, :guilabel:`Part-Time`, etc."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:63
msgid ":guilabel:`Company`: select the company the job is for."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:64
msgid ""
":guilabel:`Target`: enter the number of employees to be hired for this "
"position."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:65
msgid ""
":guilabel:`Is Published`: activate this option to publish the job online."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:66
msgid ""
":guilabel:`Website`: select the website where the job will be published."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:67
msgid ""
":guilabel:`Recruiter`: select the person who will be doing the recruiting "
"for this role."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:68
msgid ""
":guilabel:`Interviewers`: select who should perform the interview(s). "
"Multiple people can be selected."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:70
msgid ""
":guilabel:`Interview Form`: select an :ref:`Interview form <interview>` that"
" applicants will fill out prior to their interview."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:72
msgid ""
":guilabel:`Contract Template`: select a contract template that will be used "
"when offering the job to a candidate."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:74
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:78
msgid ""
":guilabel:`Time to Answer`: enter the number of days before the applicant is"
" contacted."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:79
msgid ""
":guilabel:`Process`: enter the various stages the candidate will go through "
"during the recruitment process."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:81
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:85
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-1
msgid "Enter job information details in the recruitment tab."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:96
msgid "Create interview form"
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:98
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:102
msgid ""
"All interview forms must be created, there are no pre-configured forms in "
"Odoo. To create an interview form, start from the 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:`View all`, and :guilabel:`Create and edit...`. Click "
":guilabel:`Create and edit...`. and a :guilabel:`Create Interview Form` pop-"
"up window appears."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:110
msgid ""
"The option :guilabel:`View all` 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:114
msgid ""
"First, enter a name for the form in the :guilabel:`Name` field. This should "
"be indicative of when the form should be used. For example, is the form "
"specific to a job position, or is it a general form that can be used for all"
" recruitment scenarios?"
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:118
msgid ""
"Next, select what kind of interview form is being created. The default is "
":guilabel:`Custom`, which is pre-selected. The various options are "
":guilabel:`Survey`, :guilabel:`Live session`, :guilabel:`Assessment`, "
":guilabel:`Custom`, and :guilabel:`Appraisal`."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:122
msgid ""
"Then select the person responsible for the form from the drop-down menu for "
"the :guilabel:`Responsible` field."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:125
msgid ""
"If desired, an image can be added to the interview form. Mouse over the "
"camera icon on the far right and a :guilabel:`✏️ (pencil)` icon appears. "
"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/recruitment/new_job.rst-1
msgid ""
"The top portion of the new interview form with everything filled out and "
"selected."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:135
#: ../../content/applications/hr/recruitment/new_job.rst:351
msgid "Questions"
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:137
msgid ""
"In the :guilabel:`Questions` tab, click on :guilabel:`Add a section` to add "
"a section to the form. A line appears, and a section heading can be entered."
" When complete, click off the line, or press enter to lock in the new "
"section on the form."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:141
msgid ""
"Next, click :guilabel:`Add a question` to add a question to the section. A "
":guilabel:`Create Sections and Questions` pop-up window appears where the "
"question details are entered. Type out the question in the top line."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:145
msgid "There are several :guilabel:`Question Types` to choose from:"
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:147
msgid ""
":guilabel:`Multiple choice: only one answer`: a multiple choice question "
"that only allows the candidate to select one answer"
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:149
msgid ""
":guilabel:`Multiple choice: multiple answers allowed`: a multiple choice "
"question that allows the candidate to select multiple answers"
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:151
msgid ""
":guilabel:`Multiple Lines Text Box`: allows the applicant to enter several "
"lines of text"
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:152
msgid ""
":guilabel:`Single Line Text Box`: limits the applicant to only a single line"
" of text"
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:153
msgid ":guilabel:`Numerical Value`: only allows a number to be entered"
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:154
msgid ":guilabel:`Date`: a calendar module is presented to select a date"
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:155
msgid ""
":guilabel:`Datetime`: a calendar module and a clock icon is presented to "
"select a date and time"
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:156
msgid ""
":guilabel:`Matrix`: a customizable table that allows the candidate to choose"
" an answer for each row"
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:159
msgid ""
"After selecting a question type, a sample question appears in gray. This "
"represents how the question will be displayed to applicants."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst-1
msgid "Add a new question to the interview form."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:166
msgid ""
"Questions and sections can be reorganized. Move them by clicking and "
"dragging individual section headings or question lines to their desired "
"position(s)."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:169
msgid ""
"Sections are indicated by a gray background, while questions have a white "
"background."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst-1
msgid "A sample of categories and questions for a candidate."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:176
#: ../../content/applications/hr/recruitment/new_job.rst:269
msgid "Answers"
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:178
msgid ""
"If :guilabel:`Multiple choice: only one answer`, :guilabel:`Multiple choice:"
" multiple answers allowed`, :guilabel:`Single Line Text Box`, or "
":guilabel:`Matrix` is selected for the :guilabel:`Question Type`, an "
":guilabel:`Answers` tab appears beneath the question. If another question "
"type is selected, the :guilabel:`Answers` tab remains hidden from view."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:185
msgid "Multiple choice"
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:187
msgid ""
"For both the :guilabel:`Multiple choice: only one answer` and "
":guilabel:`Multiple choice: multiple answers allowed` question type, the "
"answers are populated in the same way."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:190
msgid ""
"First, in the :guilabel:`Answers` tab, click :guilabel:`Add a line`. A line "
"appears, and an answer can be entered. After typing in the answer, click off"
" the line, or press enter to lock in the new answer on the form and have "
"another answer line appear."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:194
msgid ""
"If desired, an image can be attached to the answer. Click on a line to "
"select it, and an :guilabel:`Upload your file` button appears on the right "
"side. Click the :guilabel:`Upload your file` button and a file explorer "
"window appears. Navigate to the image file, select it, then click "
":guilabel:`Open` to select it."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:199
msgid ""
"Repeat this for all the answers to be added for the multiple choice "
"question. The answers can be rearranged in any order. To move an answer, "
"click on the six small squares on the far left of each answer line, and drag"
" the answer to the desired position. The order the answers appear in the "
"form is the order the answers will appear online."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:204
msgid ""
"To delete a line, click on the :guilabel:`🗑️ (trash can)` icon on the far "
"right side of the answer line."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:0
msgid ""
"Answers to a multiple choice question, where each line has a different "
"answer listed."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:211
msgid "Single Line Text Box"
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:213
msgid ""
"If the :guilabel:`Single Line Text Box` question type is selected, only two "
"checkboxes appear in the :guilabel:`Answers` tab:"
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:216
msgid ""
":guilabel:`Input must be an email`: activate this option if the answer must "
"be in the format of an email address."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:219
msgid ""
":guilabel:`Save as user email?`: this option appears if :guilabel:`Input "
"must be an email` is selected. This saves the email entered on the form as "
"the user's email, and will be used anytime Odoo contacts the user via email."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:223
msgid ""
":guilabel:`Save as user nickname?`: activate this option to populate the "
"answer as the user's nickname. This is stored and used anywhere Odoo uses a "
"nickname."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:0
msgid ""
"The three possible checkboxes that can appear if a single line of text is selected\n"
"for the question type."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:231
msgid "Matrix"
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:233
msgid ""
"Sometimes, a question is asked that does not fit a standard answer format, "
"and is best suited for a matrix. For example, asking an applicant what is "
"their availability to work compared to the various shifts is a perfect "
"question for a matrix format. In this example, an applicant can click on all"
" the shifts they are available to work."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:238
msgid ""
"For a :guilabel:`Matrix` question type, there are two sets of data that need"
" to be input. The rows and columns must both be configured. The columns are "
"represented by the :guilabel:`Choices` section, while the rows are "
"configured in the :guilabel:`Rows` section."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:242
msgid ""
"The method for populating both sections is the same. In the "
":guilabel:`Answers` tab, click :guilabel:`Add a line` in either the "
":guilabel:`Choices` or :guilabel:`Row` section.  A line appears, and an "
"answer can be entered. After typing in the answer, click off the line, or "
"press enter to lock in the new answer on the form and have another answer "
"line appear. Repeat this for all answers for both the :guilabel:`Choices` "
"and :guilabel:`Rows` sections."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:251
msgid ""
"This is an example matrix that asks an applicant what shifts they are "
"available to work on Saturdays and Sundays, either morning, afternoon, or "
"evening."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:255
#: ../../content/applications/hr/recruitment/new_job.rst:440
msgid "Description"
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:257
msgid ""
"Enter any information that may be helpful to an applicant. This description "
"will appear for this specific question only, and therefore should be "
"question-specific and not generalized."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:261
#: ../../content/applications/hr/recruitment/new_job.rst:345
msgid "Options"
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:263
msgid ""
"To view the options that are available to set for a question, click on the "
":guilabel:`Options` tab. The :guilabel:`Layout`, :guilabel:`Constraints`, "
"and :guilabel:`Live Sessions` sections are universal for all "
":guilabel:`Question Types`, while the :guilabel:`Answers` tab is specific to"
" the :guilabel:`Question Type` selected, and changes based on the selection."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:271
msgid ""
":guilabel:`Multiple choice: only one answer` and :guilabel:`Multiple choice:"
" multiple answers allowed`: a :guilabel:`Show Comments Field` option "
"appears. Activate the option to allow the applicant to answer the question "
"by typing in an answer (or comment). A :guilabel:`Comment Message` and "
":guilabel:`Comment is an answer` field appear if activated. Enter the text "
"to appear in the :guilabel:`Comment Message` field. This should be helpful "
"to the applicant, such as `If other, please specify`. Last, if the comment "
"should be logged as the applicant's answer, activate the box."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:278
msgid ""
":guilabel:`Multiple Lines Text Box`: a :guilabel:`Placeholder` field "
"appears. Enter any text that should appear with the question to help clarify"
" how the applicant should answer."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:280
msgid ""
":guilabel:`Single Line Text Box` and :guilabel:`Numerical Value`: a "
":guilabel:`Validate entry` option appears. Activate this option if what the "
"applicant enters must be a numerical value, *and* needs to be verified. The "
"answer can *only* be verified if it is a numerical entry. When activated, "
"several other options appear. Enter the values for the :guilabel:`Min/Max "
"Limits` in the two fields. Next, enter the text that appears when the answer"
" given does not fit within the designated minimum and maximum parameters. "
"Last, enter any text in the :guilabel:`Placeholder` field to provide any "
"additional information or directions to assist the applicant."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:287
msgid ""
":guilabel:`Date` and :guilabel:`Datetime`: a :guilabel:`Validate entry` "
"option appears. Activate this option if the applicant's answer needs to be "
"verified. When activated, several other options appear. Enter the date "
"ranges for the :guilabel:`Min/Max Limits` in the two fields. Click on a "
"field, either the :guilabel:`minimum` or :guilabel:`maximum`, and a calendar"
" appears. Select the dates for the corresponding fields. Next, enter the "
"text that appears when the answer given does not fit within the designated "
"minimum and maximum dates. Last, enter any text in the "
":guilabel:`Placeholder` field to provide any additional information or "
"directions to assist the applicant."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:295
msgid ""
":guilabel:`Matrix`: the first option that appears is :guilabel:`Matrix "
"Type`. Select either :guilabel:`One choice per row` or :guilabel:`Multiple "
"choices per row` using the drop-down menu. The next option is "
":guilabel:`Show Comments Field`. Activate the option if there should be a "
"comment displayed to the applicant. If activated, a :guilabel:`Comment "
"Message` and :guilabel:`Comment is an answer` field appear. Enter the text "
"to appear in the :guilabel:`Comment Message` field. This should be an "
"instruction helpful to the applicant, such as `If other, please specify`. "
"Last, if the comment should be logged as the applicant's answer, activate "
"the box."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:304
msgid "Constraints"
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:306
msgid ""
"If the question is required to be answered by the applicant, activate the "
"box next to :guilabel:`Mandatory Answer`. An :guilabel:`Error message` field"
" appears, with some example text in gray (*This question requires an "
"answer*). Enter the message that should appear if the applicant attempts to "
"move on to the next question without answering this required one. The text "
"should explain that the question must be answered."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:313
msgid "Layout"
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:315
msgid ""
"If the question should only appear if a previous question is answered in a "
"specific way, activate the :guilabel:`Conditional Display` option. A new "
":guilabel:`Triggering Question` field appears. Using the drop-down menu, "
"select the previous question this new question is linked to. Once a previous"
" question is selected, a :guilabel:`Triggering Answer` field appears. Select"
" the answer that must be selected in order for the new question to appear."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:322
msgid ""
"To further illustrate a triggering question, the following is an example "
"that is applicable to recruitment. The question, `Do you have experience "
"with managing a sales team?` is already added. A new question is then added,"
" `How many years of experience?`. This question should *only* appear if the "
"applicant selected `Yes` to the question `Do you have prior experience "
"managing a sales team?`."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:328
msgid ""
"To properly configure this example, activate the :guilabel:`Conditional "
"Display` option. Then, select `Do you have experience with managing a sales "
"team?` as the :guilabel:`Triggering Question`. Then, select :guilabel:`Yes` "
"for the triggering answer."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:0
msgid "The layout field when properly configured for a conditional question."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:338
msgid "Live Sessions"
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:340
msgid ""
"If the question is for a live session, activate the :guilabel:`Question Time"
" Limit` option. A :guilabel:`seconds` field appears. Enter the amount of "
"time allotted for the applicant to enter the answer, in seconds."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:347
msgid ""
"Next, configure the various options for the interview form. Click the "
":guilabel:`Options` tab to view all the options to configure, by category."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:353
msgid ":guilabel:`Pagination`: choose how the questions should be displayed."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:355
msgid ""
":guilabel:`One page per question`: display a single question on each page."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:356
msgid ""
":guilabel:`One page per section`: display each section with the "
"corresponding questions on an individual page."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:358
msgid ""
":guilabel:`One page with all the questions`: display all sections and "
"questions at the same time."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:362
msgid ""
":guilabel:`Display Progress as`: choose how to display the percentage of "
"questions remaining to answer. This option only appears if either "
":guilabel:`One page per question` or :guilabel:`One page per section` is "
"selected for :guilabel:`Pagination`."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:366
msgid ""
":guilabel:`Percentage left`: display the remaining amount in a percentage "
"(%)."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:367
msgid ":guilabel:`Number`: display the remaining amount in a numerical value."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:370
msgid ":guilabel:`Question Selection`: choose which questions are presented."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:372
msgid ""
":guilabel:`All questions`: display the entire form, with all questions form "
"all sections."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:373
msgid ""
":guilabel:`Randomized per Section`: display only a random selection of "
"questions from each section."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:377
msgid ""
":guilabel:`Back Button`: activate this option if the applicant is able to "
"click a back button to go back to previous questions."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:381
msgid ""
"Although it is a selectable option, the :guilabel:`Randomized per section` "
"option should only be used if receiving partial information/an incomplete "
"survey from every applicant is acceptable to the business."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:386
msgid "Time & Scoring"
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:388
msgid ""
":guilabel:`Survey Time Limit`: activate this option to limit the time "
"allowed to complete the form. When selected, a field to enter the minutes "
"appears next to the checked box. Enter the time (using an XX:XX "
"minute/second format) in the field."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:391
msgid ":guilabel:`Scoring`: choose how the questions should be scored."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:393
msgid ":guilabel:`No scoring`: select this option to not score the form."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:394
msgid ""
":guilabel:`Scoring with answers at the end`: select this option to score the"
" form and display the correct answers for the candidate when they are "
"finished with the form."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:396
msgid ""
":guilabel:`Scoring without answers at the end`: select this option to score "
"the form but not display the answers to the candidate."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:399
msgid ""
":guilabel:`Required Score (%)`: this option appears if one of the scoring "
"options was selected. Enter the percentage the candidate needs to pass the "
"exam (example, 80.00%). The entry should be written in an “XX.XX” format."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:403
msgid ""
":guilabel:`Is a Certification`: activate this option if the form is a "
"certification exam. When activated, a drop-down menu appears next to the "
"checkbox. Select one of the default formats for the PDF certificate that "
"will be sent to the candidate after completing the certification exam. Click"
" the :guilabel:`Preview` button to view an example of the PDF certificate."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:407
msgid ""
":guilabel:`Certified Email Template`: if the :guilabel:`Is a Certification` "
"box is activated, a :guilabel:`Certified Email Template` appears. Select the"
" email template from the drop-down menu that is to be used when the "
"applicant passes the test. Click the :guilabel:`External Link` icon to the "
"right of the email template to preview the email."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:413
msgid "Participants"
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:415
msgid ""
":guilabel:`Access Mode`: specify who can access the exam. Either "
":guilabel:`Anyone with the link` or :guilabel:`Invited people only`."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:417
msgid ""
":guilabel:`Require Login`: activate this option to require candidates to log"
" in before taking the exam, whether they have a valid token or not."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:419
msgid ""
":guilabel:`Limit Attempts`: if there is a limit to how many times the exam "
"can be taken, activate this box, then enter the maximum attempt number in "
"the field next to it."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:423
msgid "Live Session"
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:425
msgid ""
":guilabel:`Session Code`: enter the access code that will allow the viewers "
"into the live exam session."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:427
msgid ""
":guilabel:`Session Link`: the link appears in a box next to the "
":guilabel:`Session Link` option. Click the :guilabel:`Copy` button to copy "
"the link."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:429
msgid ""
":guilabel:`Reward quick answers`: if the exam is to be taken live, activate "
"this option to award more points to participants who answer quickly."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:432
msgid ""
"After all fields have been entered, click the :guilabel:`Save` button to "
"save the changes, or click :guilabel:`Discard` to delete the changes."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst-1
msgid "Various options to configure for the interview form."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:442
msgid ""
"When the applicant begins the survey, the text entered in this tab appears "
"at the top of the survey page. Enter any information or descriptions that "
"would be helpful to the applicant."
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:446
msgid "End Message"
msgstr ""

#: ../../content/applications/hr/recruitment/new_job.rst:448
msgid ""
"After the survey is complete, the message entered in this tab is displayed "
"for the applicant."
msgstr ""

#: ../../content/applications/hr/referrals.rst:3
msgid "Referrals"
msgstr ""

#: ../../content/applications/hr/referrals.rst:5
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, "
"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:12
msgid ""
"The only configuration needed for the Referrals application after it is "
"installed are the :ref:`rewards <referrals/rewards>`; everything else is "
"pre-configured when Odoo Referrals is installed."
msgstr ""

#: ../../content/applications/hr/referrals.rst:16
msgid ""
"Any user with either :guilabel:`Referral User`, :guilabel:`Officer`, or "
":guilabel:`Administrator` rights for the Recruitment application has access "
"to the Referrals application. Only user's with :guilabel:`Administrator` "
"rights for the Recruitment application have access to the :ref:`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:23
msgid "Onboarding"
msgstr ""

#: ../../content/applications/hr/referrals.rst:25
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:31
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:34
msgid "The text that appears on each slide is as follows:"
msgstr ""

#: ../../content/applications/hr/referrals.rst:36
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:38
msgid ""
":guilabel:`Browse through open job positions, promote them on social media, "
"or refer friends.`"
msgstr ""

#: ../../content/applications/hr/referrals.rst:39
msgid ""
":guilabel:`Collect points and exchange them for awesome gifts in the shop.`"
msgstr ""

#: ../../content/applications/hr/referrals.rst:40
msgid ""
":guilabel:`Compete against your colleagues to build the best justice "
"league!`"
msgstr ""

#: ../../content/applications/hr/referrals.rst:43
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:50
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:59
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:65
msgid "Modifying onboarding slides"
msgstr ""

#: ../../content/applications/hr/referrals.rst:67
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, then click "
":guilabel:`Edit`."
msgstr ""

#: ../../content/applications/hr/referrals.rst:73
msgid ""
"Make any changes to the message in the :guilabel:`Text` box. To change the "
"order the slide appear in the onboarding, the :guilabel:`Sequence` can be "
"modified. Type in the corresponding number to indicate the order in which "
"the slides should be displayed. A :guilabel:`Company` may be selected, "
"however, if this field is populated, that slide will only be displayed for "
"that particular company."
msgstr ""

#: ../../content/applications/hr/referrals.rst:78
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:85
msgid ""
"To save any changes, click :guilabel:`Save`, or click :guilabel:`Discard` to"
" delete any changes and revert to the original content."
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:92
msgid ""
"The order of the slides can also be changed directly in the Onboarding "
"dashboard, without having to edit an individual onboarding slide. Click the "
"up and down arrow symbol that appears after the checkbox and before the "
"slide text, and drag the slide to the desired position. The "
":guilabel:`Sequence` automatically changes on all the slide's onboarding "
"forms, reflecting the new sequence."
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:103
msgid "Share job positions"
msgstr ""

#: ../../content/applications/hr/referrals.rst:105
msgid ""
"In order to earn referral points, a user must first share a job position so "
"the applicant can apply for the position. There are several ways to share "
"job positions within the Referrals application, through the :ref:`View Jobs "
"<referrals/view-jobs>` button and the :ref:`Email A Friend <referrals/email-"
"jobs>` button."
msgstr ""

#: ../../content/applications/hr/referrals.rst:113
msgid "View Jobs"
msgstr ""

#: ../../content/applications/hr/referrals.rst:115
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 in its own card."
msgstr ""

#: ../../content/applications/hr/referrals.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.rst:124
msgid "Each job position card contains the following information:"
msgstr ""

#: ../../content/applications/hr/referrals.rst:126
msgid ""
"The title of the job position. This information is taken from the "
":guilabel:`Job Position` field of the job form."
msgstr ""

#: ../../content/applications/hr/referrals.rst:128
msgid ""
"The number of positions being recruited. This information is taken from the "
":guilabel:`Expected New Employees` field of the :guilabel:`Recruitment` tab "
"of the job form."
msgstr ""

#: ../../content/applications/hr/referrals.rst:130
msgid ""
"The points a user will earn when an applicant applies for the position."
msgstr ""

#: ../../content/applications/hr/referrals.rst:131
msgid ""
"The job description detailing the job position. This information is taken "
"from the :guilabel:`Job Position` tab of the job form."
msgstr ""

#: ../../content/applications/hr/referrals.rst:134
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.rst:139
msgid ""
"Only published job positions will be 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.rst:143
msgid "Refer friends"
msgstr ""

#: ../../content/applications/hr/referrals.rst:145
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` email pop-up window appears. Enter the recipient's email "
"address in the :guilabel:`Email` field."
msgstr ""

#: ../../content/applications/hr/referrals.rst:149
msgid ""
"The subject and body are populated using a default template. The subject "
"`Job for you` appears, and can be modified if desired."
msgstr ""

#: ../../content/applications/hr/referrals.rst:152
msgid ""
"The specific title of the job position will populate the :guilabel:`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. When the prospective employee receives the email, the"
" link will send 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.rst:158
msgid ""
"If desired, add any text or closing salutation to the email body. When all "
"edits have been made, click :guilabel:`Send Email` to send the email, or "
"click :guilabel:`Cancel` to close the email pop-up window."
msgstr ""

#: ../../content/applications/hr/referrals.rst-1
msgid "Referral email pop-up window with the email message inside it."
msgstr ""

#: ../../content/applications/hr/referrals.rst:167
msgid "Share a job"
msgstr ""

#: ../../content/applications/hr/referrals.rst:169
msgid ""
"There are several other ways to share a job position aside from sending an "
"email, via social media platforms and 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.rst-1
msgid "The various sharing icons that appear for each job."
msgstr ""

#: ../../content/applications/hr/referrals.rst:179
msgid "Link"
msgstr ""

#: ../../content/applications/hr/referrals.rst:181
msgid ""
"To share the job position with a customized tracking link, click the "
":guilabel:`Share Now` button with the :guilabel:`🔗 (chain)` icon inside 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. Next, share the link with the"
" prospective employee however desired."
msgstr ""

#: ../../content/applications/hr/referrals.rst:188
msgid "Facebook"
msgstr ""

#: ../../content/applications/hr/referrals.rst:190
msgid ""
"To share the job position using Facebook, click the :guilabel:`Share Now` "
"button with the :guilabel:`f (Facebook icon)` inside it. If the user is "
"already logged into Facebook, when the :guilabel:`f (Facebook icon)` 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. 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.rst:196
msgid ""
"Type in any additional information to add to the post, in the space directly"
" below your name. If desired, :guilabel:`tag` users, :guilabel:`check-in` at"
" a location, or add a :guilabel:`status` to the post. To tag a user, click "
"the :guilabel:`Tag Friends` icon and select the people to tag to the post. "
"To add a check-in location, click the :guilabel:`Check in` icon, and select "
"the location from the pop-up of predetermined locations based on your "
"current location. To add a :guilabel:`status`, click the "
":guilabel:`Feeling/Activity` icon, then select either the feeling or the "
"activity type, and lastly, if an activity type was selected, select the "
"specific activity."
msgstr ""

#: ../../content/applications/hr/referrals.rst:204
msgid ""
"There are five methods to share the job position, :guilabel:`Your Story`, "
":guilabel:`Share on a Friend's Timeline`, :guilabel:`Share in a Group`, "
":guilabel:`Share in an Event`, and :guilabel:`Share in a Private Message`. "
"To select the sharing method, click the drop-down menu located at the top of"
" the page, directly beneath the :guilabel:`Share on Facebook` banner."
msgstr ""

#: ../../content/applications/hr/referrals.rst-1
msgid ""
"The view on Facebook when sharing a job description. All the various ways to share are\n"
"highlighted, as are all the required settings."
msgstr ""

#: ../../content/applications/hr/referrals.rst:216
msgid "Share to news feed or story"
msgstr ""

#: ../../content/applications/hr/referrals.rst:218
msgid ""
"The default sharing method is through the :guilabel:`News Feed`, "
":guilabel:`Story`, or both. At the lower portion of the form are radio "
"buttons next to the two options, :guilabel:`Feed` (for the News Feed) and "
":guilabel:`Your Story` for stories. When :guilabel:`Share to News Feed or "
"Story` is selected, these buttons are active, if another option is selected,"
" these radio buttons are greyed out. Activate the radio button(s) to "
"indicate how the job position should be shared, either in the news feed, the"
" story, or both."
msgstr ""

#: ../../content/applications/hr/referrals.rst:225
msgid ""
"The :guilabel:`Share to news feed or story` option allows for specific "
"privacy settings to be selected. In the lower right corner of the screen, "
"there are two drop-down menu options, one for the :guilabel:`Feed` option, "
"the other for the :guilabel:`Your story` option. Select the posting "
"parameters from the drop-down menus. The :guilabel:`Feed` ad :guilabel:`Your"
" story` options appear different from user to user, depending on what "
"privacy settings have been created in Facebook. :guilabel:`Public` and "
":guilabel:`Friends` are default options, but other options that the user may"
" have configured will appear as well, such as custom groups."
msgstr ""

#: ../../content/applications/hr/referrals.rst:233
msgid ""
"When the post and/or story is ready to be shared, click the blue "
":guilabel:`Post to Facebook` button at the bottom of the screen."
msgstr ""

#: ../../content/applications/hr/referrals.rst:236
msgid "Share on a friend's timeline"
msgstr ""

#: ../../content/applications/hr/referrals.rst:238
msgid ""
"Instead of making a public post on the user's on Facebook page, the job "
"position can be shared directly on a friend's timeline. Click the "
":guilabel:`Share to News Feed or Story` drop-down menu near the top of the "
"page, and select :guilabel:`Share on a Fried's Timeline`."
msgstr ""

#: ../../content/applications/hr/referrals.rst:242
msgid ""
"When selected, a :guilabel:`Friend` field appears below the selection. Begin"
" to type in the friend's name. As the name is typed, a list appears, "
"populated with names that match what is entered. Select the friend from the "
"list. **Only** one friend can be selected."
msgstr ""

#: ../../content/applications/hr/referrals.rst:246
#: ../../content/applications/hr/referrals.rst:261
#: ../../content/applications/hr/referrals.rst:275
msgid ""
"When the post is ready to be shared, click the blue :guilabel:`Post to "
"Facebook` button at the bottom of the screen."
msgstr ""

#: ../../content/applications/hr/referrals.rst:249
msgid "Share in a group"
msgstr ""

#: ../../content/applications/hr/referrals.rst:251
msgid ""
"To reach a specific audience and not share the job position publicly with "
"everyone, a job can be shared in a group. Click the :guilabel:`Share to News"
" Feed or Story` drop-down menu near the top of the page, and select "
":guilabel:`Share in a Group`."
msgstr ""

#: ../../content/applications/hr/referrals.rst:255
msgid ""
"When selected, a :guilabel:`Group` field appears below the selection. The "
"available groups that can be posted to are groups the user is currently a "
"member of. Job positions cannot be shared with groups the user has not "
"joined. Begin to type in the name of the group. As the group name is typed, "
"a list appears, populated with the group names that match what is entered. "
"Select the group from the list. Only one group can be selected."
msgstr ""

#: ../../content/applications/hr/referrals.rst:264
msgid "Share in an event"
msgstr ""

#: ../../content/applications/hr/referrals.rst:266
msgid ""
"A job position can also be shared on an event page. Click the "
":guilabel:`Share to News Feed or Story` drop-down menu near the top of the "
"page, and select :guilabel:`Share in an Event`."
msgstr ""

#: ../../content/applications/hr/referrals.rst:269
msgid ""
"When selected, an :guilabel:`Event` field appears below the selection. The "
"available events that can be posted to are events the user is invited to. "
"This includes events that the user has not responded to yet, and events that"
" have occurred in the past. Begin to type in the name of the event. As the "
"event name is typed, a list appears, populated with the events that match "
"what is entered. Select the event from the list. Only one event can be "
"selected."
msgstr ""

#: ../../content/applications/hr/referrals.rst:278
msgid "Share in a private message"
msgstr ""

#: ../../content/applications/hr/referrals.rst:280
msgid ""
"The last option is to share a job position privately instead of publicly, in"
" a Facebook message. Click the :guilabel:`Share to News Feed or Story` drop-"
"down menu near the top of the page, and select :guilabel:`Share in an "
"Private Message`."
msgstr ""

#: ../../content/applications/hr/referrals.rst:284
msgid ""
"When selected, a :guilabel:`To` field appears below the selection. Begin to "
"type in the friend's name. As the name is typed, a list appears, populated "
"with names that match what is entered. Select the friend from the list. "
"Multiple friends can be selected and added to a single message. Repeat this "
"process for each friend to be added."
msgstr ""

#: ../../content/applications/hr/referrals.rst:289
msgid ""
"When the message is ready to be sent, click the blue :guilabel:`Send "
"message` button at the bottom of the screen."
msgstr ""

#: ../../content/applications/hr/referrals.rst:293
msgid "X/Twitter"
msgstr ""

#: ../../content/applications/hr/referrals.rst:295
msgid ""
"A job position can also be shared on X/Twitter. Click the :guilabel:`Share "
"Now` button with the bird icon inside it. If the user is already signed in "
"to X/Twitter, when the :guilabel:`Share Now` icon is clicked, an X/Twitter "
"page loads in a new tab with a pre-populated message ready to post, in a "
"draft pop-up. If the user is *not* already signed in, a sign-in screen loads"
" instead, prompting the user to sign in to X/Twitter."
msgstr ""

#: ../../content/applications/hr/referrals.rst:301
msgid "The default message is:"
msgstr ""

#: ../../content/applications/hr/referrals.rst:303
msgid ""
":guilabel:`Amazing job offer for (Job Position)! Check it live: (link to Job"
" Position)`"
msgstr ""

#: ../../content/applications/hr/referrals.rst:305
msgid ""
"Type in any additional information or make any edits to the message. If "
"desired, click the :guilabel:`X` in the top left corner of the thumbnail "
"preview of the webpage to remove it. To adjust the audience for the message,"
" click the drop-down button labeled :guilabel:`Everyone`. Select the "
"preferred audience from the drop-down menu. The default option is "
":guilabel:`Everyone`, and the other options is :guilabel:`Circle`. The "
":guilabel:`Circle` is a group of people that the user has selected in "
"X/Twitter."
msgstr ""

#: ../../content/applications/hr/referrals.rst:312
msgid ""
"The default setting is :guilabel:`🌎 (globe) Everyone can reply`, an allows "
"everyone on X/Twitter to reply to the message. To change this, click the "
":guilabel:`🌎 (globe) Everyone can reply` button in the lower left section of"
" the message. There are four options presented: :guilabel:`Everyone`, "
":guilabel:`Accounts you follow`, :guilabel:`Verified accounts`, and "
":guilabel:`Only accounts you mention`. Selecting one of the other options "
"restricts who can reply to the message."
msgstr ""

#: ../../content/applications/hr/referrals.rst:318
msgid ""
"There are various other items that can be added to the message. Media "
"(photos, videos, etc), GIF's, polls, emojis, and a location may all be "
"added. Click the corresponding icon in the bottom left of the message and "
"follow the prompts to add the desired additional elements."
msgstr ""

#: ../../content/applications/hr/referrals.rst:322
msgid ""
"To have the message posted at a future date and time, click the "
":guilabel:`Schedule` icon in the lower left of the message window. It is the"
" fifth icon from the left. Enter the date and time that the message should "
"be posted using the date and time selector presented. Click "
":guilabel:`Confirm` to add the scheduled time to the message."
msgstr ""

#: ../../content/applications/hr/referrals.rst:327
msgid ""
"To post the message, click :guilabel:`Post`. The message will be immediately"
" posted, or, if it was scheduled, will be posted at the scheduled date and "
"time."
msgstr ""

#: ../../content/applications/hr/referrals.rst-1
msgid ""
"The X/Twitter pop-up when sharing a job description. All the other items than can be added\n"
"to the message are highlighted, as is the visibility setting and the post button."
msgstr ""

#: ../../content/applications/hr/referrals.rst:336
msgid "LinkedIn"
msgstr ""

#: ../../content/applications/hr/referrals.rst:338
msgid ""
"To share a job position on LinkedIn, click the :guilabel:`Share Now` button "
"with the :guilabel:`in (LinkedIn logo)` inside it. 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.rst:344
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.rst:348
msgid "Share in a post"
msgstr ""

#: ../../content/applications/hr/referrals.rst:350
msgid ""
"To share the job position in a public post, click the :guilabel:`✏️ (pencil)"
" Share in a post` button in the lower-left corner of the screen. A "
":guilabel:`Create a post` window loads, with the job position link "
"populated. Enter any other information to the post in the field."
msgstr ""

#: ../../content/applications/hr/referrals.rst:354
msgid ""
"To change the audience that will see the post, click the :guilabel:`🌎 "
"(globe) Anyone` drop-down, located directly beneath the account name. Click "
"on the desired selection, then click the :guilabel:`Save` button on the far "
"right side of the screen, beneath the last listed option."
msgstr ""

#: ../../content/applications/hr/referrals.rst:358
msgid ""
":guilabel:`Anyone` allows anyone on LinkedIn to see the post. "
":guilabel:`Connections only` will only share the post with people who are "
"connected with the user, and will be hidden from everyone else. "
":guilabel:`Group` shares the post with a specific group the user is a member"
" of. The post can only be shared with one group; posting to multiple groups "
"at once is not available. If :guilabel:`Group` is selected, a page loads "
"with a list of all the groups the user is currently a member of. Click on a "
"group to select it, then click the :guilabel:`Save` button in the lower "
"right corner."
msgstr ""

#: ../../content/applications/hr/referrals.rst:366
msgid ""
"Next, select who can comment on the post. To change this setting, click on "
"the :guilabel:`💬 (speech bubble) Anyone` button located beneath the body of "
"the post. A page loads with the various options. Click on one of the three "
"options to select it. The three options are :guilabel:`Anyone`, "
":guilabel:`Connections only`, and :guilabel:`No one`. The default option is "
":guilabel:`Anyone`, which allows anyone with a LinkedIn account to comment "
"on the post. :guilabel:`Connections only` will only allow people who are "
"connected with the user to comment on the post. :guilabel:`No one` turns off"
" commenting. After making a selection, click the :guilabel:`Save` button in "
"the far lower right corner."
msgstr ""

#: ../../content/applications/hr/referrals.rst:375
msgid ""
"Finally, once the post is edited and the settings have been selected, click "
":guilabel:`Post` to share the job position."
msgstr ""

#: ../../content/applications/hr/referrals.rst-1
msgid ""
"A linkedIn post to share a job. The job position is highlighted as is the "
"post button."
msgstr ""

#: ../../content/applications/hr/referrals.rst:383
msgid "Send as private message"
msgstr ""

#: ../../content/applications/hr/referrals.rst:385
msgid ""
"Instead of making a public post, the post can be sent to a connection in a "
"private message. To do so, click the :guilabel:`Send as private message` "
"button in the lower left corner. A message window loads with the link to the"
" job description in the bottom of the window. First, select the recipient(s)"
" for the message. Type the name in the :guilabel:`Search for message "
"recipients` field. As the name is typed in, any matching connections appear."
" Click on a connection to add them. Repeat this for all the recipients to "
"send the message to. There is no limit on the number of connections that can"
" be messaged. Next, enter any additional text in the message body. Click "
":guilabel:`Send` in the lower right corner to send the message. A "
":guilabel:`Message successfully sent!` screen loads. Two options are "
"presented, :guilabel:`View Message` and :guilabel:`Continue to LinkedIn`. "
"Click on the desired selection to navigate to that choice, or close the "
"browser tab to exit."
msgstr ""

#: ../../content/applications/hr/referrals.rst:399
msgid "Email a friend"
msgstr ""

#: ../../content/applications/hr/referrals.rst:401
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 main *Referrals* app 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.rst:406
msgid ""
"Enter the email address(es) in the :guilabel:`Email` line. The email can be "
"sent to multiple recipients, simply enter a comma followed by a single space"
" after each email address. The :guilabel:`Subject` is pre-configured with "
"`Job for you`, but can be edited."
msgstr ""

#: ../../content/applications/hr/referrals.rst:410
msgid ""
"The email body is also populated with pre-configured text. The text that "
"appears is:"
msgstr ""

#: ../../content/applications/hr/referrals.rst:412
msgid "`Hello,`"
msgstr ""

#: ../../content/applications/hr/referrals.rst:414
msgid ""
"`There are some amazing job offers in my company! Have a look, they can be "
"interesting for you`"
msgstr ""

#: ../../content/applications/hr/referrals.rst:416
msgid "`See Job Offers`"
msgstr ""

#: ../../content/applications/hr/referrals.rst:418
msgid ""
"The `See Job Offers` text is a tracking link to a complete list of all job "
"positions currently being recruited for, that are live on the company's "
"website (published). Add any additional text and/or make any edits to the "
"message body, then click :guilabel:`Send Mail` to send the email. The "
"message will be sent and the window will close."
msgstr ""

#: ../../content/applications/hr/referrals.rst:426
msgid "Hired referrals"
msgstr ""

#: ../../content/applications/hr/referrals.rst:428
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:431
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:435
msgid ""
"Below this message are five avatar thumbnails to choose from. If an avatar "
"has already been assigned to a referral, the thumbnail is greyed out, and "
"the name the avatar has been chosen for appears beneath the avatar. Click on"
" an available avatar to select it."
msgstr ""

#: ../../content/applications/hr/referrals.rst:439
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:450
msgid "Modify friends"
msgstr ""

#: ../../content/applications/hr/referrals.rst:452
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:459
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:464
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:469
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:474
#: ../../content/applications/hr/referrals.rst:659
msgid ""
"Once all changes have been made, click the :guilabel:`Save` button to save "
"the changes, or click the :guilabel:`Discard` button to revert to the "
"original information."
msgstr ""

#: ../../content/applications/hr/referrals.rst-1
msgid "A friend form in edit mode."
msgstr ""

#: ../../content/applications/hr/referrals.rst:482
#: ../../content/applications/hr/referrals.rst:667
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:486
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:491
msgid "Referral points"
msgstr ""

#: ../../content/applications/hr/referrals.rst:493
msgid ""
"The referral program is based on earning points that are then exchanged for "
"rewards. On the main Referrals application dashboard, the top displays a "
"summary of the user's current points. The left side of the summary displays "
"the total points earned, and the right side displays the points that are "
"available to spend."
msgstr ""

#: ../../content/applications/hr/referrals.rst:498
msgid ""
"To see the various referrals and the points earned for each, click on one of"
" the buttons directly beneath the avatars. The options are "
":guilabel:`Referrals`, :guilabel:`Ongoing`, and :guilabel:`Successful`."
msgstr ""

#: ../../content/applications/hr/referrals.rst:502
msgid ""
"The current number of referrals who are still active in the recruitment "
"pipeline, and have not yet been hired or refused, appear above the "
":guilabel:`Ongoing` button. The number of referrals who have been hired "
"appear above the :guilabel:`Successful` button. The total number of "
"referrals (both the ongoing and successful referrals combined) appear above "
"the :guilabel:`Referrals` button."
msgstr ""

#: ../../content/applications/hr/referrals.rst:508
msgid ""
"To view the referrals associated with each of the categories, "
":guilabel:`Referrals`, :guilabel:`Ongoing`, and :guilabel:`Successful`, "
"click on the corresponding button. All the referrals for that specific "
"category are displayed."
msgstr ""

#: ../../content/applications/hr/referrals.rst:513
msgid "My referrals"
msgstr ""

#: ../../content/applications/hr/referrals.rst:515
msgid ""
"To see all the referrals (both ongoing and successful) click the "
":guilabel:`Referrals` button. A :guilabel:`My Referral` window loads. This "
"screen displays all the referrals, with each referral in its own referral "
"card."
msgstr ""

#: ../../content/applications/hr/referrals.rst:519
msgid ""
"A successful referral has a green line down the left side of the card, and "
"displays a :guilabel:`✓ Hired` image in the top right corner of the card. "
"Referrals that are in process display an :guilabel:`In Progress` image in "
"the top right corner."
msgstr ""

#: ../../content/applications/hr/referrals.rst:523
msgid ""
"Each referral card lists the name of the applicant, the department the job "
"position is in, the name of the job position, the person responsible for "
"filling the role (recruiter), and the points earned."
msgstr ""

#: ../../content/applications/hr/referrals.rst:527
msgid "Points"
msgstr ""

#: ../../content/applications/hr/referrals.rst:529
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.rst:533
msgid ""
"On each individual referral card, beneath the points earned is a bar chart "
"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.rst:537
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 check mark appears next to"
" the stage."
msgstr ""

#: ../../content/applications/hr/referrals.rst:542
msgid "The pre-configured point structure for referrals is as follows:"
msgstr ""

#: ../../content/applications/hr/referrals.rst:544
msgid ":guilabel:`Initial Qualification`: 1 point"
msgstr ""

#: ../../content/applications/hr/referrals.rst:545
msgid ":guilabel:`First Interview`: 20 points"
msgstr ""

#: ../../content/applications/hr/referrals.rst:546
msgid ":guilabel:`Second Interview`: 9 points"
msgstr ""

#: ../../content/applications/hr/referrals.rst:547
msgid ":guilabel:`Contract Proposal`: 5 points"
msgstr ""

#: ../../content/applications/hr/referrals.rst:548
msgid ":guilabel:`Contract Signed`: 50 points"
msgstr ""

#: ../../content/applications/hr/referrals.rst:550
msgid ""
"The total points earned for a referral that is hired is 85 points. "
"Modifications of the points earned for each stage is done 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.rst:557
msgid "Rewards"
msgstr ""

#: ../../content/applications/hr/referrals.rst:560
msgid "Create rewards"
msgstr ""

#: ../../content/applications/hr/referrals.rst:562
msgid ""
"The rewards are the only configurations needed when setting up the Referrals"
" application. Only users with :guilabel:`Administrator` rights for the "
"Recruitment application can create or modify rewards. To add rewards, "
"navigate to :menuselection:`Referrals app --> Configuration --> Rewards`. "
"Click :guilabel:`Create` and a reward form loads. Enter the following "
"information on the form:"
msgstr ""

#: ../../content/applications/hr/referrals.rst:567
msgid ""
":guilabel:`Product Name`: Enter the name as it should appear for the reward."
msgstr ""

#: ../../content/applications/hr/referrals.rst:568
msgid ""
":guilabel:`Cost`: Enter the amount of points required to redeem the reward."
msgstr ""

#: ../../content/applications/hr/referrals.rst:569
msgid ""
":guilabel:`Company`: Using the drop-down menu, select the company the reward"
" will appear for. If a reward is to be used for several companies, each "
"company needs to have a record of the reward, with the company listed on the"
" form."
msgstr ""

#: ../../content/applications/hr/referrals.rst:572
msgid ""
":guilabel:`Gift Responsible`: Select the person who will be responsible for "
"procuring and delivering the reward to the recipient, using the drop-down "
"menu. This person is alerted when the reward is purchased, so they know when"
" to deliver the reward to the recipient."
msgstr ""

#: ../../content/applications/hr/referrals.rst:575
msgid ""
":guilabel:`Description`: Type in the description for the reward. This will "
"be visible on the reward card, beneath the title."
msgstr ""

#: ../../content/applications/hr/referrals.rst:577
msgid ""
":guilabel:`Photo`: Add a photo of the reward, which appears on the rewards "
"page. Hover over the image square, and two icons appear, a :guilabel:`✏️ "
"(pencil)` and a :guilabel:`🗑️ (garbage can)`. Click the :guilabel:`✏️ "
"(pencil)` icon and a file explorer appears. Navigate to the photo file, then"
" click :guilabel:`Open` to select it."
msgstr ""

#: ../../content/applications/hr/referrals.rst:582
msgid ""
"The only required fields are the :guilabel:`Product Name`, "
":guilabel:`Company`, and :guilabel:`Description`."
msgstr ""

#: ../../content/applications/hr/referrals.rst-1
msgid "A filled out reward form with all details entered."
msgstr ""

#: ../../content/applications/hr/referrals.rst:590
msgid ""
"It is advised to enter a :guilabel:`Cost` and add a :guilabel:`Photo`. If a "
"cost is not entered, the default cost will be listed as zero, which would "
"list the reward as free in the reward shop. If a photo is not selected, a "
"placeholder icon will be displayed on the rewards page."
msgstr ""

#: ../../content/applications/hr/referrals.rst:595
msgid "Redeem rewards"
msgstr ""

#: ../../content/applications/hr/referrals.rst:597
msgid ""
"To redeem points for a reward, click the :guilabel:`Rewards` button on the "
"main Referrals dashboard. All the configured rewards are listed in "
"individual reward cards. The points required to purchase the reward is "
"listed in the top right corner of the card. If the user has enough points to"
" purchase a reward, a :guilabel:`🧺 (basket) 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 buy button."
msgstr ""

#: ../../content/applications/hr/referrals.rst:604
msgid ""
"Click the :guilabel:`🧺 (basket) Buy` button on a reward to purchase it. A "
"confirmation pop-up 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.rst:608
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.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.rst:620
msgid "Levels"
msgstr ""

#: ../../content/applications/hr/referrals.rst:622
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:626
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:629
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:636
msgid "Modify levels"
msgstr ""

#: ../../content/applications/hr/referrals.rst:638
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:645
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. Click "
":guilabel:`Edit` to make modifications."
msgstr ""

#: ../../content/applications/hr/referrals.rst:648
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:654
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-1
msgid "A level form in edit mode."
msgstr ""

#: ../../content/applications/hr/referrals.rst:671
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:676
msgid "Level up"
msgstr ""

#: ../../content/applications/hr/referrals.rst:678
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:683
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:687
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:696
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:701
msgid "Alerts"
msgstr ""

#: ../../content/applications/hr/referrals.rst:703
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. These alerts appear as a thin semi-transparent "
"banner, with the word :guilabel:`New!` appearing on the far left. The text "
"for the alert is in the center of the banner, and on the far right side is "
"an :guilabel:`X`."
msgstr ""

#: ../../content/applications/hr/referrals.rst:708
msgid ""
"Alerts appear on the main dashboard for the specified time configured on the"
" individual alert. If a user does not wish to see a specific alert again, "
"click the :guilabel:`X` in the far right side of the alert. This removes the"
" alert from the dashboard and will not appear again, even when opening the "
"Referrals application for the first time in a new session."
msgstr ""

#: ../../content/applications/hr/referrals.rst-1
msgid "Two alert banners appear above the user's photo."
msgstr ""

#: ../../content/applications/hr/referrals.rst:718
msgid "Create an alert"
msgstr ""

#: ../../content/applications/hr/referrals.rst:720
msgid ""
"Only users with :guilabel:`Administrator` rights for the Recruitment "
"application can create alerts. To add a new alert, navigate to the "
":menuselection:`Referrals application --> Configuration --> Alerts`."
msgstr ""

#: ../../content/applications/hr/referrals.rst:724
msgid ""
"Click :guilabel:`Create` and a blank alert form loads. Enter the following "
"information on the form:"
msgstr ""

#: ../../content/applications/hr/referrals.rst:726
msgid ""
":guilabel:`Date From`: The date the alert starts. On this date, the alert "
"will be visible on the dashboard."
msgstr ""

#: ../../content/applications/hr/referrals.rst:728
msgid ""
":guilabel:`Date To`: The date the alert ends. After this date, the alert "
"will be hidden from view."
msgstr ""

#: ../../content/applications/hr/referrals.rst:729
msgid ""
":guilabel:`Company`: The current company populates this field by default. To"
" modify the company the alert should be displayed for, select the company "
"from the drop-down menu. If this field remains blank, the alert is visible "
"to everyone with access to the Referrals application. If a company is "
"specified, only user's within that company (who also have access to the "
"Referrals application) will see the alert."
msgstr ""

#: ../../content/applications/hr/referrals.rst:734
msgid ""
":guilabel:`Alert`: Enter the text for the alert. This message appears inside"
" the alert banner on the main dashboard."
msgstr ""

#: ../../content/applications/hr/referrals.rst:736
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.rst:739
msgid ""
":guilabel:`Not Clickable`: The alert only displays text, there is no link to"
" click."
msgstr ""

#: ../../content/applications/hr/referrals.rst:740
msgid ""
":guilabel:`Go to All Jobs`: The alert contains a link that when clicked, "
"navigates to the website with all the currently posted job positions."
msgstr ""

#: ../../content/applications/hr/referrals.rst:742
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 URL in the field."
msgstr ""

#: ../../content/applications/hr/referrals.rst-1
msgid "An alert form completely filled in with all selections entered."
msgstr ""

#: ../../content/applications/hr/referrals.rst:755
msgid ""
"Only users with :guilabel:`Administrator` rights for the Recruitment "
"application have access to the Reporting feature in Referrals. To access the"
" reports, click :menuselection:`Referrals application --> Reporting`. The "
"main view is the Reporting Dashboard view, which contains three sections."
msgstr ""

#: ../../content/applications/hr/referrals.rst:759
msgid ""
"In the top portion of the window, the report displays a bar chart of how "
"many referred candidates are hired, and how many are still in the hiring "
"pipeline. The candidates are further divided by channel, showing "
"specifically where the referral came from, such as a direct referral, "
"Facebook, etc. If a channel does not appear on the report, that indicates "
"there are no referrals from that particular channel."
msgstr ""

#: ../../content/applications/hr/referrals.rst:765
msgid ""
"The middle third provides all the specific data that has been tracked. This "
"includes how many total points have been earned across all referrals, how "
"many applicants were referred, hired, or refused, how many applicants the "
"current logged-in user referred, how many total points were earned, and how "
"many points were given for refused applicants."
msgstr ""

#: ../../content/applications/hr/referrals.rst:770
msgid ""
"The bottom third displays a pivot table. This table can be inserted into a "
"new or existing spreadsheet. To do so, click the :guilabel:`Insert in "
"Spreadsheet` button right above the chart. A pop-up appears, asking which "
"spreadsheet to insert the pivot chart into. Select the desired spreadsheet "
"from the drop-down menu, or select :guilabel:`New Spreadsheet`. Click "
":guilabel:`Confirm` and the selected spreadsheet loads, with the new table "
"in it."
msgstr ""

#: ../../content/applications/hr/referrals.rst:777
msgid ""
"The spreadsheet is stored in the *Documents* application. This application "
"needs to be installed in order to use the :guilabel:`Insert in Spreadsheet` "
"option."
msgstr ""

#: ../../content/applications/hr/time_off.rst:3
msgid "Time Off"
msgstr ""

#: ../../content/applications/hr/time_off.rst:5
msgid ""
"Odoo's *Time Off* application is a centralized place, where all time off "
"information is housed. The *Time Off* app manages everything related to "
"requests, balances, allocations, approvals, and reports."
msgstr ""

#: ../../content/applications/hr/time_off.rst:9
msgid ""
"Users can :ref:`request time off <time_off/request-time-off>`, managers can "
":ref:`approve time off requests <time_off/approve-time-off>`, :ref:`allocate"
" time off <time_off/allocate>` to individuals, teams, or the whole company, "
":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:16
msgid ""
"Be advised, only users with specific access rights can see all aspects of "
"the *Time Off* application."
msgstr ""

#: ../../content/applications/hr/time_off.rst:19
msgid ""
"All users can access the :guilabel:`My Time Off` and :guilabel:`Overview` "
"sections of the *Time Off* application. All other sections require specific "
"access rights."
msgstr ""

#: ../../content/applications/hr/time_off.rst:22
msgid ""
"To better understand how access rights affect the *Time Off* application, "
"refer to the :doc:`/applications/hr/employees/new_employee` document, "
"specifically the section about configuring the work information tab."
msgstr ""

#: ../../content/applications/hr/time_off.rst:29
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:36
msgid "Time off types"
msgstr ""

#: ../../content/applications/hr/time_off.rst:38
msgid ""
"To view the currently configured time off types, navigate to "
":menuselection:`Time Off application --> Configuration --> Time Off Types`. "
"The time off types are presented in a list view. The *Time Off* application "
"comes with four types of time off pre-configured: :guilabel:`Paid Time Off`,"
" :guilabel:`Sick Time Off`, :guilabel:`Unpaid`, and :guilabel:`Compensatory "
"Days`. Any of these may be modified to suit the needs of the businesses, or "
"can be used as-is."
msgstr ""

#: ../../content/applications/hr/time_off.rst:45
msgid "Create time off type"
msgstr ""

#: ../../content/applications/hr/time_off.rst:47
msgid ""
"To create a new time off type, navigate to :menuselection:`Time Off app --> "
"Configuration --> Time Off Types`. From here, click the :guilabel:`Create` "
"button to reveal a blank time off type form."
msgstr ""

#: ../../content/applications/hr/time_off.rst:50
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:54
msgid "Time off requests section"
msgstr ""

#: ../../content/applications/hr/time_off.rst:56
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:59
msgid ""
":guilabel:`No Validation`: no approvals are required when requesting this "
"type of time off. The time off request is automatically approved when "
"requested."
msgstr ""

#: ../../content/applications/hr/time_off.rst:61
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:`Responsible"
" 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:64
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:67
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:73
msgid ""
":guilabel:`Responsible Time Off Officer`: select the person responsible for "
"approving requests and allocations for this specific type of time off."
msgstr ""

#: ../../content/applications/hr/time_off.rst:75
msgid ""
":guilabel:`Take Time Off in`: select the format the time off is requested "
"from the drop-down menu. The options are:"
msgstr ""

#: ../../content/applications/hr/time_off.rst:78
msgid ""
":guilabel:`Day`: if time off can only be requested in full day increments (8"
" hours)."
msgstr ""

#: ../../content/applications/hr/time_off.rst:79
msgid ""
":guilabel:`Half Day`: if time off can only be requested in half day "
"increments (4 hours)."
msgstr ""

#: ../../content/applications/hr/time_off.rst:80
msgid ":guilabel:`Hours`: if the time off can be taken in hourly increments."
msgstr ""

#: ../../content/applications/hr/time_off.rst:84
msgid ""
":guilabel:`Deduct Extra Hours`: tick this box if the time off request should"
" factor in any extra time accrued by the employee"
msgstr ""

#: ../../content/applications/hr/time_off.rst:88
msgid ""
"For example, if an employee worked two (2) extra hours for the week, and "
"requests five (5) hours of time off, the request would be for three (3) "
"hours, since the two (2) additionally worked hours are used first, and "
"deducted from the request."
msgstr ""

#: ../../content/applications/hr/time_off.rst:92
msgid ""
":guilabel:`Allow To Join Supporting Document`: tick this box 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:95
msgid ""
":guilabel:`Kind of Leave`: select from the drop-down menu the type of leave "
"this time off type is, either :guilabel:`Time Off` or :guilabel:`Other`."
msgstr ""

#: ../../content/applications/hr/time_off.rst:97
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."
msgstr ""

#: ../../content/applications/hr/time_off.rst:102
msgid "Allocation requests section"
msgstr ""

#: ../../content/applications/hr/time_off.rst:104
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:108
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:112
msgid ""
"For example, if ten (10) days are allocated to the employee for this "
"particular type of time off, and this option is enabled, the employee may "
"submit a request for more than ten (10) days."
msgstr ""

#: ../../content/applications/hr/time_off.rst:115
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:118
msgid ""
":guilabel:`Approval`: select the type of approval(s) required for the "
"allocation of this particular type of time off."
msgstr ""

#: ../../content/applications/hr/time_off.rst:121
msgid ""
":guilabel:`No validation needed` indicates that no approvals are required."
msgstr ""

#: ../../content/applications/hr/time_off.rst:122
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:124
msgid ""
":guilabel:`Set by Time Off Officer` indicates that the :ref:`Time Off "
"Officer <time_off/time-off-officer>` set on this form must allocate the time"
" off."
msgstr ""

#: ../../content/applications/hr/time_off.rst:128
msgid "Payroll section"
msgstr ""

#: ../../content/applications/hr/time_off.rst:130
msgid ""
"If the time off type should create :doc:`../hr/payroll/work_entries` in the "
"*Payroll* application, select the :guilabel:`Work Entry Type` from the drop-"
"down list."
msgstr ""

#: ../../content/applications/hr/time_off.rst:134
msgid "Timesheets section"
msgstr ""

#: ../../content/applications/hr/time_off.rst:137
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:140
msgid ""
"When an employee takes time off and is also using timesheets, Odoo creates "
"entries in the timesheet for the time off. This section defines how they are"
" entered."
msgstr ""

#: ../../content/applications/hr/time_off.rst:143
msgid ""
":guilabel:`Project`: select the project that the time off type entries "
"appear in."
msgstr ""

#: ../../content/applications/hr/time_off.rst:144
msgid ""
":guilabel:`Task`: select the task that appears in the timesheet for this "
"time off type. The options are: :guilabel:`Time Off`, :guilabel:`Meeting`, "
"or :guilabel:`Training`."
msgstr ""

#: ../../content/applications/hr/time_off.rst:148
msgid "Display option section"
msgstr ""

#: ../../content/applications/hr/time_off.rst:150
msgid ""
":guilabel:`Color`: select a color to be used in the *Time Off* application "
"dashboard."
msgstr ""

#: ../../content/applications/hr/time_off.rst:151
msgid ""
":guilabel:`Cover Image`: select an icon to be used in the *Time Off* "
"application dashboard."
msgstr ""

#: ../../content/applications/hr/time_off.rst:154
msgid ""
"The only required fields on the time off type form are the name of the "
":guilabel:`Time Off Type`, the :guilabel:`Approval`, the "
":guilabel:`Responsible Time Off Officer`, :guilabel:`Take Time Off in`, "
":guilabel:`Kind of Leave`, and the :guilabel:`Allocation Requests` section."
msgstr ""

#: ../../content/applications/hr/time_off.rst-1
msgid ""
"Time off type form with all the information filled out for sick time off."
msgstr ""

#: ../../content/applications/hr/time_off.rst:165
msgid "Accrual plans"
msgstr ""

#: ../../content/applications/hr/time_off.rst:167
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:171
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 (40) "
"hour work week, they earn a whole vacation day (8 hours)."
msgstr ""

#: ../../content/applications/hr/time_off.rst:176
msgid "Create accrual plan"
msgstr ""

#: ../../content/applications/hr/time_off.rst:178
msgid ""
"To create a new accrual plan, navigate to :menuselection:`Time Off app --> "
"Configuration --> Accrual Plans`. Then, click the :guilabel:`Create` button,"
" which reveals a blank accrual plan form."
msgstr ""

#: ../../content/applications/hr/time_off.rst:181
msgid ""
"Enter the accrual plan name in the :guilabel:`Name` field. If the accrual "
"plan only applies to a specific time off type, select it from the drop-down "
"menu. If this accrual plan is available for all time off types, leave this "
"field blank."
msgstr ""

#: ../../content/applications/hr/time_off.rst:185
msgid ""
"Next, select how the :guilabel:`Level Transition` occurs, either "
":guilabel:`Immediately` or :guilabel:`After this accrual's period`. By "
"default, the first level begins once the time off is approved if the time "
"off is based on an accrual plan. If :guilabel:`Immediately` is selected, "
"then the next level begins according to the time frame set on the level. If "
":guilabel:`After this accrual's period` is selected, the next level does not"
" begin until the first level is completed according to the rules set on it."
msgstr ""

#: ../../content/applications/hr/time_off.rst:195
msgid ""
"Rules must be created in order for the accrual plan to accrue time off."
msgstr ""

#: ../../content/applications/hr/time_off.rst:197
msgid ""
"To create a new rule, click the :guilabel:`Add A New Level` button right "
"beneath the word `Rules`, and a :guilabel:`Create Level` pop-up form "
"appears."
msgstr ""

#: ../../content/applications/hr/time_off.rst:200
msgid "Fill out the following fields on the form:"
msgstr ""

#: ../../content/applications/hr/time_off.rst:202
msgid ""
":guilabel:`Start after (#) (time period) after allocation date`: 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:206
msgid ""
"Then, select the type of time period using the drop-down menu in the second "
"field. The options are: :guilabel:`day(s)`, :guilabel:`month(s)`, or "
":guilabel:`year(s)`."
msgstr ""

#: ../../content/applications/hr/time_off.rst:208
msgid ""
":guilabel:`Based on worked time`: tick this box if the accrual of time off "
"is based on the time the employee has worked. If an employee takes time off "
"that is *not* considered a worked day, Odoo will not count that day towards "
"their accrual plan."
msgstr ""

#: ../../content/applications/hr/time_off.rst:211
msgid ""
":guilabel:`Rate (#) (time)`: enter the rate of time off that is accumulated."
" The first value is numerical; enter a number in the first field. Whole "
"numbers are not necessary, any decimal value may be entered."
msgstr ""

#: ../../content/applications/hr/time_off.rst:215
msgid ""
"Next, in the second field, select the type of time accrued using the drop-"
"down menu. The options are either :guilabel:`Days` or :guilabel:`Hours`."
msgstr ""

#: ../../content/applications/hr/time_off.rst:217
msgid ""
":guilabel:`Frequency (X)`: select how often the employee accrues the time "
"off for this rule using the drop-down menu. The options are "
":guilabel:`Daily`, :guilabel:`Weekly`, :guilabel:`Twice a month`, "
":guilabel:`Monthly`, :guilabel:`Twice a year`, or :guilabel:`Yearly`."
msgstr ""

#: ../../content/applications/hr/time_off.rst:221
msgid ""
"Depending on the selection, more fields appear to specify exactly when the "
"accrual renews."
msgstr ""

#: ../../content/applications/hr/time_off.rst:224
msgid ""
"If the employee should accrue one vacation day for every week worked, the "
":guilabel:`Rate` is set to `1`, and the :guilabel:`Frequency` entry is set "
"to `Frequency (Weekly) on (Friday)`. Only the :guilabel:`Frequency` and "
":guilabel:`Weekday` fields appear."
msgstr ""

#: ../../content/applications/hr/time_off.rst:228
msgid ""
"If the employee should accrue ten (10)vacation days each year, and they "
"receive these days every year on the first of January, the :guilabel:`Rate` "
"is set to `10`, and the :guilabel:`Frequency` entry is set to `Frequency "
"(Yearly) on the (1) of (January)`. The :guilabel:`Frequency`, "
":guilabel:`Date`, and :guilabel:`Month` fields appear."
msgstr ""

#: ../../content/applications/hr/time_off.rst:233
msgid ""
":guilabel:`Limit to`: enter a maximum amount of days the employee can accrue"
" with this plan."
msgstr ""

#: ../../content/applications/hr/time_off.rst:234
msgid ""
":guilabel:`At the end of the calendar year, unused accruals will be`: select"
" from the drop-down menu how unused time off is handled."
msgstr ""

#: ../../content/applications/hr/time_off.rst:237
msgid ""
"The options are either :guilabel:`Transferred to the next year`, which rolls"
" over unused time to the next calendar year, or :guilabel:`Lost`, which "
"means any unused time off is gone."
msgstr ""

#: ../../content/applications/hr/time_off.rst-1
msgid "A level form with all the data filled out."
msgstr ""

#: ../../content/applications/hr/time_off.rst:244
msgid ""
"When the form is filled out, click :guilabel:`Save & Close` to save the form"
" and close the pop-up, or :guilabel:`Save & New` to save the form and create"
" a new rule. Add as many levels as desired."
msgstr ""

#: ../../content/applications/hr/time_off.rst-1
msgid "An accrual form with all the entries filled out."
msgstr ""

#: ../../content/applications/hr/time_off.rst:254
msgid "Public holidays"
msgstr ""

#: ../../content/applications/hr/time_off.rst:256
msgid ""
"Most countries have public or national holidays, and some companies may have"
" specific days they are closed and/or give extra days as holidays."
msgstr ""

#: ../../content/applications/hr/time_off.rst:259
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:263
msgid "Create public holiday"
msgstr ""

#: ../../content/applications/hr/time_off.rst:265
msgid ""
"To create a public holiday, navigate to :menuselection:`Time Off app --> "
"Configuration --> Public Holidays`."
msgstr ""

#: ../../content/applications/hr/time_off.rst:268
msgid "All currently configured public holidays appear in a list view."
msgstr ""

#: ../../content/applications/hr/time_off.rst:270
msgid ""
"Click the :guilabel:`Create` button, and a new line appears at the bottom of"
" the list."
msgstr ""

#: ../../content/applications/hr/time_off.rst:272
msgid "Enter the following information:"
msgstr ""

#: ../../content/applications/hr/time_off.rst:274
msgid ":guilabel:`Name`: enter the name of the holiday."
msgstr ""

#: ../../content/applications/hr/time_off.rst:275
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:277
msgid ""
":guilabel:`Start Date`: using the date and time picker, select the date and "
"time that the holiday starts. 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 times <payroll/working-times>`). If "
"the user's computer is set to a different time zone, the start time is "
"adjusted according to the difference in the time zone compared to the "
"company's time zone."
msgstr ""

#: ../../content/applications/hr/time_off.rst:282
msgid ""
":guilabel:`End Date`: using the date and time picker, select the date and "
"time that the holiday ends. 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 times <payroll/working-times>`). If the user's "
"computer is set to a different time zone, the start time is adjusted "
"according to the difference in the time zone compared to the company's time "
"zone."
msgstr ""

#: ../../content/applications/hr/time_off.rst:289
msgid ""
"A company is located in San Francisco, and the working times are 9:00 AM - "
"6:00 PM (an eight (8) hour work day with a one (1) hour lunch break). A user"
" is located in New York, and their computer time zone is set to Eastern. "
"When they create a Public Holiday, the start time appears as 12:00 PM - 9:00"
" PM, since the time zone is accounted for. If a different user is located in"
" Los Angeles, and their computer time zone is set to Pacific, when they "
"create a Public Holiday, the time appears as 9:00 AM - 6:00 PM."
msgstr ""

#: ../../content/applications/hr/time_off.rst:296
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:299
msgid ""
":guilabel:`Work Entry Type`: if using the *Payroll* application, this field "
"defines how the work entry for the holiday appears. 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:311
msgid ""
"To view a color-coded schedule of both the user's time off, and/or the team "
"managed by them, navigate to :menuselection:`Time Off app --> Overview`. "
"This presents a calendar with the default filter of :guilabel:`My Team`, in "
"a month view."
msgstr ""

#: ../../content/applications/hr/time_off.rst:315
msgid ""
"To change the time period displayed, click on either the :guilabel:`Day`, "
":guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` buttons to present "
"the calendar in that corresponding view."
msgstr ""

#: ../../content/applications/hr/time_off.rst:318
msgid ""
"Each team member is displayed on a line, and any time off they requested, "
"regardless of the status (:guilabel:`Validated` or :guilabel:`To Approve`), "
"appears on the calendar."
msgstr ""

#: ../../content/applications/hr/time_off.rst:321
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:324
msgid ""
"The status of the time of is represented by the color of the request either "
"appearing solid (:guilabel:`Validated`) or striped (:guilabel:`To Approve`)."
msgstr ""

#: ../../content/applications/hr/time_off.rst:327
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:329
msgid ""
"At the bottom of the calendar, a bar graph shows how many people are "
"projected to be out on any given day. The number on the bar represents the "
"number of employees out for those highlighted days."
msgstr ""

#: ../../content/applications/hr/time_off.rst:332
msgid ""
"Hover over 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."
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:342
msgid "Allocate time off"
msgstr ""

#: ../../content/applications/hr/time_off.rst:344
msgid ""
"Once time off types and accrual plans have been configured, the next step is"
" to allocate, or give, time off to employees. This section is only visible "
"to users who have either :guilabel:`Time Off Officer` or "
":guilabel:`Administrator` access rights for the *Time Off* application."
msgstr ""

#: ../../content/applications/hr/time_off.rst:348
msgid ""
"To create a new allocation, navigate to :menuselection:`Time Off app --> "
"Approvals --> Allocations`."
msgstr ""

#: ../../content/applications/hr/time_off.rst:350
msgid ""
"This presents a list of all current allocations, including their respective "
"status."
msgstr ""

#: ../../content/applications/hr/time_off.rst:352
msgid ""
"Click :guilabel:`Create` to allocate time off, and a blank allocation form "
"appears."
msgstr ""

#: ../../content/applications/hr/time_off.rst:354
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.rst:357
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.rst:359
msgid ""
":guilabel:`Allocation Type`: select either :guilabel:`Regular Allocation` or"
" :guilabel:`Accrual Allocation`."
msgstr ""

#: ../../content/applications/hr/time_off.rst:361
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.rst:365
msgid ""
":guilabel:`Validity Period/Start Date`: if :guilabel:`Regular Allocation` is"
" selected for the :guilabel:`Allocation Type`, this field is labeled "
":guilabel:`Validity Period`."
msgstr ""

#: ../../content/applications/hr/time_off.rst:368
msgid ""
"Using the calendar, select the beginning date for the allocation. 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."
msgstr ""

#: ../../content/applications/hr/time_off.rst:372
msgid ""
"If :guilabel:`Accrual Allocation` is selected for the :guilabel:`Allocation "
"Type`, this field is labeled :guilabel:`Start Date`."
msgstr ""

#: ../../content/applications/hr/time_off.rst:375
msgid ""
"Using the calendar picker, select the start date for the allocation. If the "
"allocation expires, select the expiration date in the :guilabel:`Run until` "
"field. If the time off does *not* expire, leave the :guilabel:`Run until` "
"field blank."
msgstr ""

#: ../../content/applications/hr/time_off.rst:378
msgid ""
":guilabel:`Duration`: 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 (in days or hours)."
msgstr ""

#: ../../content/applications/hr/time_off.rst:381
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.rst:385
msgid ""
"Depending on what was selected for the :guilabel:`Mode`, this following "
"field is labeled either: :guilabel:`Employees`, :guilabel:`Company`, "
":guilabel:`Department`, or :guilabel:`Employee Tag`."
msgstr ""

#: ../../content/applications/hr/time_off.rst:388
msgid ""
"Using the drop-down menu, indicate the specific employees, company, "
"department, or employee tags who are receiving this time off."
msgstr ""

#: ../../content/applications/hr/time_off.rst:391
msgid ""
"Multiple selections can be made for either :guilabel:`Employees` or "
":guilabel:`Employee Tag`."
msgstr ""

#: ../../content/applications/hr/time_off.rst:393
msgid ""
"Only one selection can be made for the :guilabel:`Company` or "
":guilabel:`Department`."
msgstr ""

#: ../../content/applications/hr/time_off.rst:394
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.rst:400
msgid "Request time off"
msgstr ""

#: ../../content/applications/hr/time_off.rst:402
msgid ""
"Once an employee has been allocated time off, a request to use the time off "
"can be submitted. Time off can be requested in one of two ways, either from "
"the :ref:`dashboard <time_off/dashboard>` or from the :guilabel:`My Time "
"Off` view."
msgstr ""

#: ../../content/applications/hr/time_off.rst:406
msgid ""
"To access the dashboard, navigate to :menuselection:`Time Off app --> My "
"Time Off --> Dashboard`. This is also the default view for the *Time Off* "
"application."
msgstr ""

#: ../../content/applications/hr/time_off.rst:409
msgid ""
"To access :guilabel:`My Time Off`, navigate to :menuselection:`Time Off app "
"--> My Time Off --> My Time Off`. This presents a list view of all the time "
"off requests for the employee."
msgstr ""

#: ../../content/applications/hr/time_off.rst:412
msgid ""
"To create a new request for time off, click either the :guilabel:`New Time "
"Off` button on the main *Time Off* dashboard, or the :guilabel:`Create` "
"button in the :guilabel:`My Time Off` list view. Both buttons open a new "
"time off request form."
msgstr ""

#: ../../content/applications/hr/time_off.rst:418
msgid ""
":guilabel:`Time Off Type`: select the type of time off being requested from "
"the drop-down menu."
msgstr ""

#: ../../content/applications/hr/time_off.rst:419
msgid ""
":guilabel:`Dates`: enter the dates that the time off will fall under. There "
"are two fields to populate, the :guilabel:`From` and :guilabel:`To` fields. "
"Click on either the :guilabel:`From` or :guilabel:`To` field, and a calendar"
" pop-up appears."
msgstr ""

#: ../../content/applications/hr/time_off.rst:423
msgid ""
"Click on the start date, then click on the end date. The selected start and "
"end dates appear in deep purple, and the dates between them appear in pale "
"purple (if applicable)."
msgstr ""

#: ../../content/applications/hr/time_off.rst:426
msgid ""
"If the time off requested is 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.rst:429
msgid ""
"When the correct dates are selected/highlighted, click the :guilabel:`Apply`"
" button."
msgstr ""

#: ../../content/applications/hr/time_off.rst:431
msgid "The dates now populate the :guilabel:`From` and :guilabel:`To` fields."
msgstr ""

#: ../../content/applications/hr/time_off.rst:433
msgid ""
":guilabel:`Half Day`: if the time off request is for a half day, tick this "
"box. When this is selected, the :guilabel:`From` date field disappears, and "
"is replaced with a 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.rst:437
msgid ""
":guilabel:`Custom Hours`: if the time off requested is not a whole or half "
"day, tick this box. A :guilabel:`From` and :guilabel:`To` field appears "
"beneath this option if selected. Using the drop-down menu, select the start "
"and end time for the time off request."
msgstr ""

#: ../../content/applications/hr/time_off.rst:441
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 the "
":guilabel:`Date` selections."
msgstr ""

#: ../../content/applications/hr/time_off.rst:445
msgid ""
":guilabel:`Description`: enter a description for the time off request. This "
"should include any details that managers and approvers may need in order to "
"approve the request."
msgstr ""

#: ../../content/applications/hr/time_off.rst:447
msgid ""
":guilabel:`Supporting Document`: this field only appears if the "
":guilabel:`Time Off Type` selected allows for the attachments of documents. "
"Click the :guilabel:`Attach File` button, and a file explorer window "
"appears."
msgstr ""

#: ../../content/applications/hr/time_off.rst:451
msgid ""
"Navigate to the file(s) to attach, 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.rst:454
#: ../../content/applications/hr/time_off.rst:494
msgid ""
"When the form is complete, click the :guilabel:`Save` button to save the "
"information, and submit the request."
msgstr ""

#: ../../content/applications/hr/time_off.rst-1
msgid ""
"A time off request form filled out for an employee home sick for two days "
"with the flu."
msgstr ""

#: ../../content/applications/hr/time_off.rst:464
msgid "Request allocation"
msgstr ""

#: ../../content/applications/hr/time_off.rst:466
msgid ""
"If an employee has used all their time off, or is going to 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 :guilabel:`My Allocations` view."
msgstr ""

#: ../../content/applications/hr/time_off.rst:470
msgid ""
"To access the dashboard, navigate to the :menuselection:`Time Off app --> My"
" Time Off --> Dashboard`. This is also the default view for the *Time Off* "
"application."
msgstr ""

#: ../../content/applications/hr/time_off.rst:473
msgid ""
"To access :guilabel:`My Allocations`, navigate to the :menuselection:`Time "
"Off app --> My Time Off --> My Allocations`. This presents a list view of "
"all the allocations for the employee."
msgstr ""

#: ../../content/applications/hr/time_off.rst:476
msgid ""
"To create a new allocation request, click either the :guilabel:`Allocation "
"Request` button on the main *Time Off* dashboard, or the :guilabel:`Create` "
"button in the :guilabel:`My Allocations` list view. Both buttons open a new "
"allocation request form."
msgstr ""

#: ../../content/applications/hr/time_off.rst:480
msgid ""
"After entering a name for the allocation in the first blank line on the "
"form, enter the following information:"
msgstr ""

#: ../../content/applications/hr/time_off.rst:483
msgid ""
":guilabel:`Time Off Type`: select the type of time off being requested for "
"the allocation from the drop-down menu."
msgstr ""

#: ../../content/applications/hr/time_off.rst:485
msgid ""
":guilabel:`Validity Period`: the current date populates the start date by "
"default. If there is no expiration on the time off type, there is no date "
"populated as the end date. If the time off type has an expiration date, the "
"date automatically populates the end date field once the form is saved."
msgstr ""

#: ../../content/applications/hr/time_off.rst:489
msgid ""
":guilabel:`Duration`: enter the amount of time being requested. The format "
"(either days or hours) is in the same format as the time off type."
msgstr ""

#: ../../content/applications/hr/time_off.rst:491
msgid ""
":guilabel:`Add a reason...`: enter a description for the allocation request."
" This should include any details that managers and approvers may need in "
"order to approve the request."
msgstr ""

#: ../../content/applications/hr/time_off.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.rst:503
msgid "Approvals"
msgstr ""

#: ../../content/applications/hr/time_off.rst:505
msgid ""
"Most requests for time off and allocations need to go through the approval "
"process, prior to the time off being allocated, and then granted to an "
"employee. Requests either need one or two approvals, depending on how the "
"specific type of time off is configured."
msgstr ""

#: ../../content/applications/hr/time_off.rst:509
msgid ""
"Only users who can approve allocation and time off requests have the "
":guilabel:`Approvals` section visible in the *Time Off* application."
msgstr ""

#: ../../content/applications/hr/time_off.rst:513
msgid "Approve allocations"
msgstr ""

#: ../../content/applications/hr/time_off.rst:515
msgid ""
"To view allocations that need approval, navigate to :menuselection:`Time Off"
" app --> Approvals --> Allocations`. The only allocations visible on this "
"list are for employees the user has either :guilabel:`Time Off Officer` or "
":guilabel:`Administrator` access rights for in the *Time Off* application."
msgstr ""

#: ../../content/applications/hr/time_off.rst:520
msgid ""
"The default filters that are configured to be in place when navigating to "
"the :guilabel:`Allocations` list are :guilabel:`My Team` and "
":guilabel:`Active Employee`. This *only* presents employees on the user's "
"team (who they manage) and active employees. Inactive users are not shown."
msgstr ""

#: ../../content/applications/hr/time_off.rst:525
msgid ""
"The left side of the screen has various grouping options to narrow down the "
"presented allocation requests."
msgstr ""

#: ../../content/applications/hr/time_off.rst:528
msgid ""
"The options are :guilabel:`To Approve`, :guilabel:`To Submit`, "
":guilabel:`Refused`, and :guilabel:`Approved`."
msgstr ""

#: ../../content/applications/hr/time_off.rst:531
msgid "To view all allocation requests, click :guilabel:`All`."
msgstr ""

#: ../../content/applications/hr/time_off.rst:533
msgid ""
"It is also possible to display allocation requests by department. Click on "
"the department to only present allocations for that specific department."
msgstr ""

#: ../../content/applications/hr/time_off.rst:537
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`. Only the statuses for allocation requests that fall under those "
"filters are presented on the left side."
msgstr ""

#: ../../content/applications/hr/time_off.rst:541
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."
msgstr ""

#: ../../content/applications/hr/time_off.rst:544
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 pre-"
"configured filters, the list is blank."
msgstr ""

#: ../../content/applications/hr/time_off.rst:547
msgid ""
"It is always possible to remove any of the pre-configured filters, by "
"clicking the :guilabel:`✖️ (remove)` icon on the specific filter to remove "
"it."
msgstr ""

#: ../../content/applications/hr/time_off.rst:550
#: ../../content/applications/hr/time_off.rst:599
msgid ""
"The status column displays the status of each request, with the status "
"highlighted in a specific color."
msgstr ""

#: ../../content/applications/hr/time_off.rst:553
msgid ""
"The :guilabel:`To Approve` requests are highlighted in yellow, "
":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.rst:557
msgid ""
"To approve an allocation request, click :guilabel:`✔ Validate` at the end of"
" the line, to refuse a request, click :guilabel:`✖️ Refuse`."
msgstr ""

#: ../../content/applications/hr/time_off.rst-1
msgid ""
"Allocations with the filter, groupings, and status sections highlighted."
msgstr ""

#: ../../content/applications/hr/time_off.rst:564
msgid ""
"If more details are needed, click anywhere on the allocation request line "
"(except for :guilabel:`✔ Validate` and :guilabel:`✖️ Refuse`) to view the "
"request in detail."
msgstr ""

#: ../../content/applications/hr/time_off.rst:567
msgid ""
"Depending on the rights of the user, changes can be made on the allocation "
"request form that appears. To modify the request, click the :guilabel:`Edit`"
" button, make any desired changes, then click :guilabel:`Save`."
msgstr ""

#: ../../content/applications/hr/time_off.rst:571
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.rst:577
msgid "Approve time off"
msgstr ""

#: ../../content/applications/hr/time_off.rst:579
msgid ""
"To view time off requests that need approval, navigate to "
":menuselection:`Time Off app --> Approvals --> Time Off`. The only time off "
"requests visible on this list are for employees the user has either "
":guilabel:`Time Off Officer` or :guilabel:`Administrator` access rights for "
"the *Time Off* application."
msgstr ""

#: ../../content/applications/hr/time_off.rst:584
msgid ""
"The default filters in the :guilabel:`Time Off` list are :guilabel:`To "
"Approve`, :guilabel:`My Team`, :guilabel:`Active Employee`, and "
":guilabel:`Active Time Off`. This only presents time off requests that need "
"to be approved for current employees on the user's team, for requests that "
"are active and *not* in a draft mode."
msgstr ""

#: ../../content/applications/hr/time_off.rst:589
msgid ""
"The left side of the screen has various grouping options to narrow down the "
"presented time off requests. Since only time off requests that need to be "
"approved are shown, the only status options are :guilabel:`All` and "
":guilabel:`To Approve`."
msgstr ""

#: ../../content/applications/hr/time_off.rst:593
msgid ""
"To view requests with other statuses, first remove the :guilabel:`To "
"Approve` filter, by clicking the :guilabel:`✖️ (remove)` icon next to the "
":guilabel:`To Approve` filter to remove it."
msgstr ""

#: ../../content/applications/hr/time_off.rst:596
msgid ""
"To display time off requests for specific departments, click on the "
"department on the left-hand side. Only requests within the selected "
"department are then presented."
msgstr ""

#: ../../content/applications/hr/time_off.rst:602
msgid ""
"The :guilabel:`To Approve` requests are highlighted in yellow, and are the "
"only ones that appear in the list by default. If the :guilabel:`To Approve` "
"filter is removed, then all statuses appear. :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.rst:607
msgid ""
"To approve a time off request, click :guilabel:`👍 Approve` at the end of the"
" line, to refuse a request, click :guilabel:`✖️ Refuse`."
msgstr ""

#: ../../content/applications/hr/time_off.rst-1
msgid ""
"Time off requests with the filter, groupings, and status sections "
"highlighted."
msgstr ""

#: ../../content/applications/hr/time_off.rst:614
msgid ""
"If more details are needed, click anywhere on the time off request line "
"(except for :guilabel:`👍 Approve` and :guilabel:`✖️ Refuse`) to load the "
"time off request form. Depending on the rights of the user, changes can be "
"made."
msgstr ""

#: ../../content/applications/hr/time_off.rst:618
msgid ""
"To modify the request, click the :guilabel:`Edit` button, make any desired "
"changes, then click :guilabel:`Save`."
msgstr ""

#: ../../content/applications/hr/time_off.rst:621
msgid ""
"It is also possible to approve or refuse the request from this form. Click "
"the :guilabel:`Approve` button to approve, or the :guilabel:`Refuse` button "
"to refuse the request."
msgstr ""

#: ../../content/applications/hr/time_off.rst:625
#: ../../content/applications/hr/time_off.rst:676
msgid "My time off"
msgstr ""

#: ../../content/applications/hr/time_off.rst:627
msgid ""
"The :guilabel:`My Time Off` section of the *Time Off* application contains "
"the time off dashboard, as well as the user's time off requests and "
"allocations."
msgstr ""

#: ../../content/applications/hr/time_off.rst:633
msgid "Dashboard"
msgstr ""

#: ../../content/applications/hr/time_off.rst:635
msgid ""
"All users have access to the time off dashboard, which is the default view "
"in the *Time Off* application. The dashboard can also be accessed at any "
"point in the application by navigating to :menuselection:`Time Off app --> "
"My Time Off --> Dashboard`."
msgstr ""

#: ../../content/applications/hr/time_off.rst:639
msgid ""
"The current year is displayed, and the current day is highlighted in red."
msgstr ""

#: ../../content/applications/hr/time_off.rst:641
msgid ""
"To change the view, click on the desired button at the top. The options are "
":guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` "
"(the default)."
msgstr ""

#: ../../content/applications/hr/time_off.rst:644
msgid ""
"To change the presented dates, click the left and right arrows on either "
"side of the :guilabel:`Today` button. The calendar view adjusts in "
"increments of the presented view."
msgstr ""

#: ../../content/applications/hr/time_off.rst:647
msgid ""
"For example, if :guilabel:`Week` is selected, the arrows adjust the view by "
"one week."
msgstr ""

#: ../../content/applications/hr/time_off.rst:649
msgid ""
"To change the view at any point to a view that includes the current date, "
"click the :guilabel:`Today` button."
msgstr ""

#: ../../content/applications/hr/time_off.rst:652
msgid ""
"Above the calendar view is a summary of the users 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.rst:657
msgid ""
"The legend on the right side of the calendar view displays the various time "
"off types, with their corresponding colors. The status of the time off "
"requests are shown as well."
msgstr ""

#: ../../content/applications/hr/time_off.rst:660
msgid ""
"Time off that has been validated appears in a solid color (in the color "
"specified in the Time Off Types part of the legend). Time off requests that "
"still need to be approved appear with white stripes in the color. Refused "
"time off requests have a colored line through the dates."
msgstr ""

#: ../../content/applications/hr/time_off.rst:664
msgid ""
"New time off requests can be made from the dashboard. Click the "
":guilabel:`New Time Off` button at the top of the dashboard, and a new "
":ref:`time off form <time_off/request-time-off>` appears."
msgstr ""

#: ../../content/applications/hr/time_off.rst:667
msgid ""
"New allocation requests can also be made from the dashboard. Click the "
":guilabel:`Allocation Request` button at the top of the dashboard to request"
" more time off, and a new :ref:`allocation form <time_off/request-"
"allocation>` appears."
msgstr ""

#: ../../content/applications/hr/time_off.rst-1
msgid ""
"Time off dashboard view with the legend, time off summaries, and view "
"buttons highlighted."
msgstr ""

#: ../../content/applications/hr/time_off.rst:678
msgid ""
"To view a list of all the user's time off requests, navigate to "
":menuselection:`Time Off app --> My Time Off --> My Time Off`. Here, all "
"time off requests appear in a list view, both past and present."
msgstr ""

#: ../../content/applications/hr/time_off.rst:682
msgid ""
"Other than the employee's name, 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 the "
":guilabel:`Status`."
msgstr ""

#: ../../content/applications/hr/time_off.rst:686
msgid ""
"A new time off request can be made from this view. Click the "
":guilabel:`Create` button to :ref:`request time off <time_off/request-time-"
"off>`."
msgstr ""

#: ../../content/applications/hr/time_off.rst:690
msgid "My allocations"
msgstr ""

#: ../../content/applications/hr/time_off.rst:692
msgid ""
"To view a list of all the users allocations, navigate to "
":menuselection:`Time Off app --> My Time Off --> My Allocations`. All "
"allocations and requested allocations appear in a list view."
msgstr ""

#: ../../content/applications/hr/time_off.rst:695
msgid ""
"The information presented includes: the :guilabel:`Time Off Type`, "
":guilabel:`Description`, :guilabel:`Duration`, :guilabel:`Allocation Type`, "
"and the :guilabel:`Status`."
msgstr ""

#: ../../content/applications/hr/time_off.rst:698
msgid ""
"A new allocation request can be made from this view, as well. Click the "
":guilabel:`Create` button to :ref:`request an allocation <time_off/request-"
"allocation>`."
msgstr ""

#: ../../content/applications/hr/time_off.rst:704
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:709
msgid "By employee"
msgstr ""

#: ../../content/applications/hr/time_off.rst:711
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:714
msgid ""
"The default report is a stacked bar chart with the filters of "
":guilabel:`Active Employee` and :guilabel:`Type` in place."
msgstr ""

#: ../../content/applications/hr/time_off.rst:717
msgid ""
"Each employee is displayed in their own column, with the bar displaying how "
"many days of each type of time off type they requested."
msgstr ""

#: ../../content/applications/hr/time_off.rst:720
msgid ""
"The report can be displayed in other ways. Click the various options at the "
"top of the report to view the data differently."
msgstr ""

#: ../../content/applications/hr/time_off.rst:723
msgid ""
"The graph options are :guilabel:`Bar Chart`, :guilabel:`Line Chart`, or "
":guilabel:`Pie Chart`. The :guilabel:`Bar Chart` includes an option to "
"present the data :guilabel:`Stacked`. Both the :guilabel:`Bar Chart` and "
":guilabel:`Line Chart` have options to present the data in either "
":guilabel:`Descending` or :guilabel:`Ascending` order."
msgstr ""

#: ../../content/applications/hr/time_off.rst-1
msgid "Report of time off, shown by each employee in a stacked bar chart."
msgstr ""

#: ../../content/applications/hr/time_off.rst:733
msgid "By type"
msgstr ""

#: ../../content/applications/hr/time_off.rst:735
msgid ""
"To view a list of approved time off, organized by time off type, navigate to"
" :menuselection:`Time Off app --> Reporting --> by Type`. This shows each "
"time off type in its own section."
msgstr ""

#: ../../content/applications/hr/time_off.rst:738
msgid ""
"Click on a time off type to expand the list. 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:742
msgid ""
"The default filters in place for this report are :guilabel:`Approved "
"Requests`, :guilabel:`Active Employee`, the :guilabel:`Current Year`, and "
"the :guilabel:`Type`."
msgstr ""

#: ../../content/applications/hr/time_off.rst-1
msgid "Report of time off by type, with each request detailed in the list."
msgstr ""