Skip to content
Ticos Docs

Platform Settings

Platform Settings allow team administrators to manage global configuration options that span all robots, including API keys, system endpoints, data retention, and safety policies. This corresponds to the Platform Settings page in the dashboard.

General

Here you can manage your team’s basic information and API keys for various third-party service integrations.

  • Workspace Name: The display name for your team on the Ticos platform.
  • Model API Keys: Configure global API Keys for providers like OpenRouter, OpenAI, DeepSeek, Claude, etc. These keys will automatically be shared by all robots under the platform, avoiding repetitive setup.
  • Service Endpoints: Configure private LLM or TTS service endpoints (for example, your internal inference cluster URL).

Safety

Set platform-level safety guardrails and fallback strategies for all robots, which take precedence over individual robot configurations.

  • Content Moderation: Enable system-level sensitive word filtering and compliance checks to prevent the robot from outputting prohibited content.
  • Safety Overrides: Enable forced takeover options. When a robot encounters uncontrollable risks or errors, automatically switch it to the “Idle” state or trigger an emergency stop.
  • Teleops Permissions: Control which roles or personnel can take over the robot’s motion and conversation systems at any time.

Connection

Define the robot’s behavior when the network is unreliable or disconnected.

  • Reconnect Strategy: Set the automatic reconnection interval and maximum retry attempts after a network disconnection.
  • Heartbeat Timeout: The duration after which a robot’s status is marked as “Offline” if no heartbeat signal is received.
  • Low Bandwidth Mode: When the network bandwidth falls below a threshold, automatically reduce the teleops video stream resolution or switch to a text-only command mode.

Data Retention

The storage strategy for all logs and historical data generated by the platform.

  • Interaction Logs Retention: Set the storage duration for conversation history, API call logs, and base sensor data (e.g., 30 days, 90 days, or permanently).
  • Rewind Media: Set the expiration time for robot motion replay videos and point cloud segments. A longer duration helps with incident investigation but increases storage costs.
  • Face Data Expiration: Based on privacy compliance requirements, a strategy to automatically clean up long-unrecognized or expired face records.

Best Practices

  1. API Key Isolation: It is recommended to create different workspaces for development and production environments to avoid mixing test and production API keys in the same workspace.
  2. Compliance First: Configure Data Retention and Safety options as early as possible, especially the lifecycle management of face data, to ensure business compliance with local data privacy regulations.