Easyflow
Get started

IT template

System access request form and approval workflow template

Ask for access to a system, get the right approvals and keep a record of who can do what.

5 steps 16 fields

Free for 14 days. No credit card. You can change every step and field.

Access requests tend to arrive as “can you give Sam access to the CRM?” in a chat. IT grants it, nobody writes down why or at what level, and a year later nobody can explain why a former intern still has admin rights in the finance system.

This template asks for the details up front: whether the access is for the requester or someone else, the system (ERP, CRM, finance, HR, file server, BI or another one), the access level (read only, read and write, or administrator), an optional end date and a justification. The manager confirms the person needs it for their job. Administrator access adds a security approval, where the reviewer sets when the access should be reviewed again, from 30 days to a year, and notes risks and restrictions. IT then creates the access and records the username and date, never the password, and the requester confirms that it works. The approvals and the grant each have a one-business-day deadline.

It fits small IT teams at companies that need a record of who has access to what, whether for an audit, a customer’s security questionnaire or their own peace of mind.

How it runs, step by step

The process reads from top to bottom. Each step goes to its owner with a deadline, and everything that happens is recorded in the request's timeline.

  1. Request

    Whoever starts the request

    Tell us which access you need and why.

    7 fields in the request form
    • Who is the access for? *Myself, Someone else Choice
    • Name and email of the person * Text · when needed
    • System *ERP, CRM, Finance system, HR system, File server, BI and reports… Choice
    • Which system? * Text · when needed
    • Access level *Read only, Read and write, Administrator Choice
    • Needed untilLeave blank for permanent access Date
    • Justification * Long text
  2. Manager approval

    A person or team you choose

    The manager confirms the person needs this access for their job.

    Approval: Approvers you choose Due in 1 day (business time)
    2 fields
    • Need * Checkbox
    • Notes Long text
  3. Security approval

    A person or team you choose

    Administrator access needs a second approval.

    Approval: Approvers you choose Due in 1 day (business time) Runs only when needed
    2 fields
    • Review this access in *30 days, 90 days, 6 months, 1 year Choice
    • Risks and restrictions Long text
  4. Grant access

    A person or team you choose

    IT creates the access and records it.

    Due in 1 day (business time)
    3 fields
    • Username * Text
    • Granted on * Date
    • NotesNever write passwords here Long text
  5. Confirm access

    The requester

    The requester confirms the access works.

    2 fields
    • Access * Checkbox
    • Notes Long text

Make it yours

Remove temporary access on time

Add a wait step until the Needed until date, with a condition so it only runs when that date is filled, followed by a step where IT removes the access.

Re-check admin rights

Add a 90-day wait step and a review step where the manager confirms the access is still needed, both with a condition so they only run for administrator access.

Route it without thinking

Make the requester’s manager the owner of Manager approval, and give Grant access to the IT group with round robin assignment.

List your real systems

Edit the System options to match the tools you actually use, so “Other” is the exception rather than the rule.

Frequently asked questions

What is an access request form?

It is the form employees use to ask for access to a system, application or shared resource. It records who needs access, to what, at which level, until when and why, and it collects the approvals before IT grants anything.

What is the principle of least privilege?

NIST defines least privilege as restricting users’ access privileges to the minimum necessary to accomplish their assigned tasks. In practice, grant read-only access unless someone needs more, set an end date for temporary access and require a second approval for administrator rights.

How often should user access be reviewed?

There is no single rule, so base it on risk. Administrator and finance access deserve frequent reviews, while read-only access to low-risk tools can be checked less often. Whatever the frequency, record each review so you can show it was done.

Who should approve access requests?

The person’s manager should confirm the business need, and the system owner or security team should approve high-risk access such as administrator rights. IT should grant access only once those approvals are on record.

More IT templates

Start from this template

Copy it into your workspace, invite the people involved by email, and send the first request today. One plan with every feature, from $49 a month for 5 users.

Use this template