msgid "Synchronize Google Calendar with Odoo to see and manage meetings from both platforms (updates go in both directions). This integration helps organize schedules, so a meeting is never missed."
msgid "Create a new Google API project and enable the Google Calendar API. First, go to the `Google API Console <https://console.developers.google.com>`_ and log into the Google account."
msgid "If this is the first time visiting this page, Google will prompt the user to enter a country and agree to the Terms of Service. Select a country from the drop-down list and agree to the :abbr:`ToS (Terms of Service)`."
msgid "Next, click :guilabel:`Select a project` and select (or create) an API project to configure OAuth in, and store credentials. Click :guilabel:`New Project`."
msgid "Now, click on :guilabel:`Enabled APIs and Services` in the left menu. Select :guilabel:`Enabled APIs and Services` again if the :guilabel:`Search bar` doesn't appear."
msgid "After that, search for `Google Calendar API` using the search bar and select :guilabel:`Google Calendar API` from the search results. Click :guilabel:`Enable`."
msgid "Now that the API project has been created, OAuth should be configured. To do that, click on :guilabel:`OAuth consent` in the left menu and then select the :guilabel:`User Type`."
msgid "*Personal* Gmail Accounts are only allowed to be **External** User Type, which means Google may require an approval, or for *Scopes* to be added on. However, using a *Google WorkSpace* account allows for **Internal** User Type to be used."
msgid "Note, as well, that while the API connection is in the *External* testing mode, then no approval is necessary from Google. User limits in this testing mode is set to 100 users."
msgid "In the second step, :guilabel:`OAuth Consent Screen`, type `Odoo` in the :guilabel:`App name` field, select the email address for the :guilabel:`User support email` field, and type the email address for the :guilabel:`Developer contact information` section. Then, click :guilabel:`Save and Continue`."
msgid "Next, if continuing in testing mode (External), add the email addresses being configured under the :guilabel:`Test users` step, by clicking on :guilabel:`Add Users`, and then the :guilabel:`Save and Continue` button. A summary of the app registration appears."
msgid "The *Client ID* and the *Client Secret* are both needed to connect Google Calendar to Odoo. This is the last step in the Google console. Begin by clicking :guilabel:`Credentials` in the left menu. Then, click :guilabel:`Create Credentials`, and select :guilabel:`OAuth client ID`, Google will open a guide to create credentials."
msgid "Under :menuselection:`Create OAuth Client ID`, select :guilabel:`Website application` for the :guilabel:`Application Type` field, and type `My Odoo Database` for the :guilabel:`Name`."
msgid "Under the :guilabel:`Authorized JavaScript Origins` section, click :guilabel:`+ Add URI` and type the company's Odoo full :abbr:`URL (Uniform Resource Locator)` address."
msgid "Under the :guilabel:`Authorized redirect URIs` section, click :guilabel:`+ Add URI` and type the company's Odoo :abbr:`URL (Uniform Resource Locator)` address followed by `/google_account/authentication`. Finally, click :guilabel:`Create`."
msgid "Once the *Client ID* and the *Client Secret* are located, open the Odoo database and go to :menuselection:`Settings --> General Settings --> Integrations --> Google Calendar`. Check the box next to :guilabel:`Google Calendar`."
msgid "Next, copy and paste the *Client ID* and the *Client Secret* from the Google Calendar API credentials page into their respective fields below the :guilabel:`Google Calendar` checkbox. Then, click :guilabel:`Save`."
msgid "When syncing Google Calendar with Odoo for the first time, the page will redirect to the Google Account. From there, select the :guilabel:`Email Account` that should have access, then select :guilabel:`Continue` (should the app be unverifed), and finally select :guilabel:`Continue` (to give permission for the transfer of data)`."
msgid "Odoo highly recommends testing the Google calendar synchronization on a test database and a test email address (that is not used for any other purpose) before attempting to sync the desired Google Calendar with the user's production database."
msgid "Events can be created in Google Calendar without sending a notification by selecting :guilabel:`Don't Send` when prompted to send invitation emails."
msgid "To sync the Outlook Calendar with Odoo's Calendar, a Microsoft Azure account is needed. Creating an account is free for users who have never tried or paid for Azure. For more information, `click here <https://azure.microsoft.com/en-us/free/?WT.mc_id=A261C142F>`_."
msgid "Refer to `Microsoft's documentation <https://docs.microsoft.com/en-us/azure/active-directory/ develop/quickstart-create-new-tenant>`_ on how to set up an Microsoft Entra ID (formally called *Microsoft Azure Active Directory (Azure AD)*), which is a representation of an organization to manage and register apps."
msgid "Then, `Register an Application <https://docs.microsoft.com/en-us/azure/active-directory/develop/ quickstart-register-app>`_, choosing the appropriate :guilabel:`Supported account type`. Users who wish to connect their Outlook calendar to Odoo should select the :guilabel:`Accounts in any organizational directory (Any Microsoft Entra ID directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)` option for :guilabel:`Supported account types`."
msgid "When configuring the :guilabel:`Redirect URI`, choose :guilabel:`Web` and copy the Odoo database URI (URL) followed by `/microsoft_account/authentication`."
msgid "For more information on the restrictions and limitations of URIs, `check this page <https://docs. microsoft.com/en-us/azure/active-directory/develop/reply-url>`_."
msgid "Regarding the application credentials, the user *must* add a client secret, which allows Odoo to authenticate itself, requiring no interaction from the user's side. :guilabel:`Certificates` are optional."
msgid "To do add a client secret, click :guilabel:`Add a certificate or secret` and then click :guilabel:`New client secret`. Next, type a :guilabel:`Description` and select when the client secret :guilabel:`Expires`."
msgid "Since resetting the synchronization can be tricky, Odoo recommends setting the maximum allowed expiration date for the client secret (24 months), so there is no need to re-synchronize soon. Finally, click :guilabel:`Add` to generate the client secret (:guilabel:`Secret ID`)."
msgid "From the Microsoft Azure portal, under the :guilabel:`Overview` section of the application, copy the :guilabel:`Application (Client) ID`, and paste it into the :guilabel:`Client ID` field in Odoo."
msgid "In the Microsoft Azure portal, under the :guilabel:`Certificates & secrets` section, copy the :guilabel:`Client Secret Value` and paste it into the :guilabel:`Client Secret` field in Odoo."
msgid "Odoo highly recommends testing the Outlook calendar synchronization on a test database and a test email address (that is not used for any other purpose) before attempting to sync the desired Outlook Calendar with the user's production database."
msgid "If the user has any past, present, or future events on their Odoo calendar before syncing their Outlook calendar, Outlook will treat the events pulled from Odoo's calendar during the sync as new events, causing an email notification to be sent from Outlook to all the event attendees."
msgid "To avoid unwanted emails being sent to all past, present, and future event attendees, the user must add the events from the Odoo calendar to the Outlook calendar before the first ever sync, delete the events from Odoo, and then start the sync."
msgid "Even after synchronizing the Odoo Calendar with the Outlook calendar, Outlook will still send a notification to all event participants every time an event is edited (created, deleted, unarchived, or event date/time changed), with no exceptions. This is a limitation that cannot be fixed from Odoo's side."
msgid "In the Odoo database, go to the :guilabel:`Calendar` module and click the :guilabel:`Outlook` sync button. The page will redirect to a Microsoft login page, and the user is asked to log in to their account, if they are not already, and grant the required permissions."
msgid "All users that want to use the synchronization simply need to :ref:`sync their calendar with Outlook <outlook/sync>`. The configuration of Microsoft's Azure account is only done once, as Microsoft Entra ID tenants' Client IDs and Client Secrets are unique, and represent an organization that helps the user to manage a specific instance of Microsoft cloud services for their internal and external users."
msgid "Odoo *Discuss* is an internal communication app that allows users to connect through messages, notes, and file sharing, either through a persistent chat window that works across applications, or through the dedicated *Discuss* dashboard."
msgid "By default, the :guilabel:`Notification` field is set as :guilabel:`Handle by Emails`. With this setting enabled, a notification email will be sent by Odoo every time a message is sent from the chatter, a note is sent with an `@` mention (from chatter), or a notification is sent for a record that the user follows. Something that triggers a notification is changing of the stage (if an email\\ is configured to be sent, for example if the task is set to :guilabel:`Done`)."
msgid "By choosing :guilabel:`Handle in Odoo`, the above notifications are shown in the *Discuss* app's *inbox*. Messages can have the following actions taken on them: respond with an emoji by clicking :guilabel:`Add a Reaction`, or reply to the message by clicking on :guilabel:`Reply`. Additional actions may include starring the message by clicking :guilabel:`Marked as Todo`, or pinning the message by selecting :guilabel:`Pin` or even mark the message as unread by selecting :guilabel:`Marked as unread`."
msgid "Clicking :guilabel:`Mark as Todo` on a message causes it to appear on the :guilabel:`Starred` page, while clicking :guilabel:`Mark as Read` moves the message to :guilabel:`History`."
msgid "The first time a user logs in to their account, OdooBot sends a message asking for permission to send desktop notifications for chats. If accepted, the user will receive push notifications on their desktop for the messages they receive, regardless of where the user is in Odoo."
msgid "To start a chat, go to the :menuselection:`Discuss` app and click on the :guilabel:`+ (plus)` icon next to :guilabel:`Direct Messages` or :guilabel:`Channels` in the left menu of the dashboard."
msgid "To mention a user within a chat or the chatter, type `@user-name`; to refer to a channel, type `#channel-name`. The user mentioned will be notified in their *inbox* or through an email, depending on their communication settings."
msgid "When a user is mentioned, the search list (list of names) suggests values first based on the task's followers, and secondly on employees. If the record being searched does not match with either a follower or employee, the scope of the search becomes all partners."
msgid "It is helpful to see what colleagues are up to and how quickly they can respond to messages by checking their *status*. The status is shown on the left side of a contact's name on the :guilabel:`Discuss` sidebar, on the *messaging menu* and when listed in the *chatter*."
msgid "Odoo Discuss uses WebRTC API and peer-to-peer connections for voice and video calls. If one of the call attendees is behind a symmetric NAT, you need to configure an ICE server to establish a connection to the call attendee. To set up an ICE server, first, create a Twilio account for video calls, and then, connect that Twilio account to Odoo."
msgid "First, go to `Twilio <https://www.twilio.com>`_ and click :guilabel:`Sign up` to create a new Twilio account. Next, enter your name and email address, create a password, and accept Twilio's terms of service. Then, click :guilabel:`Start your free trial`. Verify your email address with Twilio, as per their instructions."
msgid "Next, enter your phone number into Twilio. Then, Twilio will send you an SMS text message containing a verification code. Enter the verification code into Twilio to verify your phone number."
msgid "To locate the Account SID and Auth Token, go to the Twilio account dashboard. Then, click :guilabel:`Develop` on the sidebar. In the :guilabel:`Account Info` section, locate the :guilabel:`Account SID` and the :guilabel:`Auth Token`. Both of these are needed to connect Twilio to Odoo."
msgid "Open the Odoo database and go to :menuselection:`Settings --> General Settings --> Discuss`. Check the box next to :guilabel:`Use Twilio ICE servers` and enter the Twilio account's :guilabel:`Account SID` and :guilabel:`Auth Token`. Finally, click :guilabel:`Save` to apply these changes."
msgid "This step is not required for the Twilio configuration. However, if Twilio is not configured or is not working at any given moment, Odoo will fall back on the custom ICE servers list. The user must define the list of custom ICE servers."
msgid "In :menuselection:`Settings --> General Settings --> Discuss`, click the :guilabel:`ICE Servers` button under :guilabel:`Custom ICE server list`."
msgid "For on-premise instances of Odoo, the package `python3-gevent` is necessary for the Discuss module to run calls/video calls on Ubuntu (Linux) servers."
msgid "Use channels in the Odoo *Discuss* app to organize discussions between individual teams, departments, projects, or any other group that requires regular communication. With channels, employees can communicate inside dedicated spaces within the Odoo database around specific topics, updates, and latest developments having to do with the organization."
msgid "A *Public* channel can be seen by everyone, while a *Private* one is only visible to users invited to it. To create a new channel, navigate to the :menuselection:`Discuss` app, and then click on the :guilabel:`➕ (plus)` icon next to the :guilabel:`Channels` heading in the left-side menu. After typing the name of the channel, two selectable options will appear: The first is a channel with a hashtag (`#`) to indicate that it is a public channel; the second option is a channel with a lock icon (`🔒`) next to it, to indicate that it is a private channel. Select the channel type that best fits the communication needs."
msgid "A public channel is best used when many employees need to access information (such as company announcements), whereas a private channel could be used whenever information should be limited to specific groups (such as a specific department)."
msgid "The channel's :guilabel:`Group Name`, :guilabel:`Description`, and :guilabel:`Privacy` settings can be modified by clicking on the channel's settings, represented by a :guilabel:`⚙️ (gear)` icon in the left sidebar menu, next to the channel's name."
msgid "When choosing :guilabel:`Invited people only`, specify in the :guilabel:`Members` tab which members should be invited. Inviting members can also be done from the *Discuss* app's main dashboard, by selecting the channel, clicking the *add user* icon in the top-right corner of the dashboard, and finally clicking :guilabel:`Invite to Channel` once all the users have been added."
msgid "When the :guilabel:`Selected group of users` option is selected, it reveals the ability to add an :guilabel:`Authorized Group`, along with the options to :guilabel:`Auto Subscribe Groups` and :guilabel:`Auto Subscribe Departments`."
msgid "The option to :guilabel:`Auto Subscribe Groups` automatically adds users of that particular user group as followers. In other words, while :guilabel:`Authorized Groups` limits which users can access the channel, :guilabel:`Auto Subscribe Groups` automatically adds users as members as long as they are part of a specific user group. The same is true for :guilabel:`Auto Subscribe Departments`."
msgid "Once at least 20 channels, direct messages, or live chat conversations (if *Live Chat* module is installed on the database) are pinned in the sidebar, a :guilabel:`Quick search…` bar is displayed. This feature is a convenient way to filter conversations and quickly find relevant communications."
msgid "Click on the settings :guilabel:`⚙️ (gear)` icon, located in the left sidebar, to the right of the :guilabel:`CHANNELS` collapsible menu item. Doing so will lead to a mosaic view containing all the public channels available. Users can join or leave channels on this screen by clicking the :guilabel:`JOIN` or :guilabel:`LEAVE` buttons that appear in the channel boxes."
msgid "There is also the ability to apply filtering criteria and save them for later use. The :guilabel:`Search...` function accepts wildcards by using the underscore character [ `_` ], and specific searches can be saved by using the :menuselection:`Favorites --> Save Current Search` drop-down menu."
msgid "Channels can be linked in the chatter (log note) of a record in Odoo. To do so, simply type: `#` and the channel name. Click or press enter on the *channel* name. Upon logging the note a link to the channel will appear. After clicking on the link a chat window with the channel conversation will pop up in the lower right corner of the screen."
msgid "`Odoo Tutorials: Using Documents with your Accounting App [video] <https://www.odoo.com/slides/slide/using-documents-with-your-accounting-app-675?fullscreen=1#>`_"
msgid "By going to :menuselection:`Documents --> Configuration --> Settings`, you can enable the centralization of files attached to a specific area of your activity. For example, by ticking :guilabel:`Human Resources`, your HR documents are automatically available in the HR workspace, while documents related to Payroll are automatically available in the Payroll sub-workspace . You can change the default workspace using the dropdown menu and edit its properties by clicking the internal link button (:guilabel:`➔`)."
msgid "If you enable the centralization of your accounting files and documents, it is necessary to click on :guilabel:`Journals` and define each journal independently to allow automatic synchronization."
msgid "Workspaces are hierarchical folders having their own set of tags and :ref:`actions <documents/workflow-actions>`. Default workspaces exist, but you can create your own by going to :menuselection:`Documents --> Configuration --> Workspaces` and clicking :guilabel:`New`. On the new page, fill in the following information:"
msgid "Tags are used within workspaces to add a level of differentiation between documents. They are organized per category, and filters can be used to sort them."
msgid "Tags can be created from the :guilabel:`Tags` tab. Click :guilabel:`Add a line`, create the :guilabel:`Tag Category`, and :guilabel:`Name` your tags."
msgid "To manage your workspace access rights, go to :menuselection:`Documents --> Configuration --> Workspaces`, open the workspace you want to edit, and go to the :guilabel:`Access Rights` tab. You can add :guilabel:`Write Groups` that can view, create, and edit the workspace's documents. You can also add :guilabel:`Read Groups` that can only view the workspace's documents."
msgid "You can add descriptive information to your workspace by going to :menuselection:`Documents --> Configuration --> Workspaces`, opening the workspace you want to describe and going to the :guilabel:`Description` tab."
msgid "When selecting or opening a document, the right panel displays different options. On the top, additional options might be available: :guilabel:`Download`, :guilabel:`Share`, :guilabel:`Replace`, :guilabel:`Lock` or :guilabel:`Split`. It is also possible to :guilabel:`Open chatter` or :guilabel:`Archive` the document."
msgid "Then, you can modify the name of your file by clicking on :guilabel:`Document`. A :guilabel:`Contact` or an :guilabel:`Owner` can be assigned. The related :guilabel:`Workspace` can be modified and it is possible to access the related :guilabel:`Journal Entry` or add :guilabel:`Tags`."
msgid "The :guilabel:`Contact` is the person related to the document and assigned to it. He can only view the document and not modify it. I.e.: an existing supplier in your database is the contact for their bill."
msgid "The person who creates a document is, by default :guilabel:`Owner` of it and has complete rights to it. It is possible to replace the owner of a document. I.e., an employee must be owner of a document to be able to see it in \"My Profile\"."
msgid "Different :ref:`Actions <documents/workflow-actions>` are available at the bottom of the right panel, depending on the workspace where your document is stored."
msgid "By default, each page of the document will be split when clicking :guilabel:`Split`. To remove a split between two pages, click on the scissors icon."
msgid "To merge documents from your dashboard, select them and click the scissors icon. Click on the scissors between the two documents and click :guilabel:`Split` to merge the documents."
msgid "Select the workspace where the file should be stored, click :guilabel:`Upload`, then :guilabel:`Request`. Add the :guilabel:`Document Name`, select the person you need it from in the :guilabel:`Request To` field, fill in the :guilabel:`Due Date In`, confirm the :guilabel:`Workspace`, the document should belong to, and add :guilabel:`Tags` and a :guilabel:`Note`, if needed. Then, click :guilabel:`Request`. A placeholder for the missing document is created in the workspace."
msgid "From the :guilabel:`Activity` view, you can send a **reminder email** to users from whom you are expecting a document. Go to the :guilabel:`Requested Document` column, click on ⋮ and :guilabel:`Document Request: Reminder`."
msgid "Click on a date to see the details of a specific request. You can update it by clicking on the pen icon, :guilabel:`Preview` the content of the reminder email, or :guilabel:`Send Now` to send a reminder email."
msgid "You can create a share link to a document or all documents of a workspace. It allows anyone to download the file(s) or upload files to a workspace."
msgid "To do so, select the workspace or the document and click the arrow next to the :guilabel:`Upload` button then :guilabel:`Share`. On the pop-up, the share :guilabel:`URL` is displayed. :guilabel:`Copy` it to share it with anyone. :guilabel:`Name` the share link and set a validity date for the URL by filling in the :guilabel:`Valid Until` field. Tick the :guilabel:`Include Sub Folders` box if you also want to share a workspace's sub-folders. To let users upload their own documents, select :guilabel:`Download and Upload`."
msgid "To create a new :doc:`spreadsheet <spreadsheet>`, click :guilabel:`New Spreadsheet`. You can select a :guilabel:`Blank spreadsheet` or an :doc:`existing template <spreadsheet/templates>`."
msgid "Workflow actions help manage documents and overall business operations. These are automated actions that can be created and customized for each workspace. With a single click you can, for example, create, move, sign, and add tags to a document, and process bills."
msgid "You can :guilabel:`Create` a new :guilabel:`Action` or edit an existing one. You can define the :guilabel:`Action Name` and then set the conditions that trigger the appearance of the action button (:guilabel:`▶`) on the right-side panel when selecting a file."
msgid ":guilabel:`Tags`: you can use the :guilabel:`Contains` and :guilabel:`Does not contain` conditions, meaning the files *must have* or *mustn't have* the tags set here."
msgid "The :ref:`developer mode <developer-mode>` needs to be activated to access the :guilabel:`Domain` condition from the :guilabel:`Actions` tab. Once done, select the :guilabel:`Domain` condition type and click :guilabel:`Add condition`."
msgid "To create a rule, you typically select a :guilabel:`field`, an :guilabel:`operator`, and a :guilabel:`value`. For example, if you want to add a workflow action to all the PDF files inside a workspace, set the :guilabel:`field` to *Mime Type*, the :guilabel:`operator` to *contains*, and the pdf :guilabel:`value`."
msgid "Click :guilabel:`Add New Rule` (plus icon) and :guilabel:`Add branch` to add conditions and sub-conditions. You can then specify if your rule should match :guilabel:`all` or :guilabel:`any` conditions. You can also edit the rule directly using the :guilabel:`Code editor`."
msgid "**Activities - Schedule Activity**: create a new activity linked to the file as configured in the action. You can choose to set the activity on the document owner."
msgid "Documents available in the Finance workspace can be digitized. Select the document to digitize, click :guilabel:`Create Bill`, :guilabel:`Create Customer Invoice`, or :guilabel:`Create credit note`, and then click :guilabel:`Send for Digitization`."
msgid "**Odoo Knowledge** is a multipurpose productivity app that allows internal users to enrich their business knowledge base and provide individually or collaboratively gathered information."
msgid "The pages on which they gather content are called *articles*. They are mainly composed of a title and a body. The latter is an HTML field containing text, images, links to other articles, records from other models, templates, etc."
msgid "To start adding content, click anywhere on the page. Your cursor is automatically set to write the article's first-level header. Once you are done writing the title, press **enter** on your keyboard to move to the next line."
msgid "Click :guilabel:`Untitled` on the left side of the top bar to automatically match your h1 :dfn:`(First-level header)` title and the article's name. To change the name of your article later, you must do it manually. To do so, click the name on the top bar and proceed to the modification."
msgid "Change the style by clicking :guilabel:`Normal`. Doing so opens a dropdown menu with multiple styles to choose from (:guilabel:`Normal, Code, Header 1 → Header 6, Quote`);"
msgid "Format the text. Click :guilabel:`B` to put it in bold, :guilabel:`I` to put it in italic, :guilabel:`U` to underline, and :guilabel:`S` to strikethrough;"
msgid "You can customize your article by adding a cover picture and an icon. Hover above the h1 title and click :guilabel:`Add Cover`. A pop-up window opens to set a cover picture."
msgid "If your database and your Unsplash account are associated, the cover picture is automatically selected based on the article's name. To modify it, hover over the picture to make the buttons appear, click :guilabel:`Change Cover`, and select another image."
msgid "The articles are responsive, and so are the cover pictures. As a result, the images cannot be repositioned manually to fit a particular screen, as they automatically resize depending on the device."
msgid "To add an icon, hover above the h1 title and click :guilabel:`Add Icon`. Doing this sets a random emoji automatically. To change it, click it and select one from the emoji window. To remove it, proceed equally and click the red-circled :guilabel:`x`."
msgid "To use a command, type `/` and open the **powerbox**. Type the command's name or select from multiple features to insert blocks, images, files, etc. Some of them, such as `/Image` or `/Article` are common to all the apps, but others are inherent to the knowledge app and cannot be found or used in any other application."
msgid "Knowledge allows to retrieve content views from other applications. To do so, go to the targeted app and create the desired view. Then, click :menuselection:`Favorite --> Insert view in article` and select an article. The view is inserted at the bottom of the selected article."
msgid "To retrieve the view below, we created it by going to :menuselection:`Sales --> Graph icon --> Pie Chart icon` and inserted it by clicking :menuselection:`Favorite --> Insert view in article` and selecting the *Sales Playbook* article."
msgid "Users who do **not** have access to the view will **not** be able to access it in **Knowledge** even though they have access to the article containing the view."
msgid "Managing articles effectively is key to maximizing the value of your knowledge resources, whether working on a research project, studying for an exam, or building a knowledge database for your business. Knowledge allows you to fully manage your articles, from :ref:`creation <management/create>` to :ref:`removal <management/remove>`, through :ref:`sharing <management/share>` and :ref:`structure <management/structure>`."
msgid "You can find most tools to manage articles by clicking the vertical ellipsis button (:guilabel:`⋮`) at the right side of the top bar. From there, you can move, lock, delete, or duplicate an article."
msgid "To create articles, click the :guilabel:`+ New` button on the right side of the top bar or the :guilabel:`+` button next to a category or another article."
msgid "You can share articles with internal or external users. To do so, open the share menu by clicking :guilabel:`Share` in the top-right menu of articles."
msgid "To share articles with specific users (internal or external, such as a partner or a customer), click :guilabel:`Invite`. This opens a pop-up window in which you can choose the :guilabel:`Permission` :ref:`(i.e, access rights) <management/categories>` and enter the :guilabel:`Recipients`' name or email."
msgid "Additionally, the share menu displays the default permission for internal members along with all the users who have been granted specific permission."
msgid "To delete an article, open it and click the vertical ellipsis button :menuselection:`(⋮) --> Delete`. The article is moved to the trash for 30 days before being permanently deleted. To restore it, click :guilabel:`Open the Trash`, select the article, and click :guilabel:`Restore`."
msgid "To archive articles, click :guilabel:`Search`, select the article(s), and click :menuselection:`Action --> Archive --> Archive`. Archived articles are hidden from the search menu. To retrieve an archived article, add a custom filter to display them (:menuselection:`Search --> Filters --> Add Custom Filter`, and set :guilabel:`Active` as :guilabel:`is No`). Then, select the article(s) and go to :menuselection:`Action --> Unarchive`."
msgid "Articles are organized into a hierarchical structure wherein the article on top is a parent article, and those underneath are called nested articles. This structure allows the grouping of related articles."
msgid "To establish this hierarchy, create new articles by clicking the :guilabel:`+` button next to the parent-to-be article, or move existing articles by either dragging and dropping them under the parent-to-be or by clicking the vertical ellipsis button (:guilabel:`⋮`), clicking :guilabel:`Move To` on the toolbox and selecting the article to use as a parent."
msgid "Additionally, articles are divided into four categories that can be found on the left sidebar. These categories give articles default **access rights**."
msgid ":guilabel:`Favorites`: You can set any article you can access as a favorite. To do so, click the star-shaped icon (:guilabel:`★`) in the top-right menu of articles. Marking articles as **favorites** is user-specific and does not affect other users."
msgid ":guilabel:`Workspace`: Articles displayed in that category are available to all internal users. These users have the right to read, modify or share these articles."
msgid "Properties are fields containing data and that can be added to articles by any user with **write** access. These fields are shared between all the child articles and article items under the same parent."
msgid "Hover above the first-level header to make the buttons appear. Click :menuselection:`⚙ Add Properties --> Field Type`, select the type and add a default value if needed. To make the fields appear in **kanban views**, check :guilabel:`View in Kanban` as well. To validate and close the property creation window, click anywhere."
msgid "To set it up, click :guilabel:`Add a Value` next to the :guilabel:`Values` field. Enter predetermined values and press **enter** to validate; you can enter as many values as needed. Click anywhere to close the property creation window."
msgid "To set it up, enter your `new_tag` in the :guilabel:`Tags` field, and press **enter** or click :guilabel:`Create \"new_tag\"`. Click anywhere to close the window. Then, add the tags into the property field. To do so, click the property field and choose from the created tags; enter the tags' name and press **enter**; enter a new tag's name and create a new one on the spot."
msgid "To set it up, click :guilabel:`Search a Model` in the :guilabel:`Model` field, select the model. Match all records by clicking :guilabel:`## Record(s)`, or filter the results by clicking :guilabel:`+ Add Filter` and show the records by clicking :guilabel:`## Record(s)`."
msgid "An **electronic signature** shows a person's agreement to the content of a document. Just like a handwritten signature, the electronic one represents a legal bounding by the terms of the signed document."
msgid "With Sign, you can upload any PDF file and add fields to it. These fields can be automatically filled in with the user's details present in your database."
msgid "Documents signed via the Sign app are valid electronic signatures in the European Union and the United States of America. They also meet the requirements for electronic signatures in most countries. The legal validity of electronic signatures generated by Odoo depends on your country's legislation. Companies doing business abroad should also consider other countries' electronic signature laws."
msgid "The `eIDAS regulation <http://data.europa.eu/eli/reg/2014/910/oj>`_ establishes the framework for electronic signatures in the `27 member states of the European Union <https://europa.eu/european-union/about-eu/countries_en>`_. It distinguishes three types of electronic signatures:"
msgid "Odoo generates the first type, **simple electronic signatures**; these signatures are legally valid in the EU, as stated in the eIDAS regulation."
msgid "Electronic signatures may not be automatically recognized as valid. You may need to bring supporting evidence of a signature's validity. While the Sign app provides a simple electronic signature, some supporting evidence is automatically collected during the signature process, such as:"
msgid "The `ESIGN Act (Electronic Signatures in Global and National Commerce Act) <https://www.fdic.gov/regulations/compliance/manual/10/X-3.1.pdf>`_, at the interstate and international levels, and the `UETA (Uniform Electronic Transactions Act) <https://www.uniformlaws.org/committees/community-home/librarydocuments?communitykey=2c04b76c-2b7d-4399-977e-d5876ba7e034&tab=librarydocuments>`_, at the state level, provide the legal framework for electronic signatures. Note that `Illinois <https://www.ilga.gov/legislation/ilcs/ilcs5.asp?ActID=89&>`_ and `New York <https://its.ny.gov/electronic-signatures-and-records-act-esra>`_ have not adopted the UETA, but similar acts instead."
msgid "The signer must show a clear **intent to sign**. For example, using a mouse to draw a signature can show intent. The signer must also have the option to opt out of the electronic document."
msgid "**The signature must be clearly attributed**. In Odoo, metadata, such as the signer's IP address, is added to the signature, which can be used as supporting evidence."
msgid "Electronically signed documents need to be **retained and stored** by all parties involved; for example, by providing the signer either a fully-executed copy or the possibility to download a copy."
msgid "The above information has no legal value; it is only provided for general informational purposes. As laws governing electronic signatures rapidly evolve, we cannot guarantee that all information is up-to-date. We advise contacting a local attorney for legal advice regarding electronic signature compliance and validity."
msgid "You can click :guilabel:`Upload a PDF to sign` from your dashboard for a one-time signature. Select your document, open it, and drag and drop the required :ref:`fields <sign/fields>` in your document. You can modify the :ref:`role <sign/role>` assigned to a field by clicking on it and selecting the one you want."
msgid "When ready, click :guilabel:`Send`, and fill in the required fields. Once sent, your document remains available. Go to :menuselection:`Documents --> All Documents` to see your document and the status of the signatures."
msgid "You can set **validity dates** on limited-duration agreement documents or send **automatic email reminders** to obtain signatures on time. From your dashboard, click :guilabel:`Send` on your document. On the new page, go to the :guilabel:`Options` section and fill in the :guilabel:`Valid Until` and :guilabel:`Reminder` fields."
msgid "You can create document templates when you have to send the same document several times. From your dashboard, click :guilabel:`Upload a PDF template`. Select the document and add the required :ref:`fields <sign/fields>`. You can modify the :ref:`role <sign/role>` of a field by clicking on it and selecting the one you want."
msgid "Click :guilabel:`Template Properties` to add :guilabel:`Tags` to your template, define a :guilabel:`Signed Document Workspace`, add :guilabel:`Signed Document Tags`, set a :guilabel:`Redirect Link` that will be available in the signature confirmation message received after the signature, or define :guilabel:`Authorized Users` if you want to restrict the use of your template to specific authorized users or groups."
msgid "Your templates are visible by default on your dashboard. You can click :guilabel:`Send` to quickly send a document template to a signer or :guilabel:`Sign Now` if you are ready to sign your document immediately."
msgid "You can **create a template from a document that was previously sent**. To do so, go to :menuselection:`Documents --> All Documents`. On the document you want to retrieve, click on the the vertical ellipsis (:guilabel:`⋮`), then :guilabel:`Template`. Click on the vertical ellipsis (:guilabel:`⋮`) again, then :guilabel:`Restore`. Your document now appears on your dashboard next to your other templates."
msgid "Each field in a Sign document is related to a role corresponding to a specific person. When a document is being signed, the person assigned to the role must fill in their assigned fields and sign it."
msgid "It is possible to update existing roles or to create new roles by clicking on :guilabel:`New`. Choose a :guilabel:`Role Name`, add an :guilabel:`Extra Authentication Step` to confirm the identity of the signing person, and if the document can be reassigned to another contact, select :guilabel:`Change Authorized` for the role. A :guilabel:`Color` can also be chosen for the role. This color can help understand which roles are responsible for which field when configuring a template."
msgid "As the owner of a document, you may request an :guilabel:`Extra Authentication Step` through :ref:`SMS verification <sign/sms>` or via :ref:`Itsme® <sign/itsme>` (available in Belgium and the Netherlands). Both authentication options require :ref:`credits <iap/buying_credits>`. If you do not have any credits left, the authentication steps will be skipped."
msgid "Go to :menuselection:`Sign --> Configuration --> Roles`. Click in the :guilabel:`Extra Authentication Step` column for the role, and select :guilabel:`Unique Code Via SMS`."
msgid "Before being able to send SMS Text Messages, you need to register your phone number. To do so, go to :menuselection:`Sign --> Configuration --> Settings` and click :guilabel:`Buy credits` under :guilabel:`Authenticate by SMS`."
msgid "Go to the document to sign, add the field for which the SMS verification is required, for example, the :guilabel:`Signature` field, and click :guilabel:`Send`. On the new page, select the :guilabel:`customer` and click :guilabel:`Send`."
msgid "The person signing the document fills in the :guilabel:`Signature` field, then :guilabel:`Sign`, and clicks :guilabel:`Validate & Send Completed Document`. A :guilabel:`Final Validation` page pops up where to add their phone number. One-time codes are sent by SMS."
msgid "Itsme® authentication can be used to allow signatories to provide their identity using itsme®. This feature is only available in **Belgium** and the **Netherlands**."
msgid "The feature can be enabled in :guilabel:`Sign Settings` and applies automatically to the :guilabel:`Customer (identified with itsme®)` role. To enable it for other roles, go to :menuselection:`Sign --> Configuration --> Roles`. Click in the :guilabel:`Extra Authentication Step` column for the role, and select :guilabel:`Via itsme®`."
msgid "Go to the document that needs to be signed and add the :guilabel:`Signature` field. Switch to any role configured to use the feature, and click :guilabel:`Validate` and :guilabel:`Send`."
msgid "Upon signing the document, the signer completes the :guilabel:`Signature` field and proceeds by clicking on :guilabel:`Validate & Send Completed Document`, triggering a :guilabel:`Final verification` page where authentication via itsme® is required."
msgid "Each time someone signs a document, a **hash** - a unique digital signature of the operation - is generated to ensure traceability, integrity, and inalterability. This process guarantees that any changes made after a signature is affixed can be easily detected, maintaining the document's authenticity and security throughout its lifecycle."
msgid "A visual security frame displaying the beginning of the hash is added to the signatures. Internal users can hide or show it by turning the :guilabel:`Frame` option on or off when signing the document."
msgid "You can manage tags by going to :menuselection:`Configuration --> Tags`. To create a tag, click :guilabel:`New`. On the new line, add the :guilabel:`Tag Name` and select a :guilabel:`Color Index` for your tag."
msgid "You can modify the tags of a signed document by going to :menuselection:`Documents --> All Documents`, clicking the vertical ellipsis (:guilabel:`⋮`) on your document, then :guilabel:`Details`, and modifying your :guilabel:`Tags`."
msgid "When a document needs to be signed by different parties, the signing order lets you control the order in which your recipients receive it for signature."
msgid "After uploading a PDF with at least two signature fields with two different roles and clicking :guilabel:`Send`, toggle the :guilabel:`Specify Signing Order` button and search for the signer's name or email information to add them. You can decide on the signing order by typing **1** or **2** in the first column."
msgid "Fields are used in a document to indicate what information must be completed by the signers. You can add fields to your document simply by dragging and dropping them for the left column into your document."
msgid "Various field types can be used to sign documents (placeholder, autocompletion, etc.). By configuring your own field types, also known as signature item types, the signing process can be even faster for your customers, partners, and employees."
msgid "You can select an existing field by clicking on it, or you can :guilabel:`Create` a new one. First, edit the :guilabel:`Field Name`. Then, select a :guilabel:`Field Type`:"
msgid ":guilabel:`Signature`: users are asked to enter their signature either by drawing it, generating an automatic one based on their name, or uploading a local file (usually an image). Each subsequent :guilabel:`Signature` field type then reuses the data entered in the first field."
msgid "The :guilabel:`Auto-fill Partner Field` setting is used to automatically fill in a field during the signature process. It uses the value of one of the fields on the contact (`res.partner`) model of the person signing the document. To do so, enter the contact model field's technical name."
msgid "The size of the fields can also be changed by editing the :guilabel:`Default Width` and :guilabel:`Default Height`. Both sizes are defined as a percentage of the full page expressed as a decimal, with 1 equalling the full page's width or height. By default, the width of new fields you create is set to 15% (0.150) of a full page's width, while their height is set to 1.5% (0.015) of a full page's height."
msgid "Next, write a :guilabel:`Tip`. Tips are displayed inside arrows on the left-hand side of the user's screen during the signing process to help them understand what the step entails (e.g., \"Sign here\" or “Fill in your birthdate”). You can also use a :guilabel:`Placeholder` text to be displayed inside the field before it is completed."
msgid "Before inserting :ref:`pivots <reporting/views/pivot>`, :ref:`graphs <reporting/views/graph>`, or lists, ensure they are tailored to your needs, as some elements are more quickly - or only - configurable in their respective view."
msgid "In the pop-up box, either create a new spreadsheet by selecting :guilabel:`Blank spreadsheet` or insert it in an existing one by selecting it and clicking :guilabel:`Confirm`."
msgid "Once inserted in a spreadsheet, your data is kept up-to-date, reflecting any changes made to your database. Reopening the spreadsheet reloads the linked data."
msgid "Using :guilabel:`Refresh all data` only updates existing pivot cells. If new cells need to be added, go to the menu bar and click :menuselection:`Data --> Re-insert pivot` to fully update the pivot. Alternatively, click :guilabel:`Insert pivot`, select the pivot, and tick :guilabel:`Display missing cells only` to preview first the missing data."
msgid "To change which records are :ref:`used by the pivot <search/preconfigured-filters>`, right-click on a pivot cell, select :guilabel:`See pivot properties`, and click :guilabel:`Edit domain`."
msgid "Budget reports compare a company's actual spending with its budget over a defined period. Two templates are available: one uses quarterly intervals (:guilabel:`Budget Report (Quarterly)`), while the other uses monthly intervals (:guilabel:`Budget Report (Monthly)`)."
msgid "The cells under the :guilabel:`Actuals` column are automatically filled in with the amount of money made and spent over the corresponding period (month or quarter). The data is taken from posted journal items under :ref:`income and expense accounts <chart-of-account/type>`."
msgid "To analyze your budget's performance, fill the cells under the :guilabel:`Budget` column with how much money you expect to make (:guilabel:`Income` rows) and spend (:guilabel:`Expenses` rows) over the related period and per account. Then, the performance (:guilabel:`Perf.`) column compares :guilabel:`Actuals` data to their corresponding budget, expressed as a percentage."
msgid "Lastly, the :guilabel:`Net Profit` row represents the total :guilabel:`Income` minus the total :guilabel:`Expenses` for the :guilabel:`Actuals` and :guilabel:`Budget` columns."
msgid "For the :guilabel:`Revenue by Salesperson` sheet, open the :guilabel:`Targets` sheet and fill in the cells next to each salesperson. Use the :guilabel:`Monthly Factor` table below to adapt the main targets depending on the month of the year."
msgid "The recurring monthly revenue is used even if the recurring plan's number of months is set to a different value than 1 month. For example, a yearly plan's revenue is divided by 12 months."
msgid "The :guilabel:`Rate` column is pre-filled with the percentage rate from the :guilabel:`Rates` tab, which can be customized for each product category according to the company's policy. Adjusting the rate for a specific product category automatically updates the commission amount for that category."
msgid "Any spreadsheet can be saved as a template. From the menu bar, click :menuselection:`File --> Save as template`. Modify the default :guilabel:`Template Name` if necessary and click :guilabel:`Confirm`."
msgid "Manage templates by going to :menuselection:`Documents --> Configuration --> Spreadsheet Templates`. Remove the :guilabel:`My Templates` :ref:`filter <search/preconfigured-filters>` to view all templates in the database."
msgid "To create a to-do, click :guilabel:`New` or the plus button (:guilabel:`➕`) next to a stage name. Add a title to your to-do, then click :guilabel:`Add` to save it or :guilabel:`Edit` to access more options."
msgid "If you choose to :guilabel:`Edit` a to-do, you have the option to add :guilabel:`Tags`, :guilabel:`Assignees`, or more information using the Odoo Editor."
msgid "You can create a new to-do on the fly from anywhere in Odoo by opening the **command palette tool** with the keyboard shortcut ´ctrl+k´ and clicking :guilabel:`Add a To-Do`, or by clicking the clock button and then :guilabel:`Add a To-Do`."
msgid "If you use the :doc:`Project app <../services/project>`, you can convert to-dos into project tasks. To do so, open a to-do and click the gear button (:guilabel:`⚙`), then :guilabel:`Convert to Task`."
msgid "Next, select the :guilabel:`Project`, :guilabel:`Assignees`, and :guilabel:`Tags`, then click :guilabel:`Convert to Task`. The to-do is now a project task and appears in the selected project."
msgid "Odoo VoIP (Voice over Internet Protocol) can be set up to work together with `Axivox <https://www.axivox.com/>`_. In that case, an Asterisk server is **not** necessary, as the infrastructure is hosted and managed by Axivox."
msgid "To use this service, `contact Axivox <https://www.axivox.com/contact/>`_ to open an account. Before doing so, verify that Axivox covers the company's area, along with the areas the company's users wish to call."
msgid "Access the domain on the Axivox administrative panel by navigating to `https://manage.axivox.com/ <https://manage.axivox.com/>`_. After logging into the portal, go to :menuselection:`Users --> Edit (next to any user) --> SIP Identifiers tab --> Domain`."
msgid "In Odoo, go to :menuselection:`Settings app --> Users & Companies --> Users`, then open the desired user's form to configure :abbr:`VoIP (Voice over Internet Protocol)`. Under the :guilabel:`Preferences` tab, fill out the :guilabel:`VOIP Configuration` section:"
msgid "Access the domain on the Axivox administrative panel by navigating to `https://manage.axivox.com/ <https://manage.axivox.com/>`_. After logging into the portal, go to :menuselection:`Users --> Edit (next to the user) --> SIP Identifiers tab --> SIP username / SIP password`."
msgid "When entering the :guilabel:`SIP Password` into the user's :guilabel:`Preferences` tab, this value **must** be typed out manually and **not** pasted in. Pasting in causes a `401 server rejection error`."
msgid "A call queue is a system that organizes and routes incoming calls. When customers call a business, and all of the agents are busy, the call queue lines up the callers in sequential order, based on the time they called in."
msgid "Implementing a call queue system reduces stress for employees, and helps build brand trust with customers. Many companies use call queues to set expectations with customers, and to distribute the workload equally amongst employees."
msgid "This document covers the process required to configure call queues (with advanced settings), as well as how to log into a call queue from the Odoo database."
msgid "To add a call queue in Axivox, navigate to the `Axivox management console <https://manage.axivox.com>`_. In the left menu, click :guilabel:`Queues`. Next, click :guilabel:`Add a queue`. Doing so reveals a blank :guilabel:`New queue` form with various fields to fill out."
msgid "Choose an :guilabel:`Internal extension` for the queue. This is a number to be dialed by users of the database to reach the login prompt for the queue."
msgid "In the :guilabel:`Maximum waiting time in seconds` field, determine the longest time a customer waits in the queue before going to a voicemail, or wherever else they are directed to in a dial plan. Enter a time in seconds."
msgid "In the :guilabel:`Maximum duration of ringing at an agent` field, determine the longest time an individual agent's line rings before moving on to another agent, or moving to the next step in the dial plan. Enter a time in seconds."
msgid "The final two fields on the :guilabel:`New queue` form revolve around adding agents. Adding :guilabel:`Static agents` and :guilabel:`Dynamic agents` are two pre-configured methods for adding agents onto the call queue during the configuration."
msgid "When :guilabel:`Dynamic agents` are added, these agents have the ability to log into this queue. They are **not** logged-in automatically, and **must** log in to receive calls."
msgid "After the initial configuration of the call queue is completed, with the changes saved and implemented, a manager can log into the `Axivox management console <https://manage.axivox.com>`_ and connect dynamic agents to the queue manually."
msgid "To connect an agent, click :guilabel:`Queues`, located in the left-hand column. Doing so reveals the :guilabel:`Queues` dashboard, with a few different columns listed:"
msgid "Connect an agent by clicking the orange button labeled, :guilabel:`Connect an agent`. Then, select the desired agent's name from the drop-down menu, and click :guilabel:`Connect`."
msgid "Click :guilabel:`Report` to check on the reporting for a particular queue, in order to see who connected when, and what phone calls came in and out of the queue. This information is showcased on a separate :guilabel:`Queue report` page, when the green :guilabel:`Report` button is clicked."
msgid "Reports can be customized by date in the :guilabel:`Period` field, and specified in the :guilabel:`From` and :guilabel:`to` fields. The information can be organized by :guilabel:`Event type`, and :guilabel:`Call ID`."
msgid "Each report can be exported to a :abbr:`CSV (comma separated value)` file for further use and analysis, via the :guilabel:`Export to CSV` button."
msgid "Clicking :guilabel:`Check all` selects all the available options from the drop-down menu, and clicking :guilabel:`Uncheck all` removes all selections from the drop-down menu."
msgid "Dynamic agents can connect manually to the Axivox call queue from the Odoo *VoIP* widget, once the *VoIP* app is configured for the individual user in Odoo."
msgid "For an agent to connect to the call queue, simply dial the :guilabel:`Agent connection` number, and press the green call button :guilabel:`📞 (phone)` icon in the *VoIP* widget. Then, the agent hears a short, two-second message indicating the agent is logged in. The call automatically ends (disconnects)."
msgid "To view the connected agents in a call queue, navigate to the `Axivox management console <https://manage.axivox.com>`_, and click :guilabel:`Queues`, located in the left-hand column."
msgid "Then, click the green :guilabel:`Refresh` button at the top of the :guilabel:`Connected agents` column. Any agent (static or dynamic) that is connected to the queue currently, appears in the column next to the queue they are logged into."
msgid "To log out of the queue, open the Odoo *VoIP* widget, dial the :guilabel:`Agent disconnection` number, and press the green call button :guilabel:`📞 (phone)` icon. The agent is disconnected from the queue after a short, two-second message."
msgid "To manually log a dynamic agent out of a call queue, navigate to the `Axivox management console <https://manage.axivox.com>`_, and click :guilabel:`Queues`, located in the left-hand column. Then, click the green :guilabel:`Refresh` button at the top of the :guilabel:`Connected agents` column."
msgid "To disconnect an agent manually, click the red :guilabel:`Disconnect` button, and they are immediately disconnected. This can be helpful in situations where agents forget to log out at the end of the day."
msgid "Conference calls help employees connect quickly and efficiently, so matters can be discussed in an open forum of sorts. Attendees can be limited, via a sign-in code. That way, confidential matters stay private."
msgid "To add a virtual conference room, navigate to the `Axivox management console <https://manage.axivox.com>`_. After logging in, click on :guilabel:`Conferences` in the menu on the left."
msgid "The internal extension is what everyone in the network uses to quickly dial into the conference call, instead of typing in the whole phone number."
msgid "Next, set the :guilabel:`Access code`, if the conference room requires security. This is a password to get into the conference, once the extension for the conference is dialed. Immediately after dialing the extension, a digital receptionist prompts for the :guilabel:`Access code`."
msgid "Finally, in the :guilabel:`Wait for the administrator to start the conference` field, click the drop-down menu, and select :guilabel:`Yes` or :guilabel:`No`."
msgid "Should the selection be :guilabel:`Yes`, then nobody is allowed to utilize the virtual conference room until the administrator is present, and logged into the conference call."
msgid "When all fields are filled in, be sure to :guilabel:`Save` the configuration. Then, click :guilabel:`Apply changes` in the upper-right corner to implement the change in production."
msgid "Upon doing so, the conference is added, and the Axivox administrator has the option to :guilabel:`Delete` or :guilabel:`Edit` the conference from the Axivox :guilabel:`Conference` main dashboard."
msgid "To invite an Axivox user to a specific conference call, click :guilabel:`Invite` to the right of the desired conference, and proceed to enter the extension or phone number of the invitee in the pop-up window that appears."
msgid "Once the extension or number is added into the :guilabel:`Please enter the phone number of the person you want to invite` field, click the green :guilabel:`Invite` button, and the recipient immediately receives a phone call, automatically linking them to the conference."
msgid "To do that, log into the `Axivox management console <https://manage.axivox.com>`_, and click :guilabel:`Incoming numbers` in the menu on the left."
msgid "On the :guilabel:`Incoming numbers` dashboard, click :guilabel:`Edit` to the far-right of the :guilabel:`Number` to which the conference should be attached."
msgid "Then, under the first field, labeled, :guilabel:`Destination type for voice call`, click the drop-down menu, and select :guilabel:`Conference`."
msgid "Next, in the :guilabel:`Conference` field, click the drop-down menu, and select the specific conference that should be attached to this incoming number."
msgid "Now, whenever this incoming number is dialed, the caller is let into the conference, if there is not an :guilabel:`Access code` required. If there *is* an :guilabel:`Access code` required, the caller is then prompted to enter the :guilabel:`Access code` to enter the conference."
msgid "Anywhere in the Odoo database, open the *VoIP* widget, by clicking the :guilabel:`☎️ (phone)` icon, located in the upper-right corner. Then, dial the specific extension number for the conference, and click the :guilabel:`📞 (phone)` icon."
msgid "By using Axivox advanced dial plan features, the process can be automated, and routing can be set up for all scenarios. This way, customers are never left waiting, or frustrated, because they cannot get in touch with anyone."
msgid "By utilizing the advanced elements in dial plans, companies can automate call routing for certain days or times, like company holidays. Companies can also allow callers to enter extensions themselves, and get transferred automatically using a digital receptionist. This way, an administrative team does **not** have to be available around the clock."
msgid "Using a browser add-on for spelling may hinder the use of the visual editor in dial plans. Do **not** use a translator with the Axivox management console."
msgid "To add one of these elements, navigate to the :guilabel:`Dial plans` page, located in the menu on the left side of the `Axivox management console <https://manage.axivox.com>`_."
msgid "Next, click on the :guilabel:`Visual Editor` button to the right of the desired dial plan to edit it. Finally, open the :guilabel:`New element` drop-down menu, select the element, and click :guilabel:`Add`."
msgid "To enable recording on Axivox, navigate to :guilabel:`Settings` in the `Axivox management console <https://manage.axivox.com>`_. Then, go to the :guilabel:`Recording` drop-down menu, near the bottom of the page. From there, select :guilabel:`Enabled` from the drop-down menu to enable recording using the :guilabel:`Record` element in a dial plan."
msgid "The first is a :guilabel:`Free text` field, where any text can be input to replace the caller ID. The second option is :guilabel:`Replace the caller ID by the called number`. This option replaces the caller's ID with the :guilabel:`Incoming number`."
msgid "A company may want to use the :guilabel:`Caller ID` element to replace the :guilabel:`Incoming number`, so employees, or outside transfers, cannot see the number, and information is kept private."
msgid "Basic routing elements in Axivox dial plans provide extension-based routing. This can be done by adding either a *Menu* to numerically link the dial-by-numbers to an action, or by using a *Digital Receptionist* to automatically route or listen for an extension, based on a key input from the caller."
msgid "The main difference between the two elements is that the *Digital Receptionist* does **not** need to be pre-configured numerically with actions. Instead, it acts as a virtual receptionist."
msgid ":guilabel:`Menu`: add a dial-by-number directory and configured downstream actions (not terminal). For example, a dial-by-numbers function could feature an element, wherein clicking '2' takes the caller to the element linked to '2' on the Menu element in the dial plan."
msgid "To add one of these elements, navigate to the :guilabel:`Dial plans` page, located in the menu on the left side of the `Axivox management console <https://manage.axivox.com>`_. Next, click on the :guilabel:`Visual Editor` button to the right of the dial plan, to edit the dial plan. Then, open the :guilabel:`New element` drop-down menu, select the element, and click :guilabel:`Add`."
msgid "The *Digital Receptionist* element is a listen-feature that accurately routes callers through a dial plan, based on the extension they enter, via the key pad."
msgid "Set a *Digital Receptionist* to eliminate the need of a team, or live receptionist, to be on-call all the time. With that element in place, calls now reach their destination, without a real person interjecting."
msgid "After adding the :guilabel:`Digital Receptionist` element to a dial plan, connect the appropriate endpoints, and double-click on the element to set the :guilabel:`Timeout` on the :guilabel:`receptionist` pop-up window that appears."
msgid "The :guilabel:`Digital Receptionist` element **requires** a :guilabel:`Play a file` element on either side of it, to explain what action to take, and when a wrong extension is entered."
msgid "While customizing a dial plan in a :guilabel:`Dialplan Editor` pop-up window, add a :guilabel:`Menu` element, with a :guilabel:`Greeting message` that might read, `Press star to dial an extension`."
msgid "Then, on the :guilabel:`Menu` element, for the :guilabel:`* (star)` option, link a :guilabel:`Play a file` element, that plays an :guilabel:`Audio message` saying, 'Enter the extension of the person you are trying to reach'."
msgid "Following the first :guilabel:`Play a file` element, add the :guilabel:`Digital Receptionist` element, followed by another :guilabel:`Play a file` element, which states, 'That is not a valid extension'."
msgid "Advanced routing elements route calls automatically as they are received into the incoming number(s). This can be configured using geo-location, whitelisting, or time-based variables. Calls pass through a filter prior to their final destination, and are routed, based on the set variable(s)."
msgid "Whitelisting is a technical term used to create a list of allowed numbers. Conversely, blacklisting is used to create a list of denied numbers."
msgid "To add one of these elements, navigate to the :guilabel:`Dial plans` page, located in the menu on the left side of the `Axivox management console <https://manage.axivox.com>`_. Next, click on the :guilabel:`Visual Editor` button to the right of the dial plan, to edit the dial plan. Then, open the :guilabel:`New element` drop-down menu, select the element, and click :guilabel:`Add`. For more information, visit :ref:`voip/axivox/dial_plans`."
msgid "A *Dispatcher* element is a dial plan feature that directs calls, based on region or geo-location. In most cases, the :guilabel:`Dispatcher` element in a dial plan is linked to the :guilabel:`Start` element, in order to filter or screen calls as they come into an incoming number."
msgid "This element checks numbers (routed through this element), according to regular expressions. To add a regular expression, click :guilabel:`Add a line` on the bottom of the :guilabel:`Dispatcher` pop-up window."
msgid "Then, under :guilabel:`Name`, enter a recognizable name to identify this expression. This is the name that appears in the :guilabel:`Dispatcher` element on the dial plan showcased in the :guilabel:`Dialplan Editor` pop-up window."
msgid "In the :guilabel:`Regular expression` field, enter the country code, or area code, which Axivox should route for incoming calls. This is especially helpful when a company would like to filter their customers to certain queues, or users based on the customer's geo-location."
msgid "A regular expression (shortened to \"regex\" or \"regexp\"), sometimes referred to as a \"rational expression,\" is a sequence of characters that specifies a match pattern in text. In other words, a match is made within the given range of numbers."
msgid "Upon doing so, the :guilabel:`Dispatcher` element appears with different routes available to configure, based on the :guilabel:`Regular Expressions` that were set."
msgid "By default, there is an :guilabel:`Unknown` path that appears on the :guilabel:`Dispatcher` element after setting at least one :guilabel:`Regular Expression`."
msgid "After adding the :guilabel:`Time Condition` element to a dial plan, double-click it to configure the variables. :guilabel:`Hour/Minute`, :guilabel:`Days of the week`, :guilabel:`Day of the month`, and :guilabel:`Month` can all be configured."
msgid "If the time which the caller contacts the incoming number matches the set time conditions, then the :guilabel:`True` path is followed, otherwise the :guilabel:`False` path is followed."
msgid "The :guilabel:`Time Condition` element is especially useful for holidays, weekends, and to set working hours. When a caller reaches a destination where they can be helped, either with a real person or voicemail, this reduces wasted time and hangups."
msgid "To set the :guilabel:`Timezone` that the :guilabel:`Time Condition` operates under, navigate to `Axivox management console <https://manage.axivox.com>`_, and click :guilabel:`Settings` in the menu on the left. Then, set the :guilabel:`Timezone` using the second field from the bottom, by clicking the drop-down menu."
msgid "After adding an :guilabel:`Access List` element to a dial plan, it can be configured by double-clicking on the element directly in the :guilabel:`Dialplan Editor` pop-up window."
msgid "Two fields appear where regular expressions can based in the :guilabel:`Allow` and :guilabel:`Deny` fields of the :guilabel:`Access List` pop-up window."
msgid "A regular expression (shortened to \"regex\" or \"regexp\"), sometimes also referred to as a \"rational expression,\" is a sequence of characters that specifies a match pattern in text."
msgid "After setting the :guilabel:`Allow` and :guilabel:`Deny` fields with regular expressions or numbers, click :guilabel:`Save` on the :guilabel:`Access List` pop-up window."
msgid "Unknown calls can be routed through the regular menu flow by adding a :guilabel:`Menu` element, and connecting it to the :guilabel:`Unknown` path. :guilabel:`Refused` calls can be routed to the :guilabel:`Hang up` element. Lastly, :guilabel:`Authorized` callers can be sent to a specific extension or queue."
msgid "Alternate routes can be configured, so that in a moments notice, they can be switched to. This could be for new availability, or to adjust traffic flow for any number of reasons."
msgid "A :guilabel:`Switch` can be set in the `Axivox management console <https://manage.axivox.com>`_ by navigating to :guilabel:`Switches` in the left menu. To create a new switch click :guilabel:`Add a switch` from the :guilabel:`Switches` dashboard, configure a :guilabel:`Name` for it, and click :guilabel:`Save`."
msgid "Then, toggle the desired switch to either :guilabel:`On` or :guilabel:`Off`, from the :guilabel:`State` column on the :guilabel:`Switches` dashboard."
msgid "The traffic travels to the :guilabel:`Active` route when :guilabel:`On` is toggled in the switch. The call traffic travels to the :guilabel:`Inactive` route when :guilabel:`Off` is toggled in the switch."
msgid "To add a :guilabel:`Switch` to a dial plan, navigate to `Axivox management console <https://manage.axivox.com>`_, and click on :guilabel:`Dial plans` in the left menu. Then, click :guilabel:`Visual Editor` next to the desired dial plan to open the :guilabel:`Dialplan Editor` pop-up window."
msgid "Then, from the :guilabel:`New element` drop-down menu, select :guilabel:`Switch`, and then click :guilabel:`Add`. Double-click on the element to further configure the :guilabel:`Switch` element."
msgid "To configure and set a :guilabel:`Multi-Switch` element, navigate to `Axivox management console <https://manage.axivox.com>`_. Then, click on the :guilabel:`Switches` menu item in the left menu."
msgid "To create a new :guilabel:`Multi-Switch`, click :guilabel:`Create new`. Then, enter a :guilabel:`Name` for the element, and then enter the :guilabel:`Available choice`. Enter one :guilabel:`Available choice` per line. Do **not** duplicate any entries."
msgid "To select the :guilabel:`State` of the :guilabel:`Multi-Switch`, click the drop-down menu next to the :guilabel:`Multi-Switch` name, under the :guilabel:`Multi-switch` tab on the :guilabel:`Switches` dashboard."
msgid "The :guilabel:`State` chosen is the route that is followed in the dial plan. The :guilabel:`State` can be edited on the fly, just be sure to click :guilabel:`Apply changes`."
msgid "To add a :guilabel:`Multi-Switch` element to a dial plan, navigate to `Axivox management console <https://manage.axivox.com>`_, and click :guilabel:`Dial plans` in the left menu."
msgid "On the :guilabel:`Dialplan Editor` pop-up window that appears, click on the :guilabel:`New element` drop-down menu, and select :guilabel:`Multi-Switch`. Then, click :guilabel:`Add`. Double-click on the element to further configure the :guilabel:`Switch` element."
msgid "When someone calls a business, they might need to get in contact with customer support, a sales team, or even a person's direct line. The caller might also be in search of some information about the business, such as store hours. Or, they might want to leave a voicemail, so someone from the company can call them back. With dial plans in Axivox, a company can manage how incoming calls like this are handled."
msgid "Using proper call architecture through a dial plan, callers get directed to the right people, or to the right information, in a quick, efficient manner."
msgid "Using a browser add-on for spelling may hinder the use of the visual editor in dial plans. Do not use a translator with the Axivox management console."
msgid "Access dial plans by navigating to `Axivox management console <https://manage.axivox.com>`_, and clicking on :guilabel:`Dial plans` from the menu on the left."
msgid "Axivox has no limit to the number of dial plans that can be created. These can be added, and improved upon, at any time. This allows for sandboxes to be created with many different configurations."
msgid ":guilabel:`Duplicate`: this action duplicates the dial plan, and puts it at the bottom of the list, with an extension of one number (+1) larger than the original extension."
msgid "When the :guilabel:`Visual Editor` button is clicked for a dial plan on the :guilabel:`Dial plan` page, a pop-up :guilabel:`Dialplan Editor` window appears."
msgid "This pop-up window is the primary place where the architecture, or structure, of the dial plan is configured. In this window, a :abbr:`GUI (graphical user interface)` appears, where various dial plan elements can be configured and linked together."
msgid "The method for saving in the :guilabel:`Dialplan Editor` is different from saving any other edits in the Axivox management console because the :guilabel:`Save` button **must** be pressed before closing the :menuselection:`Visual editor`."
msgid "Then, before these changes can take place on the Axivox platform, the user **must** click :guilabel:`Apply changes` in the upper-right corner of the :guilabel:`Dial plan` page."
msgid "From the :guilabel:`Dialplan Editor` pop-up window, users can add a new element to the dial plan. To do that, open the :guilabel:`New element` drop-down menu, and select the desired element. Then, click :guilabel:`Add`."
msgid "Doing so adds that element to the visual editor display of the dial plan being modified. This element can be moved where desired amongst the other elements present in the dial plan."
msgid "Connect elements in the dial plan by clicking and dragging outward from the :guilabel:`(open circle)` icon on the right side of the element. Doing so reveals an :guilabel:`(arrow)` icon. Proceed to drag this :guilabel:`(arrow)` icon to the desired element in the dial plan that it is meant to connect with."
msgid "In order to further configure a :guilabel:`New element`, double-click on the element inside the dial plan, to reveal a subsequent pop-up window, wherein additional customizations can be entered."
msgid "All elements **must** have a final destination in the dial plan in order to close a loop. This can be accomplished by implementing the :guilabel:`Hang up` element, or looping the element back to a :guilabel:`Menu` element or :guilabel:`Digital Receptionist` element elsewhere in the dial plan."
msgid "Once all desired dial plan elements and configurations are complete, remember to click :guilabel:`Save` before exiting the :guilabel:`Dialplan Editor` pop-up window. Then, click :guilabel:`Apply changes` on the :guilabel:`Dial plans` page to ensure they are implemented into Axivox production."
msgid "The following elements are available in the :guilabel:`New element` drop-down menu, while designing a dial plan in the :guilabel:`Dialplan Editor` pop-up window."
msgid "To attach an existing dial plan to an incoming number, go to `Axivox management console <https://manage.axivox.com>`_ , and click on :guilabel:`Incoming numbers`."
msgid "Doing so reveals a separate page wherein that number's dial plan can be modified. To do that, select :guilabel:`Dial plan` from the :guilabel:`Destination type for voice call` field drop-down menu. Then, choose the desired dial plan from the :guilabel:`Dial plan` field that appears."
msgid "With that in place, that means when that specific number calls in, the configured dial plan is activated, and runs through the prompts to properly route the caller."
msgid "The following showcases a basic dial plan scenario for call routing, where additional elements can be added to expand the setup. This basic dial plan scenario includes the following linked elements :menuselection:`Start --> Play a file --> Menu --> (Hang-up, Calls, Queues, Conferences) --> (Voicemail, Hang-up)`."
msgid "This setup does **not** include any basic or advanced call routing. For more information on call routing, reference this documentation: :doc:`dial_plan_advanced`."
msgid "*Caller ID* identifies the caller when they make a phone call. It allows the recipient of the call to see what number the caller is calling from. Caller ID shows users and clients who is calling, so they can choose to pick up or decline the call."
msgid "International numbers can be purchased to do business transactions internationally, via a phone call, from a number that has an area code or country code of the destination being called. By displaying a local number, this can increase customer engagement."
msgid "Some companies have many employees making calls from a call center. These employees are not always available to receive a return phone call from a prospective customer. In this case, :abbr:`VoIP (Voice over Internet Protocol)` can be configured in such a way that dynamic caller ID shows the main company phone number, so any number of employees in the group can answer the call. This way, a call is never missed."
msgid "In Axivox a *default number* can be set. This is a company's main number. This means, when anyone from the company (user/employee) calls a number outside the company, the default outgoing number shows up automatically on the caller ID."
msgid "If someone from outside the company tries to call back a user/employee, they are then funneled back through the main line (default number). If there is a dial plan set up, they are prompted to make selections. This is especially helpful in cases where employees change positions frequently, or if they leave the company."
msgid "To access the default number, go to the `Axivox management console <https://manage.axivox.com>`_, and log in. Then, click into :guilabel:`Settings` in the left menu, and navigate to :guilabel:`Default outgoing number`."
msgid "From here, change the :guilabel:`Default outgoing number` by clicking the drop-down menu, and making a selection from the incoming phone numbers available on Axivox."
msgid "Be sure to :guilabel:`Save` the changes, then click :guilabel:`Apply changes` in the upper-right corner of the :guilabel:`General Settings` page to implement the change."
msgid "The :guilabel:`Default outgoing number` is what shows up by default in the Axivox management portal. However, the outgoing number can also be configured differently at the user level."
msgid "To configure the outgoing number at the user level, log in to the `Axivox management console <https://manage.axivox.com>`_. Next, click :guilabel:`Users` from the menu on the left, and then click :guilabel:`Edit` to the right of the user that is to be configured."
msgid "Under :guilabel:`Outgoing number`, click the drop-down menu to select either the :guilabel:`Default outgoing number` (as specified here: :ref:`voip/axivox/dynamic-caller-id-default`), or any of the incoming numbers on the Axivox account."
msgid "Choosing the :guilabel:`Default` selection in the :guilabel:`Outgoing number` drop-down menu ensures this user has the :guilabel:`Default outgoing number` shown on their caller ID when making calls."
msgid "If a specific number is chosen, and that number is assigned to this user under :guilabel:`Incoming numbers` (in the Axivox console's menu on the left), that means this user has a direct line for customers to reach them."
msgid "Once the desired changes are complete, be sure to click :guilabel:`Save`, then click :guilabel:`Apply changes` in the upper-right corner to implement the change."
msgid "To access the :guilabel:`Advanced options`, navigate to the :guilabel:`Settings` option in the menu on the left of the `Axivox management console <https://manage.axivox.com>`_. Then, click :guilabel:`Advanced options` to the right of :guilabel:`Default outgoing number`."
msgid "By default, there are not any advanced rules set. To create one, click the green :guilabel:`+ (plus)` icon. Doing so reveals a line with two blank fields. From here, different caller IDs can be set up, depending on what location the user/employee is calling from."
msgid "To create a rule, first set the :guilabel:`Destination prefix` in the first empty field. This is the country code, complete with zero(s) in front of it. Then, in the second empty field, select the phone number that should be used for calling out from that country code."
msgid "Check the box for :guilabel:`Apply advanced rules even for users with a default outgoing number configured` to allow these rules to take precedent over all other outgoing configurations."
msgid "For example, a company wants all users/employees to utilize the configured number for Great Britain when calling from the `0044` country code (Great Britain)."
msgid "To accomplish that, simply type in `0044` into the :guilabel:`Destination prefix` field, and select the number starting with the `+44` country code. Order the rules as necessary, and select the checkbox to supersede all other rules, if needed."
msgid "Once the desired configurations are complete, be sure to click :guilabel:`Save`, then click :guilabel:`Apply changes` in the upper-right corner to implement the change."
msgid "Managing Axivox :abbr:`VoIP (Voice over Internet Protocol)` users is an important part of setting up :abbr:`VoIP (Voice over Internet Protocol)` in an Odoo database. Each Axivox user has a unique name, phone number and/or extension, and a voicemail. This way, they can be reached in a variety of convenient ways."
msgid "This documentation covers how to configure everything through a provider called, Axivox. Depending on the chosen VoIP provider, the processes to manage users may be different."
msgid "Begin at the Axivox management console by navigating to `https://manage.axivox.com <https://manage.axivox.com>`_. Log in with the appropriate administrator credentials."
msgid "Actions in the Axivox management console **must** be double-saved, in order for the changes to take effect. To save any changes, click :guilabel:`Save` in the individualized changes screen. Then, to implement those changes, click the :guilabel:`Apply Changes` button in the upper-right corner of the console."
msgid "Click on :menuselection:`Incoming numbers` from the menu on the left of the Axivox management console. Doing so reveals the :guilabel:`Incoming numbers` page, where all the incoming numbers are listed, along with their :guilabel:`Destination` and SMS information."
msgid "To edit the :guilabel:`Destination`, click the :guilabel:`Edit` button to the far-right of the incoming number line to be modified. Then, on the :guilabel:`Edit number` page that appears, the :guilabel:`Destination type for voice call` can be changed."
msgid "Depending on the selection made in the :guilabel:`Destination type for voice call` drop-down menu, a second, selection-specific drop-down menu is populated with further configuration options. Additionally, more fields are revealed, based on the selection made in the :guilabel:`Destination type for voice call` drop-down menu."
msgid "Once the desired configurations are complete, click :guilabel:`Save`, then click :guilabel:`Apply changes` in the upper-right corner to implement them."
msgid "To view existing users in the Axivox management console, click :guilabel:`Users` from the menu on the left of the console. Every user has a :guilabel:`Number`, :guilabel:`Name`, option for a :guilabel:`Voicemail`, and an :guilabel:`Outgoing number` specified."
msgid "To create a new user in the Axivox console, click :guilabel:`Add a user` to reveal a :guilabel:`New user` form. The following tabs are available for configuring the new user:"
msgid "Under the :guilabel:`General` tab of the :guilabel:`New user` form, in the :guilabel:`Extension` field, input an extension that is unique to the user. This is the number internal users dial to reach a specific employee."
msgid "Next, fill out the :guilabel:`Email address of the user` field. A valid email address for the employee should be added here, where the user receives business emails."
msgid "A country code is a locator code that allows access to the desired country's phone system. The country code is dialed first, prior to the target number. Each country in the world has its own specific country code."
msgid "In the :guilabel:`Directory` field, the administrator has the option to leave it blank, by making no changes, or selecting :guilabel:`Default` from the drop-down menu. The :guilabel:`Directory` is used in the *Digital Receptionist* feature element of a dial-plan."
msgid "The first option is :guilabel:`This user can receive multiple calls at the same time`. By selecting this option, users are able to receive calls when on another call."
msgid "If a company uses physical VoIP phones on desks, and wants their employees to be able to log in from *any* phone or desk in the office, they would make the selection for :guilabel:`This user must log-in to call`."
msgid "Under the :guilabel:`Forwardings` tab of the :guilabel:`New user` form, a company can decide what happens if someone calls a user, and the call is not answered."
msgid "For example, under the :guilabel:`Forwarding on no answer` field, when the button for :guilabel:`Add a destination` is selected, the option to add a specific user or phone number is revealed. After entering the :guilabel:`Destination`, a specific time frame can be selected by sliding the :guilabel:`seconds bar` to the desired ring time."
msgid "Ring times can be staggered, so the call is forwarded to another user after the first user does not pick up the call. The option to :guilabel:`Send to voicemail as a last resort` is available to the administrator, should the :guilabel:`Destinations` not pick up."
msgid "Under the :guilabel:`Forwarding on busy` field, an administrator can :guilabel:`Add a destination`. When clicked, they can then set the :guilabel:`Destination` (user) and time frame. Should the original user's :abbr:`VoIP (Voice over Internet Protocol)` extension, or incoming number, be busy, the call is forwarded to the destination(s)."
msgid "When the desired configurations are complete, click :guilabel:`Save`, then click :guilabel:`Apply changes` in the upper-right corner of the page."
msgid "When the :guilabel:`Follow Me` option is selected, under the :guilabel:`Follow Me` tab of the :guilabel:`New user` form, no :menuselection:`Forwardings` can be made."
msgid "Also, when the :guilabel:`Follow Me` option is selected, the :guilabel:`Add a destination` button can be selected to add users, or a destination phone number, to the original user's account. That way, these added numbers ring when a call is received."
msgid "After entering the :guilabel:`Destination`, a specific time frame can be made by sliding the :guilabel:`seconds bar` to the desired ring time. Additional :guilabel:`Destinations` can be added with different ring times."
msgid "The original user's :abbr:`VoIP (Voice over Internet Protocol)` number does **not** ring with this option selected. Ring times can also be staggered, so the call is forwarded to another user after the first user does not pick up the call."
msgid "The Odoo mobile app, or another :abbr:`SIP (Session Initiation Protocol)` mobile client, allows for simultaneous ringing of the user's extension or incoming number. For more information, visit the :doc:`VoIP Mobile Integrations <../devices_integrations>` documentation."
msgid "Under the :guilabel:`Keys` tab of the :guilabel:`New user` form, speed dial actions for the user can be configured. Some more advanced options are available, as well."
msgid ":guilabel:`BLF (Busy lamp fields)`: this action shows the status of other users' phones connected to the Axivox phone system. This is primarily used on a desk-phone."
msgid "Many of the preceding options have secondary options available, as well, that can be used to link a user, or external phone number. These **must** be filled out in conjunction with the initial action."
msgid "The :guilabel:`Number of keys` field can be changed by entering in the desired numerical value in the :guilabel:`Number of keys` field, located at the top of the :guilabel:`Keys` tab of the :guilabel:`New user` form."
msgid "*SIP*, which stands for Session Initiation Protocol telephony, allows one to make and receive calls through an internet connection. The :guilabel:`SIP Identifiers` tab on the :guilabel:`New user` form, contains credentials needed to configure Axivox users in Odoo and/or a different :abbr:`SIP (Session Initiation Protocol)` mobile client."
msgid "Under the :guilabel:`SIP Identifiers` tab, the :guilabel:`SIP username` field represents the user's information that was entered in the :guilabel:`Extension` field, under the :guilabel:`General` tab."
msgid "The value in the :guilabel:`SIP Password` field is unique for every Axivox user. This value is used to sign into Axivox on Odoo, and for any mobile :abbr:`SIP (Session Initiation Protocol)` clients."
msgid "The value listed in the :guilabel:`Address of the proxy server` field is typically: `pabx.axivox.com`, but is subject to change by Axivox, so be sure to check the :guilabel:`SIP Identifiers` tab for the most accurate value."
msgid "Under the :guilabel:`Permissions` tab of a :guilabel:`New user` form, a :guilabel:`Username` and :guilabel:`Password` can be entered for the user."
msgid "To access credentials for the Axivox user portal, navigate to the top of the :menuselection:`Permissions` tab. Then, copy the :guilabel:`Username`, and enter the correct :guilabel:`Password` for the individual user. There is a minimum of 8 characters for a user password."
msgid "These are the same permissions granted to the Axivox administrator that are listed in the menu on the left in the Axivox management console. Should a selection state :guilabel:`No`, or :guilabel:`No access`, then the menu option does **not** populate for the user."
msgid "Then, log in with the appropriate administrator credentials. From the menu on the left of the Axivox administrative panel, click into :guilabel:`User Groups`."
msgid "Next, name the group, by entering text into the :guilabel:`Name` field. Then, add a member to the group by typing the first few letters of the user's name into the :guilabel:`Members` field. The user populates in a drop-down menu below the field. Then, click on the desired user, and they are added to the user group."
msgid "Managing voicemail is an important part of any business. A company needs to access their messages with ease, and stay on top of any missed calls. Recording audio messages, like thanking a caller for reaching out, or directing them to the right extension, is also a great way to personalize the business interaction, and set the tone with the customer."
msgid "To start using voicemails and audio messages with Axivox, the global language should be set in the Axivox admin portal settings. To do that, navigate to `manage.axivox.com <axivox_admin_>`_. After logging into the portal, go to :menuselection:`Settings --> Global language (e.g.: voicemail messages,...)`."
msgid "Then, click :guilabel:`Save`, followed by :guilabel:`Apply changes` in the upper-right corner of the :guilabel:`General Settings` page to implement the change into production."
msgid "In order for a user to utilize voicemail in Axivox, the voicemail feature **must** be turned on in the Axivox administrative portal. To begin using voicemail with a user, navigate to `manage.axivox.com <axivox_admin_>`_. Then, log in with the appropriate administrator credentials."
msgid "Then, click into the specific user the voicemail should be activated for. Under the section marked, :guilabel:`Voicemail`, open the drop-down menu, and click on :guilabel:`Yes`."
msgid "The next step is to set up the individual voicemail boxes on the Axivox administrative portal. To access the portal, visit `manage.axivox.com <axivox_admin_>`_ and log in. Then, navigate to :menuselection:`Voicemails`, located in the menu on the left."
msgid "If the voicemail option was activated in the user profile, using this process :ref:`voip/axivox/activate_voicemail`, then a voicemail is automatically created on the :guilabel:`Voicemails` page."
msgid "It should be noted that some of the administrative portal language is in French, as Axivox is a Belgian company. The global language is still set to one of the four options as seen here: :ref:`voip/axivox/global_language`."
msgid "To manually create a new voicemail box, click :guilabel:`Add a voicemail` on the :guilabel:`Voicemails` page. Or, edit an existing voicemail box, by clicking :guilabel:`Edit` to the far-right of an existing voicemail box on the :guilabel:`Voicemails` page."
msgid "Suppose a sales or support team needs a general voicemail box. The voicemail would need to be created manually, and attached to an incoming number."
msgid "The new, manually-created voicemail box should be attached to an incoming number, so it can receive messages. To do so, navigate to :menuselection:`Incoming numbers`, located in the menu on the left. Then, click :guilabel:`Edit` to the far-right of the specific number the voicemail should be linked to."
msgid "In the :guilabel:`Destination type for voice call` field, click the drop-down menu, and select :guilabel:`Voicemail`. Then, open the drop-down menu on the next line labeled, :guilabel:`Voicemail`, and select the manually-created voicemail box."
msgid "If an incoming number is capable of receiving SMS/text messages, an additional field, :guilabel:`Destination email address for Incoming SMS`, is present."
msgid "To determine whether an incoming number is capable of receiving SMS/text messages, click :guilabel:`Incoming numbers` from the menu on the left, then check the :guilabel:`SMS compatible` column for the incoming number."
msgid "Then, if applicable, in the field labeled, :guilabel:`Destination email address for Incoming SMS`, enter an email to which incoming text messages sent to the incoming number can be received. Some incoming numbers (US +1) in Axivox are capable of receiving text messages from individuals and automated numbers."
msgid "Should this field be left empty, the default destination address is used, instead (as previously set in the beginning of the process for manually creating a voicemail)."
msgid "Once all desired configurations are complete, click :guilabel:`Save`, then click :guilabel:`Apply changes` in the upper-right corner of the screen to implement the change into production."
msgid "Now, whenever a voicemail is received on any of the automatically pre-configured or manually-linked voicemail boxes, an email is sent to the user's email address, as listed in the :guilabel:`Voicemails` page, or in the user's Axivox profile."
msgid "This information can be accessed by navigating to :menuselection:`Users` in the left menu, and clicking :guilabel:`Edit` next to the specific user in question."
msgid "In Axivox, there are also numerous forwarding settings for a user. To access these forwarding settings, go to `manage.axivox.com <axivox_admin_>`_ and log in."
msgid "If the user is busy on another call, or away from the phone, there is an option present in this tab to :guilabel:`Send to voicemail as a last resort`, located in the :guilabel:`Forwarding on no answer` and :guilabel:`Forwarding on busy` fields."
msgid "If the :guilabel:`Send to voicemail as a last resort` box is ticked, when the forwarding actions stated in each section are not successful, the caller is routed to the voicemail set on the particular user."
msgid "When all the desired configurations are complete, click :guilabel:`Save`, then click :guilabel:`Apply changes` in the upper-right corner of the screen to implement the change."
msgid "It is possible to add audio messages *before* a customer's call is even taken, to inform them about the waiting time for deliveries, the availability of a product, or any other important promotional messages."
msgid "Upon clicking :guilabel:`Save`, the browser redirects back to the main :guilabel:`Audio messages` page, where the newly-created message can be found on the list."
msgid "There are two different ways to make the audio message. The user could either record the message over the phone, or type the message (in text), and select a computer-generated speaker to read the message."
msgid "To record an audio message over the phone, click the orange button labeled, :guilabel:`Record/Listen`, located to the right of the desired message on the list to record, on the :guilabel:`Audio messages` page."
msgid "When clicked, a :guilabel:`Record / listen to a message` pop-up window appears. From here, the message is then recorded, via one of the extensions that is associated with the user. Under :guilabel:`Extension to use for message management` field, click the drop-down menu, and select the extension where Axivox should call to record the message."
msgid "The user **must** be active in the production database with :abbr:`VoIP (Voice over Internet Protocol)` configured. To configure :abbr:`VoIP (Voice over Internet Protocol)` for a user, see this documentation: :doc:`axivox_config`."
msgid "Press either `1` or `2`, depending on whether or not there is already a message present in the system for this particular audio message that requires a review, before recording a new one."
msgid "To type the message, and select a computerized speaker to say the text, navigate to the :menuselection:`Audio messages` in the menu on the left."
msgid "From the :guilabel:`Audio messages` page, select the blue button labeled, :guilabel:`Text message`, next to the corresponding audio message :guilabel:`Name` that the message should be attached to."
msgid "From the :guilabel:`Convert to text message` pop-up window, click the drop-down menu next to the field labeled, :guilabel:`Voice`, and select an option for the :guilabel:`Text` to be read in."
msgid "After the :guilabel:`Voice` selection has been made, and the message has been written in the :guilabel:`Text` field, click :guilabel:`Generate` to process the audio file."
msgid "The text is read in the same language it is written in the :guilabel:`Text` field. Should the language differ in the :guilabel:`Voice` field, then an accent is used by the computerized speaker."
msgid "To set a greeting or audio message in a dial plan element double-click on the element. This could be a :guilabel:`Play a file` element, or a :guilabel:`Menu` element, in which the caller should encounter an urgent message, or a dial-by-number directory."
msgid "Axivox has the option to add custom hold music to the call whenever a caller is waiting for their call to be answered. To add hold music to the Axivox administrative portal, navigate to the `manage.axivox.com <axivox_admin_>`_, and log in."
msgid "On the :guilabel:`Change the music on hold` pop-up window, click the :guilabel:`Choose File` button to select an MP3 (MPEG Audio Layer 3) or WAV (Waveform Audio File Format ) file to be uploaded."
msgid "Once the file is selected, the :guilabel:`Progression` bar shows an upload status. When this activity completes, the window can be closed, by clicking :guilabel:`Close`."
msgid ":abbr:`VoIP (Voice over Internet Protocol)` can be used on many different devices, such as a computer, tablet, mobile phone, and many more. This is helpful in that it reduces costs, and employees can work from anywhere in the world, so long as they have a broadband internet connection."
msgid "Odoo *VoIP* is SIP (Session Initiation Protocol) compatible, which means it can be used with *any* :abbr:`SIP (Session Initiation Protocol)` compatible application."
msgid "The Odoo *VoIP* (Voice over Internet Protocol) module and widget can be used from any browser on a laptop or desktop device. Simply click on the :guilabel:`☎️ (phone)` icon in the upper-right corner, while in the Odoo database, and the widget appears."
msgid "To see how to use the :abbr:`VoIP (Voice over Internet Protocol)` widget on a desktop/laptop computer, check out this documentation: :doc:`voip_widget`."
msgid "The Odoo *VoIP* app can be used on tablets and mobile phones, through the Odoo Android or Apple IOS applications. Additionally, a mobile web browser can be used to access the database."
msgid "Odoo Android and Apple IOS applications are no longer being maintained by Odoo on the Android and Apple portals. This means Odoo support only handles limited scopes of Odoo Android or Apple IOS support tickets."
msgid "While outgoing calls can be placed using Odoo on a mobile device, be aware that Odoo is **not** a full :abbr:`VoIP (Voice over Internet Protocol)` application, and does **not** ring on incoming calls. If the user needs to be reachable on a mobile device at all times, an app, like Zoiper, should be used. Apps like that stay connected in the background at all times."
msgid "While in the mobile application on a mobile device/tablet, access the Odoo *VoIP* widget, by tapping on the :guilabel:`☎️ (phone)` icon in the upper-right corner. The widget appears in the lower-left corner."
msgid "When first making a call from the tablet using the mobile application, the user is prompted to :guilabel:`Allow` the database to use the microphone. Click :guilabel:`Allow` when prompted to continue with the call using the microphone."
msgid "Odoo then asks how to make the call. The two options are : :guilabel:`VOIP` or :guilabel:`Phone` (should the tablet be enabled for calling). Click the box next to :guilabel:`Remember ?` should this decision be the default moving forward."
msgid "To start using the *Zoiper* app, download it to the device, via the `Zoiper download page <https://www.zoiper.com/en/voip-softphone/download/current>`_."
msgid "A mobile device is the most common installation, and this document covers how to set up on the *Zoiper* IOS application. Screenshots and steps may differ depending on the set up conditions."
msgid "After installing the *Zoiper* application on the mobile phone, open the application, and tap on :guilabel:`Settings`. Navigate to :menuselection:`Accounts`, and tap on the :guilabel:`+ (plus)` icon to add an account."
msgid "If the :abbr:`VoIP (Voice over Internet Protocol)` account is already set up, then click :guilabel:`Yes`. This means an account username and password has already been produced."
msgid "Next, tap on :guilabel:`Select a provider`. On the screen that populates, tap :guilabel:`Country`, in the upper-right corner, to narrow the providers down to a specific country. Choose the country for the provider that is being configured, then find the :guilabel:`Provider`, and select it."
msgid "Under :abbr:`SIP (Session Initiation Protocol)` options, enter the :guilabel:`Account name`, :guilabel:`Domain`, :guilabel:`Username`, and :guilabel:`Password`. All this information varies, based on the account."
msgid "To access this information, via the *Axivox* portal, navigate to :menuselection:`Users --> Choose user --> Edit --> SIP Identifiers tab`. The :guilabel:`SIP username`, :guilabel:`Domain`, :guilabel:`SIP password`, and :guilabel:`Address of the proxy server` are all present in this tab."
msgid "Once this account information is entered, click the green :guilabel:`Register` button at the top of the screen. Once the registration information is checked, *Zoiper* populates a message, stating :guilabel:`Registration Status: OK`."
msgid "*Linphone* is an open-source :abbr:`VoIP (Voice over Internet Protocol)` :abbr:`SIP (Session Initiation Protocol)` softphone, used for voice, video, messaging (group and individual), as well as conference calls."
msgid "To start using the *Linphone* app, download it to the device, via the `Linphone download page <https://new.linphone.org/technical-corner/linphone?qt-technical_corner=2#qt-technical_corner>`_."
msgid "A mobile device is the most common installation, and this document covers how to set up the *Linphone* IOS application. Screenshots and steps may differ depending on the circumstances."
msgid "To begin configuring *Linphone* for use with a :abbr:`SIP (Session Initiation Protocol)` provider, first open *Linphone*, and an assistant screen appears."
msgid "From this screen, select :guilabel:`Use SIP Account`. Then, on the following screen, enter the :guilabel:`Username`, :guilabel:`Password`, :guilabel:`Domain`, and :guilabel:`Display Name`. Once complete, press :guilabel:`Login`."
msgid "At this point, *Linphone* is ready to start making calls, once there is a green button at the top of the application screen that reads, :guilabel:`Connected`."
msgid "*Linphone* makes a variety of applications for mobile and desktop devices in operating systems, such as Windows, Linux, Apple, and Android. Because *Linphone* is an open-source project, many new updates are released on a regular basis."
msgid "Odoo *VoIP* can be set up to work together with `OnSIP (Odoo Landing Page) <https://info.onsip.com/odoo/>`_. OnSIP is a VoIP provider. An account is needed with OnSIP in order to use this service."
msgid "To configure the Odoo database to connect to OnSIP services, first navigate to the :menuselection:`Apps application` from the main Odoo dashboard. Then, remove the default `Apps` filter from the :guilabel:`Search...` bar, and search for `OnSIP`."
msgid "After installing the *VOIP OnSIP* module, go to the :menuselection:`Settings app`, scroll down to the :guilabel:`Integrations` section, and locate the :guilabel:`Asterisk (VoIP)` fields. Then, proceed to fill in those three fields with the following information:"
msgid "To access the OnSIP domain, navigate to `OnSIP <https://www.onsip.com/>`_ and log in. Then, click the :guilabel:`Administrators` link in the top-right of the page."
msgid "Next, in the left menu, click :guilabel:`Users`, and then select any user. By default, the selected user opens on the :guilabel:`User Info` tab."
msgid "Next, the user needs to be set up in Odoo. Every user associated with an OnSIP user **must** also be configured in the Odoo user's settings/preferences."
msgid "On the user form, click :guilabel:`Edit` to configure the user's OnSIP account. Then, click the :guilabel:`Preferences` tab, and scroll to the :guilabel:`VoIP Configuration` section."
msgid "The Odoo database also receives incoming calls that produce pop-up windows in Odoo. When those call pop-up windows appear, click the green :guilabel:`📞 (phone)` icon to answer the call."
msgid "If an *Incorrect Number* message appears in the Odoo widget, make sure to use the international format for the number. This means leading with the international country code."
msgid "In order to make and receive phone calls when the user is not in front of Odoo on their computer, a softphone app on a mobile phone can be used in parallel with Odoo *VoIP*."
msgid "Calling prospective clients, customers, or colleagues is an essential part of any business. A company also needs to be available when customers call, in order to build trust and make connections."
msgid "Starting on the Odoo dashboard, a call can be made by opening the phone widget in the the upper-right corner, which is represented by a :guilabel:`☎️ (phone)` icon."
msgid "To manually make a call, click the :guilabel:`⌨️ (keyboard)` icon, and proceed to manually key in the desired number. Do not forget to lead with the :guilabel:`+ (plus)` icon, followed by the international country code."
msgid "For the United States of America, the country code and :guilabel:`+ (plus)` icon, would look like this: `+1`. If one were to dial Belgium, the number would be prefixed by `+32`, and for Great Britain it would be `+44`."
msgid "After entering the full number, with the required :guilabel:`+ (plus)` icon prefix and country code, click the green :guilabel:`📞 (phone)` icon to start the call. When finished, click the red :guilabel:`📞 (phone)` icon to end the call."
msgid "An incoming call automatically opens the *VoIP* widget, when a user is using the Odoo database. Should the database be open in another tab, a sound plays (the sound **must** be activated on the device)."
msgid "All the contacts and customers that need to be called can be seen in one place with the Odoo *VoIP* phone widget, under the :guilabel:`Next activities` tab."
msgid "To add a call to the :guilabel:`Next activities` tab, click the green :guilabel:`📞 (phone)` icon, while in kanban view of the *CRM* application."
msgid "To remove them from the call queue, hover over the opportunity that has a call scheduled, and click the red :guilabel:`📞 (phone)` icon that appears with the :guilabel:`- (minus)` icon."
msgid "When navigating back to the *VoIP* phone widget, **only** the calls that are scheduled immediately for that day appear in the queue under the :guilabel:`Next Activities` tab of the *VoIP* pop-up widget."
msgid "To manually add a call, via the chatter, click :guilabel:`Activities` (next to the :guilabel:`🕗 (clock)` icon). Under :guilabel:`Activity Type`, select :guilabel:`Call` from the drop-down menu that appears."
msgid "Lastly, change the :guilabel:`Assigned to` field to the person that should make the call. Whomever is set in this last field (:guilabel:`Assigned to`) has this call show up in their :guilabel:`Next Activities` call queue in the Odoo *VoIP* phone widget."
msgid "Only calls for the immediate day (today's date) appear in the :guilabel:`Next Activities` tab of the *VoIP* phone widget for that specific user."
msgid "A call can be transferred from one user to another in the Odoo *VoIP* phone widget. However, this can **only** occur after speaking to the caller first. Without picking up the call in the Odoo *VoIP* phone widget, the only way to transfer a call is automatically though the provider console/portal."
msgid "Once the incoming call is answered, click the :guilabel:`↔ (left-right arrow)` icon. Then, enter the extension of the user the call should be forwarded to. Finally, click :guilabel:`Transfer` to route the call to that phone number."
msgid "To find the extension for a user, consult the :abbr:`VoIP (Voice over Internet Protocol)` administrator, or, if the user has *Settings* access rights to *Administration*, navigate to :menuselection:`Settings App --> Manage Users --> Select the user --> Preferences --> VOIP --> VoIP username / Extension number`."
msgid "To forward a call within the Odoo *VoIP* phone widget, first, answer the call using the green :guilabel:`📞 (phone)` icon. Once the incoming call is answered, click the :guilabel:`↔ (left-right arrow)` icon."
msgid "Then, enter the full phone number of the user the call should be forwarded to. Finally, click :guilabel:`Transfer` to route the call to that phone number."
msgid "The *VoIP* widget is an add-on made available to Odoo users through the *VoIP* module. It is used to incorporate virtual telephony into the database. The widget is the control center for making and managing calls in Odoo."
msgid "When clicked, a :guilabel:`VOIP` pop-up widget appears in the lower-left corner of the Odoo database. The widget allows users to freely navigate throughout the database, while making and receiving calls."
msgid "When receiving calls in Odoo, the :guilabel:`VOIP` widget rings,and displays a notification. To close the widget, click the :guilabel:`X (close)` icon in the upper-right of the widget's screen."
msgid "The :abbr:`VoIP (Voice over Internet Protocol)` number is the one provided by Axivox. It can be accessed by navigating to `https://manage.axivox.com/ <https://manage.axivox.com/>`_. After logging into the portal, go to :menuselection:`Users --> Outgoing number` (column)."
msgid "If an *Incorrect Number* error message appears in the Odoo *VoIP* widget, make sure to use the international format, leading with the :guilabel:`+ (plus)` sign, followed by the international country code."
msgid "In all, there are three tabs (:guilabel:`Recent`, :guilabel:`Next Activities`, and :guilabel:`Contacts`) present in the *VoIP* widget, which are used for managing calls and day-to-day activities in Odoo."
msgid "Under the :guilabel:`Recent` tab of the *VoIP* widget, the call history for the user is available. This includes incoming and outgoing calls. Any number can be clicked to begin a call."
msgid "Under the :guilabel:`Next Activities` tab of the *VoIP* widget, a user can see any activities assigned to them, and which ones are due to be completed for the day."
msgid "Click an activity from this tab to perform any actions including: Sending an email, accessing their contact, scheduling another activity, or accessing a linked record (such as a Sales Order, Lead/Opportunity, or Project Task)."
msgid "To call the customer related to a scheduled activity, click the :guilabel:`📞 (phone)` icon, or click the :guilabel:`⌨️ (keyboard)` icon to dial another number for the customer."
msgid "**WhatsApp** is an instant messaging and voice-over-IP app that allows users to send messages, make calls, and share content. Businesses can use `WhatsApp Business <https://developers.facebook.com/products/whatsapp/>`_ to communicate with their customers by text, send documents and provide support."
msgid "WhatsApp is an Odoo Enterprise-only application that does not work in Odoo Community edition. To sign up for Odoo Enterprise edition, click here: `Odoo Free Trial <https://www.odoo.com/trial>`_."
msgid "For more information on migrating from Odoo Community version to Odoo Enterprise version see this documentation: :doc:`/administration/on_premise/community_to_enterprise`."
msgid "WhatsApp is a messaging service operated by Meta, which is the parent company of Facebook. WhatsApp is commonly used as a communication tool in many countries and by many businesses. This documentation will cover the integration of a WhatsApp Business Account with Odoo. The company's Meta account is configured in Odoo via an :abbr:`API (Application Programming Interface)` connection."
msgid "The WhatsApp connector supports two flows: company initiated, and customer initiated. A company can initiate a discussion by sending a template to one or more people. Once the template is sent, the recipient can answer in order to trigger a discussion between the sender and the receiver (a *Discuss* chat window will pop up if the customer answers within 15 days)."
msgid "If the discussion is initiated by the client (e.g. by sending to the company's public WhatsApp number), then Odoo will open a group chat with all operators responsible for this WhatsApp channel."
msgid "It is recommended to set up multiple WhatsApp accounts for different departments. For example, the help desk team and sales teams can chat on different channels."
msgid "A WhatsApp integration with Odoo uses a standard :abbr:`API (Application Programming Interface)` connection, and is configured on Meta in the following steps:"
msgid "Once connected, messages are then sent and received through Odoo's *Discuss* application using the WhatsApp :abbr:`API (Application Programming Interface)`."
msgid "To create a Business account with Meta (owner of Facebook) navigate to: `Facebook Business Manager <https://business.facebook.com/overview>`_. Begin by clicking :guilabel:`Create account` and then enter the business name, the administrator's name, and a work email address. Then click :guilabel:`Next`, and a pop-up window will appear prompting to confirm the email address. After confirming, click :guilabel:`Done` to close the window."
msgid "If the business account is linked to a personal Facebook account then the administrator must toggle between the personal account to the business account for the remainder of the configuration."
msgid "To toggle to the business account navigate to the `Facebook Developer Console <https://developers.facebook.com>`_ and click on the *account name* in the upper right corner. Under the :guilabel:`Business Accounts` heading, click on the desired business that the WhatsApp configuration should take place in. This will be the account for which Odoo will send and receive WhatsApp messages."
msgid "In order to create a Meta business account, the user must already have a personal Facebook account that has existed for a minimum of one hour prior to setting up the Facebook Business account. Trying to create the business account prior to this time will result in an error."
msgid "On the `Meta for Developers <https://developers.facebook.com>`_ dashboard, sign in with the Meta developer account. If no account is configured yet, link a Facebook account to create a Meta developer account."
msgid "A Facebook *developer* account is different than a Facebook *business* account. While developer accounts are made up of personal Facebook accounts, business accounts are **not** as they represent a business and manage all of the business's assets in Meta, such as apps."
msgid "Click on :guilabel:`My Apps` in the top right corner after successfully signing in to the Meta developer account. This will redirect the administrator to all the apps the developer has configured in this specific developer account. Click on :guilabel:`Create App` to begin the process of configuring a new Meta application."
msgid "On the :menuselection:`Create an app` page, select :guilabel:`Other` under the section labeled, :guilabel:`Looking for something else?`, and then click :guilabel:`Next` to be directed to another page in order to select the app type. Then, click on the first option listed under the :guilabel:`Select an app type` label, titled :guilabel:`Business`. This selection allows for the creation and management of the WhatsApp :abbr:`API (Application Programming Interface)`."
msgid "Now, click :guilabel:`Next` to configure the app, as desired. When the app *type* has been configured, the administrator will move onto the app *details* section."
msgid "On the :guilabel:`Details` section of the :guilabel:`Create an app` process, enter `Odoo` in the field under the :guilabel:`Add an app name` label."
msgid "Trademarks and branded elements may not be used in this text section. These include the Meta group of companies. Do not include the word: `WhatsApp` or the system will flag this in error."
msgid "Lastly, set the :guilabel:`Business Account - Optional` field to the Meta business account profile, using the drop-down menu. To finish, click :guilabel:`Create app`. This action will create the app and prompts the *Meta Platform Terms* and *Developer Policies* agreements."
msgid "To accept the agreements, enter the Facebook password for security purposes, and click :guilabel:`Submit` to finalize the app creation. The browser will then direct to the :guilabel:`Meta for Developers` dashboard."
msgid "If the Meta business account is prohibited from advertising, claiming an app won't be allowed. To resolve this issue navigate to `<https://business.facebook.com/business>`_ for assistance."
msgid "Now that the basic structure of the app has been created, a product will need to be added to the app. Begin by accessing the Meta app dashboard by navigating to `<https://developers.facebook.com/apps>`_, and clicking on the app that is being configured."
msgid "On the next page: since WhatsApp will be used, click :guilabel:`Set up` next to the box containing WhatsApp, located towards the bottom of the page."
msgid "The page then directs to the configuration page for the :guilabel:`WhatsApp Business Platform API`. Use the drop-down menu to select the Meta business to be configured for the :guilabel:`Select a Meta Business Account` option, and then click :guilabel:`Continue` to confirm the selection."
msgid "After finishing the previous WhatsApp product wizard, and clicking :guilabel:`Continue`, the browser should have directed to the WhatsApp :guilabel:`Quickstart` page; this :guilabel:`Quickstart` page is where to begin configuring the WhatsApp API by adding a phone number and then sending an initial test message."
msgid "If the browser isn't on the :guilabel:`Quickstart` page for WhatsApp, navigate to `<https://developers.facebook.com/apps>`_ and click on the app that is being configured, (the app name is `Odoo` if the instructions above were followed)."
msgid "Then, in the menu on the left-hand side of the page, click the :guilabel:`v (menu toggle)` icon next to the :guilabel:`WhatsApp` section heading. A small menu will open, containing the following options:"
msgid "After clicking on :guilabel:`Start using the API`, the page navigates to the :guilabel:`API Setup`. Now that the test number has been created, a test message can be sent to confirm that WhatsApp is working properly. To begin, navigate to the section on the page labeled :guilabel:`Send and receive messages` and click the drop-down menu next to :guilabel:`To`, under :guilabel:`Step 1 Select phone numbers`."
msgid "Now, select the only option available: :guilabel:`Manage phone number list`. Follow the steps and add up to five numbers to send the free test messages to. After entering the appropriate country code and phone number, click on :guilabel:`Next`."
msgid "Adding a phone number to send to in this step will allow for a successful test to be sent by the terminal. This is critical to ensure the WhatsApp :abbr:`API (Application Programming Interface)` is working."
msgid "A verification code from WhatsApp Business is then sent to the phone number, which needs to be input on the next screen to verify ownership of the number. Enter the verification code and click :guilabel:`Next` to verify the number."
msgid "Next, send a test message via the terminal. Under the section labeled :guilabel:`Step 2 Send messages with the API`, click :guilabel:`Send Message`. A test message will then be sent to the phone number that was set in the previous section."
msgid "The next steps configured in this section are all within the Odoo database. A few different values for a token, phone number, and account IDs all need to be configured in Odoo; these values are necessary in order to create a :guilabel:`Callback URL` and :guilabel:`Webhook Verify Token`, which are then used to configure the webhooks (in order to receive messages back into the database)."
msgid "In Odoo, navigate to :menuselection:`WhatsApp app --> Configuration --> WhatsApp Business Accounts`. Then click :guilabel:`New` to configure the WhatsApp business account in Odoo."
msgid "In another browser tab, navigate to :menuselection:`https://developers.facebook.com --> My Apps --> WhatsApp --> API Configuration`, and then copy the following values from the Meta developer console into the corresponding fields in Odoo:"
msgid "To retrieve the :guilabel:`App Secret`, navigate to the Meta developer console, `<https://developers.facebook.com/apps>`_ and select the app that Odoo is being configured in. Then in the left-side menu, under :guilabel:`App settings`, select :guilabel:`Basic`."
msgid "Next, click :guilabel:`Show` next to the field :guilabel:`App secret`, and enter the account password to verify ownership. Copy the :guilabel:`App secret` and then paste that copied value into the :guilabel:`App Secret` field on the Odoo :guilabel:`WhatsApp Business Account` configuration dashboard."
msgid "To complete the setup of the WhatsApp business account in Odoo, click :guilabel:`Test Connection`. A successful message in green will populate in the upper-right corner of the dashboard if the configuration is set correctly."
msgid "To configure the webhooks for WhatsApp in Odoo, navigate to `<https://developers.facebook.com/apps>`_ and select the app that Odoo is being configured in. Next under the :guilabel:`WhatsApp` menu heading on the left side of the screen, click on the :guilabel:`API Setup` menu item. Finally go to the section marked :guilabel:`Step 3: Configure webhooks to receive messages` and click on :guilabel:`Configure webhooks`."
msgid "Another way to configure *Webhooks* is to navigate to `<https://developers.facebook.com/apps>`_ and select the app that Odoo is being configured in. Then select :guilabel:`Webhooks` in the left hand menu."
msgid "On the :menuselection:`Webhook configuration` page, click on :guilabel:`Edit`, where both the :guilabel:`Callback URL` and :guilabel:`Webhook Verify Token` values from the Odoo will be added."
msgid "Both the :guilabel:`Callback URL` and :guilabel:`Webhook Verify Token` values were automatically populated after clicking on :guilabel:`Test Connection` in the previous step."
msgid "In a separate browser window, retrieve the necessary values in Odoo by navigating to :menuselection:`WhatsApp app --> Configuration --> WhatsApp Business Accounts` and select the account that is being configured. Locate the values under the section labeled :guilabel:`Receiving Messages`."
msgid "Copy and paste the :guilabel:`Callback URL` from Odoo into the :guilabel:`Callback URL` field in Meta. Similarly, copy and paste the :guilabel:`Webhook Verify Token` into the :guilabel:`Verify Token` field on the Meta developer console, as well."
msgid "Now input individual webhook fields into Meta's developer console, under the :guilabel:`Webhook fields` section. Click :guilabel:`Manage` and when the pop-up window appears, check the boxes in the :guilabel:`Subscribe` column for the following *field names*:"
msgid "The :guilabel:`Webhook fields` will only appear once the subscription is confirmed using the :guilabel:`Callback URL` and :guilabel:`Webhook Verify Token`."
msgid "To configure the phone number to use for WhatsApp in Odoo, navigate back to the Meta developer console (`<https://developers.facebook.com/apps>`_) and again select the app that Odoo is being configured in. Under the :guilabel:`WhatsApp` menu heading on the left side of the screen, click on the :guilabel:`API Setup` menu item. From there, go to the section marked: :guilabel:`Step 5: Add a phone number`, and click on :guilabel:`Add phone number`."
msgid "Complete filling out the business information by next selecting the country that the company does business in from the drop-down menu in the :guilabel:`Country` section. Add an address if desired, however, this information is optional. After adding the location, click :guilabel:`Next` to continue."
msgid "Once these sections are complete, click :guilabel:`Next`. The page refreshes and then prompts the administrator to :guilabel:`Add a phone number for WhatsApp` in the respective field. Here, enter the phone number to configure in WhatsApp."
msgid "`Migrate an Existing WhatsApp Number to a Business Account <https://developers.facebook.com/docs/whatsapp/cloud-api/get-started/migrate-existing-whatsapp- number-to-a-business-account>`_."
msgid "Next, choose a verification method for the phone number. Select either :guilabel:`Text message` or :guilabel:`Phone call`, and then click :guilabel:`Next` proceed."
msgid "The phone number entered will receive either a text or a phone call by WhatsApp with a code, depending on the verification method chosen. Enter that verification code into the :guilabel:`Verification code` field and click :guilabel:`Next` to finish."
msgid "If a payment method hasn't been added this will be necessary to proceed. `Visit Meta's documentation on how to add a payment method in Meta's Business Manager <https://www.facebook.com/business/help/915454841921082?id=180505742745347>`_. This is part of Meta's fraud detection system, in order to ensure that the account/company are real a payment method is required to proceed."
msgid "`Meta for Developers: System User Access Tokens <https://developers.facebook.com/docs/whatsapp/business-management-api/get-started#system-user- access-tokens>`_."
msgid "Begin by navigating to `<https://business.facebook.com/>`_ and then go to :menuselection:`Business settings --> User --> System Users`. Select an existing system user or create a new system user by clicking on :guilabel:`Add`."
msgid "Click on :guilabel:`Add assets`, and when the pop-up window appears select :guilabel:`Apps` under the :guilabel:`Select asset type`. Then, select the Odoo app and toggle the permissions to *On* under the :guilabel:`Full control` option. Set this new permission setting by clicking :guilabel:`Save Changes`, to which a confirmation window will appear, acknowledging the addition of the asset to the system user. Finish by clicking :guilabel:`Done`."
msgid "Next, the permanent token will be generated. Click on :guilabel:`Generate new token`, and a pop-up window will appear asking which app this token should be generated for. Select the :guilabel:`App` that this token is for. Then determine the expiration date of either :guilabel:`60 days` or :guilabel:`Never`."
msgid "With that token value, update the :guilabel:`Access Token` field in the WhatsApp business account in Odoo by navigating to :menuselection:`WhatsApp app --> Configuration --> WhatsApp Business Accounts`."
msgid "Finally, to launch the app, the Meta app must be set to :guilabel:`Live` in the Meta developer console. Navigate to `<https://developers.facebook.com/apps>`_ and click on the app that is being configured. In the top menu, toggle the :guilabel:`App Mode` field from :guilabel:`Development` to :guilabel:`Live`."
msgid "A privacy policy URL must be set in order for the app to be set to live. Go to the Meta developer console, `<https://developers.facebook.com/apps>`_ and select the app that Odoo is being configured in. Then, using the menu on the left side of the screen, go to :menuselection:`App Settings --> Basic`. Then, enter the privacy policy hyperlink address under the :guilabel:`Privacy Policy URL` field of the form. Click :guilabel:`Save changes` to apply the privacy policy to the app."
msgid "WhatsApp templates are saved messages that are used repeatedly to send messages from the database. They allow users to send quality communications, without having to compose the same text repeatedly."
msgid "Creating different templates that are tailored to specific situations lets users choose the right message for the right audience. This increases the quality of the message and the overall engagement rate with the customer."
msgid "WhatsApp templates can be created on both the Odoo and Meta consoles. The following process will overview the process for creating templates in Odoo and then afterward in Meta."
msgid "At the bottom of an individual template's form, there are three tabs: :guilabel:`Body`, :guilabel:`Buttons`, and :guilabel:`Variables`; these three tabs combined create the WhatsApp template."
msgid "The text is entered into the :guilabel:`Body` tab, and dynamic content that is called out in the :guilabel:`Body` tab is specified in the :guilabel:`Variables` tab. Every piece of dynamic content (e.g., placeholders) in the message (body) is specifically called out and specified in the :guilabel:`Variables` tab."
msgid "Templates are prefabricated layouts that allow users to send professional looking messages to customers. These templates are capable of containing dynamic data that will populate in the end message using variables that are set in the template configuration. For example, messages can contain the end user's name, call out specific products, or reference a sales order, to name a few convenient and impactful variables."
msgid "To create a WhatsApp template, go to the :menuselection:`WhatsApp app --> Templates` dashboard and click :guilabel:`New`. On the form, enter a :guilabel:`Name` for the template, and select a :guilabel:`Language`."
msgid "In order to complete this next task, administrator access rights are needed to edit the :guilabel:`Applies to` field. See this :doc:`access rights documentation <../general/users/access_rights>` for more information."
msgid "In the :guilabel:`Account` drop-down menu, select the *WhatsApp business account* in Odoo that this template should link to. Next, under the :guilabel:`Applies to` field select the *model* the server action will apply to for this template."
msgid "These models can also be accessed in :ref:`developer mode <developer-mode>`. On a contact form (or similar relevant form in Odoo), navigate to the model that will be referenced, and hover over any field name. A box of backend information will reveal itself with the specific Odoo :guilabel:`Model` name in the backend. Search (using the front-end name) for this model in the :guilabel:`Applies to` drop-down menu in the WhatsApp template."
msgid "Often when changing the model or :guilabel:`Applies to` field, the :guilabel:`Phone Field` may produce an error The :guilabel:`Phone Field` should always be set to the `Phone` or `Mobile` model."
msgid "To search available fields, type in the front-end name in the :guilabel:`Search...` box. This will find a result from all of the available fields for the model (:guilabel:`Applies to`) that the template is created for."
msgid "In order to find specific fields, multiple levels may need to be navigated in the search results box. Use the :guilabel:`> (right chevron)` and :guilabel:`⬅️ (left arrow)` icons to navigate between the menu levels."
msgid "Change the :guilabel:`Category` to fit either a :guilabel:`Marketing`, :guilabel:`Utility`, or :guilabel:`Authentication` category. In most instances the first two options will be used, unless the user would like to send a password reset or something security related. Set to :guilabel:`Marketing` should there be anything promotional being sent and set to :guilabel:`Utility` should there be general transactional messages being sent (i.e., sales order, event ticket, etc)."
msgid "Add any :guilabel:`Users` that are allowed to use this template. In the right-side column, a :guilabel:`Header type` can be configured along with a :guilabel:`Header message`, as well."
msgid "When all the necessary changes are made to the template, click on the :guilabel:`Submit for approval` button in the upper-left corner. This will cause the status of the template to change to :guilabel:`Pending`."
msgid "The status will remain in :guilabel:`Pending` until a decision has been made by Meta, whereby a confirmation email will then be sent indicating that the template has been approved (or rejected). The templates will then need to be synced from the Odoo database."
msgid "There are pre-configured demo data templates available in Odoo to use or modify. These templates can be used as-is or modified to suit a specific business need."
msgid "To use these templates, navigate to :menuselection:`WhatsApp app --> Templates` and select a pre-configured template. Click :guilabel:`Submit for Approval` to start the approval process. An email will be sent to the administrator of the Meta account when the template has been approved."
msgid "Buttons can be added into the message from the :guilabel:`Buttons` tab. Enter the :guilabel:`Type` (either :guilabel:`Visit Website`, :guilabel:`Call Number`, or :guilabel:`Quick Reply`), and then specify the :guilabel:`Button Text`, :guilabel:`Call Number` or :guilabel:`Website URL` (including :guilabel:`Url Type`), depending on the :guilabel:`Type` of button."
msgid "Buttons can also be added on the Meta business console. See Meta's WhatsApp template dashboard by navigating to `<https://business.facebook.com/wa/manage/home>`_. Then go to :menuselection:`Account tools --> Message templates`."
msgid "Dynamic variables reference certain fields within the Odoo database to produce unique data in the WhatsApp message when using a template. Dynamic variables are encoded to display fields from within the database, referencing fields from within a model."
msgid "Many companies like to customize their WhatsApp messages with a personalized piece of customer information to grab attention. This can be accomplished in Odoo by referencing a field within a model by setting a dynamic variable. For example, a customer's name can be referenced in the email from the :guilabel:`Customer` field on the :guilabel:`Sales Order` model."
msgid "Dynamic variables can be added in to the :guilabel:`Body` by adding :guilabel:`placeholders` in the *text*. To add a placeholder in the *message body* enter the following text `{{1}}`. For the second placeholder enter `{{2}}` and increase incrementally as more placeholders are added to the text."
msgid "These placeholders must be configured on the :guilabel:`Variables` tab of the template before submitting for approval from Meta. To edit the dynamic variables on a template, first change the :guilabel:`Type` to :guilabel:`Field of Model`. This allows Odoo to reference a field within a model to produce unique data in the message being sent."
msgid "Next, edit the :guilabel:`Field` of the dynamic variables. The :guilabel:`Applies to` field in the template should be edited prior to ensure the correct model and field are referenced."
msgid "To search the available fields, type in the front-end name of the field in the search box. This will find a result from all of the available fields for the model (:guilabel:`Applies to`) that the template is created for. There may be multiple levels that need to be configured."
msgid "For example, in the :guilabel:`Body` tab, if the following is typed, \"Hello {{1}},\", then `{{1}}` must be set in the :guilabel:`Variables` tab. For this specific case, the message should greet the customer by name, so the `{{1}}` should be configured to populate the `{{1}}` :guilabel:`Field` with the :guilabel:`Customer` name."
msgid "After updating the dynamic variables on the template, the template needs to be submitted to Meta for approval again. Click :guilabel:`Submit for Approval` to start the approval process. An email will be sent to the administrator of the Meta account when the template has been approved."
msgid "To see the status to Meta's WhatsApp template dashboard by navigating to `<https://business.facebook.com/wa/manage/home>`_. Then go to :menuselection:`Account tools --> Message templates`."
msgid "Templates must be synced on the Odoo database once they are approved by the Meta team. To do so, begin by navigating to :menuselection:`WhatsApp app --> Configuration --> WhatsApp Business Accounts` and select the configuration that should be synced. Under the section marked :menuselection:`Sending messages`, towards the bottom, click on :guilabel:`Sync Templates`. Meta will update the templates that are approved so that they can be utilized with various apps in the database."
msgid "Templates can also be synced individually from the template itself. Navigate to the :menuselection:`WhatsApp app --> Templates` dashboard and select the template to sync. Then, click on the :guilabel:`Sync Template` button located in the top menu of the template's form."
msgid "First, navigate to `Meta's WhatsApp template dashboard <https://business.facebook.com/wa/manage/home>`_, and then go to :menuselection:`Account tools --> Message templates`."
msgid "To create a WhatsApp template, click on the blue :guilabel:`Create template` button, and then select the :guilabel:`Category`. The options listed include: :guilabel:`Marketing`, :guilabel:`Utility`, and :guilabel:`Authentication`. In most instances the first two options will be used, unless the user would like to send a password reset or something security related."
msgid "After making the appropriate selections, click on :guilabel:`Continue` in the upper-right corner. The page redirects to the :guilabel:`Edit template` page. Here the :guilabel:`Header`, :guilabel:`Body`, :guilabel:`Footer` and :guilabel:`Buttons` are configured. To the right of the template is a preview of what the template will look like in production."
msgid "When all the necessary changes are made to the template, click on the :guilabel:`Submit` button in the upper-right corner. A confirmation window appears to confirm the language— click :guilabel:`Confirm` to approve and then another window appears stating that the template will be submitted to Meta for review and approval."
msgid "The :guilabel:`Status` of the template will remain in :guilabel:`In review` until a decision has been made by Meta. Once an email confirmation is received approving the template, the templates will need to be synced from within the Odoo database."
msgid "For more information on configuring templates on the Meta developer console visit `Meta's WhatsApp template documentation <https://developers.facebook.com/docs/whatsapp/business-management-api/message-templates/>`_."
msgid "Notifications in WhatsApp are handled similar to a message conversation in Odoo. A pop-up window appears with the received conversation from the customer. By default, notifications are set in the WhatsApp business account configuration in Odoo."
msgid "Notification settings can be adjusted by navigating to :menuselection:`WhatsApp app --> Configuration --> WhatsApp Business Accounts`. From there, select the account and scroll down to the :menuselection:`Control` section where notifications are handled. Under the :guilabel:`Notify users` heading, type in the field which user(s) should be notified for this particular WhatsApp channel."
msgid "Once a conversation is initiated between a user and a customer, notifications to all the users specified in the WhatsApp business account configuration won't occur. Only notifications to the user(s) in the conversation will occur. Should the user not respond within 15 days, the customer's reply after the 15 days will populate once again to all the users specified in the WhatsApp configuration."
msgid "Users can be added to a WhatsApp chat by expanding the WhatsApp pop-up window. WhatsApp conversations are located in the *Discuss* app. Click on the :guilabel:`👤+ (add user)` icon next to it, and a window appears to invite users to the conversation."
msgid "As of February 1, 2023, if the Meta app requires advanced level access to permissions, a complete business verification may need to be completed. This includes submitting office business documents to Meta. `See this documentation <https://developers.facebook.com/docs/development/release/business-verification>`_."
msgid "When syncing the templates there may be an instance when there are multiple templates with the same name on Meta's business manager and in Odoo. This causes a duplicate validation error. To correct this issue, rename the duplicate template name on Odoo and sync the templates once again by following the steps here: :ref:`productivity/whatsapp/sync`."
msgid "Should the temporary token not be replaced with a permanent token a user error will populate in Odoo when testing the connection after sending fails. To correct this issues see :ref:`productivity/whatsapp/token`."
