trio.so
Templates

Application Access Request Form Template (Word, Excel + PDF)

Free application access request form in Word and PDF, with a change and removal form, a filled-in example and an Excel log that flags expired access.

Mountain landscape representing leadership perspective and vision
Written by
Atena Ladchartabi

Content writer, trio.so

Published on
Modified on

Someone needs access to the finance system. They send a chat message, a manager replies "fine by me", and IT adds them to the admin group because that was quickest. Six months later nobody remembers who approved it, the person has moved teams, and the access is still there.

An application access request form fixes that with one page: who needs access, to which app, at what level, for how long and why, and who approved it before IT granted anything. This free template gives you that form in Word and PDF, a second form for changing or removing access, a filled-in example, and an Excel log that flags approvals that are stuck, access granted without approval and temporary access that should have ended.

In short

  • Use one form per app: requester details, the app and role, data sensitivity, standard or privileged, ongoing or temporary, and a business reason.
  • Get two approvals for every request (manager and app owner) and a third from security for privileged access or restricted data.
  • IT grants exactly the approved role, records what it did and sets a review date. Temporary access gets an end date.
  • Use a change or removal form when people move or leave, and keep every form for access reviews and audits.

What an Application Access Request Form Is For

An application access request form is the written record of one decision: this person may use this app, in this role, for this reason, until this date. It turns a casual "can you give me access?" into something an app owner can judge and an auditor can check later.

It does three jobs:

  • It makes people ask for the right thing. A form with a role field and a justification box gets better requests than an email that says "same access as Sam". Copying a colleague's access is an easy way to end up with far more than the job needs.
  • It puts the decision with the people who can make it. The manager knows whether the job needs it; the app owner knows what each role can do. IT carries out the decision instead of making it.
  • It leaves evidence. When someone asks who approved a person's access to payroll, the answer is a dated, signed form, not a search through old chat threads.

Access Request vs Account Creation Request

This form is for people who already have a work account and need access to an app, a system, a database or a higher role. A new starter who doesn't have an account yet goes through account creation first: use our user account creation request form template for that, then this form for each app beyond the standard set. Many teams bundle the standard apps for a role (email, chat, the intranet) into onboarding and use access requests only for everything else. Our IT onboarding checklist covers the bundle.

What to Include: The Form Section by Section

The template has eight sections. Each one is filled in by one person, so nobody signs for something they didn't check.

SectionFieldsFilled in by
1. Requester detailsName, ID, job title, department, manager, worker type, contract end date for non-employeesRequester
2. Access requestedApp or system, module or environment, role, data sensitivity, standard or privileged, ongoing or temporary, start and end dates, devices, business justificationRequester
3. Manager approvalDecision, conditions, signature, dateLine manager
4. Owner approvalDecision, role approved if different, conditions, signature, dateApp or data owner
5. Security approvalMFA, separate admin account, end or review date, decision (privileged access and restricted data only)Security lead
6. IT provisioningWho granted it, when, account, group or role assigned, ticket reference, requester told, removal scheduledIT
7. Review and removalNext review date, review outcome, date removed, removed byApp owner and IT
8. AcknowledgmentBusiness use only, no shared passwords, data handling, report when no longer neededRequester

A few fields do most of the work:

  • Role or permission level. Read only, standard user, power user or administrator, plus the role's real name in the app if the requester knows it. The App Catalog tab in the workbook lists each app's roles from smallest to largest, so requesters can pick the right one.
  • Data sensitivity. Public, internal, confidential or restricted. It tells the owner how careful to be and decides whether security needs to approve.
  • Standard or privileged. Privileged means admin rights, the right to change security settings, or direct access to production data. It always needs the security section.
  • Duration and end date. Ongoing access is reviewed on a schedule. Temporary access, for a project, cover or an audit, has an end date on the form, and IT removes it that day.
  • Business justification. What the person will do with the access and why their current access isn't enough. "Need it for my job" isn't a justification; "Enter supplier invoices in the AP module from 3 November" is.

Who Approves Access Requests

Most access requests need two approvals, and privileged ones need a third. Each approver answers a different question:

ApproverWhat they checkWhen
Line managerDoes this person need this access to do their job? Is the duration right?Every request
App or data ownerIs this the smallest role that does the job? Is the data's sensitivity understood? Any conflict with other duties?Every request
Security or IT security leadIs this privileged or restricted access? Is MFA on, is there a separate admin account, is there an end date?Privileged access and restricted data
IT (provisioner)Are all approvals present before anything is granted? Was exactly the approved role given?Every request, before provisioning

Two rules keep approvals honest. Nobody approves their own request, and the person who grants access in the system isn't the person who approved it. That split, between asking, approving and granting, is a small piece of segregation of duties. It matters most where one person could both enter and release payments, change and approve their own code, or create and use an admin account. Our guide to segregation of duties goes further, and the role-based access control guide shows how to design roles so owners have sensible options to approve.

Least privilege is the test every approver applies: the smallest role that lets the person do the job, for as long as they need it. NIST SP 800-53 calls this AC-6 Least Privilege, and the same idea runs through ISO/IEC 27001 and SOC 2 (more on those below).

The Access Request Process, Step by Step

The access request process: request, three approvals, provisioning, then review and removal
The access request process: request, three approvals, provisioning, then review and removal
StepWhat happensOutput
1. RequestThe requester (or their manager) fills in the form: who, which app, which role, why, and for how long.A complete request with a business reason
2. Manager approvesThe manager confirms the person needs this access for their job, and nothing more.Business need confirmed
3. Owner approvesThe app or data owner checks the role matches the job and the data's sensitivity.Role and data checked
4. Security approvesFor privileged access or restricted data only: security checks MFA, a separate admin account and an end date.Extra check for high-risk access
5. IT provisionsIT creates the account or adds the role, records what was done, and tells the requester.Access granted and recorded
6. Review and removeOwners review access on a schedule; temporary access ends on its date; leavers lose access on their last day.Access that matches the job today

Set a target for each step and write it into your access control policy. A common pattern is approvals within two or three working days and provisioning within a day of the last approval, but pick numbers your team can keep. The workbook flags any request still waiting for an approval after the number of days you set.

Provisioning is where shortcuts happen. IT should grant exactly the role on the form, not "admin, to save time", and never before every required approval is recorded. The workbook's Control check column marks any row that was provisioned without its approvals. It's the first thing an auditor will look for in a sample.

Access Provisioning Procedure for IT

  • Check the form is complete and every required approval is there, signed and dated before today.
  • Grant the approved role, ideally by adding the person to an existing group rather than giving rights to the individual account.
  • For privileged access, use a separate admin account with MFA, not the person's everyday account.
  • Record the account, the group or role, the date and the ticket reference in section 6, and log the request in the tracker.
  • Tell the requester, and for temporary access schedule the removal on the end date.
  • File the form with the ticket so it can be found at the next access review.

Standard, Privileged and Temporary Access

What changes when access is privileged or temporary: extra approval, a separate admin account, MFA and an end date
What changes when access is privileged or temporary: extra approval, a separate admin account, MFA and an end date

Most requests are standard: a sales rep needs the CRM, a finance analyst needs read access to reports. They follow the two-approval path.

Privileged access is different because a mistake or a stolen password does far more damage. That covers admin roles, rights to change security settings, direct production database access and cloud console administrator roles. ISO/IEC 27001:2022 gives it its own control, 8.2 Privileged access rights. For these requests, the form asks security to confirm three things before IT acts:

  • multi-factor authentication is required for the access (see our guide to multi-factor authentication);
  • the work uses a separate admin account, not the person's everyday login;
  • there is an end date, or a short review date if the role is ongoing.

Temporary access is any access with a known end: a project, holiday cover, a contractor's engagement, an incident, or an external auditor who needs read access for a month. Put the end date on the form, and treat removal on that date as part of the request, not a separate task someone might forget. The workbook flags temporary access that ends within 14 days and any that has already expired without a removal date. If your team grants short-lived admin rights often, our guide to just-in-time access explains how to make admin rights expire on their own.

Access Change and Removal Requests

Granting access gets attention because someone is waiting for it. Removing access gets forgotten because nobody is. The template's second form covers the moments when access should shrink:

  • Role change or transfer. Remove what the old role needed before adding what the new one needs. Otherwise people collect access with every move.
  • Leaving. List every app the person used and remove all of it on the last day. Our IT offboarding checklist covers accounts, devices and data.
  • Project ended or no longer needed. The person or their manager asks for removal; no approval chain is needed to take access away.
  • Temporary access ended. The end date on the original form triggers the removal.
  • Security concern. Suspected misuse or a compromised account. Remove first and investigate after.

The change form lists each app with its current access and the change (remove, reduce or change role to), then has IT record who did it and when. For leavers it also asks whether company devices were returned or wiped and whether shared passwords the person knew were rotated. Removals need the manager's sign-off only; a role change that adds access goes back through the owner, like a new request.

A Filled-In Access Request Example

Here is the example from the download, for a made-up company. Every name, ticket and date is fictional.

FieldExample entry
RequesterJordan Sample, accounts payable specialist, Finance (new to the team)
App and roleERP, accounts payable module, production; AP Clerk (enter and edit invoices; cannot release payments)
Sensitivity and typeConfidential; standard; ongoing (reviewed on schedule)
JustificationJoined the AP team on 2 Nov 2026 to enter and match supplier invoices. Releasing payments stays with the AP lead.
ApprovalsManager approved 2 Nov; finance systems owner approved 3 Nov with a condition (clerk role only, no payment release); security not needed
ProvisioningAdded to group ERP-AP-Clerk on 3 Nov by the IT service desk, ticket REQ-1042, requester told
ReviewNext review 1 May 2027

Why it works: it names one app and one role, the justification describes the work, the owner narrowed the role so the same person can't enter and pay an invoice, both approvals are dated before the provisioning date, and a review date is set. The workbook's Example tab shows ten more requests at the same fictional company, including a privileged request that was provisioned before security approved it and temporary admin access that expired two days ago without being removed.

System and Database Access Requests

The same form works for systems and databases, with more care in section 2:

  • Name the environment. Access to a test database and access to production are different requests. Production data access is usually privileged.
  • Say read or write. Read-only reporting access and the right to change records carry very different risks. For databases, say which schemas or tables if you can.
  • Prefer a role over a personal login. Ask for membership of an existing reporting or analyst role instead of rights granted to one person.
  • Service accounts. When an app or integration needs access, the requester is the system owner. The form records who owns the account, what it can reach and when its password or key is rotated.
  • Remote and admin tools. Remote desktop, VPN and server admin access go through the security section. Our remote desktop access policy template sets the rules for remote sessions, and the conditional access policy template covers sign-in conditions.

Keeping a Record for Access Reviews and Audits

A completed form is evidence. Keep it with the ticket, log it in the tracker, and keep it for as long as the access exists and then for the period your records policy or your auditors set.

Auditors testing access usually pick a sample of people who gained access in the period and ask to see who requested it, who approved it and when it was granted. Then they pick a sample of leavers and check their access was removed on time. The tracker gives you the population for both samples, and the forms give you the evidence for each one.

The same records feed your access reviews: for each app, the owner looks at who has access today, compares it with the log and the job, and removes what isn't needed. Our user access review template runs that review step by step.

Frameworks that ask for this kind of record, in general terms:

FrameworkWhere access requests fit
NIST SP 800-53 Rev. 5AC-2 Account Management (how accounts are requested, approved, created, changed and removed) and AC-6 Least Privilege (people get only the access their duties need).
ISO/IEC 27001:2022 Annex A5.15 Access control, 5.16 Identity management, 5.18 Access rights (provide, review, change and remove access) and 8.2 Privileged access rights.
SOC 2 Trust Services CriteriaCC6.1 to CC6.3, the logical access criteria: access is registered and authorized before it is granted, based on role and least privilege, and removed when it is no longer needed.

These are pointers, not a mapping. Read the publisher's text at NIST, ISO and the AICPA before you rely on them, and see our IT audit checklist for how access controls are tested alongside everything else.

When an Access Request Form Outgrows Email and Word

A Word form and a spreadsheet log work well for a few hundred people and a few dozen apps. Signs you have outgrown them:

  • requests get lost in inboxes, and people ask "did you get my form?";
  • approvers sign forms without the context to judge them;
  • the log falls behind the real state of access;
  • access reviews take weeks because nobody can say who has what;
  • auditors find access with no matching form.

The usual next step is to move the same form into your IT ticketing system or service catalog, so each request has a ticket, approvals are recorded in the ticket and nothing is granted without them. Our IT service request form template covers that kind of request. Larger organizations then add an identity and access management (IAM) or identity governance (IGA) tool, which connects to the apps, offers approved roles in a catalog, routes approvals, grants and removes access automatically and runs access reviews. Whatever the tool, the fields on this form are the ones it will ask for, so the template is a good way to agree them first.

What's in the Download

The access request form PDF: cover, the request form and the filled-in example
The access request form PDF: cover, the request form and the filled-in example
  • Word form (Application-Access-Request-Form-trio.so.docx): the application access request form with fillable fields, tick boxes and date pickers, the access change and removal form, the filled-in example and a one-page guide.
  • PDF (Application-Access-Request-Form-trio.so.pdf): the same forms and guide, ready to print and sign.
  • Excel tracker (Application-Access-Request-Form-trio.so.xlsx): a request log with approval, control and temporary-access flags, an app catalog with owners and roles, a filled-in example for a made-up company, a dashboard and sources. Formulas only, no macros.
The workbook's Example tab: a made-up company's access requests with their approval, control and temporary access flags
The workbook's Example tab: a made-up company's access requests with their approval, control and temporary access flags

Where trio.so Fits

trio.so does not run an access request approval workflow and is not an IAM or identity governance tool. The requests, approvals and access reviews on this form stay with your managers, app owners and IT team, or your ticketing system.

It helps once a request is approved: setting up the person and their apps on company devices, and showing later who can manage what. trio.so is device management for Windows, macOS, Linux, iOS/iPadOS and Android, from one console. For the provisioning and review steps of the process, it gives you:

  • User and group sync from Microsoft Entra ID and Google Workspace, and SCIM 2.0 provisioning from Entra ID, Okta and OneLogin, so the people in trio.so follow your directory.
  • Single sign-on and multi-factor authentication at user sign-in (Zero Trust plan).
  • An app catalog for deploying approved apps to managed devices, and removing them again when access ends.
  • A device inventory that shows each device's owner and the apps installed on Windows, macOS, iOS and Android devices, so you can check what is on company devices.
  • Built-in and custom console roles, so IT staff get only the device management rights their job needs.
  • A CSV export of console members with their roles, status and last-active dates, for reviewing who can manage your devices.

See how app management and the device inventory work. Plans start at $5 per device.

Start free trial Book a demo

14-day free trial. No credit card required.

Related Templates

Sources. Last reviewed November 2026. Framework references are general pointers to NIST SP 800-53 Rev. 5 controls, ISO/IEC 27001:2022 Annex A controls and the SOC 2 Trust Services Criteria; the wording of every field is ours. trio.so is not affiliated with or endorsed by NIST, ISO or the AICPA.

Ready-to-use Templates

Must-have Template Toolkit for IT Admins

Explore All
Template Toolkit

Set up approved access on every device

trio.so syncs users from Entra ID and Google Workspace, deploys approved apps from your app catalog to managed devices and shows the apps installed on each one.

Start free trial

Manage Every Device From One Console

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

14-day free trial. No credit card required.

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

Smiling womanAbstract geometric patternAbstract geometric patternSmiling womanSmiling woman

Frequently Asked Questions (FAQ)

Have questions? We've got answers. This section covers some of the most commonly asked questions related to this topic.

The requester's details, the app or system, the role or permission level, the data's sensitivity, whether the access is standard or privileged, whether it is ongoing or temporary with an end date, and a business justification. Then approvals from the manager and the app owner (and security for privileged access), IT's provisioning record and a review date.

The requester's manager confirms the job needs the access, and the app or data owner confirms the role is the smallest one that does the job. Privileged access and restricted data also need security's approval. Nobody should approve their own request, and the person who grants the access shouldn't be the one who approved it.

Standard access lets someone use an app for everyday work. Privileged access means admin rights, the right to change security settings, or direct access to production data, where a mistake or a stolen password does much more damage. Privileged requests get an extra security approval, a separate admin account, MFA and an end or short review date.

Put an end date on the request form, approve it like any other request, and schedule the removal when IT grants the access. Track temporary access in a log that flags anything past its end date. If the person still needs it, they submit a new request rather than the access quietly continuing.

An account creation request sets up a new person's work account, usually during onboarding. An access request is for someone who already has an account and needs a specific app, system, database or a higher role. Many teams bundle a role's standard apps into onboarding and use access requests for everything beyond that.

Keep each form for as long as the access exists, then for the retention period your records policy or auditors set. Auditors often sample people who gained access during the period they review, so a form that was thrown away after provisioning leaves a gap in the evidence.

When requests get lost in email, the log no longer matches who really has access, or access reviews take weeks. The usual first step is putting the same form into your ticketing system or service catalog. Larger organizations then add an IAM or identity governance tool that routes approvals and grants and removes access.

Related

From the blog

The related industry news, interviews, technologies, and resources.