Before
IT staff likely had to extract URLs from each request, create tracking records, submit URLs for analysis, retrieve the results, and decide how to handle each request. They then had to update the allowlist or notify the requester and record the final decision in the tracking system.
How it works
- Extract each requested URL and create a tracking issue for it.
- Submit the URL for analysis, retrieve the result, and route it through the configured unblock-or-deny decision.
- Apply the approved access change or send the denial notice, then update the tracking issue with the outcome.
Workflow details
- Request intake and tracking: The workflow extracts every URL included in a user's allowlist request and creates a task for each URL so the request has a dedicated record for accountability and follow-up.
- URL analysis: Each URL is submitted for external analysis, and the resulting scan information is retrieved to support an informed allowlist decision.
- Decision routing: The workflow evaluates whether each URL should be unblocked or denied, keeping the handling consistent across all URLs in the request.
- Approved access changes: When the decision is to unblock a URL, the allowed-URL list is updated and the corresponding tracked issue is updated with the outcome.
- Denied request handling: When a URL is denied, the requester receives an email explaining the decision and is directed to IT support using the associated case number, after which the tracked issue is updated.
What changed
Every URL now follows a consistent tracked sequence from intake through analysis and decision. Approved requests update the allowlist automatically, while denied requests trigger a requester notification, with both outcomes recorded in the corresponding issue.
Work removed
Manually extracting URLs from requests, creating individual tracking issues, submitting URLs for analysis, retrieving scan results, applying the allowlist update, sending denial emails, and recording the final decision in issue comments.
Expected outcome
Conservatively, at least five recurring per-URL processing actions are automated, covering tracking, analysis submission and retrieval, decision routing, outcome handling, and final record updates.
