odoo-forge-bundle 0.1.0

package/payload/skills/odoo18-docs/references/docs/applications/general/users/portal.md

@@ -0,0 +1,168 @@
+---
+title: "Portal access"
+source_url: "https://docs.odoo.sbggai.top/applications/general/users/portal.html"
+---
+
+=============
+# Portal access
+
+.. _portal/main:
+
+Portal access is given to users who need the ability to view certain documents or information within
+an Odoo database.
+
+Some common use cases for providing portal access include allowing customers to read/view any or all
+of the following in Odoo:
+
+- leads/opportunities
+- quotations/sales orders
+- purchase orders
+- invoices & bills
+- projects
+- tasks
+- timesheets
+- tickets
+- signatures
+- subscriptions
+
+> **note**:
+>    Portal users only have read/view access, and will not be able to edit any documents in the
+   database.
+
+.. _portal/access:
+
+# Provide portal access to customers
+
+From the main Odoo dashboard, select the :guilabel:`Contacts` application. If the contact is not yet
+created in the database, click on the :guilabel:`Create` button, enter the details of the contact,
+and then click :guilabel:`Save`. Otherwise, choose an existing contact, and then click on the
+:guilabel:`Action` drop-down menu located at the top-center of the interface.
+
+.. image:: portal/grant-portal-access.png
+   :align: center
+   :alt: Use the Contacts application to give portal access to users.
+
+Then select :guilabel:`Grant portal access`. A pop-up window appears, listing three fields:
+
+- :guilabel:`Contact`: the recorded name of the contact in the Odoo database
+- :guilabel:`Email`: the contact's email address that they will use to log into the portal
+- :guilabel:`In Portal`: whether or not the user has portal access
+
+To grant portal access, first enter the contact's :guilabel:`Email` they will use to log into the
+portal. Then, check the box under the :guilabel:`In Portal` column. Optionally, add text to the
+invitation message the contact will receive. Then click :guilabel:`Apply` to finish.
+
+.. image:: portal/add-contact-to-portal.png
+   :align: center
+   :alt: An email address and corresponding checkbox for the contact need to be filled in before
+         sending a portal invitation.
+
+An email will be sent to the specified email address, indicating that the contact is now a portal
+user for that Odoo database.
+
+> **tip**:
+>    To grant portal access to multiple users at once, navigate to a company contact, then click
+   :menuselection:`Action --> Grant portal access` to view a list of all of the company's related
+   contacts. Check the box under the :guilabel:`In Portal` column for all the contacts that need
+   portal access, then click :guilabel:`Apply`.
+
+> **note**:
+>    At any time, portal access can be revoked by navigating to the contact, clicking
+   :menuselection:`Action --> Grant portal access`, and then unselecting the checkbox under the
+   :guilabel:`In Portal` column and clicking :guilabel:`Apply`.
+
+.. _portal/login:
+
+# Change portal username
+
+There may be times when a portal user wants to change their user login. This can be done by any user
+in the database with administrator access rights. The following process outlines the necessary steps
+to change the portal user login.
+
+.. seealso::
+   :doc:`See the documentation on setting access rights
+   </applications/general/users/access_rights>`.
+
+First, navigate to :menuselection:`Settings app --> Users`. Then, under :guilabel:`Filters`, select
+:guilabel:`Portal Users`, or select :guilabel:`Add Custom Filter` and set the following
+configuration :guilabel:`Groups` > :guilabel:`contains` > `portal`. After making this selection,
+search for (and open) the portal user that needs to be edited.
+
+Next, click :guilabel:`Edit` (if necessary), click into the :guilabel:`Email Address` field, and
+proceed to make any necessary changes to this field. The :guilabel:`Email Address` field is used to
+log into the Odoo portal.
+
+> **note**:
+>    Changing the :guilabel:`Email Address` (or login) only changes the *username* on the customer's
+   portal login.
+
+   In order to change the contact email, this change needs to take place on the contact template in
+   the *Contacts* app. Alternatively, the customer can change their email directly from the portal,
+   but the login **cannot** be changed. :ref:`See change customer info <portal/custinfo>`.
+
+# Customer portal changes
+
+There may be times when the customer would like to make changes to their contact information,
+password/security, or payment information attached to the portal account. This can be performed by
+the customer from their portal. The following process is how a customer can change their contact
+information.
+
+.. _portal/custinfo:
+
+## Change customer info
+
+First enter the username and password (login) into the database login page to access the portal user
+account. A portal dashboard will appear upon successfully logging in. Portal documents from the
+various installed Odoo applications will appear with the number count of each.
+
+.. seealso::
+   :ref:`Portal access documentation <portal/main>`.
+
+Next, navigate to the upper-right corner of the portal, and click the :guilabel:`Edit` button, next
+to the :guilabel:`Details` section. Then, change the pertinent information, and click
+:guilabel:`Confirm`.
+
+## Change password
+
+First enter the username and password (login) into the database login page to access the portal user
+account. A portal dashboard will appear upon successfully logging in.
+
+If the customer would like to change their password for portal access, click on the :guilabel:`Edit
+Security Settings` link, below the :guilabel:`Account Security` section. Then, make the necessary
+changes, by typing in the current :guilabel:`Password`, :guilabel:`New Password`, and verify the new
+password. Lastly, click on :guilabel:`Change Password` to complete the password change.
+
+> **note**:
+>    If a customer would like to change the login, as documented above, contact the Odoo database
+   point-of-contact. :ref:`See above documentation on changing the portal username <portal/login>`.
+
+> **note**:
+>    Passwords for portal users and Odoo.com users remain separate, even if the same email address is
+   used.
+
+## Add two-factor authentication
+
+First enter the username and password (login) into the database login page to access the portal user
+account. A portal dashboard will appear upon successfully logging in.
+
+If the customer would like to turn on two-factor authentication (2FA) for portal access, click on
+the :guilabel:`Edit Security Settings` link, below the :guilabel:`Account Security` section.
+
+Click on :guilabel:`Enable two-factor authentication` to turn on :abbr:`2FA (two-factor
+authentication)`. Confirm the current portal password in the :guilabel:`Password` field. Then, click
+on :guilabel:`Confirm Password`. Next, activate :abbr:`2FA (two-factor authentication)` in a
+:abbr:`2FA (two-factor authentication)` app (Google Authenticator, Authy, etc.), by scanning the
+:guilabel:`QR code` or entering a :guilabel:`Verification Code`.
+
+Finally, click :guilabel:`Enable two-factor authentication` to complete the setup.
+
+.. _users-portal-payment-methods:
+
+## Change payment info
+
+First enter the username and password (login) into the database login page to access the portal user
+account. A portal dashboard will appear upon successfully logging in.
+
+If the customer would like to manage payment options, navigate to the :guilabel:`Manage payment
+methods` in the menu on the right. Then, add the new payment information, and select :guilabel:`Add
+new card`.

package/payload/skills/odoo18-docs/references/docs/applications/general/users.md

@@ -0,0 +1,235 @@
+---
+title: ""
+source_url: "https://docs.odoo.sbggai.top/applications/general/users.html"
+---
+
+:show-content:
+# 
+# Users
+
+Odoo defines a *user* as someone who has access to a database. An administrator can add as many
+users as the company needs and, in order to restrict the type of information each user can access,
+rules can be applied to each user. Users and access rights can be added and changed at any point.
+
+.. seealso::
+   - :doc:`users/language`
+   - :doc:`users/access_rights`
+   - :ref:`access-rights/superuser`
+   - :ref:`access-rights/groups`
+
+.. _users/add-individual:
+
+# Add individual users
+
+To add new users, navigate to :menuselection:`Settings app --> Users section --> Manage Users`, and
+click on :guilabel:`New`.
+
+.. image:: users/manage-users.png
+   :alt: View of the settings page emphasizing the manage users field in Odoo.
+
+Fill in the form with all the required information. Under the :doc:`Access Rights
+<users/access_rights>` tab, choose the group within each application the user can have access to.
+
+The list of applications shown is based on the applications installed on the database.
+
+.. image:: users/new-user.png
+   :alt: View of a user's form emphasizing the access rights tab in Odoo.
+
+After filling out all the necessary fields on the page, :icon:`fa-cloud-upload` :guilabel:`(Save
+manually)`. An invitation email is automatically sent to the user, using the email in the
+:guilabel:`Email Address` field. The user must click on the link included in the email to accept the
+invitation, and to create a database login. email is automatically sent to the user, using the email
+in the :guilabel:`Email Address` field. The user must click on the link included in the email to
+accept the invitation, and to create a database login.
+
+.. image:: users/invitation-email.png
+   :alt: View of a user's form with a notification that the invitation email has been sent in Odoo.
+
+> **warning**:
+>    If the company is on a monthly subscription plan, the database automatically updates to reflect
+   the added users. If the company is on a yearly or multi-year plan, an expiration banner appears
+   in the database. An upsell quotation can be created by clicking the banner to update the
+   subscription. Alternatively, [send a support ticket ](https://www.odoo.com/help) to resolve the
+   issue.
+
+## User type
+
+:guilabel:`User Type` can be chosen on the :guilabel:`Manage Users` page by clicking on the search
+bar, and then :ref:`setting a filter <search/preconfigured-filters>` for either :guilabel:`Internal
+User` or :guilabel:`Portal User`.
+
+Odoo databases have three types of users: :guilabel:`Internal User`, :guilabel:`Portal`, and
+:guilabel:`Public`. Users are considered *internal database* users. Portal users are *external
+users*, who only have access to the database portal to view records. Public users are those visiting
+websites, via the website's frontend. See the documentation on :doc:`users/portal`.
+
+The :guilabel:`Portal` user option does **not** allow the administrator to choose access rights.
+These users have specific access rights pre-set (such as, record rules and restricted menus), and
+usually do not belong to the usual Odoo groups.
+
+.. _users/deactivate:
+
+# Deactivate users
+
+To deactivate (i.e. archive) a user, navigate to :menuselection:`Settings app --> Users section -->
+Manage Users`. Then, tick the checkbox to the left of the users to be deactivated.
+
+After selecting the appropriate user to be archived, click the :icon:`fa-cog` :guilabel:`(Actions)`
+icon, and select :guilabel:`Archive` from the resulting drop-down menu. Then, click :guilabel:`OK`
+from the :guilabel:`Confirmation` pop-up window that appears.
+
+.. danger::
+   **Never** deactivate the main/administrator user (admin). Making changes to admin users can have
+   a detrimental impact on the database. This includes *impotent admin*, which means that no user in
+   the database can make changes to the access rights. For this reason, Odoo recommends contacting
+   an Odoo Business Analyst, or our Support Team, before making changes.
+
+## Error: too many users
+
+If there are more users in an Odoo database than provisioned in the Odoo Enterprise subscription,
+the following message is displayed.
+
+.. image:: users/add-more-users.png
+   :alt: Too many users on a database error message.
+
+When the message appears, the database administrator has 30 days to act before the database expires.
+The countdown is updated every day.
+
+To resolve the issue, either:
+
+- Add more users to the subscription by clicking the :guilabel:`Upgrade your subscription` link
+  displayed in the message to validate the upsell quotation, and pay for the extra users.
+- :ref:`Deactivate users <users/deactivate>`, and reject the upsell quotation.
+
+> **warning**:
+>    If the company is on a monthly subscription plan, the database automatically updates to reflect
+   the added users. If the company is on a yearly or multi-year plan, an expiration banner appears
+   in the database. An upsell quotation can be created by clicking the banner to update the
+   subscription. Alternatively, users can [send a support ticket ](https://www.odoo.com/help) to
+   resolve the issue.
+
+Once the database has the correct number of users, the expiration message disappears automatically
+after a few days, when the next verification occurs.
+
+.. _users/passwords-management:
+
+# Password management
+
+Password management is an important part of granting users autonomous access to the database at all
+times. Odoo offers a few different methods to reset a user's password.
+
+> **tip**:
+>    Odoo has a setting to specify the length needed for a password. This setting can be accessed by
+   navigating to :menuselection:`Settings app --> Permissions` section, and entering the desired
+   password length in the :guilabel:`Minimum Password Length` field. By default the value is `8`.
+
+.. image:: users/minimum-password-length.png
+   :alt: Minimum Password Length highlighted in the Permissions section of General Settings.
+
+.. _users/reset-password:
+
+## Reset password
+
+Sometimes, users might wish to reset their personal password for added security, so they are the
+only ones with access to the password. Odoo offers two different reset options: one initiated by the
+user to reset the password, and another where the administrator triggers a reset.
+
+.. _users/reset-password-login:
+
+### Enable password reset from login page
+
+It is possible to enable/disable password resets directly from the login page. This action is
+completed by the individual user, and this setting is enabled by default.
+
+To change this setting, go to :menuselection:`Settings app --> Permissions` section, activate
+:guilabel:`Password Reset`, and then click :guilabel:`Save`.
+
+.. image:: users/password-reset-login.png
+   :alt: Enabling Password Reset in Odoo Settings.
+
+On the login page, click :guilabel:`Reset Password` to initiate the password reset process, and have
+a reset-token sent to the email on file.
+
+.. _users/reset-password-email:
+
+### Send reset instructions
+
+Go to :menuselection:`Settings app --> Users & Companies --> Users`, select the user from the list,
+and click on :guilabel:`Send Password Reset Instructions` on the user form. An email is
+automatically sent to them with password reset instructions.
+
+> **note**:
+>    The :guilabel:`Send Password Reset Instructions` button **only** appears if the Odoo invitation
+   email has already been confirmed by the user. Otherwise, a :guilabel:`Re-send Invitation Email`
+   button appears.
+
+This email contains all the instructions needed to reset the password, along with a link redirecting
+the user to an Odoo login page.
+
+.. image:: users/password-reset-email.png
+   :alt: Example of an email with a password reset link for an Odoo account.
+
+.. _users/change-password:
+
+## Change user password
+
+Go to :menuselection:`Settings app --> Users & Companies --> Users`, and select a user to access its
+form. Click on the :icon:`fa-cog` :guilabel:`(Actions)` icon, and select :guilabel:`Change Password`
+from the resulting drop-down menu. Enter a new password in the :guilabel:`New Password` column of
+the :guilabel:`Change Password` pop-up window that appears, and confirm the change by clicking
+:guilabel:`Change Password`.
+
+.. image:: users/change-password.png
+   :alt: Change a user's password on Odoo.
+
+> **note**:
+>    This operation only modifies the password of the users locally, and does **not** affect their
+   Odoo account.
+
+   If the Odoo password needs to be changed, use the :ref:`send the password reset
+   <users/reset-password-email>`. Odoo.com passwords grant access to the *My Databases* page, and
+   other portal features.
+
+After clicking :guilabel:`Change Password`, the page is redirected to an Odoo login page where the
+database can be re-accessed using the new password.
+
+.. _users/multi-companies:
+
+# Multi Companies
+
+The :guilabel:`Multi Companies` field on a user form allows an administrator to provide access to
+multiple companies for users. To configure a multi-company environment for a user, navigate to the
+desired user by going to: :menuselection:`Settings app --> Users section --> Manage users`. Then,
+select the user to open their user form, and configure with multi-company access.
+
+Under :guilabel:`Multi Companies` in the :guilabel:`Access Rights` tab, set the fields labeled
+:guilabel:`Allowed Companies` and :guilabel:`Default Company`.
+
+The :guilabel:`Allowed Companies` field can contain multiple companies. These are the companies the
+user can access and edit, according to the set access rights. The :guilabel:`Default Company` is the
+company the user defaults to, upon logging in each time. This field can contain only **one**
+company.
+
+> **warning**:
+>    If multi-company access is not configured correctly, it could lead to inconsistent multi-company
+   behaviors. Because of this, only experienced Odoo users should make access rights changes to
+   users for databases with a multi-company configuration. For technical explanations, refer to the
+   developer documentation on :doc:`../../../developer/howtos/company`.
+
+.. image:: users/multi-companies.png
+   :alt: View of a user's form emphasizing the multi companies field in Odoo.
+
+.. seealso::
+   :doc:`companies`
+
+.. toctree::
+   :titlesonly:
+
+   users/language
+   users/2fa
+   users/access_rights
+   users/portal
+   users/facebook
+   users/google
+   users/azure
+   users/ldap

package/payload/skills/odoo18-docs/references/docs/applications/general.md

@@ -0,0 +1,18 @@
+---
+title: "General settings"
+source_url: "https://docs.odoo.sbggai.top/applications/general.html"
+---
+
+================
+# General settings
+
+.. toctree::
+
+    general/apps_modules
+    general/users
+    general/companies
+    general/multi_company
+    general/iot
+    general/email_communication
+    general/integrations
+    general/developer_mode

package/payload/skills/odoo18-docs/references/docs/applications/hr/appraisals/appraisal_analysis.md

@@ -0,0 +1,117 @@
+---
+title: "Appraisal analysis"
+source_url: "https://docs.odoo.sbggai.top/applications/hr/appraisals/appraisal_analysis.html"
+---
+
+==================
+# Appraisal analysis
+
+The **Appraisals** app has the ability to report on all the appraisals in the system, including
+past, present, and future appraisals, and their respective statuses. This report helps managers
+track scheduled appraisals, and identify any overdue or unconfirmed ones.
+
+To access the *Appraisal Analysis* report, navigate to :menuselection:`Appraisals app --> Reporting
+--> Appraisal Analysis`.
+
+On the :guilabel:`Appraisal Analysis` page, a report loads, displaying all the appraisals in the
+database. Each entry is highlighted in a different color to represent their status:
+
++-----------+----------------------------+------------------------------------------------+
+| Color     | Status                     | Meaning                                        |
++===========+============================+================================================+
+| Yellow    |:guilabel:`Done`            | The appraisal was completed.                   |
++-----------+----------------------------+------------------------------------------------+
+| Orange    |:guilabel:`Appraisal Sent`  |The appraisal was confirmed, but not completed. |
++-----------+----------------------------+------------------------------------------------+
+| Red       |:guilabel:`Cancelled`       |The appraisal was cancelled.                    |
++-----------+----------------------------+------------------------------------------------+
+| Gray      |:guilabel:`To Start`        | The appraisal was scheduled, but not confirmed.|
++-----------+----------------------------+------------------------------------------------+
+
+> **note**:
+>    Appraisals are scheduled automatically (appear in gray), according to their respective
+   :ref:`appraisals/appraisal-plan`.
+
+The report displays the current year, in a default Gantt view, grouped by department, with the
+current month highlighted.
+
+To change the period of time that is presented, adjust the date settings in the top-left corner of
+the report by clicking the default :guilabel:`Year` to reveal a drop-down menu of options. The
+options to display are :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, and :guilabel:`Year`.
+Use the adjacent arrows to move forward or backward in time.
+
+At any point, click the :guilabel:`Today` button to have the Gantt view include today's date in the
+view.
+
+To view the details of any appraisal, click on any appraisal. A pop-over window appears, displaying
+the due date for the appraisal. To view more details, click the :guilabel:`View` button, and further
+details appear in a pop-up window.
+
+The report can have other :ref:`filters <search/filters>` and :ref:`groupings <search/group>` set in
+the search bar at the top.
+
+.. image:: appraisal_analysis/analysis.png
+   :align: center
+   :alt: A report showing all the appraisals for the Appraisal Analysis report.
+
+.. _appraisals/group-status:
+
+# Group by status
+
+When a company has a large number of employees, the default :guilabel:`Appraisal Analysis` report
+may display too much information to view easily. In this scenario, viewing the data by status can be
+beneficial.
+
+First, remove the default :icon:`oi-group` :guilabel:`Department` grouping from the search bar.
+Next, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon in the far-right of the search
+bar. Click :guilabel:`Status` in the :icon:`oi-group` :guilabel:`Group By` column. Click away from
+the drop-down menu to close it.
+
+All the appraisals are now organized by status, in the following order: :guilabel:`Cancelled`,
+:guilabel:`Done`, :guilabel:`To Start`, and :guilabel:`Appraisal Sent`.
+
+This view makes it easy to see which appraisals need to be completed, and when, as well as which
+appraisals still need to be confirmed.
+
+.. image:: appraisal_analysis/by-status.png
+   :align: center
+   :alt: A report showing all the appraisals, grouped by status.
+
+# Use case: view only the user's appraisals
+
+When viewing the :guilabel:`Appraisal Analysis` report, it can save time to only view the appraisals
+the signed-in user is responsible for, and hide the rest.
+
+To only view this data, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon in the
+far-right of the search bar, revealing a drop-down menu.
+
+> **note**:
+>    It is not necessary to remove the default :icon:`oi-group` :guilabel:`Department` grouping. If it
+   remains active, the results are grouped by department. If it is removed, the results appear in a
+   list, alphabetically.
+
+Click :guilabel:`Add Custom Filter` at the bottom of the :icon:`fa-filter` :guilabel:`Filters`
+column, and a :guilabel:`Add Custom Filter` pop-up window appears.
+
+Click into the first field, and a pop-over appears with a variety of options. Click the
+:icon:`fa-chevron-right` :guilabel:`(right arrow)` icon after the word :guilabel:`Employee`, then
+scroll down and click on :guilabel:`Manager`. Next, set the middle field to :guilabel:`=`
+:guilabel:`(equal)`. Last, click the third field and select the desired user from the list. When all
+the fields are set, click :guilabel:`Add`.
+
+.. image:: appraisal_analysis/custom.png
+   :align: center
+   :alt: A customized filter to show only the user's employees.
+
+Now, the only appraisals that appear are the appraisals that the selected user is responsible for,
+instead of viewing *all* the appraisals.
+
+This report can also be :ref:`grouped by status <appraisals/group-status>`.
+
+.. image:: appraisal_analysis/users-appraisals.png
+   :align: center
+   :alt: A report showing only the appraisals the user is responsible for, by status.
+
+.. seealso::
+   - :doc:`Odoo essentials reporting <../../essentials/reporting>`
+   - :doc:`../../essentials/search`

package/payload/skills/odoo18-docs/references/docs/applications/hr/appraisals/goals.md

@@ -0,0 +1,87 @@
+---
+title: "Goals"
+source_url: "https://docs.odoo.sbggai.top/applications/hr/appraisals/goals.html"
+---
+
+=====
+# Goals
+
+The Odoo *Appraisals* application allows managers to set goals for their employees. That way,
+employees know what to work toward before their next review.
+
+To view all goals, navigate to :menuselection:`Appraisals app --> Goals`. This presents all the
+goals for every employee, in a default Kanban view.
+
+.. _appraisals/goal-card:
+
+Each goal card contains the following information:
+
+- :guilabel:`Goal`: the name of the goal.
+- :guilabel:`Employee`: the employee the goal is assigned to.
+- :icon:`fa-clock-o` :guilabel:`(clock)` icon: displays the corresponding :doc:`activity icon
+  <../../essentials/activities>` for the record. If no activities are scheduled, the default icon is
+  the :icon:`fa-clock-o` :guilabel:`(clock)`. If any activities have been scheduled, the icon
+  represents the activity scheduled soonest.
+- :guilabel:`Deadline`: the due date for the goal.
+- :guilabel:`Progress`: the percentage of competency set for the goal. The options are
+  :guilabel:`0%`, :guilabel:`25%`, :guilabel:`50%`, :guilabel:`75%`, or :guilabel:`100%`.
+- :guilabel:`Employee Icon`: the profile icon of the employee the goal is assigned to.
+
+If a goal is completed, a :guilabel:`Done` banner appears in the top-right corner of the goal card.
+
+.. image:: goals/goals.png
+   :align: center
+   :alt: The goals Kanban view, with nine goal cards.
+
+> **note**:
+>    Every individual goal requires its own record for each employee. If multiple employees have the
+   same goal, a goal card for each employee appears on the list.
+
+   For example, if Bob and Sara have the same goal of `Typing`, two cards appear in the Kanban view:
+   one `Typing` goal for Bob, and another `Typing` goal for Sara.
+
+# New goal
+
+To create a new goal, navigate to :menuselection:`Appraisals app --> Goals`, and click
+:guilabel:`New` top-left corner to open a blank goal form.
+
+Input the :guilabel:`Goal`, :guilabel:`Employee`, :guilabel:`Progress`, and :guilabel:`Deadline`,
+information on the goal card, as discussed in the :ref:`goal card <appraisals/goal-card>` section of
+this document.
+
+The information requested is all the same information that appears on the goal card in the Kanban
+view, with the addition of a :guilabel:`Tags` field and a :guilabel:`Description` tab.
+
+> **tip**:
+>    The *Appraisals* application does **not** have any pre-configured tags, so all tags need to be
+   added. To add a tag, enter the name of the tag on the line, then click :guilabel:`Create
+   "(tag)"`. Repeat this for all tags that need to be added.
+
+The current user populates the :guilabel:`Employee` field, by default, and the :guilabel:`Manager`
+field populates with the manager set on the employee profile.
+
+Make any necessary changes to the form, and add any notes that might be useful to clarify the goal
+in the :guilabel:`Description` tab.
+
+.. image:: goals/new-goal.png
+   :align: center
+   :alt: A goal form filled out for a Python skill, set to 50% proficiency.
+
+# Completed goals
+
+When a goal has been met, it is important to update the record. A goal can be marked as `Done` in
+one of two ways: from the main :guilabel:`Goals` dashboard, or from the individual goal card.
+
+To mark a goal as `Done` from the main :guilabel:`Goals` dashboard, click on the
+:icon:`fa-ellipsis-v` :guilabel:`(vertical ellipsis)` icon in the top-right of a goal card.
+
+> **note**:
+>    The :icon:`fa-ellipsis-v` :guilabel:`(vertical ellipsis)` icon **only** appears when the mouse
+   hovers over the top-right corner of a goal card.
+
+Then, click :guilabel:`Mark as Done` from the resulting drop-down menu. A green :guilabel:`Done`
+banner appears in the top-right corner of the goal card.
+
+To mark a goal as `Done` from the goal card itself, click on a goal card to open that goal's form.
+Then, click the :guilabel:`Mark as Done` button in the top-left of the form. When clicked, a green
+:guilabel:`Done` banner appears in the top-right corner of the goal form.