Approvals
Everything waiting for a decision, in one place.
Stage 4 · The client’s side · In development
Approvals
5 decisions from 4 places · each button acts where the request came fromAll · 5Portal · 2Leave · 1Offers · 1Connected systems · 1
Today2 decisions
Portal
Lazur Furniture · new category “Garden furniture”waiting since yesterday
The client asked for it in the portal yesterday. If you approve, it becomes a task and counts toward the contract hours.
Hours≈ 3 hContractmaintenance
Decline with reasonApprove
Offers
Cafe Verde accepted the quote for a new site
Accepted by the owner with an email code. Next: a project and a contract from the quote.
Total€1,450.00Versionv2
LaterCreate project and contract
This week3 decisions
Leave
Peter · paid leave, 28–31 December
4 working days. He has 11 days left, then 7. Nobody else is away on those days.
DeclineApprove
Connected system
Content calendar · 3 posts
The posts for Ritam Fitness are waiting for approval. The button sends your decision back to the system that prepared them.
Send backApprove and publish
Approvals gathers decisions from several sources: client portal requests, leave, accepted quotes and decisions from connected systems. You can filter by source.
- The button acts where the request came from. “Approve” on a portal request creates a task; “Approve” on leave records it in the calendar.
- A decline carries a reason that the client or employee sees.
- An accepted quote becomes a project and a contract with one button.
- Everything is recorded in the client’s history.
Connected systems send their own decisions here through the same public interface. See Connected systems.