msgid "**Odoo Attendances** functions as a time clock. Employees check in and check out of work, while managers can see who is available at any given time."
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."
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."
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>`_."
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."
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."
msgid "When a new employee is hired, the first step is to create a new employee record. Starting in the :menuselection:`Employees` app dashboard, click the :guilabel:`New` button and a new employee form appears. Fill out the required information and any additional details."
msgid "The employee form automatically saves as data is entered, but the save manually icon (a could with an up arrow inside it) may be clicked at any time to manually save the form."
msgid ":guilabel:`Company`: Select the company from the drop-down menu that the new employee is hired by, or create a new company by typing the name in the field."
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."
msgid ":guilabel:`Job Position`: Enter the employee's job position title under their name, or select the job position from the :guilabel:`Job Position` drop-down menu to have this 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."
msgid "It is recommended to have the job positions match, but if desired, the typed-in description in this field can contain more information than the selected drop-down job position."
msgid "An example where this may be applicable is if someone is hired for a sales representative position configured as :guilabel:`Sales Representative` in the *Recruitment* app, and that is selected for the drop-down :guilabel:`Job Position` field."
msgid "In the typed in job position field beneath the employee's name, the position could be more specific, such as `Sales Representative - Subscriptions` if the employee is focused solely on subscription sales."
msgid "Tags: Click on a tag in the drop-down menu to add any tags applicable 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."
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 employee's name 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."
msgid ":guilabel:`Next Appraisal Date`: This 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."
msgid "After a :guilabel:`Manager` is selected, if the :guilabel:`Coach` field is blank, the selected manager automatically populates the :guilabel:`Coach` field."
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."
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."
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 \"(new entry)\"`."
msgid ":guilabel:`Date Start` and :guilabel:`Date End`: Enter the start and end dates for the work experience. To select a date, use the :guilabel:`< (left)` and :guilabel:`> (right)` arrow icons to scroll to the desired month, then click on the day to select it."
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."
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*."
msgid "An employee's skills can be entered in the :guilabel:`Resumé` tab in the same manner that a resumé line is created. When creating a skill for the first time, click the :guilabel:`Create a new entry` button under :guilabel:`Skills` and a :guilabel:`Create Skills` form appears. After a skill is added, the :guilabel:`Create a new entry` button is replaced with an :guilabel:`Add` button. Enter the following information for each skill."
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)\"`."
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."
msgid "Once all the information is entered, 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 create a new entry."
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."
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. 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 skill types needed."
msgid ":guilabel:`Levels`: Click :guilabel:`Add a line` and a :guilabel:`Create Levels` form appears. Enter the name of the level, and assign a number for the :guilabel:`Progress` percentage (0-100) for that level. Click :guilabel:`Save & New` to save the entry and add another level, or click :guilabel:`Save & Close` to save the level and close the form. Once all the levels are entered, click the :guilabel:`Save manually` icon at the top of the screen. Next, select a default level for this skill type. Click :guilabel:`Set Default` on the line to be the default value. This is typically the lowest level, but any level can be set as the default. A check mark appears in the :guilabel:`Default Level` column, indicating which level is the default."
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. Then, click :guilabel:`Save & Close`, then click the :guilabel:`Save manually` icon at the top. Last, click :guilabel:`Set Default` on the `Beginner` line to set this as the default skill level."
msgid "The Work Information tab is where the employee's specific job related information is housed. Their working schedule, various roles, who approves their specific requests (time off, timesheets, and expenses), and specific work location details are listed here. Click on the :guilabel:`Work Information` tab to access this section, and enter the following information for the new employee."
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. Use the breadcrumb menu to navigate back to the new employee form when done. 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."
msgid ":guilabel:`Approvers`: In order to see this section, the user must have either :guilabel:`Administrator` or :guilabel:`Officer: Manage all employees` rights set for the :guilabel:`Employees` application. Using the drop-down menus, select the users responsible for approving :guilabel:`Expenses`, :guilabel:`Time Off`, and :guilabel:`Timesheets` for the employee. Hover over any of the selections to reveal the :guilabel:`Internal Link` arrow. 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. Use the breadcrumb menu to navigate back to the new employee form when done."
msgid ":guilabel:`Homeworking`: Using the drop-down menu, select the specific location the employee will work from, for each day of the week. The default options are :guilabel:`Home`, :guilabel:`Office`, or :guilabel:`Other`. 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. After edits are done, click :guilabel:`Save & Close`, and the new location is added, and populates the field. For days the employee does not work, for example, Saturday and Sunday, leave the field blank (:guilabel:`Unspecified`)."
msgid "It is also possible to add or modify work locations by navigating to :menuselection:`Employees app --> Configuration --> Employee: Work Locations`. Click :guilabel:`New` to create a new location, then enter the details on the form. To modify a location, click on an existing location, then make any changes on the form."
msgid ":guilabel:`Schedule`: Select the :guilabel:`Working Hours` and :guilabel:`Timezone` for the employee. The :guilabel:`Internal Link` arrow opens up a detailed view of the specific daily working hours. Working hours can be modified or deleted here."
msgid "Working hours can also be modified in the *Payroll* application, where they are referred to as :guilabel:`Working Schedules`. For more information on how to create or modify :guilabel:`Working Schedules` in Payroll, refer to the :doc:`../../hr/payroll` documentation."
msgid ":guilabel:`Planning`: Click on a role from the drop-down menu for both the :guilabel:`Roles` and the :guilabel:`Default Role` fields to add a role. There is no limit to the amount of :guilabel:`Roles` that can be selected for an employee, but there can only be one :guilabel:`Default Role`. The default role is the *typical* role that the employee performs, where the :guilabel:`Roles` are *all* the specific roles the employee is able to perform. The :guilabel:`Default Role` must be selected as a :guilabel:`Role`, if not, when the :guilabel:`Default Role` is selected, that role is automatically added to the list of :guilabel:`Roles`."
msgid "The :guilabel:`Planning` section affects the *Planning* app, and will only appear if the *Planning* app is installed. When planning work in the *Planning* app, employees can only be scheduled for specific work that corresponds to their selected roles. For example, only an employee with a *Functional Tester* role can be assigned to perform any activity that requires a *Functional Tester*."
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. 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."
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."
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."
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."
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."
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. To add or modify a working time, go to the :menuselection:`Payroll app --> Configuration --> Working Times`, and add a new working time or edit an existing one."
msgid "After the new working time is created, or an existing one is modified, select the employee's working hours using the drop-down menu in the :guilabel:`Schedule` section of the :guilabel:`Work Information` tab."
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."
msgid "Here, the employee's :guilabel:`Private Contact`, :guilabel:`Education`, :guilabel:`Work Permit`, :guilabel:`Family Status`, :guilabel:`Emergency` contact, and :guilabel:`Citizenship` information is entered. Fields are entered either using a drop-down menu, activating a check box, or typing in the information."
msgid ":guilabel:`Private Contact`: Enter the personal :guilabel:`Address` for the employee. The selection can be made with the drop-down menu. If the information is not available, type in the name for the new address. To edit the new address, click the :guilabel:`Internal Link` arrow to open the address form. On the address form, enter or edit the necessary details. Some other information in the :guilabel:`Private Contact` section may auto-populate, if the address is already listed in the drop-down menu."
msgid "Enter the employee's :guilabel:`Email` address and :guilabel:`Phone` number in the respective fields. Next, enter the employee's :guilabel:`Bank Account Number` using the drop-down menu. 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 information, then click :guilabel:`Save & Close`."
msgid "Then, select the employee's preferred :guilabel:`Language` from the drop-down menu. Next, enter the :guilabel:`Home-Work Distance` in the field. This field is only necessary if the employee is receiving any type of commuter benefits. Lastly, enter the employee's license plate information in the :guilabel:`Private Car Plate` field."
msgid ":guilabel:`Education`: Select the highest level of education completed by the employee from the :guilabel:`Certificate Level` drop-down menu. Options include :guilabel:`Graduate`, :guilabel:`Bachelor`, :guilabel:`Master`, :guilabel:`Doctor`, or :guilabel:`Other`. Type in the :guilabel:`Field of Study`, and the name of the :guilabel:`School` in the respective fields."
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. Using the calendar selector, select the :guilabel:`Visa Expire Date` and/or the :guilabel:`Work Permit Expiration Date` to enter the expiration date(s). If available, upload a digital copy of the work permit document. Click :guilabel:`Upload Your File`, navigate to the work permit file in the file explorer, and click :guilabel:`Open`."
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."
msgid ":guilabel:`Emergency`: Type in the :guilabel:`Contact Name` and :guilabel:`Contact Phone` number of the employee's emergency contact in the respective fields."
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. 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. Type in the information for the :guilabel:`Identification No` (identification number, :guilabel:`Passport No` (passport number), and :guilabel:`Place of Birth` fields. Last, if the employee is not a resident of the country they are working in, activate the check box next to the :guilabel:`Non-resident` field."
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."
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`."
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. After the :guilabel:`User` is created and saved, the new user will appear in the :guilabel:`Related User` field."
msgid "After the employee is created, create the user. Click the :guilabel:`⚙️ (gear)` icon, then click :guilabel:`Create User`. A :guilabel:`Create User` form appears. Type in the :guilabel:`Name` and :guilabel:`Email Address`, and then select the :guilabel:`Company` from the drop-down menu. Click :guilabel:`Save` after the information is entered, and the employee record is automatically updated with the newly created user populating the :guilabel:`Related User` field."
msgid ":guilabel:`Payroll`: If applicable, enter the :guilabel:`Registration Number of the Employee` in this section. The :guilabel:`Attestation (N-1)` and :guilabel:`Attestation (N)` sections appear only for Belgian companies, and will not be visible for other locations. These sections log the days that will be paid to the new employee. Enter any :guilabel:`Amount to recover`, :guilabel:`Number of days`, and :guilabel:`Recovered Amount` of :guilabel:`Holiday Attest (year) - Simple Holiday Pay from previous employer to recover in (year)`, for both N and N-1 categories. For the :guilabel:`Holiday Attest (year) - Previous occupation for Double Holiday Pay Recovery in (year)` section, click :guilabel:`Add a line`, and enter the number of :guilabel:`Months`, the :guilabel:`Amount`, and :guilabel:`Occupation Rate`. Repeat for all entries. Click the :guilabel:`🗑️ (trash can)` icon to delete a line."
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. The :guilabel:`PIN Code` is used to sign in and out of the *Attendance* app kiosk, and a :abbr:`POS (Point Of Sale)` system."
msgid ":guilabel:`Application Settings`: Enter the employee's :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>`. This value affects the manufacturing costs for a product, if the value of the manufactured product is not a fixed amount. This value does not affect the *Payroll* application. If applicable, enter the :guilabel:`Fleet Mobility Card` number."
msgid "All documents associated with an employee are stored in the :guilabel:`Documents` app. The number of documents associated with the employee appear in the :guilabel:`Documents` smart button above the employee record. Click on the smart button, and all the documents appear. For more information on the :guilabel:`Documents` app, refer to the :doc:`../../productivity/documents` documentation."
msgid "This document outlines all of the configurations and settings for the *Fleet* application, including :ref:`settings <fleet/settings>`, :ref:`manufacturers <fleet/manufacturers>`, :ref:`vehicle models <fleet/models>`, and :ref:`model categories <fleet/categories>`."
msgid "To access the settings menu, go to :menuselection:`Fleet application --> Configuration --> Settings`. There are only two settings that need configuration, the vehicle contract end date alert delay, and a new vehicle request limit."
msgid "The :guilabel:`End Date Contract Alert` field defines an alert delay for the persons responsible for vehicle contracts. The responsible person(s) will receive an email informing them a vehicle contract is about to expire in the number of days defined in this field."
msgid "To determine who the responsible person is for a contract, open an individual contract. The person listed as :guilabel:`Responsible` under the :guilabel:`Contract Information` section of the contract is the person who will receive the alert."
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."
msgid "An individual contract can also be found by navigating to :menuselection:`Fleet app --> Fleet --> Fleet` and clicking on an individual vehicle. On the vehicle form, click the :guilabel:`Contracts` smart button at the top of the page. The contract(s) associated with this vehicle only appears in the list. Click on an individual contract to open it. The :guilabel:`Responsible` person is listed on the contract."
msgid "The :guilabel:`New Vehicle Request` field sets a limit on how many new vehicles are requested based on fleet availability. An employee filling out the salary configurator form (after being offered a position), will *not* be able to request a new car if the number of existing cars is greater than the number specified in the :guilabel:`New Vehicle Request` field. Enter the specific number limit for existing available cars in this field."
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."
msgid "Odoo *Fleet* comes pre-configured with sixty-six commonly used car and bicycle manufacturers in the database, along with their logos. To view the pre-loaded manufacturers, go to :menuselection:`Fleet app --> Configuration --> Manufacturers`."
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 six pre-configured :ref:`models <fleet/models>` from four major auto manufacturers and one major bicycle manufacturer: Audi, BMW, Mercedes, Opel (cars), and Eddy Merckx (bicycle)."
msgid "To add a new manufacturer to the database, click :guilabel:`Create`. A manufacturer form will load. Only two pieces of information are needed, the :guilabel:`Name` of the manufacturer, and the logo. Type the name of the manufacturer in the name field, and select an image to upload for the logo. When the information is entered, click :guilabel:`Save`."
msgid "Many manufacturers have a variety of models that they produce. When adding a vehicle to the fleet, it is important to specify the vehicle model being added. Odoo comes with pre-configured car models from four major auto manufacturers, and one pre-configured bicycle model from one bicycle manufacturer: Audi, BMW, Mercedes, Opel (cars), and Eddy Merckx (bicycle). If a vehicle *other* than the pre-configured models from these manufacturers are part of a fleet, the model (and/or manufacturer) needs to be added to the database."
msgid "New vehicle models can easily be added to the database. To add a new model, navigate to :menuselection:`Fleet app --> Configuration --> Vehicle Models`. Click :guilabel:`Create` and a vehicle model form will load. Enter the following information on the form, then click :guilabel:`Save`. Be advised, some fields are specific to Belgian based companies, so not all fields or sections may be visible depending on the location of the company."
msgid ":guilabel:`Manufacturer`: select the manufacturer from the drop-down menu. If the manufacturer is not configured, type in the manufacturer and then click :guilabel:`Create` or :guilabel:`Create & Edit`."
msgid ":guilabel:`Vehicle Type`: select one of two preconfigured vehicle types, either :guilabel:`Car` or :guilabel:`Bike`, from the drop-down menu. The vehicle types are hardcoded in Odoo and are integrated with the *Payroll* application since vehicles can be part of an employee's benefits. Adding additional vehicle types is not possible as it will affect payroll."
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 and then click :guilabel:`Create (new category)`."
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.)`."
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."
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."
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. 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. 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."
msgid ":guilabel:`Total Cost (Depreciated)`: this value is the :guilabel:`Cost (Depreciated)` and the :guilabel:`C02 fee` fields combined, and also is depreciated over time."
msgid ":guilabel:`Fuel Type`: select the type of fuel the vehicle uses form the drop-down menu. The options are :guilabel:`Diesel`, :guilabel:`Gasoline`, :guilabel:`Hybrid Diesel`, :guilabel:`Hybrid Gasoline`, :guilabel:`Plug-in Hybrid Diesel`, :guilabel:`Plug-in Hybrid Gasoline`, :guilabel:`CNG`, :guilabel:`LPG`, :guilabel:`Hydrogen`, or :guilabel:`Electric`."
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."
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."
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."
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 used by the *Purchase* app."
msgid "The vendor(s) the vehicle can be purchased from may be added in this tab. To add a vendor, click :guilabel:`Add`, and a pop-up loads with a list of all the vendors currently in the database. Select the vendor to add by clicking the checkbox next to the vendor name, then click :guilabel:`Select`. There is no limit to the number of vendors that can be added to this list."
msgid "If a vendor is not in the database, add a vendor by clicking :guilabel:`Create`. A vendor form will load. Enter the information in the vendor tab, 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."
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. Model categories are set on the :ref:`vehicle model form <fleet/add-model>`."
msgid "To view all the models currently set up, navigate to :menuselection:`Fleet application --> Configuration --> Model Category`. All models are displayed in a list view."
msgid "To add a new category, click :guilabel:`Create`. A new entry line appears at the bottom of the list. Type in the new category, then click :guilabel:`Save` to save the entry."
msgid "To reorganize how the categories appear in the list, click on the up and down arrows 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."
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`."
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`."
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`."
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."
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."
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`."
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."
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`."
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."
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."
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."
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."
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."
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."
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)`."
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`."
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."
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`."
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."
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."
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."
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."
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."
msgid ":guilabel:`Catalog Value (VAT Incl.)`: enter the MSRP (Manufacturer's Suggested Retail Price) for the vehicle at the time of purchase or lease."
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."
msgid "If the model for the new vehicle is already configured in the database, the :guilabel:`Model` tab will be populated with the corresponding information. If the model is not already in the database and the :guilabel:`Model` tab needs to be configured, :ref:`configure the new vehicle model <fleet/add-model>`."
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."
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."
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`."
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."
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."
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."
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."
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."
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."
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."
msgid ":guilabel:`Stage`: the status of the service or repair. Options are :guilabel:`New`, :guilabel:`Running`, :guilabel:`Canceled`, or :guilabel:`Done`."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
msgid "Odoo *Payroll* is used to process work entries and create payslips for employees, including both regular pay and commission. Payroll works in conjunction with other Odoo apps, such as *Employees*, *Timesheets*, *Time Off*, and *Attendances*."
msgstr ""
#: ../../content/applications/hr/payroll.rst:12
msgid "The *Payroll* app helps ensure there are no issues or conflicts when validating work entries, handles country-specific localizations to ensure that payslips follow local rules and taxes, and allows for salary assignments. Payroll configuration is critical to ensure accurate and timely processing of payslips."
msgstr ""
#: ../../content/applications/hr/payroll.rst:20
msgid "To access the *Settings*, go to :menuselection:`Payroll --> Configuration --> Settings`. Whether or not payslips are posted in accounting, and whether SEPA payments are created, is selected here."
msgstr ""
#: ../../content/applications/hr/payroll.rst:23
msgid "The :guilabel:`Settings` screen is where localization settings are configured. *Localizations* are country-specific settings pre-configured in Odoo at the creation of the database, and account for all taxes, fees, and allowances for that particular country. The :guilabel:`Localization` section of the :guilabel:`Settings` includes a detailed view of all benefits provided to employees."
msgstr ""
#: ../../content/applications/hr/payroll.rst:-1
msgid "Settings available for Payroll."
msgstr ""
#: ../../content/applications/hr/payroll.rst:32
msgid "Any country-specific localizations are set up in the :guilabel:`Localization` section of the :guilabel:`Settings` screen. All localization items are pre-populated when the country is specified during the creation of the database. It is not recommended to alter the localization settings unless specifically required."
msgstr ""
#: ../../content/applications/hr/payroll.rst:38
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 setup as their own company/branch using the multi-company method."
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. For more information on companies refer to :doc:`this documentation <../general/companies>` on setting up companies."
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:59
msgid ":doc:`Manage work entries <payroll/work_entries>`"
msgstr ""
#: ../../content/applications/hr/payroll.rst:62
msgid "Work entry types"
msgstr ""
#: ../../content/applications/hr/payroll.rst:64
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:69
msgid "To view the current work entry types available, go to :menuselection:`Payroll --> Configuration --> Work Entries --> Work Entry Types`."
msgstr ""
#: ../../content/applications/hr/payroll.rst:72
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:80
msgid "New work entry type"
msgstr ""
#: ../../content/applications/hr/payroll.rst:82
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:86
msgid "General information section"
msgstr ""
#: ../../content/applications/hr/payroll.rst:88
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:90
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:93
msgid ":guilabel:`DMFA code`: This code is used to identify :abbr:`DMFA (De Multifunctionele Aangifte)` entries on a corresponding DMFA report. The DMFA 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:97
msgid ":guilabel:`External Code`: This code is used for exporting data to a third-party payroll service. Check with the third-party being used in order to determine the :guilabel:`External Code` to enter for the new work entry type."
msgstr ""
#: ../../content/applications/hr/payroll.rst:100
msgid ":guilabel:`SDWorx code`: This code is only for companies that use SDWorx, a payroll service provider."
msgstr ""
#: ../../content/applications/hr/payroll.rst:102
msgid ":guilabel:`Color`: Select a color for the particular work entry type."
msgstr ""
#: ../../content/applications/hr/payroll.rst:105
msgid "Display in payslip section"
msgstr ""
#: ../../content/applications/hr/payroll.rst:107
msgid ":guilabel:`Rounding`: The rounding method selected determines how quantities on timesheet entries are displayed on the payslip."
msgstr ""
#: ../../content/applications/hr/payroll.rst:110
msgid ":guilabel:`No Rounding`: A timesheet entry is not modified."
msgstr ""
#: ../../content/applications/hr/payroll.rst:111
msgid ":guilabel:`Half Day`: A timesheet entry is rounded to the closest half day amount."
msgstr ""
#: ../../content/applications/hr/payroll.rst:112
msgid ":guilabel:`Day`: A timesheet entry is rounded to the closest full day amount."
msgstr ""
#: ../../content/applications/hr/payroll.rst:115
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:121
msgid "Unpaid section"
msgstr ""
#: ../../content/applications/hr/payroll.rst:123
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:129
msgid "Valid for advantages section"
msgstr ""
#: ../../content/applications/hr/payroll.rst:131
msgid ":guilabel:`Meal Voucher`: If the work entry should count towards a meal voucher, check the box."
msgstr ""
#: ../../content/applications/hr/payroll.rst:132
msgid ":guilabel:`Representation Fees`: If the work entry should count towards representation fees, check the box."
msgstr ""
#: ../../content/applications/hr/payroll.rst:134
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:138
msgid "Time off options section"
msgstr ""
#: ../../content/applications/hr/payroll.rst:140
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. 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. 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:146
msgid ":guilabel:`Keep Time Off Right`: This is for Belgian-specific companies only, and will not appear for other localizations. Check this box if the work entry is for time off that will affect 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 will receive or accrue the following year."
msgstr ""
#: ../../content/applications/hr/payroll.rst:153
msgid "Reporting section"
msgstr ""
#: ../../content/applications/hr/payroll.rst:155
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."
msgid "To view the currently configured working schedules, go to :menuselection:`Payroll --> Configuration --> Work Entries --> Working Schedules`. The working schedules that are available for an employee's contracts and work entries are found in this list."
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."
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."
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."
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`."
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)."
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."
msgid "There are two default structure types configured in Odoo: *Employee* and *Worker*. Typically, *Employee* is used for salaried employees, which is why the wage type is *Monthly Fixed Wage*, and *Worker* is typically used for employees paid by the hour, so the wage type is *Hourly Wage*."
msgstr ""
#: ../../content/applications/hr/payroll.rst:-1
msgid "List of all currently configured structure types available to use."
msgid "To make a new structure type, click the :guilabel:`New` button and a structure type form appears. Enter the information in the fields. Most fields are pre-populated, but all the fields can be modified."
msgid ":guilabel:`Wage Type`: Select what type of wage the new structure type will use, either :guilabel:`Monthly Fixed Wage` or :guilabel:`Hourly Wage`. If the wage type is going to be used for salaried employees who receive the same wage every pay period, select :guilabel:`Monthly Fixed Wage`. If the wage type is going to be used for employees who receive wages based on how many hours they worked during a pay period, select :guilabel:`Hourly Wage`."
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 type of structure type is paid out."
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>`."
msgid ":guilabel:`Default Work Entry Type`: Select the default type of work entry the new structure type will fall under from the drop-down menu. 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`, and :guilabel:`Out Of Contract`."
msgstr ""
#: ../../content/applications/hr/payroll.rst:-1
msgid "New structure type form to fill out when creating a new structure type."
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 will pop 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 filled out, click :guilabel:`Save & Close`."
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`."
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 shard between companies. Each company needs to have their own working hours set."
msgid ":guilabel:`Average Hour Per Day`: The average hours per day field will be auto-populated based on the working hours configured in the *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."
msgid ":guilabel:`Company Full Time`: Enter the number of hours per week an employee would need to work in order 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)."
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 *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."
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 working hours tab is pre-populated with a default 40-hour week, with each day divided into three timed sections. 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. 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."
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 will change the working hours tab to display two weeks of working times that can be adjusted."
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`."
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."
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."
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."
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 will affect accounting reports and payroll processing."
msgid ":guilabel:`Condition Based on`: In the :guilabel:`General` tab, 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)."
msgid ":guilabel:`Amount Type`: In the :guilabel:`General` tab, 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."
msgstr ""
#: ../../content/applications/hr/payroll.rst:-1
msgid "Enter the information for the new rule on the new rule form."
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."
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 going to :menuselection:`Payroll --> 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"
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."
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."
msgid "The various options under the :guilabel:`Salary Package Configurator` section of the :menuselection:`Payroll --> Configuration --> Salary Package Configurator` menu all affect an employee's potential salary. These sections (:guilabel:`Advantages`, :guilabel:`Personal Info`, :guilabel:`Resume`, and :guilabel:`Offers`) specify what benefits can be offered to an employee in their salary package."
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."
msgid "When offering potential employees a position, there can be certain *advantages* or 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.)."
msgid "To see the advantages, go to :menuselection:`Payroll --> Configuration --> Salary Package Configurator --> Advantages`. Advantages are grouped by :guilabel:`Structure type`, and the advantage 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 advantages or benefits that is available for each structure type."
msgid "A company has two structure types, one labeled :guilabel:`Employee`, and anther labeled :guilabel:`Intern`. The :guilabel:`Employee` structure type contains an advantage of using a company car, while the :guilabel:`Intern` structure type does not. Instead, the :guilabel:`Intern` structure type has a meal voucher advantage available, while the :guilabel:`Employee` structure type does not."
msgid "A person hired under the :guilabel:`Employee` structure type can use a company car, but cannot have meal vouchers. The opposite is true for someone hired under the :guilabel:`Intern` structure type. They would have meal vouchers available to them, not the use of a company car."
msgid ":guilabel:`Advantage Type`: Select from the drop-down menu what type of advantage the benefit is. Select from :guilabel:`Monthly Benefit in Kind`, :guilabel:`Monthly Advantages in Net`, :guilabel:`Monthly Advantages in Cash`, or :guilabel:`Yearly Advantages in Cash`."
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."
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."
msgid "The *Personal Information* section lists all of the fields that are available to enter on the employee's card. To access this section, go to :menuselection:`Payroll --> Configuration --> Salary Package Configurator --> Personal Info`."
msgstr ""
#: ../../content/applications/hr/payroll.rst:-1
msgid "A list of all the personal information that appears on employee card to enter."
msgid "To edit a personal info entry, select the entry from the list, and modify the personal info. To create a new personal info entry, click the :guilabel:`New` button."
msgid "The required fields, aside from entering the :guilabel:`Information` name, are :guilabel:`Related Model`, :guilabel:`Related Field`, and :guilabel:`Category`. 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. 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 going to be stored in the backed. 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`."
msgid "The two most important fields on the personal info form are :guilabel:`Is Required` and :guilabel:`Display Type`. 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, from a :guilabel:`Text` box, to a customizable :guilabel:`Radio` button, a :guilabel:`Checkbox`, a :guilabel:`Document`, and more."
msgid "Currently, the :guilabel:`Resume` feature found inside the :menuselection:`Payroll app --> Configuration --> Salary Package Configurator --> Resume` 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."
msgid "When a candidate is offered a position, there are several items that need to be tracked in order for a business to stay organized, such as where in the offer process the candidate is, how long the offer is valid for, as well as all the offer details. These details are all stored in each *offers* record."
msgid "To view all offers, go to :menuselection:`Payroll --> Configuration --> Salary Package Configurator --> Offers`. All offers that have been sent to either potential candidates or current employees appears in this list. The status, offer start date and expiration date, amount of the contract, and more, can all be found in this list. Offers sent via the :guilabel:`Recruitment` application appear here, but there is an option to create a new offer from the :guilabel:`Payroll` application as well."
msgstr ""
#: ../../content/applications/hr/payroll.rst:-1
msgid "A list of all offers given to a current employee or potential candidate along with the\n"
msgid "To create a new offer, click the :guilabel:`New` button. The two required fields are the :guilabel:`Contract Template`, and the :guilabel:`Company`. Select the :guilabel:`Contract Template` and :guilabel:`Company` from the drop-down menus. Fill in any other details for the offer, such as the :guilabel:`Job Title`, :guilabel:`Department`, the :guilabel:`Contract Start Date` and the :guilabel:`Offer Validity Date`."
msgid "Every employee in Odoo is required to have a contract in order to be paid. A contract outlines the terms of an employee's position, their compensation, working hours, and any other details about their position."
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."
msgid "To view the employee contracts, go to the :menuselection:`Payroll app --> Contracts --> Contracts` from the top menu. All employee contracts, and their current contract status, are displayed in a Kanban view, by default. The Kanban view displays running contracts, contracts that require action, expired contracts, and cancelled contracts."
msgid "In order for an employee to be paid, an active contract is required. If a new contract is needed, click the :guilabel:`Create` button on the :guilabel:`Contracts` dashboard. A contract form appears where the information can be entered. Required fields are underlined in bold."
msgid ":guilabel:`Contract Start Date`: the date the contract starts. Choose a date by clicking on the drop-down menu, navigating to the correct month and year by using the :icon:`fa-chevron-left` :icon:`fa-chevron-right` :guilabel:`(arrow)` icons, then clicking on the desired date. This field is **required**."
msgid ":guilabel:`Contract End Date`: the date the contract ends. Choose a date by clicking on the drop-down menu, navigating to the correct month and year by using the :icon:`fa-chevron-left` :icon:`fa-chevron-right` :guilabel:`(arrow)` icons, then clicking on the desired date. This field is **required**."
msgid ":guilabel:`Salary Structure Type`: select one of the salary structure types from the drop-down menu. The default salary structure types are :guilabel:`Employee` or :guilabel:`Worker`. A new salary structure type can be created by typing the name in the field. This field is **required**."
msgid ":guilabel:`HR Responsible`: if there is a specific person in HR that is responsible for the contract, select the person from the drop-down menu. This field is required."
msgid "The :guilabel:`Working Schedule` drop-down menu displays all the working times for the selected :guilabel:`Company`. To modify or add to this list, go to :menuselection:`Payroll app --> Configuration --> Working Times`, and either :guilabel:`Create` a new working time, or click on an existing working time, then edit it by clicking :guilabel:`Edit`."
msgid "The :guilabel:`Contract Details` tab allows for the addition and editing of a contract, along with specifying which template to use when a new contract is created. These fields **must** be populated in order to create a new contract."
msgid "To access the various contract template fields in the :guilabel:`Contract Details` tab, the *Salary Configurator* (`hr_contract_salary`) module **must** be :ref:`installed <general/install>`."
msgid "When the *Salary Configurator* module is installed, the *Salary Configurator - Holidays* and *Salary Configurator - Payroll* modules install, as well."
msgid ":guilabel:`Contract Template`: select a pre-existing contract template from the drop-down menu. Contract templates are typically created through the *Recruitment* application."
msgid ":guilabel:`Contract Update Document Template`: select a contract from the drop-down menu, if the employee has an existing contract that requires updating."
msgid "Click the :icon:`fa-external-link` :guilabel:`(external Link)` icon at the end of either the :guilabel:`New Contract Document Template` or :guilabel:`Contract Update Document Template` to open the corresponding contract template, and proceed to make any desired changes."
msgid ":guilabel:`Signed Document Workspace`: this is where the signatures are stored. Choose a pre-configured workspace, or create a new one. To create a new :guilabel:`Signed Document Workspace`, type in the name of the workspace, then click either :guilabel:`Create` to add the new workspace, or :guilabel:`Create and Edit` to add the workspace and modify the workspace details."
msgid ":guilabel:`Signed Document Tags`: select or create any tags that are only associated with the signed contract, as opposed to the original unsigned contract."
msgid ":guilabel:`Redirect Link`: enter a redirect link for the employee to access the contract. A redirect link takes the user from one URL to another. In this case, it takes them to the newly-updated contract specifically written for them."
msgid ":guilabel:`Document`: the attached document can be replaced by clicking the :icon:`fa-pencil` :guilabel:`(pencil)` icon. A pop-up window appears, so another document can be selected for upload. The file **must** be a PDF. To remove the document, click the :icon:`fa-trash-o` :guilabel:`(trash can)` icon."
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."
msgid "This section is where the specific salary details are defined. This section is country-specific, so these fields vary, depending on where the company is located."
msgid "Enter the amount in the various fields, or tick a checkbox to apply a benefit. Some options that can be entered here include :guilabel:`Group Insurance Sacrifice Rate` and :guilabel:`Canteen Cost`, for example."
msgid "Some fields may be automatically filled in as other fields are entered. For example, the :guilabel:`Yearly Cost (Real)` and :guilabel:`Monthly Cost (Real)` updates once the :guilabel:`Wage` is populated."
msgid "This tab **only** appears after an :guilabel:`Employee` is selected, and houses any documents that are linked to the employee on their employee record. Documents cannot be added to this tab, this tab **only** shows documents that are already uploaded and associated with the employee."
msgid "The available documents in this tab can be downloaded. Click the :icon:`fa-download` :guilabel:`(download)` icon next to the document to download it."
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."
msgid ":guilabel:`Generate Simulation Link`: this option is **only** for Belgian companies. Clicking this opens a pop-up window that contains the basic information from the contract, as well as a link for the contract when using the salary configurator. Click :guilabel:`Send` to send an email to the employee, so they can sign the contract."
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."
msgid ":guilabel:`Signature Request`: clicking this reveals a pop-up window, where an email can be typed to the employee. Select the document (such as a contract, NDA, or Homeworking Policy) from the drop-down menu, and fill out the email section. Click :guilabel:`Send` when the email is ready to be sent."
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."
msgid "To add a new deduction, first navigate to :menuselection:`Payroll app --> Contracts --> Salary Attachments`. Next, click :guilabel:`Create`, and a new salary attachment form loads."
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."
msgid ":guilabel:`Assignment of Salary`: any deduction that is not required, but voluntary, such as a pre-tax allocation to a college savings account."
msgid ":guilabel:`Start Date`: the date the salary attachment starts. Choose a date by clicking on the drop-down menu, navigating to the correct month and year by using the :icon:`fa-chevron-left` :icon:`fa-chevron-right` :guilabel:`(arrow)` icons, then clicking on the desired date. This field is **required**."
msgid ":guilabel:`Estimated End Date`: this field automatically populates after both the :guilabel:`Monthly Amount` and :guilabel:`Total Amount` fields are populated. This field is **not** modifiable."
msgid ":guilabel:`Document`: attach any documents relevant to the salary attachment. Click the :guilabel:`Upload Your File` button, navigate to the desired document in the file explorer, then click :guilabel:`Open` to select the document, and attach it to the form. To change the attached document, click the :icon:`fa-pencil` :guilabel:`(pencil)` icon, and select a different document. To remove a document, click the :icon:`fa-trash-o` :guilabel:`(trash can)` icon."
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."
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`."
msgid "These three sections provide all the tools needed to create payslips for employees, including individual payslips, a batch of payslips, or commission payslips."
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."
msgid "Each payslip will list the :guilabel:`Reference` number for the individual payslip, the :guilabel:`Employee` name, :guilabel:`Batch Name`, the :guilabel:`From` and :guilabel:`To` date range, the :guilabel:`Company`, the :guilabel:`Basic Wage`, :guilabel:`Net Wage`, and the :guilabel:`Status` of the payslip."
msgid "A new payslip can be created from the :guilabel:`Payslips To Pay` page (:menuselection:`Payroll app --> Payslips --> To Pay`) or the :guilabel:`Employee Payslips` page (:menuselection:`Payroll app --> Payslips --> All Payslips`), by clicking the :guilabel:`Create` button in the top-left corner."
msgid "On the blank payslip form, a number of fields are required to be filled in with the necessary information. These required fields are represented by **bold** lines."
msgid ":guilabel:`Employee`: Type in the name of an employee, or select the desired employee from the drop-down list. Upon selecting an employee, several other fields on the payslip form may auto-populate. Typically, after making a selection in the :guilabel:`Employee` field, Odoo auto-populates the :guilabel:`Contract`, :guilabel:`Structure`, and :guilabel:`Payslip Name` fields, but **only** if that information is already on that employee's form in the *Employees* app."
msgid ":guilabel:`Period`: Click the default date to reveal a pop-up calendar. On this calendar, use the :guilabel:`< (less-than)` and :guilabel:`> (greater than)` icons to select the desired month, and click on the desired day to select that specific date as the start date for the payslip. Repeat this process to add an end date for the payslip in the field below."
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."
msgid ":guilabel:`Structure`: Using the drop-down menu, select the salary structure type. Only the available corresponding structures for the selected contract for that specific employee appear as options."
msgid ":guilabel:`Payslip Name`: In the blank field, type in the name for the payslip. The name should be short and descriptive, such as `April 2023`."
msgid ":guilabel:`Company`: In the :guilabel:`Accounting Information` tab, select the company the payslip applies to from the :guilabel:`Company` drop-down menu."
msgid ":guilabel:`Salary Journal`: In the :guilabel:`Accounting Information` tab, enter the salary journal in which the payment will be reflected, and found in the *Accounting* application."
msgid ":guilabel:`Worked Days`: In the :guilabel:`Worked Days \\& Inputs` tab, 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."
msgid ":guilabel:`Salary Computation`: The :guilabel:`Salary Computation` tab is automatically filled in after the :guilabel:`Compute Sheet` button is clicked. Doing so displays all the wages, deductions, taxes, etc. for the entry."
msgid ":guilabel:`Batch Name`: Located in the :guilabel:`Accounting Information` tab, select the payslip batch this new payslip should be added to from the drop-down menu."
msgid ":guilabel:`Date Account`: Located in the :guilabel:`Accounting Information` tab, enter the date on which the payslip should be posted, by clicking on the drop-down menu, and navigating to the correct month and year using the :guilabel:`< > (less-than/greater-than)` icons in the calendar pop-up window. Then, click on the desired date."
msgid ":guilabel:`Salary Journal`: This field, located in the :guilabel:`Accounting Information` tab, represents the journal that the payslip will be logged in, and is automatically selected when the :guilabel:`Contract` and :guilabel:`Structure` are entered in the payslip form."
msgid ":guilabel:`Accounting Entry`: This field, located in the :guilabel:`Accounting Information` tab, is automatically filled in once the payslip is confirmed."
msgid "When all the necessary information on the payslip is entered, click :guilabel:`Save` to save the data, or click :guilabel:`Discard` to delete the entry."
msgid "Saving the entry is not required in order to compute the sheet, although it is considered best practice to do so. The :guilabel:`Compute Sheet` button can be clicked without first saving the payslip. Doing so will save the entry *and* compute the sheet."
msgid "Click the :guilabel:`Compute Sheet` button to register all the information, and have the :guilabel:`Salary Computation` tab populated. If any modifications need to be made, click the :guilabel:`Edit` button, make the desired changes, then click the :guilabel:`Recompute Worked Days` button to have the changes reflected in the :guilabel:`Worked Days` and :guilabel:`Salary Computation` tabs."
msgid "Once everything on the payslip form is correct, click the :guilabel:`Create Draft Entry` button to create the payslip. The chatter is automatically updated to show the email sent to the employee, along with a PDF copy of the payslip."
msgid "Next, the payment must be sent to the employee. To do this, click the :guilabel:`Make 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."
msgid "If a payment needs to be cancelled or refunded, click the corresponding :guilabel:`Refund` or :guilabel:`Cancel Payslip` button, located at the top of the payslip form."
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 will appear when the :guilabel:`Make Payment` button is clicked. Banking information can be found in the :guilabel:`Private Information` tab on the employee's card. Edit the employee card, and add banking information, if it is missing."
msgid "To view all payslips regardless of status, go to :menuselection:`Payroll app --> Payslips --> All Payslips`. Here, all payslips are organized by batch (in a default list view)."
msgid "Click on the :guilabel:`▶ (arrow)` next to the individual batch name to view all the payslips in that particular batch, along with all the payslip details. 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 if it is in :guilabel:`Draft Mode`, :guilabel:`Waiting`, or if it is :guilabel:`Done`."
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."
msgid "A new payslip can be created from the :guilabel:`Employee Payslips` page, by clicking the :guilabel:`Create` 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 a new payslip <payroll/new-payslip>` section."
msgid "To print PDF versions of payslips from the :guilabel:`Payslips to Pay` or :guilabel:`Employee Payslips` pages, first select the desired payslips by clicking on the individual checkbox next to each payslip to be printed. Or, click the box next to :guilabel:`Reference`, which selects all visible payslips on the page. Then, click the :guilabel:`Print` button to print the payslips."
msgid "Payslips can also be exported to an Excel spreadsheet. When exporting, all payslips are exported regardless of whether some are selected or not. Click on the :guilabel:`Export All` button (download icon) to export all payslips to an Excel spreadsheet."
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."
msgid "Each batch displays the :guilabel:`Name`, :guilabel:`Date From` and :guilabel:`Date To` dates, whether it was a :guilabel:`Credit note`, its :guilabel:`Status`, and the :guilabel:`Company`."
msgid "Click on an individual batch to view the details for that batch on a separate page. On this batch detail page, modifications can be made. To make any modifications to a batch, click the :guilabel:`Edit` button. Then, proceed to make any necessary changes."
msgid "When all desired changes have been made, click either :guilabel:`Save` to save the changes, or :guilabel:`Discard` to revert back to the original data."
msgid "After modifications have been saved, click the :guilabel:`Generate Payslips` button to reveal a :guilabel:`Generate Payslips` pop-up form, in which payslips affected by the changes can be created or modified."
msgid "All payslips associated with the batch are displayed in the employees section of the :guilabel:`Generate Payslips` pop-up. To filter the results by either the :guilabel:`Salary Structure` and/or the :guilabel:`Department`, select a salary structure and/or department from the respective drop-down menus."
msgid "Only employees that match the selected :guilabel:`Salary Structure` and/or :guilabel:`Department` appear in the employees list. Click the :guilabel:`Generate` button at the bottom of the :guilabel:`Generate Payslips` pop-up window to generate the modified payslips, and close the pop-up window."
msgid "Once the draft payslips are created, the button changes to say :guilabel:`Make Payment`. Click the :guilabel:`Make Payment` button. A pop-up window appears, in which the bank journal information must be entered. Select the :guilabel:`Bank Journal` from the drop-down list, and click :guilabel:`Confirm` to process the payslips, and pay the employees."
msgid "On the batch detail page, the number of payslips in the batch is accessible via the :guilabel:`Payslips` smart button, located in the top-right corner. Individual payslips for the batch can be viewed by clicking the :guilabel:`Payslips` smart button in the top-right corner."
msgid "To create a new batch of payslips from the :guilabel:`Payslips Batches` page (:menuselection:`Payroll app --> Payslips --> Batches`), click the :guilabel:`Create` button in the upper-left corner. Doing so reveals a blank payslip batch form on a separate page."
msgid "On the new payslip batch form, enter the :guilabel:`Name` for the batch, and select the date range to which the batch applies, by clicking the :guilabel:`▼ (drop-down arrow)` icon in the :guilabel:`Period` fields, which reveals a calendar pop-up window. From this calendar pop-up window, navigate to the correct month, and click on the corresponding day for both the start and end dates."
msgid "If the batch is a credit note, check the box next to :guilabel:`Credit Note`. Then, in the :guilabel:`Generation Date` field, select the date the payslips should be generated from a calendar pop-up window. This generated date is reflected in the accounting journal entries."
msgid "When all the information on the payslip batch form is correct, click the :guilabel:`Save` button to save the information. To delete the entry, click the :guilabel:`Discard` button."
msgid "When clicked, a pop-up window appears showing all the payslips that will be created. To remove any individual payslips, click the black :guilabel:`✖ (x mark)` icon at the far right of the payslip line."
msgid "If a specific :guilabel:`Salary Structure` or :guilabel:`Department` needs to be specified for the batch, select them from the corresponding drop-down menus."
msgid "On the :guilabel:`Generate Payslips` pop-up window, selecting a :guilabel:`Department` and/or :guilabel:`Salary Structure` only displays payslips that apply to those specifically-selected parameters."
msgid "If there are any errors or issues preventing the payslips from being generated, an error message appears in the top-right section. This error box disappears on its own after several seconds, or the :guilabel:`✖ (x mark)` icon can be clicked to close the alert."
msgid "To remedy the issue, make any necessary modifications (e.g. removing any payslip lines that cannot be processed), then click the :guilabel:`Generate` button again."
msgid "Once payslips have been generated, click the :guilabel:`Make Payment` button to process the payments. Doing so reveals a pop-up window, in which the proper banking information must be entered. In this pop-up window, select the appropriate :guilabel:`Bank Journal` from the drop-down menu, and enter the appropriate file name."
msgid "Commission payslips can be generated directly from the :guilabel:`Payslips Batches` page (:menuselection:`Payroll app --> Payslips --> Batches`). To generate commission payslips from this page, click on the desired batch (or batches) to create commissions payslips for, then click the :guilabel:`Generate Commission Payslips` button."
msgid "On 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)` arrows, navigate to the correct month, and click on the date to select it."
msgid "Under the :guilabel:`Employee` section, enter the :guilabel:`Commission Amount` for each employee in the appropriate column. To remove an employee, click the :guilabel:`🗑️ (trash)` icon to remove the line."
msgid "Using the drop-down menu beside the :guilabel:`Commission Type` field, select either :guilabel:`Classic Commission` or :guilabel:`Warrant`. :guilabel:`Classic` is the most typical of commission, while :guilabel:`Warrant` is primarily used for Belgium companies."
msgid "The :guilabel:`Reporting` section of the *Payroll* app offers a variety of reports to choose from. The :guilabel:`Payroll`, :guilabel:`Meal Vouchers`, :guilabel:`Attachment of Salary`, and :guilabel:`DMFA` reports are universal and available for all companies regardless of location. The :guilabel:`Paid Time Off Allocation`, :guilabel:`273S Sheet`, and :guilabel:`274.XX Sheets` reports are specific to Belgian companies only."
msgid "At the top of each report, click on :guilabel:`Filters` to display the optional filters for the specific report. Filters show information that matches the specific filter parameters. For example, when selecting the :guilabel:`Last 365 Day Payslip` filter, only payslips for the last 365 days appear. All reports have the option to add a custom filter, and each have different default custom filter options. Select the parameters, then click the :guilabel:`Apply` button."
msgid "Clicking on :guilabel:`Favorites` displays three options: :guilabel:`Save the current search`, :guilabel:`Add the search to the dashboard`, or :guilabel:`Insert the search to a Google spreadsheet`."
msgid "This shows all the payslips generated in the last 365 days. The report can display metrics for a variety of parameters. Click the :guilabel:`Measures` box to view a drop-down menu with the various options to display. The options available include: :guilabel:`# Payslip`, :guilabel:`Basic Wage`, :guilabel:`Basic Wage for Time Off`, :guilabel:`Days of Paid Time Off`, :guilabel:`Days of Unforeseen Absence`, :guilabel:`Days of Unpaid Time Off`, :guilabel:`Gross Wage`, :guilabel:`Net Wage`, :guilabel:`Number of Days`, :guilabel:`Number of Hours`, :guilabel:`Work Days`, :guilabel:`Work Hours`, and :guilabel:`Count`."
msgid "A line chart is the default view for the *Payroll Analysis* report. If a different view was selected, click on the :guilabel:`Line Chart` icon (middle icon) in the menu bar to change the view back to a line chart. An option to display the line chart in ascending or descending order appears at the end of the options."
msgid "Click the :guilabel:`Stacked` icon to view the bar chart in a stacked format (where multiple values appear in each column). An option to display the columns in ascending or descending order appears at the end of the options."
msgid "Clicking an option enables it. To disable the option, click it again. When the option is enabled it appears grey. When it is inactive, it appears white."
msgid "To display the data in a pie chart, click on the :guilabel:`Pie Chart` icon (last icon) in the menu bar. There are no additional options available in this view."
msgid "The bottom half of the :guilabel:`Payroll Analysis` dashboard presents a pivot table no matter which type of chart is selected for the top of the dashboard. The default information displayed is the number of payslips, net wage, gross wage, days of paid time off, and days of unpaid time off. The information is divided by department. To display more information on the report, select the :guilabel:`Measures` drop-down menu, then click on any other items to display."
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."
msgid "The data can be inserted into a spreadsheet by clicking the :guilabel:`Insert in Spreadsheet` button. A pop-up appears asking which spreadsheet to place the information in. Select an existing spreadsheet or enter the name for a new spreadsheet. Click the :guilabel:`Confirm` button to move to a spreadsheet view with all the information populated."
msgid "Once in the spreadsheet view, click on :guilabel:`File`, then select :guilabel:`Save` to save the data, or :guilabel:`Save as Template` to save the setting as a template to use in the future."
msgid ":guilabel:`Meal Vouchers` provides an overview of the meal vouchers used by employees, and can be shown by :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, :guilabel:`Quarter`, or :guilabel:`Year`. The default view is by month."
msgid "To change the displayed view, click on :guilabel:`Total`. The data collapses, showing only the count column. Click on :guilabel:`Total` again, then hover over :guilabel:`Day`, then click on one of the other time-period options available."
msgid "It is possible to compare the current meal voucher report to the one for the previous time period or the previous year. To view these comparisons, click on the :guilabel:`Comparison` drop-down menu at the top, then select either :guilabel:`Date: Previous Period` or :guilabel:`Date: Previous Year`."
msgid "Once in the spreadsheet view, click on :guilabel:`File`, then select :guilabel:`Save` to save the data, or :guilabel:`Save as Template` to save the settings as a template to use in the future."
msgid "The :guilabel:`Attachment of Salary` report shows all deductions or allocations per employee, such as child support payments and wage garnishments."
msgid "Clicking on the :guilabel:`Measures` button shows options for how the data is 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 check mark, it is displayed."
msgid "The salary attachment report can be compared to the one for the previous time period or the previous year. To view these comparisons, click on the on the :guilabel:`Comparison` drop-down menu at the top, then select either :guilabel:`Payslip End Date: Previous Period` or :guilabel:`Payslip End Date: Previous Year`."
msgid "The *Work Entries* dashboard, which can be found by going to :menuselection:`Payroll --> Work Entries --> Work Entries`, provides a visual overview of the individual time sheets of every employee, with each day split into a morning shift and an afternoon shift."
msgid "To change the view so that only the entries for a single day, week, or month are shown, click on one of the corresponding links for :guilabel:`Day`, :guilabel:`Week`, or :guilabel:`Month`, located at the top of the dashboard."
msgid "Use the :guilabel:`⬅️ (left arrow)` and :guilabel:`➡️ (right arrow)` icons on the left and right side of the :guilabel:`Today` button to adjust the displayed dates. The arrows will adjust the date based on the type of time selected. For example, if month is selected, the arrows will move one month with each click of the arrow. If week or day is selected, the time will move by either a week or a day for each click of the arrow, respectively."
msgid "If a work entry is missing and needs to be added, such as sick time or time off, click :guilabel:`Add` to create a new work entry. A pop-up will appear, with several fields to fill in."
msgid "Enter the :guilabel:`Work Entry Name`, such as `Sick Time` or any other short description. Select the :guilabel:`Employee` and the :guilabel:`Work Entry Type` from the respective drop-down lists."
msgid "Next, enter the date and time for the work entry in the :guilabel:`From` and :guilabel:`To` drop-downs. First, 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."
msgid "Then, select the time by clicking on the :guilabel:`⏰ (clock)` icon, and using the :guilabel:`⬆️ (up arrow)` and :guilabel:`⬇️ (down arrow)` icons for each section to enter the hour, minute, and second for the time period."
msgid "Before clicking either :guilabel:`Save & Close` or :guilabel:`Save & New`, it is good to double check the :guilabel:`Period` to ensure the time stated corresponds to the :guilabel:`To` and :guilabel:`From` fields."
msgid "Once the information is entered, click :guilabel:`Save & Close` to save the entry and close the pop-up, or :guilabel:`Save & New` to save the entry and create another :guilabel:`Work Entry Type`."
msgid "After a work entry has been either added or modified, the work entries need to be regenerated for the affected employee(s). Click on the :guilabel:`Regenerate Work Entries` button at the top of the main dashboard, and a pop-up will appear."
msgid "Select the :guilabel:`Employee` to regenerate work entries for from the :guilabel:`drop-down menu`, and adjust the :guilabel:`From` and :guilabel:`To` fields so the correct date range is displayed. Click the :guilabel:`Regenerate Work Entries` button and the work entries will be recreated. Once finished, the pop-up will close."
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."
msgid "Any work entry that has a conflict to be resolved is indicated on the main :guilabel:`Work Entry` overview dashboard, located by going to :menuselection:`Payroll --> Work Entries --> Conflicts`, where only conflicts needing resolution are shown."
msgid "Conflicts are indicated with an orange triangle in the top left corner of each individual entry. Click on an individual work entry to see the conflict details in a pop-up."
msgid "The :guilabel:`Work Entry Name`, :guilabel:`Employee`, and :guilabel:`Work Entry Type` are listed on the left side of the pop-up. The :guilabel:`From` and :guilabel:`To` date range, as well as the total time requested (in hours), appear in the :guilabel:`Period` field on the right side."
msgid "If there is a conflict because a time-off request for the same time already exists in the system, the time-off will be entered in the :guilabel:`Time Off` field. Clicking the :guilabel:`External Link` button next to the :guilabel:`Time Off` entry will bring up the duplicate time-off request."
msgid "The details for the time-off request appear in the pop-up. The request can be modified if needed. Click either the :guilabel:`Validate` or :guilabel:`Refuse` button to approve or deny the request, then click the :guilabel:`Save` button to save the changes."
msgid "Once the duplicate time-off request has been approved and saved, the screen goes back to the conflict. Click :guilabel:`Refuse Time Off` or :guilabel:`Approve Time Off` via the buttons in the top right to either approve or deny the request. Repeat for all conflicts until there are no conflicts to resolve."
msgid "After conflicts have been resolved, work entries must be regenerated for each employee by clicking the :guilabel:`Regenerate Work Entries` button, and entering the corresponding information for each employee."
msgid "To generate payslips, navigate to the time period the payslips should be generated for, either day, week, or month. When the desired pay period is displayed, click the :guilabel:`Generate Payslips` button."
msgid "If the :guilabel:`Generate Payslips` button is not active (appears light turquoise instead of dark turquoise), that indicates there are conflicts. *Solve conflicts first* will appear as a warning when :guilabel:`Generate Payslips` is moused over. Resolve all conflicts before generating payslips."
msgid "A batch entry will appear for the time period selected. The batch name appears at the top in the :guilabel:`Name` field, typically listing the month and year for the particular batch."
msgid "The date range the payslips apply to appears in the :guilabel:`Period` field. The company appears in the :guilabel:`Company` field, along with an option to mark the payslips as a credit note. To make changes, click the :guilabel:`Edit` button in the top left, make any changes, then click either :guilabel:`Save` to accept the changes or :guilabel:`Discard` to revert to the original data."
msgid "Payslips will have a status of *Waiting* until the :guilabel:`Create Draft Entry` button has been clicked. After, the payslip status will change to *Done*."
msgid "Payslips can be printed by clicking the box next to each payslip to print, or clicking the box next to :guilabel:`Reference` to select all the payslips at once. Click the :guilabel:`Print` button, and a PDF file will be created with all the specified payslips."
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'."
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."
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."
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."
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."
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."
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:"
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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)."
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."
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."
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:"
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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`."
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."
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."
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."
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."
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."
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`."
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`."
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."
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`."
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."
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`."
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."
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."
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."
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."
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."
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`"
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."
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."
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."
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."
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."
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\"`."
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."
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."
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.`"
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."
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."
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."
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`."
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."
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`."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
msgid ":guilabel:`Organizer`: the employee who created the meeting is populated in this field. Use the drop-down menu to change the selected employee."
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."
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."
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."
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."
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."
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`."
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."
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."
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."
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."
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."
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."
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."
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`)."
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."
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`."
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."
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."
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`."
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`."
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`."
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."
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`."
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."
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`."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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...`."
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?"
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`."
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."
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."
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."
msgid "Questions and sections can be reorganized. Move them by clicking and dragging individual section headings or question lines to their desired position(s)."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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?`."
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."
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."
msgid "Next, configure the various options for the interview form. Click the :guilabel:`Options` tab to view all the options to configure, by category."
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`."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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`."
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."
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."
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."
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."
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."
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`."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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.*"
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."
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`."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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:"
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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."
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.*"
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."
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."
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."
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`."
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."
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`."
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."
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."
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."
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."
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."
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."
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."
msgid "In Odoo *Referrals*, users can earn referral points by sharing job positions with potential applicants. Job positions can be shared in several ways, through the :ref:`View Jobs <referrals/view-jobs>` button and the :ref:`Email A Friend <referrals/email-jobs>` button, located at the bottom of the *Referrals* app dashboard."
msgid "To see all job positions that are actively recruiting candidates, click the :guilabel:`View Jobs` button on the main *Referrals* dashboard. This presents all job positions, with each individual job presented with its own card."
msgid "The number of :guilabel:`Open Positions` being recruited. This information is taken from the *Expected New Employees* field of the *Recruitment* tab of the job form."
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."
msgid "Only published job positions are visible in the *Referrals* app. To check which job positions are published or not, refer to the :doc:`../recruitment/new_job` documentation."
msgid "To share a job position with someone, click the :guilabel:`Refer Friend` button on the specific job position card. A pre-configured :guilabel:`Send Job Offer by Mail` pop-up window appears. Enter the recipient's email address in the :guilabel:`Email` field."
msgid "The :guilabel:`Subject` and :guilabel:`Body` are populated using a default template. The :guilabel:`Subject` `Job for you` is present, by default, but can be modified, if desired."
msgid "The specific title of the job position populates the *Job Position* placeholder in the email body. The `See Job Offer` text in the email body is an individualized tracking link to the specific job position listed on the website."
msgid "When the prospective employee receives the email, the link sends them to the job position page, where they can apply for the position, and the person who referred them is tracked in the *Referrals* application."
msgid "If desired, add any text or closing salutation to the email body. When all edits have been made, click :guilabel:`Send Mail` to send the email, or click :guilabel:`Cancel` to close the pop-up window."
msgid "Other than sending an email, job positions can be shared, via social media platforms, and by tracking links to the job position. At the bottom of each job position card are four icons, and corresponding tracking links, that can be used to share the job position, keeping track of applicants in the *Referrals* application."
msgid "To share the job position with a customized tracking link, click the :guilabel:`Share Now` button with the :icon:`fa-chain` :guilabel:`(link)` icon above it. A :guilabel:`Link to Share` pop-up window appears with the tracking link. Click :guilabel:`Copy` to copy the link. After the link is copied, click the :guilabel:`Close` button to close the pop-up window. Next, share the link with the prospective employee."
msgid "To share the job position using Facebook, click the :guilabel:`Share Now` button with the :icon:`fa-facebook` :guilabel:`(Facebook)` icon above it."
msgid "If the user is already logged into Facebook, when the the :guilabel:`Share Now` button is clicked, a :guilabel:`Share on Facebook` page loads in a new tab, with the link populated in the main body of the new post in a pop-up window. If the user is *not* already logged in, a log-in screen loads, instead, prompting the user to log-in to Facebook first."
msgid "If the user is already signed-in to X, when the :guilabel:`Share Now` button is clicked, an X page loads in a new tab with a pre-populated message ready to post, in a draft pop-up window. If the user is *not* already signed-in, a sign-in screen loads instead, prompting the user to first sign-in to X."
msgid "If the user is already logged into LinkedIn, when the :guilabel:`Share Now` button is clicked, a new tab loads in LinkedIn, with a link to the job position at the top. If the user is *not* already logged in, a log-in screen loads instead, prompting the user to log-in to LinkedIn first."
msgid "Another way to share job opportunities is to share the entire current list of open job positions, instead of one job position at a time. To do this, navigate to the :menuselection:`Referrals` main dashboard. Click the :guilabel:`Email a friend` button at the bottom of the screen. A :guilabel:`Send Job Offer by Mail` pop-up window appears."
msgid "Enter the email address in the :guilabel:`Email` field. The email can be sent to multiple recipients by separating each email address with a comma followed by a single space. The :guilabel:`Subject` is pre-configured with :guilabel:`Job for you`, but can be edited."
msgid "The :guilabel:`See Job Offers` text is a tracking link to a complete list of all job positions currently being recruited for. Add any additional text and make any edits to the message body, if necessary. Then, click :guilabel:`Send Mail` to send the email. This sends the message, and closes the window."
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:27
msgid "Configuration"
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:82
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:86
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:90
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:93
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:95
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:100
msgid "Allocation requests section"
msgstr ""
#: ../../content/applications/hr/time_off.rst:102
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:106
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:110
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:113
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:116
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:119
msgid ":guilabel:`No validation needed` indicates that no approvals are required."
msgstr ""
#: ../../content/applications/hr/time_off.rst:120
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:122
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:126
msgid "Payroll section"
msgstr ""
#: ../../content/applications/hr/time_off.rst:128
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:132
msgid "Timesheets section"
msgstr ""
#: ../../content/applications/hr/time_off.rst:135
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:138
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:141
msgid ":guilabel:`Project`: select the project that the time off type entries appear in."
msgstr ""
#: ../../content/applications/hr/time_off.rst:142
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:146
msgid "Display option section"
msgstr ""
#: ../../content/applications/hr/time_off.rst:148
msgid ":guilabel:`Color`: select a color to be used in the *Time Off* application dashboard."
msgstr ""
#: ../../content/applications/hr/time_off.rst:149
msgid ":guilabel:`Cover Image`: select an icon to be used in the *Time Off* application dashboard."
msgstr ""
#: ../../content/applications/hr/time_off.rst:152
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:163
msgid "Accrual plans"
msgstr ""
#: ../../content/applications/hr/time_off.rst:165
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:169
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:174
msgid "Create accrual plan"
msgstr ""
#: ../../content/applications/hr/time_off.rst:176
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:179
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:183
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:193
msgid "Rules must be created in order for the accrual plan to accrue time off."
msgstr ""
#: ../../content/applications/hr/time_off.rst:195
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 ":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:204
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:206
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:209
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:213
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:215
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:219
msgid "Depending on the selection, more fields appear to specify exactly when the accrual renews."
msgstr ""
#: ../../content/applications/hr/time_off.rst:222
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:226
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:231
msgid ":guilabel:`Limit to`: enter a maximum amount of days the employee can accrue with this plan."
msgstr ""
#: ../../content/applications/hr/time_off.rst:232
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:235
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:242
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:252
msgid "Public holidays"
msgstr ""
#: ../../content/applications/hr/time_off.rst:254
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:257
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:261
msgid "Create public holiday"
msgstr ""
#: ../../content/applications/hr/time_off.rst:263
msgid "To create a public holiday, navigate to :menuselection:`Time Off app --> Configuration --> Public Holidays`."
msgstr ""
#: ../../content/applications/hr/time_off.rst:266
msgid "All currently configured public holidays appear in a list view."
msgstr ""
#: ../../content/applications/hr/time_off.rst:268
msgid "Click the :guilabel:`Create` button, and a new line appears at the bottom of the list."
msgstr ""
#: ../../content/applications/hr/time_off.rst:270
msgid "Enter the following information:"
msgstr ""
#: ../../content/applications/hr/time_off.rst:272
msgid ":guilabel:`Name`: enter the name of the holiday."
msgstr ""
#: ../../content/applications/hr/time_off.rst:273
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:275
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:280
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:287
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:294
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:297
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:307
msgid "Overview"
msgstr ""
#: ../../content/applications/hr/time_off.rst:309
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:313
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:316
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:319
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:322
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:325
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:327
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:330
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:340
msgid "Allocate time off"
msgstr ""
#: ../../content/applications/hr/time_off.rst:342
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:346
msgid "To create a new allocation, navigate to :menuselection:`Time Off app --> Approvals --> Allocations`."
msgstr ""
#: ../../content/applications/hr/time_off.rst:348
msgid "This presents a list of all current allocations, including their respective status."
msgstr ""
#: ../../content/applications/hr/time_off.rst:350
msgid "Click :guilabel:`Create` to allocate time off, and a blank allocation form appears."
msgstr ""
#: ../../content/applications/hr/time_off.rst:352
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:355
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:357
msgid ":guilabel:`Allocation Type`: select either :guilabel:`Regular Allocation` or :guilabel:`Accrual Allocation`."
msgstr ""
#: ../../content/applications/hr/time_off.rst:359
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:363
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:366
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:370
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:373
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:376
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:379
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:383
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:386
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:389
msgid "Multiple selections can be made for either :guilabel:`Employees` or :guilabel:`Employee Tag`."
msgstr ""
#: ../../content/applications/hr/time_off.rst:391
msgid "Only one selection can be made for the :guilabel:`Company` or :guilabel:`Department`."
msgstr ""
#: ../../content/applications/hr/time_off.rst:392
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:398
msgid "Request time off"
msgstr ""
#: ../../content/applications/hr/time_off.rst:400
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:404
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:407
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:410
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:414
msgid "Enter the following information on the form:"
msgstr ""
#: ../../content/applications/hr/time_off.rst:416
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:417
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:421
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:424
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:427
msgid "When the correct dates are selected/highlighted, click the :guilabel:`Apply` button."
msgstr ""
#: ../../content/applications/hr/time_off.rst:429
msgid "The dates now populate the :guilabel:`From` and :guilabel:`To` fields."
msgstr ""
#: ../../content/applications/hr/time_off.rst:431
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:435
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:439
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:443
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:445
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:449
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:452
#: ../../content/applications/hr/time_off.rst:492
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:462
msgid "Request allocation"
msgstr ""
#: ../../content/applications/hr/time_off.rst:464
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:468
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:471
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:474
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:478
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:481
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:483
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:487
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:489
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:501
msgid "Approvals"
msgstr ""
#: ../../content/applications/hr/time_off.rst:503
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:507
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:511
msgid "Approve allocations"
msgstr ""
#: ../../content/applications/hr/time_off.rst:513
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:518
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:523
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:526
msgid "The options are :guilabel:`To Approve`, :guilabel:`To Submit`, :guilabel:`Refused`, and :guilabel:`Approved`."
msgstr ""
#: ../../content/applications/hr/time_off.rst:529
msgid "To view all allocation requests, click :guilabel:`All`."
msgstr ""
#: ../../content/applications/hr/time_off.rst:531
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:535
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:539
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:542
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:545
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:548
#: ../../content/applications/hr/time_off.rst:597
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:551
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:555
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:562
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:565
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:569
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:575
msgid "Approve time off"
msgstr ""
#: ../../content/applications/hr/time_off.rst:577
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:582
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:587
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:591
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:594
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:600
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:605
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:612
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:616
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:619
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:623
#: ../../content/applications/hr/time_off.rst:674
msgid "My time off"
msgstr ""
#: ../../content/applications/hr/time_off.rst:625
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:631
msgid "Dashboard"
msgstr ""
#: ../../content/applications/hr/time_off.rst:633
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:637
msgid "The current year is displayed, and the current day is highlighted in red."
msgstr ""
#: ../../content/applications/hr/time_off.rst:639
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:642
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:645
msgid "For example, if :guilabel:`Week` is selected, the arrows adjust the view by one week."
msgstr ""
#: ../../content/applications/hr/time_off.rst:647
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:650
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:655
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:658
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:662
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:665
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:676
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:680
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:684
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:688
msgid "My allocations"
msgstr ""
#: ../../content/applications/hr/time_off.rst:690
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:693
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:696
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:702
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:707
msgid "By employee"
msgstr ""
#: ../../content/applications/hr/time_off.rst:709
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:712
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:715
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:718
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:721
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:731
msgid "By type"
msgstr ""
#: ../../content/applications/hr/time_off.rst:733
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:736
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:740
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."
