Requests
Requests allow you to ask a colleague to take action on a project, directly from within OrderEazi. Instead of sending a separate email or message, you can create a request tied to the project itself, so nothing gets lost.
π§Ύ What is a Request?
A Request is a task or action that one user sends to another, linked to a specific project.
Each request consists of:
A Title describing what you need
An optional Description with more detail
An Assigned User who is responsible for actioning the request
A Status tracking whether the request has been addressed
Requests live on the project they relate to, making them easy to find and providing full context to the person receiving them.
βοΈ How Requests Work
Creating a Request
You can create a request from two places:
The Project Actions menu on any project (via the "Make a Request" option)
The Requests tab on a project that already has existing requests
When creating a request, you select the user you want to assign it to, give it a title, and optionally add a description. The assigned user receives an email notification with a link to the project.
Request Lifecycle
Every request follows a simple lifecycle:
Pending
The request has been created and is awaiting action
Completed
The assigned user has marked the request as done
Declined
The assigned user has declined the request
Cancelled
The person who created the request has withdrawn it
Only the assigned user can complete or decline a request
Only the requester (the person who created it) can cancel a request
When completing or declining, the assigned user can add a response comment explaining their action
Notifications
When a request is created, the assigned user receives an email notification. A bell icon in the top navigation bar shows a badge with the number of pending requests assigned to you.
Clicking the bell icon opens a dropdown showing your most recent pending requests. You can action them directly from the dropdown or click through to view the full details.
π Where to Find Requests
There are three places to view requests:
Top bar bell icon - Shows a quick-access dropdown of your pending requests, visible from any page
Requests page - A dedicated page (accessible via the bell icon's "View All Requests" link) with two tabs: "Assigned to Me" and "Created by Me"
Project Requests tab - On any project that has requests, a "Requests" tab appears showing all requests for that project
π Project History
All request activity is recorded in the project's history. This includes when a request is created, completed, declined, or cancelled, along with who performed the action.
π‘ Why Use Requests?
Requests are particularly useful for:
Asking a warehouse team member to check stock or prepare an order
Requesting a manager's input or approval on a project
Flagging something that needs attention from a specific colleague
Keeping all project-related communication in one place
Ensuring follow-up actions don't fall through the cracks
Because requests are tied to the project, the full context is always available to the person actioning them.
β
Summary
Requests provide a simple way to:
Ask a colleague to take action on a project
Track whether the action has been completed, declined, or cancelled
Receive email notifications and in-app alerts for pending requests
Keep a full audit trail in the project's history
This keeps your team aligned without relying on external communication tools.
Last updated