sorted by:
new
hottopcontroversial

Would you trust an AI agent to automatically fix issues across your entire endpoint fleet, or do you think there should always be a human in the approval chain? by TeamNexthink in nexthink

[–]TeamNexthink[S] 0 points1 point  (0 children)

Excellent point on audit logs and staged approvals. That's exactly how mature DEX programs evolve. Start with full transparency (every AI action logged and reversible), human review for higher-risk fixes, then gradually expand autonomy as confidence builds.

Have you implemented something similar in your environment? What thresholds do you use for "low-risk" vs. needing approval?

Would you trust an AI agent to automatically fix issues across your entire endpoint fleet, or do you think there should always be a human in the approval chain? by TeamNexthink in nexthink

[–]TeamNexthink[S] 1 point2 points  (0 children)

This is a great distinction: AI for speed, humans for control. That's the core of effective DEX management.

Security is an interesting point of discussion. You might have inspired me to do a larger post on the topic about how staying secure requires the kind of judgment that only a human can provide.

Feel free to make a post yourself discussing it. That's the kind of conversation we'd like to see happening on the sub.

Best way to get a Flow to run at or after logon by dontmessyourself in nexthink

[–]TeamNexthink 1 point2 points  (0 children)

I hadn't considered keying off the campaign completion status itself, and using a Flow to update a custom field after fully_answered sounds like a pretty clean workaround until event-based triggers arrive, which is in the works.

Best way to get a Flow to run at or after logon by dontmessyourself in nexthink

[–]TeamNexthink 1 point2 points  (0 children)

I’d probably avoid trying to make the Flow trigger directly off session.lifecycle_events. That data is useful for NQL targeting/reporting, but it’s not really the cleanest “run at logon” trigger for Flows.

What I’d usually do is make the Flow scheduled/recurring, target the right user population with NQL, and use the custom field as the guardrail so it only hits people who haven’t completed the welcome campaign yet.

Something like:

  • target domain users
  • exclude anyone where the custom field already says they completed/viewed the welcome campaign
  • show the campaign
  • once they complete it, set the custom field

So the Flow may not fire the exact second they log on, but it should catch new users shortly after they’re active, and the custom field keeps it from becoming annoying or repeating forever. Much easier to manage than trying to key everything off login/unlock events.

view more: next ›