Platform overview
TriostackOne is a single workspace with one identity and permission model underneath every product — CRM, HRMS, Payroll, LMS, Projects, and Finance. Understanding that structure up front makes it much easier to reason about how data and permissions will behave once you connect or build on top of it.
1. One workspace, many apps
A workspace is the top-level container for your company. Every app you enable — CRM, HRMS, and so on — runs inside that same workspace and reads from the same user directory, rather than being a separate tenant with its own login.
This means a person exists once per workspace, not once per app. Their role and permissions are configured per app, but their identity, name, and account status are shared.
2. Shared data model across apps
Apps aren't fully isolated from each other. HRMS employee records are the source Payroll reads compensation and attendance from; CRM deals can spin up linked Projects; Payroll runs post automatically as expenses in Finance. Building an integration against one app should account for the fact that its data may already be feeding, or be fed by, another app in the suite.
3. Permissions are scoped per app, not global
A role like Admin or Manager sets a baseline, but actual permissions — what a person can view, edit, or approve — are configured per app. Someone can be a Manager in HRMS with approval rights over leave, while holding only Member-level access in Finance. Any integration or automation you build should respect these per-app scopes rather than assuming a single global permission level.
4. What's connected automatically today
A few cross-app connections already run natively, without any custom integration: CRM deals to Projects, Projects and Payroll costs to Finance, and HRMS attendance to Payroll pay runs. If what you're building overlaps with one of these flows, check the relevant product's documentation guide first — the connection may already exist.