Skip to content
Approvals / TenXshift

Approvals

Approvals module in TenXshift: a unified approvals inbox across departments, with configurable paths.

A clearer answer to: where is the request?

What does Approvals provide?

When the request path differs by department without a clear reference, follow-up depends on correspondence. The Approvals module brings approvals together across departments with configurable paths in TenXshift.

Approvals are a backbone of NGO governance: purchasing, spend, travel, and exceptions. Approvals provides a unified inbox and configurable paths — configurability does not mean organisation policy is applied automatically without setup and testing.

Who is it designed for? Finance director, country director, and department managers.

Module capabilities

Choose a clear scope, and review the functions your team will actually use.

01

Unified approvals inbox

02

Configurable paths

03

Cross-department approvals

04

Supports segregation of duties with security

Expected operational outcomes

What helps the team evaluate the module before full enablement.

  • Clearer visibility of where a request sits in the path
  • Paths configured by roles and thresholds
  • A basis to test segregation of duties before production

What does the approvals inbox provide?

It gathers requests across departments in a trackable path, with roles and review thresholds adjustable to organisation policy.

Is enabling the module enough?

No. You must define roles and the review and approval path and test it. Configurability does not mean every policy is applied automatically.

How it relates to procurement, finance, and security

It is often used with Procurement and Finance, and reviewed with Security when segregation of duties and step-up verification are needed.

Demo scenario

Route a sample purchase request through the involved roles, then review its handoff and path. Test required segregation-of-duties cases with Security and Settings modules.

Suggested demo walkthrough

Start from a real working day.

Route a sample purchase request through the involved roles, then review its handoff and path. Test required segregation-of-duties cases with Security and Settings modules.

This is a product-evaluation scenario, not a measured client outcome.

Approvals FAQ

Is enabling the module enough to apply organisation policy?

You must define roles and the review and approval path and test it. Configurability does not mean every policy is applied automatically.

Does it cover every request type?

The inbox is unified across departments within the supported scope; review the request types you need in the evaluation session.

How does Approvals relate to segregation of duties?

Segregation of duties is reviewed with the security module; approvals run the path while SoD addresses conflicting responsibilities.

What is the price of the Approvals module?

It is billed as part of a module bundle in your organisation plan; the price depends on active users and enabled bundles. See the pricing page for details.

How do we assess fit before subscribing?

Email info@tenxshift.com to request a 20-minute demo. Prepare a non-sensitive example from your team’s work, roles, and reports you need — then review implementation requirements before agreeing.

Explore related modules

All modules ↖
Procurement

Procurement ↖

From purchase request to approval, RFQ, then purchase order.

Finance

Finance & spend ↖

Link spend to grant budget lines so figures read in the right context.

Security

Security ↖

Multi-factor authentication, step-up verification, sessions, IP, segregation of duties, and export audit.

Test your grant. Then choose your scope.

Self-explore, then a 20-minute demo, then a subscription by modules and users.