Skip to main content

Privacy & Data Collection

Job Queue Admin is designed with privacy in mind. This page explains what data is collected, how it's used, and how to maintain compliance with data protection regulations.

Privacy Acknowledgment​

Why Acknowledgment Is Required​

Before Job Queue Admin can be enabled, an administrator must acknowledge the data privacy terms. This requirement:

  • Ensures informed consent for data processing

  • Documents compliance for audit purposes

  • Meets GDPR Article 7 requirements

  • Creates accountability trail

How to Acknowledge​

  1. Open Job Queue Admin Setup page

  2. In the Privacy FastTab, click Privacy Policy to review the JEMEL Privacy Policy

  3. Toggle Data Privacy Acknowledged to Yes

The system automatically records your User ID and the acknowledgment date.

image-20260208-130820-20260208-152413.png

What Gets Recorded​

When you acknowledge privacy terms:

FieldValue
Data Privacy AcknowledgedYes
Privacy Acknowledged DateCurrent date
Privacy Acknowledged ByYour User ID

This information is stored in the Job Queue Admin Setup table and visible on the Setup page.

Revoking Acknowledgment​

To revoke privacy acknowledgment:

  1. Open Job Queue Admin Setup

  2. Set Enabled to No

  3. This effectively disables all data collection

Note: The acknowledgment record remains for audit purposes, but no new data is collected when disabled.

Data Collection Details​

What Data IS Collected​

Job Queue Admin collects the following data when processing job failures:

Job Queue Information​

DataPurposeRetention
Job Queue Entry IDIdentify the specific jobDuration of notification log
Job DescriptionDisplay in notificationsDuration of notification log
Object Type/IDIdentify job typeDuration of notification log
Error MessageInclude in notificationsDuration of notification log
Failure TimestampTrack when failure occurredDuration of notification log
Company NameMulti-company contextDuration of notification log

Notification Tracking​

DataPurposeRetention
Channel CodeTrack delivery channelDuration of notification log
Delivery StatusMonitor success/failureDuration of notification log
HTTP Response CodeTroubleshoot delivery issuesDuration of notification log
Attempt CountTrack retry attemptsDuration of notification log
Sent TimestampAudit trailDuration of notification log

Configuration Data​

DataPurposeRetention
Channel SettingsNotification routingUntil deleted by admin
Restart RulesAuto-restart configurationUntil deleted by admin
Maintenance WindowsSchedule definitionsUntil deleted by admin

What Data Is NOT Collected​

Job Queue Admin explicitly does NOT collect:

  • Job parameters: Actual data being processed by jobs

  • Business data: Customer, vendor, or transaction data

  • User credentials: Passwords or authentication tokens

  • Personal information: Beyond User ID for acknowledgment

  • Cross-company data: Each company's data stays isolated

  • External telemetry: No data sent to third-party analytics services

External Communication​

Notification Channels​

When notifications are sent, the following data leaves your Business Central environment:

Email Notifications​

  • Sent via BC's built-in email system

  • Uses your configured SMTP settings

  • Message contains: Job description, error message, timestamp, deep link

Teams Notifications​

  • Sent to configured Teams Workflow URL

  • HTTPS POST to Microsoft's webhook service

  • Message contains: Job description, error message, timestamp, deep link

Slack Notifications​

  • Sent to Slack API using Bot Token

  • HTTPS POST to Slack's servers

  • Message contains: Job description, error message, timestamp, deep link

Telemetry​

Job Queue Admin logs diagnostic events (error counts, notification delivery metrics) using BC's built-in Session.LogMessage to the extension publisher's Application Insights. This telemetry:

  • Contains only system metadata (error codes, channel types, delivery status)

  • Does NOT include: Job parameters, business data, or user information

  • Is standard BC extension telemetry — no additional external services involved

Data Retention​

Notification Log​

  • Records kept indefinitely by default

  • Administrator can delete old records manually

  • Use Notification Log page to review and clean up

Recommended Practice: Periodically delete notification log entries older than your retention policy (e.g., 90 days).

Notification Queue​

  • Queue entries deleted after successful delivery

  • Failed entries retained until manually cleared

  • Stale entries (older than Stale Notification Minutes) automatically skipped

Configuration Data​

  • Kept until explicitly deleted by administrator

  • No automatic cleanup

  • Survives company copy operations

GDPR Compliance​

Data Subject Rights​

Job Queue Admin supports GDPR data subject rights:

Right to Access​

  • All collected data visible in BC pages

  • Notification Log shows all notification records

  • Setup pages show all configuration

Right to Erasure​

  • Administrator can delete notification log entries

  • Channel configurations can be deleted

  • Restart rules and windows can be removed

Right to Rectification​

  • All configuration data is editable

  • Incorrect entries can be corrected

Right to Data Portability​

  • Standard BC export functions work with all tables

  • Excel export available on all list pages

Data Processing Agreement​

Job Queue Admin processes data on behalf of your organization:

  • Controller: Your organization

  • Processor: Job Queue Admin extension (within BC)

  • Sub-processors: Email service, Teams, Slack (when used)

Ensure your organization has appropriate agreements with Microsoft (for Teams) and Slack if using those channels.

Security Considerations​

Credential Storage​

  • Email: Uses BC's email account system (no separate credentials)

  • Teams: Workflow URL stored in BC (not a secret, but protect it)

  • Slack: Bot Token stored in BC (protect access to Channel setup)

Interactive Button Security​

Teams notifications include interactive buttons (Restart, Put On Hold) that are protected:

  • Signed URLs: Action links are cryptographically signed to prevent tampering

  • Time-limited: Links expire after 7 days for security

  • Unique per notification: Each notification has its own action links

  • No credentials exposed: Action links don't contain passwords or tokens

Access Control​

  • Use BC permission sets to control access

  • JML JQA Admin: Full access to all setup and logs

  • JML JQA User: Read-only access to logs

Recommendations​

  1. Limit Setup Access: Only administrators should access Job Queue Admin Setup

  2. Protect Webhook URLs: Treat Teams URLs as sensitive

  3. Secure Bot Tokens: Limit who can view Slack channel settings

  4. Review Logs Regularly: Monitor for unexpected notification patterns

  5. Clean Up Old Data: Delete notification logs per retention policy

Audit Trail​

What's Tracked​

Job Queue Admin maintains audit trail through:

  • Privacy Acknowledgment: Who, when

  • Notification Log: Every send attempt with timestamp and user context

  • Modification Timestamps: Standard BC SystemModifiedAt on all records

Accessing Audit Information​

  1. Privacy Acknowledgment: Job Queue Admin Setup > Privacy FastTab

  2. Notification History: Search > Notification Log

  3. System Fields: Available on all records via personalization

Summary: Job Queue Admin collects only the minimum data necessary to provide job failure notifications. No business data is collected, and all data remains within your Business Central environment unless explicitly sent through configured notification channels.