Platform overview
TriostackOne is the platform underneath all ten Business Suite products: CRM, Wabiz, Desk, Mail, Website, HRMS, Payroll, LMS, Projects, and Finance. They aren't separate products bundled together — they share one identity model, one set of roles and permissions, and one data model.
Read this guide before designing an integration. Most integration problems come from not knowing which records are shared between apps, who is allowed to change them, and which connections already exist natively.
1. Workspaces
A workspace is the top-level container for one company. Every app the company enables runs inside that workspace and reads from the same user directory — there is no separate tenant or login per app.
Customer data is logically separated by account. Anything you build should treat one workspace as the boundary of the data it can see and change.
2. Unified identity
TriostackOne Identity gives each person one login and one profile across every app. A person exists once per workspace, not once per product. Role changes made in HRMS update that person's access across the platform automatically, and removing someone from the workspace revokes their access to every app at once.
For integrations this means user records should be matched once, at the workspace level — not reconciled separately for CRM, HRMS, and Payroll.
3. Roles and per-app permissions
A role (Admin, Manager, or Member) sets a baseline, but actual permissions — what a person can view, edit, or approve — are configured per app. Someone can approve leave as a Manager in HRMS while holding only Member-level access in Finance. CRM additionally has its own roles (from Sales Executive to CRM Administrator) and a reporting-manager hierarchy that controls which leads and reports each manager sees.
Integrations and automations should respect these per-app scopes rather than assuming one global permission level.
4. Shared data model
Key records are shared rather than copied. The CRM customer directory is kept consistent across every subscribed product, so sales, support, and finance work from the same customer record. The HRMS employee record is what Payroll, LMS, and access permissions read from.
Before writing data into one app, check whether that data is already produced or consumed by another — the Cross-app data flows guide lists every native connection.
5. Where external integrations are configured
External services — ad platforms, messaging, telephony, payment gateways, calendars, and the APIs and webhooks — are connected from the Integrations Hub in Triostack CRM. Every integration in the hub is available on every CRM plan, including the free trial.
6. Audit and data protection
Meaningful changes are recorded in audit logs; in CRM, every entry carries the actor, module, description, and IP address, so activity performed by an integration can be reviewed like any user's. Data is protected in transit and at rest, and access runs through centralized identity and role-based permissions. See the Security & responsible disclosure guide for details.
Best practices
- Map which TriostackOne records your integration reads and writes before you build — and which app owns each one.
- Prefer the native cross-app flows where they exist; build custom integrations only for systems outside TriostackOne.
- Run integrations under an account with the minimum permissions they need, in the specific apps they touch.
Frequently asked questions
Is each app a separate account?
No. All apps run inside one workspace with one user directory. A person has one login and one profile across every app you enable for them.
Are permissions the same in every app?
No. Roles set a baseline, but permissions are configured per app, so the same person can have different rights in HRMS and Finance.