An internal software request process works best when it starts with the business problem, not a purchase link. Airtable can hold each request, its reviewer and the next decision, while miniExtensions gives employees a focused way to submit the need and follow its progress. Keep business approval separate from security review, purchasing and account provisioning.
Consider a fictional design team that wants a new feedback tool. Riley needs to collect comments on campaign mockups from six colleagues. A manager may agree that the problem deserves attention without approving a particular vendor, accepting a contract or granting anyone access. This guide models that distinction.
Define what a request does and does not authorize
The intake form should say what happens after submission: an assigned reviewer will consider the need and identify the next step. It should not imply that submitting a request starts a subscription, installs software or creates an account.
Use business review to answer whether the need is real, who benefits and whether an existing tool could meet it. Use separate organizational processes for vendor security, procurement and provisioning. The stages below are a proposed workflow that your team maintains in Airtable, not an automatic miniExtensions approval service.
Model requests, people and the existing tool catalog
Create these tables with fictional example records before collecting real requests:
- Employees: Employee name as primary single line text, Work email as email and Team as a single select.
- Reviewers: Reviewer name as primary text and Work email as email. Keep this separate if reviewers need a different portal from requesters.
- Tools: Tool name as primary text, Purpose as long text, Internal contact as single line text and Catalog status as a single select with Available, Under review and Retired. These are your internal labels, not vendor certifications.
- Software Requests: Request title as primary text, Requester as one link to Employees, Reviewer as one link to Reviewers, Problem to solve as long text, Requested tool as single line text, Vendor website as URL, Intended users as an integer number, Desired date as date, Existing tools considered as links to Tools and Why those tools do not fit as long text.
- Review fields on Software Requests: Business decision as a single select with Pending, More information, Supported and Not supported; Review explanation as long text; Next step as long text; Follow-up owner as single line text; and Last reviewed as date.
Add Data categories as a multiple select using broad categories such as Public content and Internal project information. Ask for categories, not examples of confidential material. Do not invite passwords, API keys, private customer documents or payment details into a general request form.
Collect enough context for a useful first decision
Riley’s request title is “Collect campaign feedback in one place.” The problem describes comments arriving in separate messages, the intended users field is six, and the desired date is the next project kickoff. Riley names a candidate tool but explains the required outcome independently of that product.
Ask what was tried already and who would own the workflow. This gives the reviewer a basis for suggesting an existing solution rather than treating every request as a new license purchase. A catalog link records which alternatives were considered; it does not prove the proposed software meets company requirements.
A standalone Form can serve a short intake process. A Portal is more useful when employees need to revisit multiple requests. The Form and Portal comparison explains the different record workflows.
Separate employee input from reviewer decisions
For a requester Portal, use Software Requests as the Data Table and Requester as its User Field. Establish the linked Employees records before configuring login and creation. Follow the Users Table setup, and verify that newly created requests are linked to the correct person rather than exposing an editable requester selector.
Use a separate reviewer Portal linked through Reviewer. Keep decision fields outside the employee’s editable form. The existing two-role approval Portal tutorial provides a detailed setup pattern for separate requester and reviewer experiences. Apply it to software requests instead of rebuilding every configuration step here.
For each relevant table view, check Portal Tables, Views, Filter and Sort, then Choose Records to Display. Use Personal records only (linked to the logged in user), as described in the personal-record documentation. This relationship must be configured for each data table; a status filter alone is not a substitute.
Make the handoff explicit
The reviewer first asks whether an existing collaboration tool could solve Riley’s feedback problem. If not, Business decision may become Supported, with an explanation of the intended benefit. Next step could read “Operations to assess the proposed vendor and confirm the purchasing route.” That is a handoff, not a statement that the tool is cleared for use.
If you track downstream steps here, add separate manually maintained fields for Security review, Procurement review and Provisioning. Use values such as Not started, In review and Completed, with the responsible person and a reference to the actual decision record. Do not infer completion of one stage from another. A supported business request can still be declined during a later review.
When more information is needed, tell the requester the precise question through the organization’s chosen communication process. Updating a field does not itself send an email. Preserve the prior explanation when a request is revised, and record what changed; this simple model is not an immutable audit trail.
Check the workflow before rollout
Use two fictional employees and one reviewer. Confirm that each employee sees only intended requests, that decision fields cannot be changed through any employee form and that catalog links do not expose unrelated information. Test a request needing clarification, an existing-tool alternative and a supported request still awaiting procurement.
Reload each saved record and check the actual relationships and displayed status. These are recommended acceptance checks, not observed tests. The result should be a clear review queue and visible next steps. It should never suggest that a submitted form has purchased software, granted access or completed a security assessment.


