> For the complete documentation index, see [llms.txt](https://codice.gitbook.io/codice-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://codice.gitbook.io/codice-docs/configuration-guide/application-configuration.md).

# Application Configuration

### Repository User Management

Repository Users configured in Codice are those who have permissions to access and manage Git repositories. These users maintain the necessary credentials (SSH and tokens) to securely interact with different repository providers (GitLab, GitHub, Bitbucket).

**Available Operations:**

* Create new users through "Add User" button
* Edit existing users via action menu
* Delete users via action menu
* View user details

**User Properties:**

* **Username** (required)
* **SSH Key** (required): Private SSH key for repository authentication, you must set the public key in the repository provider to grant access to the user
* **Access Token** (required): Access token for GitLab/GitHub/Bitbucket with read/write repository permissions
* **Description** (optional): Additional user information

<div align="left"><figure><img src="/files/1nh6YG1HkjXS8biZnwCk" alt="" width="563"><figcaption></figcaption></figure></div>

### Repository Management

Repository management allows you to configure the Git repositories in which you want to use Codice.

**Available Operations:**

* Add new repositories through "Add Repository" button
* Edit repository details via action menu
* Delete repositories via action menu
* View repository information

**Repository Properties:**

* **Name** (required): Repository name
* **Repository Type** (required): GitLab/GitHub/Bitbucket
* **Repository ID** (required): Unique identifier
  * Bitbucket: owner/projectId (e.g., "myorg/myproject")
    * Obtained directly from repository URL \
      ![](/files/EzrzNjOcdQhBU3u9G6tW)
  * GitLab: Numeric project ID (e.g., "123456")
    * Visible in project's main page: Settings > General > Project ID \
      ![](/files/To82zbXVULGw5uicMOCp)
  * GitHub: Project ID from API response

    * Can be obtained through API:\ <img src="/files/7IHIWBQ2zXfnHLxWNWt0" alt="" data-size="original">

    ```bash
    curl -H "Authorization: token YOUR_TOKEN" \
         -H "Accept: application/vnd.github.v3+json" \
         https://api.github.com/repos/owner/repo
    ```
* **Owner**: Repository owner
* **SSH URL** (required): SSH clone URL
* **HTTP URL** (required): API URL from repository provider
  * Bitbucket Cloud: <https://api.bitbucket.org>
  * GitLab Cloud: <https://gitlab.com>
  * GitHub: <https://api.github.com>
  * On-premise: Use your local installation base URL (e.g., <https://gitlab.mycompany.com> or whatever you have configured in the repository provider)
* **Associated User** (required): User from users list (with permissions to access and write to the repository)

<div align="left"><figure><img src="/files/30vV3Z7RBZ9Tl1wHNIOn" alt="" width="563"><figcaption></figcaption></figure></div>

### Maven Settings

Maven settings configuration allows you to manage internal dependencies through a custom settings.xml file. This configuration is essential for:

* Accessing private artifact repositories
* Managing internal dependencies
* Authenticating with your organization's Maven repositories

**Key Points:**

* Configure custom Maven settings through XML editor
* The configured user inside the settings.xml file must have proper permissions to access artifact repositories
* Save/Update Maven configuration
* Empty configuration will use system defaults

<div align="left"><figure><img src="/files/sJMJgHjxNRPqbJkYY6k6" alt="" width="563"><figcaption></figcaption></figure></div>
