ION Factory OS
  • Welcome to ION
  • Features
    • Procedures
      • Steps
        • Content
        • Datagrid
        • Fields
        • Attributes
      • Dependencies
      • Part-Procedure Relationship
      • Attributes
      • Standard Steps
      • Installation Requirements (Beta)
      • Nested Steps and Nested Standard Steps
      • Procedure Best Practices
    • Runs
      • Run Execution Overview
      • Runs And Step States
      • Batching Runs
        • Batching 2.0 Changes
      • Workcenter execution
      • Split Inventory on a Run
      • Redlines
      • Export run data
      • Scheduling runs
      • Time Tracking
      • Attributes
      • Outside Processing
      • Runs Best Practices
    • Parts Library
      • As-built Bill of Materials (aBOM)
        • Editing aBOM build requirements
        • aBOM Beta Changes
          • aBOM actions for developers
      • Inventory
        • Inventory status
        • Inventory splitting
        • Inventory merging
        • Inventory scrapping
        • Kitting
        • Inventory Movement Automations
      • Manufacturing bill of materials (mBOM)
        • mBOM versions
        • Made on Assembly (MOA)
        • Part Substitutes
        • Reference designators
      • Part Attributes
      • Part revision interchangeability
      • Supplier Part Numbers & Purchase Unit Conversions
    • Kitting and Inventory Fulfilment
      • Kit Statuses and Workflows
      • Inventory requests
      • Kitting and runs
      • Fulfilling Multiple Kits
      • Kanban Kitting
    • Purchasing
      • Purchase Orders
        • Types of Purchases
        • Purchase Order Approvals
        • Purchase Order FAQs
        • Supplier Part Numbers & Unit Conversions
        • PO Requirements, Terms, and Quality Clauses
      • Receiving/Inspection
      • Outside Processing
      • Consigned Parts
    • Barcode Labels
      • Templating
        • ION barcode minimum sizes
        • Sample templates
      • Printing
        • Configuring Zebra Browser Print
        • Server Based Barcode Printing (PrintNode)
      • Scanning
        • Scan barcodes from other systems
    • Quality
      • Issues
      • Further Actions - CAPA
      • Issues States, Dispositions, and Resolutions
      • Quality Best Practices
    • Tools
    • Locations
    • Attributes
    • Labels
      • Deleting labels
    • Notifications
    • Search
    • Settings
      • Role based access control
        • Full Glossary of ION Permissions
    • ION Actions
      • ION Actions examples for Quality
      • ION Actions examples for Runs and Procedures
      • ION ACTIONS examples for Supply Chain
  • Analytics
    • Inventory valuation
    • Part impact analysis
    • Users, Roles, Teams
    • Analytics FAQ
    • Data Connector
    • Data Products
  • Plans and Autoplan
    • Autoplan
    • Autoplan glossary
    • Preparing to use Autoplan
    • Clear to build reporting
    • Running Autoplan on a schedule
    • Firm and blocked plan items
    • Location constraints
    • Autoplan suggested suppliers and procedures
    • Reorder point
    • Plan input serial numbers
    • Applying a calendar
    • Plan Reservations
    • Independent schedules
    • Drive demand from kits
    • Drive demand below buy parts configuration
    • Group plan items with the same date
    • Manualy Changing Autoplan Status
  • API
    • How to create an App with ION
    • Access Tokens
    • About GraphQL
    • Interactive API explorer
    • API Keys
    • Examples
      • Notifications
      • Runs
      • Automatically updating fields in runs
      • Parts and Part Revisioning
      • mBOMs
      • Part Inventory and Kitting
      • aBOM (As-built Bill of Materials)
      • Edit time-tracking session data
    • Changelog
    • Webhooks
    • Pagination
  • Automations
    • Auto-checkout of Run Steps
    • Auto-Consumption of Lineside Inventory
    • Automatically Send Purchases to Suppliers
    • Set Close by Run Step on Issue Creation
    • Intent Management / Grade / Tier / Pedigree
      • Data Imprinting
      • ION Actions for Intent
    • Auto-Update mBOM Revision on Part Revision Update
    • Auto-approve part-procedure relationships
    • Purchase Order PDF and Versions
    • Auto Populate PO Line Attributes
    • Imprint Attributes from One Object to Another on a Desired Event
  • Integrations
    • Deploying Integrations and Automations
    • Arena
    • Cofactr
    • Datum
    • Duro
    • NetSuite
      • Purchasing in NetSuite, Receiving in ION
      • Work Order/Assembly Builds
    • Procurable
    • PDF Generator
    • Quickbooks
    • Ramp
    • Silkline Integration
    • Slack
    • Smartsheet
    • SOLIDWORKS
    • Teamcenter
  • Training
    • Standard Operating Procedures
      • Cycle Counting
      • Tool Utilization
    • Guided Flows
    • ION Sandbox
    • Chat Support for ION
  • Troubleshooting
    • Resetting your password
    • Resetting your Multi-Factor Authentication
    • You have no roles... error
  • Changelog
  • Adminstration
    • Security
      • Backups and Security FAQ
      • Single Sign-On (SSO)
        • Okta SAML connection setup
      • Export Control
      • Report Generator Disclaimer
    • Browser and Device Compatibility
    • Authentication
      • My company is new to ION, logging in for the first time.
      • I'm told I'm not authorized to access the application
      • My account has been deactivated
    • Login Page
  • Tickets Portal
Powered by GitBook
On this page
  • Subscriptions
  • Notification Types
  • Platform Wide:
  • Issues:
  • Part Kits:
  • Procedures:
  • Runs:
  • Purchases:
  • Custom Notifications:

Was this helpful?

  1. Features

Notifications

PreviousDeleting labelsNextSearch

Last updated 5 months ago

Was this helpful?

Notifications notify users and teams of status changes, approval requests, comments, mentions, and assignments across the platform via in-app notifications and emails!

At the moment, team based notifications only apply to run step sign offs, issue assignments, and issue approvals. team notifications will be rolled out to the rest of the platform over time.

Subscriptions

Users that are subscribed to objects (i.e. issues, procedures, etc.) will receive future notifications for that object that are detailed below. Creating an object or assigning a user to that object automatically subscribes that user to that object. In addition, users can be manually subscribed and unsubscribed as seen below.

Notification Types

Platform Wide:

These are notifications that are triggered throughout the application.

  • Comment: Indicates someone has commented on an object a user is subscribed to.

  • Mention: The user is @ mentioned in a comment

Issues:

Issue notifications are sent to any issue subscribers. If the issue is related to a run, then all subscribers of that run will automatically be subscribed to the issue.

  • Issue Created: Indicates that an issue has been created.

  • Issue Status Change: Indicates that an issue has changed status.

Certain issue notifications are only sent to the assignee and not to all issue subscribers. Those notifications are listed below.

  • Issue Assigned: Indicates that a user has been assigned to an issue.

  • Issue Approval Request: Indicates to a user that they have been requested to review an issue.

Part Kits:

Part kit notifications are sent to any part kit subscribers.

  • Part Kit Status Changed: Indicates that a part kit has changed statuses.

Certain part kit notifications are only sent to the assignee and not to all issue subscribers. Those notifications are listed below.

  • Part Kit Assigned: Indicates that a user has been assigned to a part kit.

Procedures:

Procedure notifications are sent out to any procedure subscribers and all requested procedure reviewers.

  • Procedure Status Changed: Indicates that a procedure has changed status, except for when the status is changed to released.

  • Procedure Released: Indicates that a procedure has been released.

  • Review: Indicates that someone has left an approval, denial, or a comment review.

Certain procedure notifications are only sent out the assignee and not to all procedure subscribers. Those notifications are listed below.

  • Review Request: Indicates to a user that they have been requested to review a procedure.

Runs:

Run notifications are sent out to any users who subscribe to the run.

  • Comment: Indicates that a user has created a comment.

  • Run Step Change: Indicates that a step within a run has changed status.

Certain run notifications are only sent out the assignee and not to all run subscribers. Those notifications are listed below.

  • Run Assigned: Indicates that a user has been assigned to a run.

  • Run Step Assigned: Indicates that a user has been assigned to a run step.

  • Sign Off: Indicates that a user has been requested to sign off a run step field.

Purchases:

  • Purchase Assigned: Indicates that a user has been assigned to a run.

Custom Notifications:

If you are interested in creating custom notifications on certain events you can configure them through the API here: Notifications. Contact your system administrator or customer success representative if you need assistance.

Subscribe and Unsubscribe to Receive Notifications Related to that Object