34.2.7. Configuration repository administration
To administer the configuration repository, use a special window called up by the menu item Main menu ‑ Configuration ‑ Configuration repository ‑ Repository administration.
A window is displayed (see fig. 664).
The Users tab contains the user list configuration developers management controls (hereinafter in this chapter referred to as users). All users can change their own settings (username, password), except for changing rights. Bold font identifies those users who are currently connected to the repository. In fig. 664, the user is Administrator.
IMPORTANT! Adding, deleting, and changing rights are available only to users with administrative rights.
The Connections tab displays the list of users connected to the repository.

Fig. 665. Connected users
To disconnect any of the specified users that are not currently working with the repository, click Disable.
IMPORTANT! The Disable button is available to users with administrative rights.
On the Unlock tab, objects for the specified user are unlocked.

Fig. 666. Unlocking objects
At the same time, the user who locked the objects loses the ability to store changes to these objects in the repository.
IMPORTANT! This button is available to users with administrative rights.
The Other tab contains the settings that control the operation of the repository.

Fig. 667. Repository parameters
The group of the Global cache of configuration versions parameters is used to set the size of the global cache of configuration versions. The cache clearing algorithm is the same as the versions local cache clearing algorithm. The Clear cache button results in a full cache clear.
To control the global version cache settings, use the cfgrepo.conf file.
The group of settings Repository compatibility mode controls the repository format and the way it interacts with the repository server.
The following table shows which system versions can work with the repository with one or another compatibility mode set:
Compatibility mode |
Implemented in version |
Can work |
Version 8.3.2 and lower: |
8.3.3 |
Any version |
Version 8.3.3 ‑ 8.3.5 |
8.3.6 |
Version 8.3.3 and higher: |
Do not use |
8.3.3 and higher |
If the Compatibility mode property is set to Version 8.3.2 and lower, then any versions of 1C:Enterprise can work with the repository. If this property is set to Version 8.3.3 ‑8.3.5 and above (including Not to use), then after clicking the Install button, the repository will be converted to an optimized format. After optimization, working with the repository will be faster (including when using the repository server). Compatibility mode can be changed by a user with administrative rights only.
IMPORTANT! Converting repository might take some time.
If necessary, you can convert the configuration repository back to a format appropriate for use by any versions of 1C:Enterprise. To do this, set the Compatibility Mode property to Version 8.3.2 and lower and press the Install button. In addition, you may need to perform the conversion of the repository file itself. Such an operation may be required if the configuration repository was created in 1C:Enterprise version 8.3.10 and higher. For conversion, you must use the cnvdbfl utility program.
For the new configuration repository, the Compatibility mode property is set to Not to use, and the repository database file is created in the version 8.3.8 format.
The Repository data optimization group allows you to optimize repository that is not in compatibility mode with version 8.3.2. As a result of optimization, the speed of work with the repository will be increased. Optimization should be performed only after the system has prompted to do this.
For a user with administrative rights, a recommendation to perform optimization may be included after an operation with the repository (adding objects, rolling back versions, merging versions). For this purpose, the Suggest optimization after the operations with the repository check box is intended on the Other tab of the repository administration dialog box. In this case, after completion of the operation with the repository, the user may be shown the dialog box:

Fig. 668. Suggestion to optimize repository
If the user (repository administrator) refuses to perform optimization immediately after the recommendation appears, then optimization can be performed later. In this case, go to the repository administration dialog box and click the Optimize button on the Others tab. The button should be pressed if the recommendation to perform optimization is displayed to the right of it. Repository optimization might take some time.

Fig. 669. Optimization is recommended
During the optimization, it is not recommended to work with repository.
Optimization can also be performed using the command line parameter of Designer start /ConfigurationRepositoryOptimizeData.
To configure the local repository data settings, use the dialog box, which is accessible via Main menu ‑ Configuration ‑ Configuration repository ‑ Local repository data usage settings.

Fig. 670. Local repository data usage setting
Characteristics of the local version cache is specified in this dialog box, and you can also perform optimization of the repository containing the information about development objects.
A local cache is generated when the configuration repository is located on a network drive or is operated using the repository server. The Directory property is used to specify a directory on the local file system where the cache will be located. By default, the cache is located in the directory:
- On Windows: %APPDATA%\1C\1Cv8\<Infobase UUID>\cfgrepo\cache.
- On Linux: ~/.1cv8/1C/1cv8/<Infobase UUID>/cfgrepo/cache.
The Maximum size value determines the size of the local cache in megabytes. The default value is 500 Mb. If during operation the local cache size exceeds the set size, the oldest versions of 50% of the cache size will be automatically deleted. The Clear cache button causes complete clearing of the local cache.
To control the local version cache settings, use the cfgrepo.conf file.