iAttendance · Guide
Requests & approvals
Requester → approver → executor, with reusable request templates and support tickets.
Request Manager ✅ Before you start
- The kinds of request your company handles: purchases, repairs, proposals, internal help…
- Who approves and who executes each kind.
🧭 Step by step
🏷️ Declare your properties
Request Manager › Request & Ticket Properties
Open "Request & Ticket Properties" to create the fields shared by requests and tickets — priority, handling team and so on.
Declaring these first keeps every template consistent and makes reporting meaningful.
🗂️ Create a template group
Request Manager › Approval Request Template
Group related templates together so people can find the right one when raising a request.
📝 Build a request template
Request Manager › Approval Request Template
Open "Approval Request Template", pick the group in "Select Template Group", then fill "Template Name" and "Description".
"Select Property" is optional — use it to attach the properties you declared earlier. "How Many Days This Request Will Expire" defaults to 30 days.
Three more fields control visibility: "Select Template Status", "Who requester can see ?" and "Who Approver/Executor Can See ?".
The model is: the requester submits → the approver decides → the executor carries it out.
The page is organised into three panels. "Request Settings" holds everything above; "Approval Flow" and "Execution Flow" below it hold one card per step, and the execution panel is marked in purple so the two chains never get confused.
Set "Number Approver" and "Number Executor" and the cards are rebuilt to match. Each is numbered and badged — ✅ for an approval step, ⚙️ for an execution step. Execution steps only start once every approval step has passed.
- Each field now carries a short italic note explaining what it decides. The ones worth reading: "Minimum How Many Approvers To Approve To Pass This Station" is a quorum, so 1 means any single person on the list is enough, and "Order" is set automatically and shown for reference only.
- Step cards can be dragged to reorder them on screen and resized from the grip at the bottom-right. It is a viewing convenience — the real order comes from the step number, and the arrangement is not saved.
- Drag from the card header. Clicking into a field never starts a drag.
🎫 Build a ticket template
Request Manager › Ticket Template
Tickets cover requests for help, internal or from customers, and are kept separate from things that need approval.
📥 Work the queues
Request Manager › Approval Requests To Process · Tickets To Support
"Approval Requests To Process" is your approval queue. "Tickets To Support" is the help queue.
Both are handled in place, without switching to another tool.
👁️ Track and follow
Request Manager › All Your Requests & Tickets · You Are Following
"All Your Requests & Tickets" shows everything you raised or took part in.
"You Are Following" collects the items you want to keep an eye on without owning.
🙋 How employees raise a request
User portal › Approval Request
Everything above is the company side. Staff work from their own portal: they sign in with the "User" button rather than the admin one, then click "Approval Request" in the left menu.
The view has three tabs. "Received" holds requests waiting on them, "Sent" holds what they raised, and "All Requests" is the searchable history, with filters for date range, request type, role, status and Request ID. The grid shows Actions, Title, Status, Request ID, Request Type, Requested By, Organization, Sent To, Priority and the created and updated dates.
Pressing "New Approval Request" opens the create dialog. "Request Type" is the important field: "Basic" lets the requester pick their own approvers, while "Need Approval" hands that decision to one of your templates. A third option, "Support", raises a ticket to a department instead.
- "Need Approval" and "Support" only appear once you have configured approval templates or support types. If a company has neither, staff simply get "Basic".
- "Amount" and "Currency" stay disabled until "The Request Will" is changed away from "Not Related in Monetary" — so a request with no money attached needs no extra input.
- Attachments are accepted up to 3 MB each, as Zip, 7Z, PDF, PNG or JPEG.
📨 Basic versus template requests
User portal › Approval Request › New Approval Request
With "Request Type" = "Basic" the requester fills in "Title Of Request", picks one or more people in "Approvers", optionally sets a priority, an amount and a description, and presses "Send". Both the title and at least one approver are required — leaving either empty stops the send with "Title is required" or "Approver is required" and keeps the dialog open.
Switching to "Need Approval" changes the dialog: the "Approvers" picker disappears and "Template Group" and "Template Name" take its place. The approvers are no longer the requester decision — they come from the stations you defined on the template, which is exactly why templates exist.
Choosing a template also renders whatever extra fields it carries, each marked with (*). Those come from the properties you attached to the template, and they can be a date, a free-text box or a number.
- Both comboboxes pre-select their first entry, so a requester who does not care simply presses "Send".
- On success the message is "Created request", the dialog closes and the view jumps to the "Sent" tab so the requester sees their new row immediately.
- A "Support" ticket reuses the same two comboboxes, relabelled "Department" and "Type".
- A required NUMBER property is pre-filled with 0 and always counts as answered, so it can never block a send. If a number genuinely must be supplied, say so in the property name or use a text field instead.
- Requesters can cancel their own request from the "Sent" tab while it is still submitted or returned to them; once it has moved further, "Cancel Request" is greyed out and only the approvers can move it.
❓ Frequently asked questions
1 What roles are involved in an approval?
Three: the requester raises it, the approver decides, and the executor carries it out once approved.
2 How is a ticket different from a request?
A request must pass approval before it is acted on. A ticket is a call for help and is handled directly.
They have separate templates and separate queues.
3 Why bother with templates?
They make sure every request of a given kind arrives with the information the approver needs, and keep your reporting consistent.
4 Can I be alerted about new requests?
Yes — pair this with Telegram notifications for immediate alerts when something needs approval.