> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/server/knowledge-base/how-to-articles/create-server-staging-instance/devolutions-server-staging-checklist.md). # Devolutions Server staging checklist Before deploying a Devolutions Server instance to production, it is recommended to run a few tests to make sure that essential configurations are working properly. We've compiled this checklist to ensure you don't miss anything: * Vaults root folders are correctly configured. * [Logs](https://docs.devolutions.net/server/web-interface/utilities/reports/logs/) are functional. * The [system dashboard](https://docs.devolutions.net/server/web-interface/system/system-dashboard-status/) shows a high security score and the services are up and running. * [Permissions at vault, folder, and/or entry levels](https://docs.devolutions.net/server/web-interface/user-groups-based-security/permissions/) are customized and assigned to users and/or user groups. * Product [licenses](https://docs.devolutions.net/server/web-interface/administration/security-management/licenses/) have been added and assigned to the right users. * [Cache/offline mode](https://docs.devolutions.net/rdm/workspaces/offline-mode/devolutions-server-offline-mode/) is enabled. * [System settings](https://docs.devolutions.net/server/web-interface/administration/configuration/system-settings/) fits your needs, e.g., to determine if users can access user vaults. * [Advanced connection settings](https://docs.devolutions.net/server/web-interface/administration/configuration/server-settings/general/advanced/#features) are verified. * [Authentication](https://docs.devolutions.net/server/web-interface/administration/configuration/server-settings/general/authentication/) methods have been enabled. * [Service accounts](https://docs.devolutions.net/server/kb/knowledge-base/pre-deployment-account-survey/) used by Devolutions Server are validated. * The [SSL/TLS certificate](https://docs.devolutions.net/server/kb/how-to-articles/configure-ssl/#import-certificate-or-create-self-signed-certificate) is valid and trusted. * An [automatic user creation](https://docs.devolutions.net/server/web-interface/administration/configuration/server-settings/general/authentication/office-365/#automatic-user-creation) policy is defined. * Vaults are accessible through the web interface. * [Notification](https://docs.devolutions.net/server/web-interface/administration/security-management/notifications/) policies are defined for specific users and user groups. #### Optional verifications based on configuration **Devolutions Gateway** * Devolutions Gateway is properly [installed and configured](https://docs.devolutions.net/gateway/getting-started/server/server-configuration/). * RDP and SSH session can be launched through the web. * Session recording and monitoring are functional. **PAM module** {% hint style="warning" %} Make sure the PAM accounts and providers used in staging are not the same as the ones used in production. {% endhint %} * The [PAM module](https://docs.devolutions.net/pam/server/) is configured correctly. * [Permissions](https://docs.devolutions.net/pam/server/roles-permissions/) are assigned to users and user groups for PAM entries. * [Password resets](https://docs.devolutions.net/pam/server/getting-started/reset-pam-account-passwords/) are working. * The [checkout request](https://docs.devolutions.net/pam/server/checkout-process/request-checkout/) and [check-out/check-in](https://docs.devolutions.net/pam/concepts/checkout-checkin/) processes are operational. * [Conditional access policies](https://docs.devolutions.net/server/web-interface/administration/configuration/server-settings/security/conditional-access-policies/) have been defined. * [GeoIP security](https://docs.devolutions.net/server/web-interface/administration/configuration/server-settings/security/geoip-security/) is enabled. * [Email](https://docs.devolutions.net/server/web-interface/administration/configuration/server-settings/general/email/) integration is completed. * [IP and auto-lock settings](https://docs.devolutions.net/server/web-interface/administration/configuration/server-settings/security/) are configured. * The [documentation](https://docs.devolutions.net/server/web-interface/vault/entries/entry-section/documentation/) feature for entries works. * The [entry](https://docs.devolutions.net/server/web-interface/administration/templates/entry-templates/) and [password](https://docs.devolutions.net/server/web-interface/administration/templates/password-templates/) templates function as intended. * Files can be [attached](https://docs.devolutions.net/server/web-interface/vault/entries/entry-section/attachments/) to entries. * The [backup](https://docs.devolutions.net/server/web-interface/administration/backup/backup-manager/) configuration is valid. * [Clean up logs](https://docs.devolutions.net/server/web-interface/administration/logs/cleanup-logs/) allows archiving and deleting logs properly. * [Notification preferences](https://docs.devolutions.net/server/web-interface/account-menu/notifications-preferences/) have been defined. * [Applications identities](https://docs.devolutions.net/server/web-interface/administration/security-management/applications/) can be created and modified. Applications can communicate with Devolutions Server seamlessly. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.devolutions.net/server/knowledge-base/how-to-articles/create-server-staging-instance/devolutions-server-staging-checklist.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.