# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 10.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-07-26 15:12+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#: ../../discuss.rst:5
msgid "Discuss"
msgstr ""

#: ../../discuss/email_servers.rst:3
msgid "How to use my own email servers to send and receive email in Odoo"
msgstr ""

#: ../../discuss/email_servers.rst:6
msgid "When is it needed"
msgstr ""

#: ../../discuss/email_servers.rst:7
msgid "Using your own email servers is required to send and receive messages in Odoo Community or Enterprise. Odoo Online embeds an out-of-box email solution that works straight away. However you can still use your own email servers with the online edition. Some insights are provided here below."
msgstr ""

#: ../../discuss/email_servers.rst:14
msgid "How to set it up"
msgstr ""

#: ../../discuss/email_servers.rst:15
msgid "As a system admin, go to :menuselection:`Settings --> General Settings` and check *External Email Servers* (watch out: this checkbox only shows up after Odoo 10). Then, go through the following steps."
msgstr ""

#: ../../discuss/email_servers.rst:21
msgid "Office 365 email servers don't allow easily to send external emails from hosts like Odoo. Refer to the `Office 365 documentation`_ to make it working."
msgstr ""

#: ../../discuss/email_servers.rst:27
msgid "Set an outgoing email server for outbound messages"
msgstr ""

#: ../../discuss/email_servers.rst:28
msgid "You need the SMTP data of your email provider (Gmail, Outlook, Yahoo, AOL, etc.) as well as your admin credentials. Once all the information has been filled out, click on *Test Connection*."
msgstr ""

#: ../../discuss/email_servers.rst:36
msgid "Set an incoming email server for inbound messages"
msgstr ""

#: ../../discuss/email_servers.rst:37
msgid "Fill out the form according to your email provider’s settings. Leave the *Actions to Perform on Incoming Mails* blank. Once all the information has been filled out, click on *TEST & CONFIRM*."
msgstr ""

#: ../../discuss/email_servers.rst:44
msgid "By default inbound messages are fetched every 5 minutes. You can change this value in developer mode. Go to :menuselection:`Settings --> Technical --> Automation --> Scheduled Actions` and look for *Mail: Fetchmail Service*."
msgstr ""

#: ../../discuss/email_servers.rst:50
msgid "Set the domain name"
msgstr ""

#: ../../discuss/email_servers.rst:51
msgid "Enter the domain name of your email servers (e.g. mycompany.com) in General Settings."
msgstr ""

#: ../../discuss/email_servers.rst:58
msgid "Create a catchall address"
msgstr ""

#: ../../discuss/email_servers.rst:59
msgid "When a contact replies to an email sent from Odoo, the *reply-to* address is a generic address used to route the reply to the right discussion thread in Odoo (opportunity, order, task, etc.) and to the inbox of all its followers. By default this address is \"catchall@\" but it can be changed."
msgstr ""

#: ../../discuss/email_servers.rst:64
msgid "Create a catchall address in your email server settings. We advise you to use \"catchall@\" so that everything works out straight away. If you want to use another alias, you have extra steps in Odoo:"
msgstr ""

#: ../../discuss/email_servers.rst:68
msgid "Activate the developer mode from your Settings Dashboard."
msgstr ""

#: ../../discuss/email_servers.rst:73
msgid "Refresh your screen. Then go to :menuselection:`Settings --> Technical --> Parameters --> System Parameters` and enter your custom catchall alias in *mail.catchall.alias*."
msgstr ""

#: ../../discuss/email_servers.rst:80
msgid "You can edit the email alias used for bounced messages the same way."
msgstr ""

#: ../../discuss/email_servers.rst:83
msgid "How to use my own email servers with Odoo Online"
msgstr ""

#: ../../discuss/email_servers.rst:84
msgid "Odoo Online comes up with an embedded and ready-to-use email solution with *@yourcompany.odoo.com* as domain. We recommend to keep this default setup as it is really convenient."
msgstr ""

#: ../../discuss/email_servers.rst:88
msgid "Nevertheless you can still use your own email servers if you want to manage your email server's reputation (blacklisting, etc). The configuration for both incoming and outgoing mail servers is given here above."
msgstr ""

#: ../../discuss/email_servers.rst:93
msgid "However when it comes to incoming messages, we don't recommend to exclusively use your own email server. Indeed, Odoo Online is fetching incoming messages from the email server once every hour only. To receive emails in real time, you should rather use a **catchall redirection** (your server -> Odoo server). To do so:"
msgstr ""

#: ../../discuss/email_servers.rst:99
msgid "Create a catchall address in your email server settings (e.g. catchall)."
msgstr ""

#: ../../discuss/email_servers.rst:100
msgid "Still from such settings, set a redirection from this catchall address to Odoo's one: catchall@yourdomain.ext -> catchall@yourcompany.odoo.com."
msgstr ""

#: ../../discuss/email_servers.rst:103
msgid "In Odoo check *External Email Servers* in :menuselection:`Settings --> General Settings` and enter your email domain name (i.e. yourdomain.ext)."
msgstr ""

#: ../../discuss/email_servers.rst:105
msgid "No need to set up an incoming email server in such a case."
msgstr ""

#: ../../discuss/email_servers.rst:109
msgid "How to be SPF-compliant when using external email servers in Odoo"
msgstr ""

#: ../../discuss/email_servers.rst:110
msgid "Sender Policy Framework (SPF) is an email-validation system that checks that incoming mail from a domain comes from a host authorized by that domain's administrator. Such a security system is used in most email servers. If you don't comply with it, your emails sent from Odoo will be likely flagged as spam."
msgstr ""

#: ../../discuss/email_servers.rst:116
msgid "To be SPF-compliant, you need to authorize Odoo as a sending host in your domain name settings:"
msgstr ""

#: ../../discuss/email_servers.rst:119
msgid "Sign in to your domain’s account at your domain host."
msgstr ""

#: ../../discuss/email_servers.rst:120
msgid "Locate the page for updating your domain’s DNS records."
msgstr ""

#: ../../discuss/email_servers.rst:121
msgid "If no TXT record is set, create one with following definition: v=spf1 include:_spf.odoo.com ~all"
msgstr ""

#: ../../discuss/email_servers.rst:123
msgid "In case a TXT record is already set, add \"include:_spf.odoo.com\"."
msgstr ""

#: ../../discuss/email_servers.rst:125
msgid "e.g. for a Gmail server it should be:"
msgstr ""

#: ../../discuss/email_servers.rst:127
msgid "v=spf1 include:_spf.odoo.com include:_spf.google.com ~all"
msgstr ""

#: ../../discuss/email_servers.rst:129
msgid "Find `here <https://www.mail-tester.com/spf/>`__ the exact procedure to create or modify TXT records in your own domain registrar."
msgstr ""

#: ../../discuss/email_servers.rst:132
msgid "Your new SPF record can take up to 48 hours to go into effect, but this usually happens more quickly."
msgstr ""

#: ../../discuss/email_servers.rst:135
msgid "Adding more than one SPF record for a domain can cause problems with mail delivery and spam classification. Instead, we recommend using only one SPF record by modifying it to authorize Odoo."
msgstr ""

#: ../../discuss/email_servers.rst:140
msgid "How to choose between Odoo and my traditional email box"
msgstr ""

#: ../../discuss/email_servers.rst:141
msgid "Odoo Discuss is a perfect tool to send and read messages related to business documents. However it doesn't aim to replace a full-featured email solution (Gmail, Outlook, Yahoo, AOL, etc.). We recommend to take the most out of both systems without mingling them: What is related to Odoo business objects or applications goes into Odoo; What is not can be managed into your external email box."
msgstr ""

#: ../../discuss/email_servers.rst:148
msgid "To do so, create specific email aliases to use in Odoo (to generate leads or opportunities, helpdesk tickets, etc.). If you take an email alias already used for messaging outside of Odoo, incoming messages will land into both systems. This will negatively impact your productivity."
msgstr ""

#: ../../discuss/mail_twitter.rst:3
msgid "How to follow Twitter feed from Odoo"
msgstr ""

#: ../../discuss/mail_twitter.rst:8
msgid "You can follow specific hashtags on Twitter and see the tweets within the Odoo Discuss channels of your choice. The tweets are retrieved periodically from Twitter. An authenticated user can retweet the messages."
msgstr ""

#: ../../discuss/mail_twitter.rst:13
msgid "Setting up the App on Twitter's side"
msgstr ""

#: ../../discuss/mail_twitter.rst:15
msgid "Twitter uses an \"App\" on its side which is opens a gate to which Odoo asks for tweets, and through which a user can retweet. To set up this app, go to http://apps.twitter.com/app/new and put in the values:"
msgstr ""

#: ../../discuss/mail_twitter.rst:19
msgid "Name: this is the name of the application on Twitter"
msgstr ""

#: ../../discuss/mail_twitter.rst:21
msgid "Website: this is the external url of your Odoo database, with \"/web\" added. For example, if your Odoo instance is hosted at \"http://www.example.com\", you should put \"http://www.example.com/web\" in this field."
msgstr ""

#: ../../discuss/mail_twitter.rst:25
msgid "Callback URL: this is the address on which Twitter will respond. Following the previous example you should write \"http://www.example.com/web/twitter/callback\"."
msgstr ""

#: ../../discuss/mail_twitter.rst:28
msgid "Do not forget to accept the terms **Developer agreement** of use and click on **Create your Twitter application** at the bottom of the page."
msgstr ""

#: ../../discuss/mail_twitter.rst:33
msgid "Getting the API key and secret"
msgstr ""

#: ../../discuss/mail_twitter.rst:35
msgid "When on the App dashboard, switch to the **Keys and Access Tokens** tab."
msgstr ""

#: ../../discuss/mail_twitter.rst:40
msgid "And copy those values in Odoo in :menuselection:`Settings--> General Settings--> Twitter discuss integration` and click on **Save** to save the settings."
msgstr ""

#: ../../discuss/mentions.rst:3
msgid "How to grab attention of other users in my messages"
msgstr ""

#: ../../discuss/mentions.rst:5
msgid "You can **mention** a user in a channel or chatter by typing **@user-name**. Mentioning a user in the chatter will set them as a follower of the item (if they are not already) and send a message to their inbox. The item containing the mention will also be bolded in the list view. Mentioning a user in a channel will send a message to their inbox. You cannot mention a user in a channel who is not subscribed to the channel. Typing **#channel-name** will provide a link to the mentioned channel in either a chatter or another channel."
msgstr ""

#: ../../discuss/mentions.rst:15
msgid "Direct messaging a user"
msgstr ""

#: ../../discuss/mentions.rst:17
msgid "**Direct messages** are private messages viewable only by the sender and recipient. You can send direct messages to other users from within the Discuss module by creating a new conversation or selecting an existing one from the sidebar. Direct messages can be sent from anywhere in Odoo using the speech bubble icon in the top bar. The online status of other users is displayed to the left of their name. A **green dot** indicates that a user is Online, an **orange dot** that they are Idle, and a **grey dot** that they are offline."
msgstr ""

#: ../../discuss/mentions.rst:28
msgid "Desktop notifications from Discuss"
msgstr ""

#: ../../discuss/mentions.rst:30
msgid "You can choose to see **desktop notifications** when you receive a new direct message. The notification shows you the sender and a brief preview of the message contents. These can be configured or disabled by clicking on the gear icon in the corner of the notification.."
msgstr ""

#: ../../discuss/monitoring.rst:3
msgid "How to be responsive at work thanks to my Odoo inbox"
msgstr ""

#: ../../discuss/monitoring.rst:5
msgid "Use the **Inbox** in Discuss app to monitor updates and progress on everything you do in Odoo. Notifications and messages from everything you follow or in which you are mentioned appear in your inbox."
msgstr ""

#: ../../discuss/monitoring.rst:13
msgid "You can keep an eye on your **Inbox** from any screen."
msgstr ""

#: ../../discuss/monitoring.rst:18
msgid "Marking an item with a check marks the message as **read** and removes it from your inbox. If you would like to save an item for future reference or action, mark it with a star to add it to the **Starred** box. You can star any message or notification in Discuss or any of the item-specific chatters throughout Odoo to keep tabs on it here."
msgstr ""

#: ../../discuss/overview.rst:3
msgid "Why to use Odoo Discuss"
msgstr ""

#: ../../discuss/overview.rst:5
msgid "Odoo Discuss is an easy to use messaging app for teams that brings all your organization's communication into one place and seamlessly integrates with the Odoo platform. Discuss lets you send and receive messages from wherever you are in Odoo as well as manage your messages and notifications easily from within the app. Discuss allows you to create **channels** for team chats, conversations about projects, meeting coordination, and more in one simple and searchable interface."
msgstr ""

#: ../../discuss/team_communication.rst:3
msgid "How to efficiently communicate in team using channels"
msgstr ""

#: ../../discuss/team_communication.rst:5
msgid "You can use **channels** to organize discussions between individual teams, departments, projects, or any other group that requires regular communication. By having conversations that everyone in the channel can see, it's easy to keep the whole team in the loop with the latest developments."
msgstr ""

#: ../../discuss/team_communication.rst:12
msgid "Creating a channel"
msgstr ""

#: ../../discuss/team_communication.rst:14
msgid "In Discuss there are two types of channels - **public** and **private**."
msgstr ""

#: ../../discuss/team_communication.rst:17
msgid "A **public channel** can only be created by an administrator with write privileges and can be seen by everyone in the organization. By contrast, a **private channel** can be created by any user and by default is only visible to users who have been invited to this channel."
msgstr ""

#: ../../discuss/team_communication.rst:24
msgid "A public channel is best used when many employees need to access information (such as interdepartmental communication or company announcements), whereas a private channel should be used whenever information should be limited to specific users/employees (such as department specific or sensitive information)."
msgstr ""

#: ../../discuss/team_communication.rst:31
msgid "Configuring a channel"
msgstr ""

#: ../../discuss/team_communication.rst:33
msgid "You can configure a channel's name, description, access rights, automatic subscription, and emailing from :menuselection:`#channel-name --> Settings`. Changing channel access rights allows you to control which groups can view each channel. You can make a channel visible by all users, invited users, or users within a selected user group. Note that allowing \"Everyone\" to follow a private channel will let other users view and join it as they would a public channel."
msgstr ""

#: ../../discuss/team_communication.rst:47
msgid "How to set up a mailing list"
msgstr ""

#: ../../discuss/team_communication.rst:49
msgid "A channel can be configured to behave as a mailing list. From within :menuselection:`#channel-name --> Settings`, define the email you would like to use. Users can then post to the channel and choose to receive notifications using the defined email address. An envelope icon will appear next to the channel name in the list to indicate that a channel will send messages by email."
msgstr ""

#: ../../discuss/team_communication.rst:57
msgid "Locating a channel"
msgstr ""

#: ../../discuss/team_communication.rst:59
msgid "If you do not see a channel on your dashboard, you can search the list of **public channels** to locate the correct channel or create a new channel by clicking the plus icon."
msgstr ""

#: ../../discuss/team_communication.rst:66
msgid "You can also click the **CHANNELS** heading to browse a list of all public channels. This allows the user to manually **join** and **leave** public channels from a single screen."
msgstr ""

#: ../../discuss/team_communication.rst:71
msgid "It is always wise to search for a channel before creating a new one to ensure that duplicate entries are not created for the same topic."
msgstr ""

#: ../../discuss/team_communication.rst:76
msgid "Using filters to navigate within Discuss"
msgstr ""

#: ../../discuss/team_communication.rst:78
msgid "The topbar search provides access to the same comprehensive search function present in the rest of Odoo. You can apply multiple **filter criteria** and **save filters** for later use. The search function accepts wildcards by using the underscore character \"\\ **\\_**\\ \" to represent a **single character wildcard.**"
msgstr ""

#: ../../discuss/tracking.rst:3
msgid "How to follow a discussion thread and define what I want to hear about"
msgstr ""

#: ../../discuss/tracking.rst:6
msgid "How to follow a discussion thread"
msgstr ""

#: ../../discuss/tracking.rst:7
msgid "You can keep track of virtually any business object in Odoo (an opportunity, a quotation, a task, etc.), by **following** it."
msgstr ""

#: ../../discuss/tracking.rst:14
msgid "How to choose the events to follow"
msgstr ""

#: ../../discuss/tracking.rst:15
msgid "You can choose which types of events you want to be notified about. The example below shows the options available when following a **task** in the **Project** app."
msgstr ""

#: ../../discuss/tracking.rst:23
msgid "How to add other followers"
msgstr ""

#: ../../discuss/tracking.rst:24
msgid "You can invite other users and add channels as followers. Adding a channel as a follower will send messages posted in the chatter to the channel with a link back to the original document."
msgstr ""

#: ../../discuss/tracking.rst:34
msgid "How to be a default follower"
msgstr ""

#: ../../discuss/tracking.rst:35
msgid "You are automatically set as a default follower of any item you create. In some applications like CRM and Project, you can be a default follower of any new record created to get notified of specific events (e.g. a new task created, an opportunity won)."
msgstr ""

#: ../../discuss/tracking.rst:40
msgid "To do so, start following the parent business object (e.g. the sales channel in CRM, the project in Project). Then, choose the events you want to hear about."
msgstr ""

