How far a background job may act by itself

Every scheduled job hands what it finds to people. Platform, Automation Levels says, per job, whether it only tells them, asks for approval and then acts, or acts and tells them.

A job that finds something (purchase orders running late, bins to count, probation reviews due, onboarding tasks overdue) no longer only writes "would change" in its run. It hands what it found over, at the level your company chose for that job. With no level set, it only tells people and changes nothing.

• Tell people (notify): what it found goes to the people named, in My approvals under From the background jobs, and by email. Nothing changes.
• Ask for approval, then act (approve): an approval is raised for the first person named (or the first role). Approving it in My approvals makes the change; rejecting it closes the finding.
• Act, then tell people (act): the change is made at once, and the people named are told what was done.

What acting does, for the jobs set up here: the expediting list mails the buyer of each late order; the cycle-count job raises an open count for each bin; the probation review reminds each manager; the onboarding chase mails whoever holds the overdue task's role. Dunning, the pipeline sweep and the other supply-chain, finance and HR jobs act through their own rules and are set the same way. A finding already acted on is not acted on twice. Jobs that cannot act are only ever told about.

Each person sees only the findings they may open: an item that cites a record they cannot open (its module, its screen, or the part of the organisation they are confined to) is left out for them. The email counts the findings and points to My approvals; it does not list them.

1. Open Platform, Automation, Automation Levels, and choose New.
2. Choose the Job and the Level.
3. Name the People told and the Roles told. With nobody named, the company's administrators are told.
4. Save. Run automation now does at once what the dispatcher would do on its next pass.