Understand Orbit and its built-in views

Use Orbit for project environment, detected integrations, and reusable structured records.

Before you start

Open the project whose information you want. Orbit’s built-in views and custom modules serve different purposes.

Orbit settings identifies the fixed built-ins and the reusable modules you can add to individual projects.

Step by step

1. If Orbit is absent from the project rail, open Manage and enable Orbit.

2. Open Orbit → Environment to inspect the environment files found in the project. Values begin hidden; choose the correct file before editing.

3. Open Integrations to inspect services recognized from dependencies and configuration. Detection is a starting point for investigation, not a connection health test.

4. Open Settings → Orbit to see the fixed built-ins and reusable module definitions. Create a module when a repeatable set of fields is more useful than a free-form doc.

5. Return to the project’s Orbit and use Add to enable the module there. Creating its definition alone does not add it to every project.

6. Create records in the project’s module or select its slash command in an agent request. Review both record updates and any code changes the agent makes.

What to expect

You can distinguish discovered project configuration from the structured information you deliberately maintain in custom modules.

Troubleshooting and useful details

The Settings screenshot shows Environment and Integrations as built-ins. Their structure is fixed. Custom module definitions are reusable, while records belong to the project where the module is used. A module is not automatically a live connection to an external analytics service.