TRST Docs

Appearance

Projects ​

Projects are the operational unit in the trst platform. Created by organizations, projects manage terminals, sensors, end user memberships, and point to an environment for palm vein biometric data storage and verification.

What is a Project? ​

A project in trst represents a specific biometric authentication deployment or application:

  • Created by an organization (org_id)
  • Points to one environment for palm data (environment_id)
  • Manages PalmSecure sensors and terminals
  • Controls access permissions based on environment ownership
  • Manages end user memberships
  • Tracks verifications and usage analytics

Think of a project as your application or deployment that uses biometric authentication.

See Organizational Hierarchy → to understand how projects fit into the overall trst platform structure.

Creating a Project ​

Contact trst support or your account manager to create a new project.

You wil need to provide the following information:

  1. Project details:
    • Project name
    • Description
    • Organization (if applicable)
  2. Environment type:
    • Global Environment - For public-facing applications
    • Multi-tenant Environment - For organization-specific systems

Project-Environment Control Model ​

Full Control (Org Matches) ​

When project.org_id == environment.owner_org_id:

json
{
	"project": {
		"id": "proj_acme_access",
		"org_id": "org_acme_corp_2024",
		"environment_id": "env_acme_employees"
	},
	"environment": {
		"id": "env_acme_employees",
		"owner_org_id": "org_acme_corp_2024",
		"type": "organization"
	}
}

Project Can:

  • ✅ Verify users against environment
  • ✅ Create and manage user profiles
  • ✅ Manage user memberships to project
  • ✅ Update user metadata
  • ✅ Delete enrollments
  • ✅ Trigger re-enrollment

Use Cases: Corporate access control, employee management, tenant-specific applications

Read-Only (Org Mismatch - Global Environment) ​

When project.org_id != environment.owner_org_id:

json
{
	"project": {
		"id": "proj_retail_app",
		"org_id": "org_retail_co",
		"environment_id": "env_sg_national"
	},
	"environment": {
		"id": "env_sg_national",
		"owner_org_id": "org_trst_sg",
		"type": "global"
	}
}

Project Can:

  • ✅ Verify users against environment
  • ✅ Query enrollment status (limited metadata)
  • ❌ Cannot create enrollments (user-initiated only)
  • ❌ Cannot manage user profiles
  • ❌ Cannot delete enrollments
  • ❌ Cannot update user metadata

Use Cases: Public applications, payment systems, cross-organizational verification

Project Configuration ​

Project Types ​

Sandbox:

  • For development and testing
  • Limited API usage
  • Isolated test data
  • Full feature access
  • No SLA guarantees

Production:

  • For live deployments
  • Usage-based pricing
  • Real user data
  • 99.9% uptime SLA
  • Priority support

Regional Settings ​

Projects can be configured to use specific regions for API routing. Contact trst support to set the region.

Note: Environment region controls data storage; project region controls API routing

Project Organization ​

DO:

  • Create separate projects for production and sandbox
  • Use descriptive project names
  • Choose environment that matches your control needs
  • Organize by application or business unit
  • Organize by geographic region

DON'T:

  • Mix production and test data in same project
  • Point to wrong environment type
  • Share API keys across projects
  • Ignore permission implications

Next Steps ​

Now that you understand projects:

  1. Learn about Environments → - Understand data storage
  2. Explore Sensors → - Choose hardware
  3. Create Your First Project → - Get started

Additional Resources ​