# Common Configuration Guidelines

## Overview

The images and logos are saved in S3 accounts. To ensure they are accessible in the application, these images should be configured as publicly accessible.

The AWS S3 bucket is used to store and configure logos and global configuration files in the Complaints Management (CMS). Refer to the [AWS S3 Bucket configuration step](https://docs.digit.org/complaints-management/deploy/configure/aws-s3-bucket)s for details.

## Guidelines

### City-Level Logos

* Configure city logos in the tenant.json file for each city.\
  These details are part of the master data and can also be updated through the UI screen.
* Logo images should be uploaded to S3 buckets, and the corresponding image reference path should be used in the configuration. Update the same in the tenant.json file.

### State-Level Logos

* Update the state logo and landing page image paths in the stateinfo.json file.\
  📄 Reference: [common-masters.StateInfo.json](https://github.com/egovernments/Citizen-Complaint-Resolution-System/blob/master/utilities/default-data-handler/src/main/resources/mdmsData/common-masters/common-masters.StateInfo.json)

### Module Mapping Per City

* Use the citymodule.json file to map the set of modules enabled for each city tenant.
* This determines which modules are enabled or disabled at the city level.

### SLA Colour Configuration

* Configure SLA colour codes (used in status indicators, UI highlights, etc.) in:\
  📄[ common-masters.wfSlaConfig.json](https://github.com/egovernments/Citizen-Complaint-Resolution-System/blob/master/utilities/default-data-handler/src/main/resources/mdmsData/common-masters/common-masters.wfSlaConfig.json)

###  ID Format Configuration

* Define custom ID formats for different services/modules in:\
  📄[ common-masters.IdFormat.json](https://github.com/egovernments/Citizen-Complaint-Resolution-System/blob/master/utilities/default-data-handler/src/main/resources/mdmsData/common-masters/common-masters.IdFormat.json)