> For the complete documentation index, see [llms.txt](https://doc.engenius.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.engenius.ai/edcc-user-manual/administration-and-platform/system-settings.md).

# System Settings

## Chapter 16: Configuring the System (System Settings)

Your comprehensive guide to the System Settings area—the central administration console for managing the EDCC platform itself.

> 🔒 **Organization Administrator Only**
>
> * **Required Role**: Organization Admin only
> * **Access Level**: Complete EDCC platform administration
> * **Restriction**: POD Admin and Viewers cannot access this section
> * **Scope**: Platform-wide configuration and management

***

## Overview: The Engine Room of Your EDCC Platform

The **`System Settings`** area, accessible from the main navigation menu, is the "engine room" of your entire EDCC platform. The configurations made here are global, foundational, and affect the entire Organization's ability to function correctly.

This is where you manage the lifecycle of your hardware assets, monitor the health of the EDCC host system, integrate with essential external services like email, and perform critical data protection tasks.

{% hint style="danger" %}
**Platform-Wide Impact**: All settings in this area have Organization-wide effects and require the highest level of administrative privilege.
{% endhint %}

***

## The Four Pillars of System Administration

The **System Settings** area is organized around four key administrative responsibilities. Use this guide to quickly find the section that corresponds to your immediate task.

| If you need to...                                                                                                                                | Go to this Section                                                                                                                          |
| ------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------- |
| **Manage the entire lifecycle of your nodes**, from initial discovery and registration to assigning them to a POD for active management          | [**16.1 Managing the Device Inventory**](/edcc-user-manual/administration-and-platform/system-settings/inventory.md)                        |
| **Check the health of the EDCC host system itself**, manage its time zone, or perform a software update on the EDCC platform                     | [**16.2 Monitoring EDCC Platform Health**](/edcc-user-manual/administration-and-platform/system-settings/system-information.md)             |
| **Integrate EDCC with essential external services**, such as an SMTP server for email notifications or an HTTPS server for OS image deployment   | [**16.3 Configuring Mail and File Servers**](/edcc-user-manual/administration-and-platform/system-settings/applications.md)                 |
| **Protect your environment from data loss** by creating and managing backups for both individual POD configurations and the entire EDCC platform | [**16.4 Backing Up and Restoring the EDCC Platform**](/edcc-user-manual/administration-and-platform/system-settings/backup-and-restores.md) |

***

## Key System Administration Concepts

### **Platform vs. Node Management**

{% hint style="danger" %}
**Critical Distinction**: The System Settings area manages the EDCC platform itself, not the individual nodes it manages.
{% endhint %}

**System Settings manages**:

* EDCC platform configuration and health
* Device lifecycle and assignment
* Integration with external services
* Platform-wide backup and recovery

**Node management happens in**:

* **MANAGE** module for monitoring and operations
* **CONFIGURE** module for POD-level settings
* **Node Detail** pages for individual server management

### **Organization-Level Administration**

**Why Organization Admin Only?**

* **Platform Stability**: These settings affect the entire EDCC infrastructure
* **Security Requirements**: Controls access to sensitive configuration data
* **Data Protection**: Manages backup and recovery capabilities
* **Service Integration**: Configures external dependencies like SMTP and file servers

### **Global Impact Considerations**

**Settings That Affect All Users**:

* Device inventory and assignment policies
* Platform time zone and logging
* Email notification capabilities
* Backup and recovery procedures

***

#### What's Next

This chapter serves as the introduction to the four essential modules of system administration. Each sub-chapter provides detailed, step-by-step instructions for using each page within the **System Settings** area.

Please proceed to **Chapter 16.1: Managing the Device Inventory** to begin your deep dive into platform management.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.engenius.ai/edcc-user-manual/administration-and-platform/system-settings.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
