Teralo
Back to Teralo Host

Tools Configuration

Configure the full suite of Teralo tools at the organisation and project level, including types, statuses, templates, and custom fields.

How Tools Configuration Works

Teralo uses a two-level configuration system:

  1. Organisation Level: Define default tool settings, types, and templates that apply across all your projects
  2. Project Level: Activate and customise tools for individual projects

This approach ensures consistency while allowing project-specific adjustments.

Organisation Tools

Accessing Organisation Tools

  1. Go to Organisation > Tools
  2. Browse the available tool categories
  3. Configure defaults for your organisation

Available Tool Categories

Configure each of these at the organisation level:

Tool What You Configure
Mail Mail types (RFI, Site Instruction, etc.) and statuses
Documents Document types, disciplines, and statuses
Contracts Contract types and statuses
Budget Codes Cost codes for financial tracking
Procurement Procurement categories and settings
Inspections Inspection templates with sections and items
Incidents Incident type classifications
Injuries Injured person types and nature of injury categories
Observations Observation types with custom fields
Meetings Meeting types with agenda templates
Equipment Equipment types with custom fields
Permits Work permit types
Submittals Submittal types and specification sections
Program Schedule settings and calendars
Method Statements SWMS types
Inductions Induction tiers, job titles, license types, medical questions
Public Site Public portal settings

Project Tools

Activating Tools

Not every project needs every tool. Activate only what's relevant:

  1. Go to Project > Tools
  2. Each tool can be enabled or disabled for the project
  3. Enabled tools appear in the project sidebar
  4. Disabled tools are hidden from the project

Project-Level Customisation

After activation, customise tools for the specific project:

  1. Select a tool category in Project > Tools
  2. Activate organisation-level types and templates
  3. Add project-specific types if needed
  4. Configure settings unique to this project

Common Configuration Patterns

Types and Statuses

Most tools follow a types and statuses pattern:

  • Types: Categorise items (e.g., mail types, contract types, incident types)
  • Statuses: Track lifecycle stages (e.g., Draft, Active, Completed)
  • Activation: Choose which organisation-level types are active per project

Custom Fields

Some tools support custom fields for structured data capture:

  • Observations: Custom fields per observation type
  • Equipment: Custom fields per equipment type
  • Bookings: Custom fields per bookable location

Templates

Several tools use templates for standardised content:

  • Inspection Templates: Sections and items for quality/safety checks
  • Meeting Templates: Standard agenda sections per meeting type
  • Method Statement Templates: Hazard and control templates per SWMS type

Numbering Prefixes

Configure numbering prefixes for auto-generated reference numbers:

  • Mail prefix (set at organisation level)
  • Submittal type prefixes
  • Contract numbering

Configuration Workflow

When setting up a new project:

  1. Review organisation tools: Ensure defaults are up to date
  2. Activate project tools: Enable the tools this project needs
  3. Activate types: Select which types are relevant
  4. Customise settings: Add project-specific configuration
  5. Set up templates: Activate inspection and meeting templates
  6. Configure workflows: Set up approval workflows (see Workflows & Approvals)

Best Practices

  • Configure at the organisation level first: Set up comprehensive defaults so projects can activate rather than recreate
  • Only activate what's needed: Keep projects focused by enabling only relevant tools
  • Standardise types across projects: Use consistent type names for meaningful cross-project reporting
  • Review configuration periodically: Update organisation-level settings as your processes evolve
  • Use custom fields sparingly: Only add fields that capture data you'll actually use