TARG ONE / Core
ONE Core.
Company setup, permissions, master data, workflow, and audit trail. Every other module is a view into what ONE Core holds, not a separate system next to it.
- AUD-5510Role “Finance Staff” permissions updatedPosted
- AUD-5509New supplier record addedPosted
- AUD-5508Approval workflow updated, Purchase OrdersPosted
- AUD-5507New branch added: SurabayaPosted
What it covers
The foundation every module builds on.
Company setup
Multi-entity and multi-branch configuration.
Roles and permissions
Who can see and do what, by role.
Master data
Customers, suppliers, items, and other shared records every module reads from.
Workflow and approvals
Approval chains and process rules configured once, enforced everywhere.
Audit trail
A record of who changed what, and when.
What every module depends on
One foundation, not eight separate ones.
ONE Core is not a module other modules connect to. It is what they are built on. This is the difference between an integrated platform and separate tools with a shared login screen.
Every module
Customers, suppliers, and items are read from one master record, not kept as separate copies per module.
Every module
The same roles and permissions apply everywhere, rather than separate logins and access rules per module.
Every module
Changes write to one audit trail, so a company-wide change history exists.
ONE Intelligence
Ask Targ reads the same permission model, so it only surfaces what a person is already allowed to see.
Run your business as one
See ONE Core underneath your operation.
Tell us how roles, approvals, and master data are managed today and we will show how ONE Core carries them across every module.