Approval

Yes, it does. The signature count set on a document type applies to approvals and rejections alike, and whichever is reached first decides.

In practice: set two signatures on a type approved by four people and two dissents end the process as rejected – even if the other two would have agreed. That symmetry is worth thinking through in advance.

No. The notification e-mail carries Approve and Reject buttons that work without logging in; the link is secured by a unique hash of that specific request.

That is precisely why the e-mail counts as a sensitive message – whoever gets hold of it can decide. The approver can of course also decide the ordinary way in the request detail.

Because write permission and the approver role are two separate settings. Write permission lets you create requests and add notes; only somebody on the approver list for that round may approve.

Approvers are set by an administrator under Settings → Approval in the Stage 1 – may approve and Stage 2 – may approve columns. Confusing the two is the commonest cause of this report.

It depends on the Close automatically option, which the requester ticks when creating the request. If it is on, the system moves the request to Rejected once the Approve by deadline passes and notes in the record that it was an automatic rejection due to the date expiring.

Without that option the request stays open past the deadline and approvers can still decide on it. A notification e-mail about automatic closure goes to the requester and to the approvers.

Up to five. For each you choose a name and one of three types: text/number up to 250 characters, unlimited text, or a date.

The field appears in the form when creating a request and in the overview table, so it can be sorted and filtered on. Every request always has the fixed fields: Name, Description, Created by, Date and time created, Approve by, Approved by and Rejected by.

No. The Approval module supports at most two rounds – a signature count of 0 for round 2 means a single-round process.

For more complex workflow – multi-round chains, forms filled in during a later round, branching by amount – we recommend the Requests module, which is designed for those cases.

Yes, provided the Paper Mail module is active. At the bottom of the incoming item detail there is a button that passes it into the approval process; you fill in the parameters and send it.

The scanned document stays attached to the original mail record, so nothing gets retyped. It is the commonest way of getting incoming invoices and contracts into the module.

Yes, if the requester ticked the Agree/disagree even after approval or rejection option when creating it. Comments can be added no later than the date given in the Approve by field.

Later comments do not change the resulting status of the request – they serve to map the views of everybody involved, not to revisit the decision.

No. The number of requests, document types or approval rounds has no effect on the price. That is a material difference from electronic signature tools, which routinely bill per document or per envelope.

The price follows the number of users. An account is needed by whoever raises requests and whoever decides on them – in a company of fifty that tends to be ten to fifteen people.