Regisseur · Product walkthrough
One application. Three processes. One connected hire.
Follow Idris Balogun from a public job application to a provisioned, signed-in employee with plant-system access — hiring, onboarding and access request, each opened by the one before it through the company's own monday.com boards, with a named person making every decision that matters.
3
Connected cases, one application
0
Times anyone opened, assigned or started a case
8
Decisions by named people
2
Messages approved before sending
2
People named on a case by hand
~6 min
Application to last close
Idris Balogun
The candidate, then the new hire. Applies on the public page, answers the invitation by email, signs the offer and the safety acknowledgement. Holds no login.
Candidate / New hireMarcus Delgado
Field Supervisor. Screening review, interview outcome, the onboarding plan, the access request — four decisions in his own session.
Field SupervisorAisha Rahman
HR Coordinator. Names the candidate and the new hire on their cases; records the screen result and the hire record.
HR CoordinatorLena Okafor
IT Administrator. Issues the equipment; grants the historian access in the plant system and confirms it.
IT AdministratorTomasz Wierzbicki
OT Security. Approves the high-risk plant-system access — a second, independent approver by design.
OT SecurityThe journey — three connected cases
Idris Balogun — Field Technician Application
Hiring — application to signed offer
completed→writes the hire onto
the Onboarding board
the Onboarding board
Idris Balogun
Onboarding — account, equipment, acknowledgement
completed→opens the request on
the Access Requests board
the Access Requests board
OT access -- Idris Balogun -- Historian read
Access — historian read, three approvals
completedAbout this walkthrough
Every screen below is a real screenshot from an automated, end-to-end run of Regisseur, captured live — not a mock-up. The people and the company are fictional; the data is illustrative. The application was a real browser submission with a real PDF. The two board items that opened the second and third cases were written by the cases themselves onto a real monday.com account, and the cases opened through its real webhooks. The Microsoft account and the two register rows were checked directly in the directory and the lists, outside the product. Three things are narrated rather than performed by the candidate himself: his email reply was sent over Microsoft Graph from the company's own mailbox (the inbox, the matching and the fulfilment are real; only the sender identity is stood in for), and both signatures were applied through the signing service's own interface rather than drawn by hand. The background screen is done by an outside vendor; HR records the result. The plant historian itself is outside the platform by design: IT grants access there and confirms it here. Company groups and a mailbox were not created, as recorded in the onboarding walkthrough. Nothing that arrives over the page or a webhook was pre-loaded.
Part 1
Setting up
What the company configured: the role requirements document, the templates, two doors into the workspace
The document is split into passages the platform can retrieve and quote. Nothing about the candidate is in here; it is the company's own rulebook.
Hiring, Onboarding and Access Request sit side by side. They are configuration, installed once. The cases they open are not: every case in this walkthrough is created by a real event, never typed in.
The public careers page is one door; the monday.com boards are another. Each has its own key. A key for one door cannot open the other.
No login, no product chrome. A name, contact details, the role, a site, an earliest start date, a résumé PDF and a consent box.
Part 2
The application
A candidate applies on the public careers page — the case opens itself, reads the résumé, judges it against the role requirements
Idris Balogun applies for Field Technician II at Permian North with his résumé attached — a real browser submission, exactly as an applicant would make it.
The candidate gets a reference and a status link. Behind the page, the application and the résumé were handed to the workspace by the server; the candidate never sees a case or a login.
The same public status view every applicant gets, in Fabrikam's own look, written for a candidate.
The first entry on the case is the application's own arrival — the only thing that opened this case.
Seconds after the application, the hiring case exists and is running. Nobody in the company created, assigned or started it.
The PDF the candidate uploaded is attached to the first step, landed by the intake itself.
The platform reads the PDF and records the candidate's certifications, years of field experience and licences as case facts the next step can use.
The qualification step quotes the role requirements document, scores the candidate, lists any gaps, and names the plant-system role the job carries — read from the document, never invented.
Part 3
Screening and interview
The hiring manager decides; the invitation goes out; the candidate answers by email; the case moves on by itself
Aisha Rahman, HR, records Idris as the candidate at his personal address. What he may do — sign his own offer letter — comes from the role, not from the person entering it.
The candidate is now a party to the case, bound by hand. This is the one place a person must act before the platform will send anything to him.
The case has no external party yet. The candidate is the only person outside the company involved, and the platform will not let an automated step grant them the right to sign anything.
His decision and his note are on the record. Approving moves the case to the interview invitation; rejecting would have sent a decline notice.
Marcus Delgado, the field supervisor, sees the assessment — score, gaps, plant-system role — and decides. The platform recommends; it does not decide.
A person approves the draft. Only now does the email go out.
The platform drafts the interview invitation with two windows at Permian North. Nothing is sent until someone approves it.
The real email is on the case's communications log. The case is now waiting for one thing: the candidate's reply.
The open request shows the deadline and what happens if nobody answers. Only the candidate can close it.
The candidate's reply lands in the inbox, is matched to this case, and the waiting step completes. No one re-keyed a slot or re-opened the case.
The open request closed itself the moment the reply arrived. No chasing, no follow-up needed.
Marcus records the hire. Rejecting here would have sent the decline notice instead.
The hiring manager records the outcome in his own session.
Part 4
The hire
HR records the screen and the hire record; the offer letter is signed; the hiring case writes the new hire onto the Onboarding board
The background and drug screen are done by an outside vendor. The platform asks HR to record the result, the corporate account name, the start date and the supervisor — the facts onboarding needs.
Screen cleared, account name assigned, start date and supervisor set. Each field is checked before it is accepted — a bad date or account name is refused, not recorded.
The hire record is now case data. The next step can only proceed because the screen cleared.
A real signing envelope goes to the candidate at his personal address, addressed by his role on the case.
The signed offer letter is back on the case as a document. In this walkthrough the signature was applied through the signing service's own interface rather than drawn by hand; everything after that is the product's normal path.
The last hiring step writes the new hire onto Fabrikam's monday.com Onboarding board — name, role, site, start date, supervisor, personal address, the plant-system role, the account name — and marks it Submitted. The board is the company's system; the case wrote to it exactly as HR would have.
Part 5
Onboarding opens itself
The Onboarding item opens Case 5 through the webhook — a real account, the equipment, the register, the acknowledgement, the welcome email
The first entry on the onboarding case is the board's own notification.
The board item opened the onboarding case through the same webhook a person's item would. Nobody in the company created it.
Aisha Rahman records Idris as the new hire on the onboarding case.
The new hire is a party to the onboarding case, bound by a person.
Onboarding starts with no external party. The new hire will sign his own safety acknowledgement, so a person must name him first.
Onboarding reads the board item in full — and records which case created it, so the two cases are linked from here on.
Drafted from the company's access policy for a Field Technician II at Permian North.
Approved. Provisioning may begin.
Nothing is provisioned until Marcus confirms the plan in his own session.
The platform creates the new hire's Microsoft account. The walkthrough checks it directly in the directory, outside the product: it exists, it is enabled, and it carries the plain name from the board. The initial password was generated once, used in the create call, and never stored or shown.
The asset note is on the record.
Issuing and enrolling the laptop is done by IT, not by the platform. Lena Okafor confirms it here in her own session.
The platform writes the equipment outcome to the company's Device Register list. The walkthrough reads the row back directly.
A real signing envelope to the new hire for Fabrikam's field safety orientation.
The signed acknowledgement is on the onboarding case. Applied through the signing service's own interface in this walkthrough, as with the offer letter.
Only now does the welcome email go out.
It names only what is actually ready — the account — and what is still pending. A person approves before it goes.
The Onboarding item's status column reads Done and carries a comment with the outcome — read back directly from monday.com.
Part 6
Access opens itself
Onboarding's own hand-off opens the access request — supervisor, OT security and IT, then the register and the board
Because the role carries a plant-system permission, onboarding opens an access request on the Access Requests board for it — and records which case asked.
The first entry is the board's notification, again.
The second hop. The board item opened the access request through the webhook; nobody typed it.
The access case reads its item in full and records that onboarding created it — the chain is declared from the child's side.
The policy check names the system's category and risk level. Historian access is a plant system: high risk, and so a second approval is required.
On the record.
Marcus confirms the access request he never typed — the onboarding case opened it for the role.
A second, independent approver by design.
Because the policy marked the request high risk, Tomasz Wierzbicki, OT Security, must approve it in his own session.
The grant note is on the record.
The plant historian is outside the platform by design. Lena grants read access there and confirms the outcome here.
The platform records the grant in the company's Access Grants list. The walkthrough reads the row back directly.
Status Done and a comment on the Access Requests item — read back directly from monday.com.
Part 7
Everything connected
Three closed cases, linked in the product, one candidate, zero re-keying
Open the hiring case and the product shows Hiring → Onboarding → Access, each a real case you can click through to.
The same chain, seen from the middle.
The same chain, seen from the end. Each case declared where it came from; the product joins them up.
Every decision, send and signature in one trail.
Every step settled: extraction, qualification, the screening review, the invitation and the reply, the interview outcome, HR's record, the signed offer, the hand-off.
The case history as the platform recorded it.
Decisions, directory and board calls, the envelope and the approved send.
The plan, the account, the device, the access request, the acknowledgement, the welcome email, the write-back.
The case history as the platform recorded it.
Three named approvals and two independent verifications in one trail.
The policy check, the approvals, the grant, the register row, the write-back.
The case history as the platform recorded it.
One application opened all three. Nobody typed the second or the third.
