Skip to content

User journeys — step-by-step flow guides

Where the module pages explain everything a module offers, these guides walk one flow at a time, click by click — from the sidebar item to the finished document — and always say who performs each step. Follow them in order the first time; afterwards they work as a checklist.

The personas

Every step is labelled with a persona. A persona is simply a user group in your BusinessIntents installation — a task addressed to a group appears in the Inbox of everyone in that group (and of administrators). One person can of course wear several hats in a small company.

PersonaGroupWhat they do
EmployeeEmployee / personalClaims expenses, requests vacation, fills in timesheets — always from the Personal shell (/services/web/personal/), where they see only their own records.
ManagerManagerApproves vacation requests and employee timesheets.
ApproverApproverApproves invoices, orders and expense claims; posts goods documents, stocktakes and payroll runs.
IssuerIssuerIssues approved sales invoices, credit and debit notes — the step that stamps the real number.
SenderSenderSends the issued invoice and records how it went out.
PayerPayerPays purchase invoices and reimburses expense claims.
Billing clerk(any office user)Creates and maintains sales invoices, payments, credit/debit notes, proformas.
AP clerk / Buyer(any office user)Enters supplier invoices; raises purchase orders and RFQs.
Sales rep(record owner)Works leads, opportunities and quotations — their own pipeline appears in the Personal shell.
Storekeeper(any office user)Receives, issues, transfers, returns, adjusts and counts stock.
Support agentAgentTriages, works and resolves service tickets.
Project manager(any office user)Plans projects, assigns people, invoices approved timesheets.
Payroll officer(any office user)Maintains salary data and runs the monthly payroll.
AccountantAccountantPosts journal entries and reviews automatic postings and stornos.
HR / back office(any office user)Maintains vacation entitlements and employee records.

Prerequisite for every Personal-shell journey: the signed-in user must have an Employee record whose Username equals their login — that is how the suite knows who "me" is. Without it the personal pages are simply empty. (The match is on Username, not on the e-mail: a login need not be e-mail-shaped, and the Email field enforces an address format.)

Entering data for someone else ("act as"). Where the crew never touches a computer, an entitled user can work the personal pages in a chosen employee's name: pick Enter data as… in the user menu and type that employee's username. A coloured banner then reads "Acting as … — entries are recorded in this person's name; the log keeps yours", every personal page and the Inbox serve that person's world, and Exit returns you to yourself. It is not a login as them: your own permissions still apply and the audit trail keeps your real user. This is also the way an administrator with no Employee record of their own can walk any personal journey below. Details in How it works.

The journeys

Sell and get paid

Win the deal

Buy and pay

Run the store

People

Projects and time

Serve the customer

Keep the books


Conventions: each guide opens with its personas and the modules it covers (with a coverage marker, like the module pages). The guides describe the generated web UI — the application shell at /services/web/application/ and the Personal shell at /services/web/personal/.

The BusinessIntents Business Suite - end-user guide.