Locations in LogCentral represent physical or virtual sites where your logs are collected. Each location within your organization can have its own configuration, IP addresses, and server assignments, making it easy to organize and manage logs from different sources.

You can access your locations through the main navigation in LogCentral. The locations page is available at /organizations/:orgId/locations where :orgId is your organization's unique identifier.

When you first set up your organization, you'll see a prompt to create your first location on the dashboard. This helps you get started quickly with log collection.

Locations serve as organizational units within LogCentral that help you:

Each location contains important information such as:
- Location name
- Assigned port for log collection
- Associated server information
- Current status (active or inactive)

If your organization operates across multiple physical locations, you can create a separate location entry for each site. This makes it easy to:
- Filter logs by geographic location
- Monitor specific sites independently
- Manage different network configurations per site

Many teams use locations to separate different environments:
- Production systems
- Staging environments
- Development servers
- Testing infrastructure

You can also organize locations by department or team, allowing different groups to manage their own log sources while maintaining centralized oversight.

New locations can be created from your organization dashboard. When your organization doesn't have any locations yet, you'll see a dedicated card prompting you to create your first location.

Locations can be either active or inactive. This status affects:
- Whether logs are actively collected from that location
- How the location appears in your organization overview
- Administrative actions available for that location

Only inactive locations can be deleted. This safety measure ensures you don't accidentally remove locations that are actively collecting logs. When an organization is deleted, all its inactive locations are also removed.

Access to location management depends on your role within the organization:

Use clear, descriptive names for your locations that make them easy to identify at a glance. Consider including:
- Geographic information (e.g., "NYC Data Center")
- Environment type (e.g., "Production Web Servers")
- Department or team name (e.g., "Engineering Dev Environment")

Periodically review your locations to:
- Identify and deactivate unused locations
- Update network configurations as needed
- Ensure server assignments are optimal
- Clean up inactive locations that are no longer needed

Plan your location structure based on how you need to access and filter logs. A well-organized location hierarchy makes it easier to find relevant logs quickly and manage your log collection infrastructure efficiently.

Locations work together with other LogCentral features to provide comprehensive log management:
- Organizations - Locations belong to organizations and inherit organization-level settings
- Dashboard - View location statistics and quick access to location management
- Audit Logs - Track changes and actions performed on locations

If you need assistance with location management or have questions about organizing your log sources, contact your organization owner or reach out to LogCentral support.