Structure

The web console is built around teams, projects, and snapshots, creating a hierarchical structure that keeps your data organized and secure. Understanding this structure helps you navigate efficiently and manage your debugging workflow effectively, from team management to snapshot analysis.

How it's organized

Jahro follows this clear structure:

  Team 
  └── Project
    ├── API Keys
    └── Snapshot
      ├── Logs
      └── Screenshots

Teams

Teams are the top level in Jahro, and everything starts with a team. This provides the foundation for collaboration and data isolation.

What you get:

• Team Overview: Dashboard showing your recent projects and team members
• Team Members: Manage team members with different roles (Owner, Admin, Member) through team management

• Security: Your data is isolated - only your team can see your production logs

Projects

Projects belong to teams and represent your Unity games or applications. Each project has its own API keys and snapshot collection.

What you get:

• Project Dashboard: Overview of recent snapshots
• API Keys: Project-specific keys for Unity client integration
• Snapshots: Collection of captured debugging sessions
• Settings: Project configuration and management

Snapshots

Snapshots are captured debugging sessions that contain logs, screenshots, and metadata from your Unity applications.

What you get:

• Session Overview: Summary of the debugging session with metadata
• Logs Viewer: Detailed log analysis with filtering and search
• Screenshots Viewer: Visual debugging with lightbox viewing
• Sharing: Share sessions with team members or external collaborators

Security and data isolation

Team isolation

Each team's data is completely isolated from other teams. This ensures that your production logs and debugging data remain private and secure, accessible only to members of your team.

Project isolation

Within a team, projects are isolated from each other. This allows you to organize different Unity applications or game versions while maintaining clear separation of debugging data.

API key security

Each project has its own API keys, ensuring that Unity clients can only access the specific project they're configured for. This prevents accidental data mixing between different projects.

Next steps

Now that you understand the structure, explore the specific features:

• Team Management - Learn how to invite members and manage roles
• Snapshots - Discover how to capture and share debugging sessions
• Logs & Screenshots - Master the viewing tools for debugging data

For Unity integration, check out Getting Started and learn about Unity Snapshots for capturing debugging sessions.