Hello, I’m Nora, your AI guide from Technology Last Stop. This guide covers Security findings tickets and email acceptance. Review security findings, configure Microsoft or Google notifications and distinguish provider acceptance from delivered email. Current availability: Implemented; verification required.

Before you start. An authorized administrator in the correct company or the TLS owner console, with mandatory verification completed. Use an approved synthetic account for acceptance. Keep credentials, personal data and recovery codes out of recordings.

Step 1. Choose the company Security section. TLS can manage security delivery for Managed IT; company Workspace security managers can manage their permitted configuration. The paid tier and selected services must include security operations.

Step 2. Authorize an implemented security collector for the customer’s provider and verify its returned tenant and device scope. Enable collection only after reviewing the permissions and evidence.

Step 3. Configure the company notification mailbox using Microsoft application credentials or Gmail OAuth/delegation. Verify the sender mailbox identity. Microsoft shared mailboxes require the appropriate application access; a Google Group is a recipient, not automatically a Gmail sending mailbox.

Step 4. Set the company security recipient. A licensed shared mailbox, approved distribution group or Google address can receive notices when its delivery and external-sender settings permit it. Confirm membership and avoid including unnecessary sensitive incident details.

Step 5. Enable ticket and email behavior for qualifying findings. Each finding keeps its company identity and delivery claim. Repeated collection updates the same event instead of creating an unlimited number of tickets.

Step 6. Review an authorized synthetic finding, its ticket and the email delivery entry. A provider-accepted send is not proof that every distribution-list member received it. Obtain approved recipient confirmation.

Step 7. Pause on unexpected recipients or provider failure. Explicit failures can retry under the delivery policy; an uncertain send requires review to avoid duplicates. Record incident resolution and verify recovery before closing the event.

Now verify the result. Cross-company findings and recipients remain isolated. A failed token request does not count as a sent email. Uncertain provider outcomes are not automatically resent.

If you get stuck. Real provider consent, a scheduler invocation and approved inbox delivery are required. ManageEngine inventory alone is not a vulnerability feed.

Use the current written guide for exact URLs, permission names, and provider documentation. Pause before entering credentials, and keep them in protected configuration. I’m Nora, your TLS guide.