Prepare a clear access request
Fictional example: at Northstar Works, a project coordinator is preparing a request for the fictional Atlas planning system. Use this page to define the work need, narrow the requested role, and identify the approver before submitting through your organization's authorized service-desk route.
Prepare these three details
Be specific enough for the approver and system owner to understand what access is needed and why.
Choose the system and role
Name the system and the role that supports your work task. If role names are unclear, ask the system owner or IT/Security specialist before requesting a broad role.
- State the system by its recognized name.
- Name the specific role or permission set.
Explain the work need
Connect access to a defined work task, and request only the capabilities needed for that task.
- Describe what you need to view or do.
- Say when editing or other capabilities are not needed.
Name the approver and duration
Identify the accountable approver for the business need and give the requested end date or duration. Follow the organization's confirmed process if either is unclear.
- Name the approver by role or established team.
- Include an end date or stated duration.
From preparation to handoff
Complete the preparation first; submitting is a separate step.
The requester prepares the details; the authorized service desk is the handoff destination. Approval and fulfillment take place through the organization's established process.
-
1
Identify the system and task
Write down the system name and the work task that requires access.
-
2
Select the narrowest useful role
Choose the least broad role that supports the task. If you cannot tell which role fits, ask the system owner or IT/Security specialist.
-
3
State the business need and duration
Explain what you need to view or do, what you do not need to do, and how long the access is requested.
-
4
Identify the accountable approver
Use the confirmed approver role or route for the system and business need. Do not assume that the requester and approver are the same person.
-
5
Gather required reference materials
Include only materials the confirmed request process asks for, such as a project or work reference. Keep sensitive details in the appropriate system.
-
6
Submit through the authorized service desk
After preparation, use your organization's established service-desk destination. This page does not submit or track a request.
Worked example: request only what the task needs
Fictional example for preparation—not an approval, policy, or request status.
System and role: Atlas planning — Viewer role.
Business need: “I need to review the approved project schedule for the Northstar launch coordination work; no editing is needed.”
Duration: Through 30 September for this assignment.
Approver: The project lead.
The Viewer role is a narrower example than Editor because the stated task is to review a schedule, not change it. The approver role and end date are illustrative details, not a statement of local approval rules. If a real task requires editing, describe that task and have the appropriate approver or system owner clarify the role before requesting access.