Routes the request to the manager with sufficient budgetary authority to approve it. Typical uses for the financial workflow would be capital purchase, e.g., if a user asked for a new $100 cell phone, the request simply goes to their direct manager, but a new laptop request might be routed all the way to the company president.

Define custom workflows with the Individual type. Create a Request Type which allows you to name specific individuals needed to approve this request. You can also set the sequence of their approvals. This workflow is especially useful for directing a request to a specific user, or selected group who need to review a given type of request.

The Level workflow is similar to the Financial, except that the approval process stops when it reaches the person whose level is equal to or greater than the level required. For example, most companies classify their employees with a title. Employee, Manager, Director, Vice President, CEO and so on. The Level workflow is useful when an approval can only be granted at a certain level.

The Manager workflow routes a request to the user's manager and no farther. Many organizations use this for expense reports and other day-to-day management oversight.

Send a request to anyone for any reason within your organization.  Ad Hoc requests are great when you need to get something approved on-the-fly while still maintaining a record of the process.

Similar to Internal Ad Hoc, except you can send an approval request to someone outside the company.  For example, sending a sales quote, digital graphic or other document to a client or channel partner would usually be handled by email.  ApprovalTrack can consolidate these business exchanges in a single location, eliminating the confusing maze of email folders and multiple filing rules.

Requests are typically serial in nature: One person, then another, then another. Using the Group workflow, the approval request may be routed to several people at the same time.

ApprovalTrack can be used to manage various task assignments.  Often, a request does not require an approval.  For these cases, simply create Task types and incorporate them into your workflow, or assign and generate follow-up tasks to be completed as the result of an approved request. For example, once a request has been approved to buy something, the purchasing department needs to issue a PO. With ApprovalTrack, once the request is approved, a task can be automatically sent to the appropriate person(s) for action.