Simply AskingDocs

Handling Resource Requests (Admin View)

Review incoming resource requests, create or link content through multiple resolution paths, and close the feedback loop with your team.

This guide is for admins and owners who review and fulfill resource requests from team members. You will learn how to triage incoming requests, choose the best resolution path, and close the loop so requesters get notified with the result.

This is the companion guide to Requesting a Resource You Need, which shows the member side of the same workflow.

1

See Incoming Requests

New resource requests appear as a notification badge in the header. Here is how to get to the queue.

Open Requests in the header. As a reviewer you land on Needs you, then open the To review subtab. Review the queue: each request shows the requester, topic, urgency, access group, and submission date.

2

Review a Request

Open a request to see the full details before deciding how to resolve it.

Click any request to open its detail view. Read the full description: what was requested, the preferred format (document, FAQ, quick reference, video), and the urgency level. Check the similar resources section. The system automatically surfaces existing content that might already answer the request.

3

Choose Your Resolution Path

There are four ways to resolve a request. Pick the one that best fits the situation.

Option A: Quick AnswerType a direct response without creating a full document. Optionally save it as a searchable FAQ entry. Best for short clarifications.
Option B: Create with AILet AI draft a document from the request and your existing knowledge. Choose a resource type, add instructions, review, then publish.
Option C: Create ManuallyUpload or create a document yourself, then link it to the request. Best when you already have the content ready.
Option D: Link ExistingIf the content already exists, search and link it. Fastest option. The requester gets a notification with a link to the document.
4

Confirm Fulfillment

Completing any of the four fulfillment options closes the request and notifies the requester. There is no separate Mark Complete step after you fulfill.

Add optional notes when the dialog offers them, so the requester understands what was provided. They can open the linked resource and leave a rating afterward.

You have resolved the request and your team member has been notified. As your knowledge base grows, explore how all of this content connects together in the Knowledge Graph.

Was this helpful?