11ab0203b1
* Add builtin plugin for auto-issuing orders * Add plugin to auto-issue orders * Add placeholder documentation * Fix typo * Adds image macro - To replace img.html - includes checking if file exists * Fix tooltips * More docs * Adjust plugin settings filters * docs * More docs * More docs * Updates * Less restrictive URL checking * Refactor build order page * Fix typo * Allow 429 * Debug output * More debug * Construct assets dir * Cleanup * Update docs README * Refactoring more pages * Fix image link * Fix SSO settings * Add hook to check for missing settings - Ensure that all settings are documented! * Add missing user settings * Update docstring * Tweak SSO.md * Image updates * More updates * Tweaks * Exclude orders without a target_date * Fix for issuing build orders * Further refactoring * Fixes * Image refactoring * More refactoring * More refactoring * Refactor app images * Fix pathing issues * Suppress some openapidocs warnings in logs (much easier to debug docs build issues) * Fix image reference * Reduce error messages * Fix image links * Fix image links * Reduce docs log output * Ensure settings are loaded before displaying them * Fix for UI test * Fix unit test * Test tweaks
2.8 KiB
title
| title |
|---|
| Part Notifications |
General Notification Details
Users can select to receive notifications when certain events occur.
!!! warning "Email Configuration Required" External notifications require correct email configuration. They also need to be enabled in the settings under notifications`.
!!! warning "Valid Email Address" Each user must have a valid email address associated with their account to receive email notifications
Notifications are also shown in the user interface. New notifications are announced in the header.
{{ image("part/notification_header.png", "Notification header") }}
They can be viewed in a flyout.
{{ image("part/notification_flyout.png", "Notification flyout") }}
All current notifications are listed in the inbox.
{{ image("part/notification_inbox.png", "Notification inbox") }}
All past notification are listed in the history. They can be deleted one-by-one or all at once from there.
{{ image("part/notification_history.png", "Notification history") }}
Part Notification Events
Low Stock Notification
If the minimum stock threshold is set for a Part, then a "low stock" notification can be generated when the stock level for that part falls below the configured level.
Any users who are subscribed to notifications for the part in question will receive a low stock notification via email.
Build Order Notification
When a new Build Order is created, the InvenTree software checks to see if any of the parts required to complete the order are low on stock.
If there are any parts with low stock, a notification is generated for any users subscribed to notifications for the part being built.
Subscribing to Notifications
Users can "subscribe" to either a Part or Part Category, to receive notifications.
Part
When subscribed to a Part, a user will receive notifications when events occur which pertain to:
- That particular part
- Any parts which are variants of that part
If a user is subscribed to a particular part, it will be indicated as shown below:
{{ image("part/part_subscribe_on.png", "Part subscribed") }}
If the user is not subscribed, the subscription icon is greyed out, as shown here:
{{ image("part/part_subscribe_off.png", "Part not subscribed") }}
Clicking on this icon will toggle the subscription status for this part.
Part Category
When subscribed to a Part Category, a user will receive notifications when particular events occur which pertain to:
- That particular category
- Any sub-categories at lower levels
- Any parts contained in the category
- Any parts contained in the lower level categories
Subscribing to a part category operates in the same manner as for a part - simply click on the notification icon.