mirror of
https://github.com/inventree/InvenTree.git
synced 2026-07-10 09:00:57 +00:00
[docs] Docs updates (#10678)
* Display PendingShipments panel - Overview of all outstanding shipments * Update UI tests * add separate page for troubleshooting * Restructure menus a bit * Fix top-level page for mobile app * Add option to override default value in docs * Update global.md * Formatting updates * Update sales pages * Move order images to "purchasing" * Small tweaks * Make "Concepts" a top-level documentation item * Update image
This commit is contained in:
@@ -29,7 +29,7 @@ It is recommended to disable a company rather than deleting it, as this will pre
|
||||
|
||||
To disable a company, simply edit the company details and set the `active` attribute to `False`:
|
||||
|
||||
{{ image("order/company_disable.png", "Disable Company") }}
|
||||
{{ image("purchasing/company_disable.png", "Disable Company") }}
|
||||
|
||||
To re-enable a company, simply follow the same process and set the `active` attribute to `True`.
|
||||
|
||||
@@ -49,7 +49,7 @@ Each company can have multiple assigned *Contacts*. A contact identifies an indi
|
||||
|
||||
The list of contacts associated with a particular company is available in the <span class='badge inventree nav main'>{{ icon("users") }} Contacts</span> navigation tab:
|
||||
|
||||
{{ image("order/contact_list.png", "Company Contacts") }}
|
||||
{{ image("purchasing/contact_list.png", "Company Contacts") }}
|
||||
|
||||
A *contact* can be assigned to orders, (such as [purchase orders](../purchasing/purchase_order.md) or [sales orders](../sales/sales_order.md)).
|
||||
|
||||
|
||||
@@ -37,10 +37,10 @@ By default, project code support is disabled. Select the *Enable Project Codes*
|
||||
|
||||
Project codes can be assigned to an order when the order is created, or at any later stage by simply editing the order. If project code support is enabled, a *Project Code* field is available in the order details form:
|
||||
|
||||
{{ image("order/assign_project_code.png", "Assign Project Code") }}
|
||||
{{ image("purchasing/assign_project_code.png", "Assign Project Code") }}
|
||||
|
||||
## Filtering by Project Codes
|
||||
|
||||
The order tables can be easily filtered or sorted by project code:
|
||||
|
||||
{{ image("order/filter_by_project.png", "Filter by Project Code") }}
|
||||
{{ image("purchasing/filter_by_project.png", "Filter by Project Code") }}
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: Threat Model
|
||||
---
|
||||
|
||||
## Thread Model
|
||||
## Threat Model
|
||||
|
||||
Deploying InvenTree to production requires to knowledge of the security assumptions and threat model of the underlying system. This document outlines the security assumptions and threat model of InvenTree as a software. It is assumed that the system that InvenTree is deployed on top of is configured following best practices and is trusted.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user