# Site Settings

The settings of a Site allow you to change properties for the site, and are explained in the sections below.

## Modifying a Site

To modify a Site, navigate to the *Settings* tab for a given Site and click on the *Site* section. After updating the Name and Description fields, click the *Save Changes* button.

<figure><img src="https://3704730939-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4lSQNVI3DZ15V7kjkMCA%2Fuploads%2FlGvhANEEAog1DFRfPWSb%2FWebApp_SiteSettings_Site.png?alt=media&#x26;token=71d9f7e8-e93f-40a1-bc48-f6c2de95e9e7" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
You cannot edit the Time Zone after creating a Site. Doing so would alter all dates and times of actions performed within the Site.
{% endhint %}

### Notifications

In this section you can enable watching all projects in a site, and subscribe to watch new projects for a site. &#x20;

<figure><img src="https://3704730939-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4lSQNVI3DZ15V7kjkMCA%2Fuploads%2F8TcuiqbnzusJ2aPi09qf%2FSite_Notifications.png?alt=media&#x26;token=e3baf75e-f665-4d8a-b819-1233480a8e78" alt=""><figcaption></figcaption></figure>

To learn more about watching a project and notifications, see these sections:

* [Watching Projects](https://docs.copia.io/docs/projects-and-devices#watching-projects)
* [DeviceLink Notifications](https://docs.copia.io/docs/devicelink/administration/notifications)

### **Sitewide Backup Schedule**

A sitewide job backs up all the projects in a site. At the scheduled start time, a job run for each project will be queued and run in order. This ensures all projects are backed up, without having to configure a job for each project manually.  More information about this and other jobs can be found in the [Creating Jobs](https://docs.copia.io/docs/devicelink/jobs/creating-jobs) section. &#x20;

The scheduler provided allows you to create a queue of backups for every project in the site.  At the time(s) chosen, DeviceLink will create and process those backup operations sequentially.

{% hint style="info" %}
**Example**:  If you set the schedule to "daily at 7AM", Copia will queue a backup operation for every project in the site at 7AM every day.
{% endhint %}

If the agent is unable to complete the backups before a new set of backup operations is scheduled (*e.g. because there were too many, or the agent went offline*), the site admins will receive an email letting them know. If the agent was online and running the whole time, this may mean you need additional agent capacity. **These notifications are only sent to users with DeviceLink notifications enabled** – see [#some-backups-did-not-start-notifications](https://docs.copia.io/docs/administration/notifications#some-backups-did-not-start-notifications "mention")for details.

<figure><img src="https://3704730939-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4lSQNVI3DZ15V7kjkMCA%2Fuploads%2FdOWWdVv5K5JNHgfKwKVh%2FSW_Backup_Settings1.png?alt=media&#x26;token=25086966-47ca-4462-b1a7-af753208bdcb" alt=""><figcaption></figcaption></figure>

The "Time Out After" field contains the timeout value which will be applied to all backup operations once a backup has started.  It is recommended to set this value to the time needed for the slowest project to back up.

In addition to the above, every project is configured to auto-commit to the default branch in its repository, generally the "main" branch. Projects can also be configured to auto-commit to a specific branch for backups named "DeviceLink/\<Name of site>". This option can be configured in the job scheduler.

{% hint style="info" %}
Standard jobs are prioritized over pending sitewide backup jobs, but do not interrupt jobs in progress.
{% endhint %}

Once configured, the sitewide job will be visible on the Job Management page as shown in the screenshot below.

<figure><img src="https://3704730939-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4lSQNVI3DZ15V7kjkMCA%2Fuploads%2Fb20zyh1SVnV5ckI90FPY%2FSW_Backup_Settings2.png?alt=media&#x26;token=2a48d673-66c5-4b7d-9280-1a3c195670a7" alt=""><figcaption></figcaption></figure>

Projects can be excluded from a sitewide backup schedule on an individual basis. Activating this feature can be useful if you are running a sitewide backup schedule but want to exclude a project from that schedule for any reason (for example, to reduce backup failures when you expect a Project to be offline due to extended maintenance or upgrades). To exclude a single Project from a sitewide backup schedule, open the project detail view and enable the "Exclude from Sitewide Backup Schedule" toggle.&#x20;

<figure><img src="https://3704730939-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4lSQNVI3DZ15V7kjkMCA%2Fuploads%2FqoHLlJwa15ux6eLxISxg%2FScreenshot%202025-03-06%20at%2011.21.15%E2%80%AFAM.png?alt=media&#x26;token=3636dd7f-5a7e-4d52-9fb3-f15930831a21" alt=""><figcaption><p>Activate this toggle to exclude a Project from a configured sitewide backup schedule.</p></figcaption></figure>

To see at a glance whether any project is not backing up, Copia labels Projects that are not associated with a scheduled job (including sitewide schedules) with a "Not Backing Up" label on the Projects page. This feature helps ensure that Projects excluded from sitewide backup schedules do not "fall through the cracks" and can be used as a reminder to re-enable backup jobs for these Projects when they are ready to resume backing up.

<figure><img src="https://3704730939-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4lSQNVI3DZ15V7kjkMCA%2Fuploads%2FHHXk4xYrqhcQZACJgEBr%2FScreenshot%202025-03-06%20at%2011.45.46%E2%80%AFAM.png?alt=media&#x26;token=e1a40e55-f791-484c-87cd-93e7b2b7fdc0" alt=""><figcaption><p>The "Not Backing Up" label is shown on a Project card when a Project is not associated to a scheduled job (including the sitewide backup schedule, if applicable).</p></figcaption></figure>

## File Lists

File Lists are explained in the [File Lists](https://docs.copia.io/docs/devicelink/sitesandagents/sites/file-lists) sub-section of this topic.

## Deleting a Site

To delete a Site, navigate to the *Settings* tab for a given Site and click on the *Delete Site* section.

<figure><img src="https://3704730939-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4lSQNVI3DZ15V7kjkMCA%2Fuploads%2FNpPKDbNYYONPo1woaaW8%2FWebApp_SiteSettings_DeleteSite.png?alt=media&#x26;token=039bdf52-389b-45dd-acd8-227714216b73" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Only Owners can delete a Site. Check out [this section](https://docs.copia.io/docs/devicelink/administration/permissions-by-account-type) to learn more about permission levels for DeviceLink.
{% endhint %}

Click on the *Delete Site* button and confirm that you want to delete the Site.

<figure><img src="https://3704730939-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4lSQNVI3DZ15V7kjkMCA%2Fuploads%2FwO1uB2oNdZC4JGk2laoZ%2FWebApp_SiteSettings_ConfirmDeleteSite.png?alt=media&#x26;token=255b2dd7-7d06-47c7-8063-3c0fff427997" alt=""><figcaption></figcaption></figure>