Guest-access hygiene — with sponsor warnings and an audit log

Once a week the scenario finds abandoned guest access in microsoftEntra, queues it in Quick Base and warns the sponsor in botHelp; after three days the overdue ones are closed with an audit record.

  • Abandoned access is found automatically, every week
  • A three-day window and a 'keep' flag guard against over-deletion
  • The sponsor is warned in advance in botHelp
  • Every access closure is recorded in the audit log
Microsoft Entra ID
Set this upScriptera

How it works

To connect Quick Base and botHelp, you don't need a developer: a ready-made scenario links them in minutes.

  1. Starts when: Daily Cron Trigger
  2. Then: Config (Executioner)
  3. Then: Get Overdue Pending Deletions
  4. Check: Any Due For Deletion?
  5. If yes: Split Pending Items
  6. Then: Check Retention Exception
  7. Check: Retention Exception?
  8. If yes: Delete Stale Guest Account
  9. Check: Delete Succeeded?
  10. If yes: Log Deletion to Audit List
  11. Then: Mark Pending as Deleted
  12. If no: Delete Error Alert
  13. Then: Mark Pending as Error
  14. If no: Mark Pending as Retained
  15. Then: Log Retention to Teams
  16. Then: Queue Pending Deletion
  17. Check: Valid Sponsor Email?
  18. If yes: Notify Sponsor via Teams Channel
  19. If no: Alert IT Security - No Sponsor
  20. Check: Not Yet Queued?
  21. Then: Already Queued?
  22. Then: Filter Stale Per Page
  23. Then: Get Guest Users
  24. Then: Config
  25. Starts when: Weekly Cron Trigger
  26. Starts when: When Weekly Triggered at 8 AM
  27. Then: Set Configuration Parameters
  28. Then: Fetch Guest Users from Graph
  29. Then: Filter Stale Accounts
  30. Then: Check if Already Queued
  31. Check: Check Not Yet Queued
  32. If yes: Queue for Pending Deletion
  33. Check: Check for Valid Sponsor Email
  34. If yes: Notify Sponsor via Teams
  35. If no: Alert IT of Missing Sponsor
  36. Starts when: When Daily Triggered at 9 AM
  37. Then: Set Execution Parameters
  38. Then: Fetch Overdue Pending Deletions
  39. Check: Check Due for Deletion
  40. If yes: Distribute Pending Items
  41. Then: Verify Retention Exception
  42. Check: Is Retention Exception Present?
  43. If yes: Remove Stale Guest Account
  44. Check: Verify Deletion Success
  45. If yes: Record Deletion in Audit Log
  46. Then: Update Status to Deleted
  47. If no: Notify Delete Error via Teams
  48. Then: Update Status to Error
  49. If no: Update Status to Retained
  50. Then: Notify Retention via Teams

You can launch this Quick Base + botHelp integration in Scriptera: describe the task in plain words — the scenario is built, launched and monitored for you.

Similar scenarios