There is no automation rule engine in NoxOrigin. Not a limited one, not a plan-gated one — none.
This page used to sell trigger, condition and action rules, scheduled reminders, automatic approval routing and a log of runs you could inspect. That engine does not exist in the current application, so the page now says what does: a dated follow-up, a status you change, a permission that stops an action, and a person who decides. If a rule engine is what you are buying, NoxOrigin is the wrong product and this page is worth the thirty seconds it takes to find that out.
No plan on this site adds the rule engine to you. If rules are the requirement, evaluate a product whose engine has shipped.
What the current application actually contains
Five things, none of which is a rule. This is the whole of the mechanism, and it is enough for a team that works its own queue.
Write the next action down, with a date on it
An opportunity carries a next action and a date. A project carries tasks with assignees and due dates. A follow-up carries the same. This is the whole of the follow-up mechanism in NoxOrigin today: an item with a date and a name against it, which is enough to work a queue and not enough to fire anything by itself.
Work the queue in Today, by role and by what is overdue
Today reads the dated work across projects, opportunities and invoices: what is due soon, what is overdue, what is waiting. A person works it. Nothing in NoxOrigin decides that something crossed a state and therefore a task should exist — the task exists because somebody created it.
Change the status yourself when the state actually changes
A task moving from planned to in progress to done, an opportunity moving stage, an invoice moving from issued to paid: these are status changes, and a person (or a client action such as a payment allocation) makes them. `work.workflows` configures which transitions a task may take and who may make them. That is a task-state configuration, not a rule engine, and it does not create anything by itself.
Gate the sensitive action with a permission, and let a person decide
Permissions decide who may apply a discount, issue a credit note, or approve a quote. What NoxOrigin does not have is anything that routes an exception to the right person on its own: a discount beyond a threshold does not queue itself for an owner, and an absent approver does not hand the decision to somebody else. A person asks, or waits. The permission is real; the router is not.
Read the audit history to find out who did what
Platform audit shows who did what, and to what. That is genuinely useful when a question is asked six weeks later. It is not a rule log: there is nothing running, so there is nothing to have failed, and no way to replay a run that never happened.
What is not here, named rather than softened
These are the requirements a buyer types into a search box when they land on this URL. None of them is met today.
Rules that fire
No configurable rule, no trigger or condition to write, and nothing that acts when a record changes state. A person makes the change and the person creates the work.
Anything on a schedule
No delays, no recurring jobs, and no reminders the product sends on its own. A follow-up is a date on a record, worked by whoever owns it.
Automatic approval routing
Permissions stop the wrong person acting, and audit records who did. No threshold routes an exception onward, and no absent approver hands a decision to somebody else.
A record of runs
Nothing runs, so there is nothing to inspect, nothing to diagnose, and nothing to retry. Platform audit answers a much narrower question about who changed a record.
Screenshots of the above
There are none, and there will not be any invented for this page. The current application has no automation surface to capture.
The records that do the work instead
Opportunity and next action
Where a follow-up is written down, with the date and the name it belongs to.
Task and assignment
The dated work itself, and who is behind it. Status transitions a person makes.
Today queue
The working day: due soon, overdue, and waiting, scoped by role.
Role and permission
Who may approve a quote, apply a discount, or issue a credit note. The gate exists; nothing routes to it.
Audit entry
Who changed what, and when. The history you read when the question arrives later.
What this means before you buy anything
The problem this page is about is real. A quote is sent on Tuesday and nobody follows it on Friday, because Friday depends on a memory that was never written down. Rules are the obvious answer, and rule engines are good at the parts where something crossed a state and the next step is unambiguous. The reason this page exists is not that the problem is wrong. It is that NoxOrigin does not contain the answer, and a buyer who is told otherwise will find out in month three, from a customer, rather than in month zero, from a page.
The follow-up is an item with a date and an owner, so it can be worked and audited — and it still depends on a person noticing it.
Permissions stop an action the wrong person attempts, and the audit history says who acted. Neither of those acts on a schedule.
Nothing in NoxOrigin creates a task, sends a message, or moves anything because a field changed. A person does that.
Process knowledge stays in the heads of the people who run it, which is the cost this page is really describing.
If that cost is unacceptable for your business, the honest conclusion is that you need a product whose rule engine has shipped, not a plan tier of this one.
Questions, answered with the absence rather than around it
Can NoxOrigin act by itself when something changes?
No. Nothing in NoxOrigin creates a task, sends a message, or moves anything because a field changed. A person does that, working a queue of dated items. There is no configurable rule, no scheduled job, and nothing that fires on a state change.
Can an approval happen without a person deciding?
No. Permissions stop an action the wrong person attempts, and an audit entry records who acted. What does not exist is a threshold that routes an exception to the right person on its own, an automatic escalation when an approver is unavailable, or a substitute approver chain. A person hands the decision across.
Can I see what a rule did, and retry it?
There is no rule and therefore no history of one. Platform audit answers 'who changed this, and when', which is a different and much narrower question. There is nothing to inspect after a run because nothing runs.
Is the rule engine on the roadmap?
The approval-engine contract is recorded as a proposal for a future release, with the explicit note that it is a foundation contract and has no runtime code. This page is noindex for that reason: a designed capability is not a capability, and we would rather you read that here than discover it later.
What should I buy if I need rules?
A product whose rule engine has shipped and whose documentation describes it as a feature you can use today. The requirements above — state-change rules, delays, reminders, approval routing, a run log — are stable requirements, and NoxOrigin meets none of them today.