Organizational Hierarchy

The trst platform uses a simple hierarchy to organize biometric authentication deployments.

Structure Overview

How It Works

Organizations

An organization represents your business or entity in the trst platform. Every resource (environments, projects, terminals) belongs to an organization.

Environments

Environments store encrypted palm vein biometric data. They are owned by organizations via owner_org_id.

• Contains palm templates for biometric matching
• Can be owned by trst (global) or your organization (private)
• Supports 1:N matching (one scan against many templates)

Learn more about Environments →

Projects

Projects are your applications or deployments that use biometric authentication. They are created by organizations and point to an environment for data storage.

• Created by your organization (org_id)
• Points to one environment (environment_id)
• Manages terminals and sensors
• Controls user memberships
• Level of control depends on environment ownership

Learn more about Projects →

Control Model

The relationship between projects and environments determines access permissions:

Full Control (project.org_id == environment.owner_org_id):

• Create, update, delete user profiles
• Manage enrollments and memberships
• Complete data control

Read-Only (project.org_id != environment.owner_org_id):

• Verify users only
• Cannot manipulate user data
• User-controlled enrollment

Example

A retail company (org_retail_co) creates a project (proj_retail_app):

• Private Environment: Points to env_retail_employees owned by org_retail_co → Full control
• Global Environment: Points to env_sg_national owned by org_trst_sg → Read-only verification

Next Steps

1. Understand Environments → - Learn about data storage options
2. Understand Projects → - Learn about application deployment
3. Get Started → - Create your first deployment