Skip to content

System Settings Reference

System Settings Reference: Configuration and Administration Guide for rConfig V8

Section titled “System Settings Reference: Configuration and Administration Guide for rConfig V8”

The System Settings interface in rConfig V8 provides centralized access to all configuration, security, maintenance, and administrative functions. This reference guide maps each settings section to its purpose and detailed documentation, enabling administrators to quickly locate configuration areas and understand their impact on system operations.

Organizations can use this reference to navigate system configuration efficiently, understand relationships between settings sections, and maintain consistent administrative practices across deployment lifecycle.

Settings sections for initial system configuration and ongoing assistance.

Purpose: Access to rConfig documentation, video tutorials, community resources, and support contact information.

Key Functions:

  • Links to comprehensive documentation library
  • Video tutorial series for common tasks and troubleshooting
  • Community forum access for peer assistance
  • Support ticket submission for technical assistance
  • Knowledge base articles for frequently asked questions

When to Use: When seeking guidance on system features, troubleshooting issues, or contacting support for assistance with complex problems.

Related Documentation:


Core system configuration, maintenance, and operational settings.

Purpose: General system configuration including application name, timezone, date formats, and default user preferences.

Key Settings:

  • Application name and branding
  • Timezone configuration for timestamps
  • Date and time display formats
  • Default language and localization
  • Session timeout settings
  • User interface preferences

When to Use: During initial deployment to configure organizational standards, or when adjusting system-wide display and behavior preferences.

Related Documentation: PLACEHOLDER - System Configuration Guide

Purpose: Performance tuning settings including memory allocation, queue workers, connection pools, and caching strategies.

Key Settings:

  • PHP memory limits and execution timeouts
  • Queue worker counts and priorities
  • Database connection pool sizing
  • Cache driver configuration
  • Performance monitoring thresholds

When to Use: When optimizing system performance for larger deployments, troubleshooting performance issues, or scaling to accommodate growing device inventories.

Related Documentation:

Purpose: Configuration of automated system backups including schedule, retention policies, and backup destinations.

Key Settings:

  • Backup schedule frequency (daily, weekly, custom)
  • Backup retention policies (how many backups to retain)
  • Backup destination (local storage, FTP server)
  • FTP server configuration for offsite backups
  • Backup notification settings

When to Use: During initial deployment to establish backup strategy, or when modifying backup frequency and retention based on operational requirements.

Related Documentation:

  • Backups - Comprehensive backup configuration and management

Purpose: License key management for activating rConfig features and maintaining subscription status.

Key Functions:

  • Enter or update license key
  • View license status and expiration
  • Display licensed features and limits
  • Subscription renewal information

When to Use: During initial installation to activate license, when upgrading subscription tiers, or when renewing expired licenses.

Related Documentation: PLACEHOLDER - Licensing Guide

Purpose: In-place system upgrade management for updating rConfig to newer versions.

Key Functions:

  • Check for available updates
  • View release notes and change logs
  • Execute upgrade process
  • Rollback procedures if needed
  • Upgrade history and status

When to Use: When new rConfig versions are released with features, improvements, or security updates requiring deployment.

Related Documentation: PLACEHOLDER - Upgrade Procedures Guide

Purpose: Patch management for minor updates, security fixes, and hotfixes between major versions.

Key Functions:

  • Check for available patches
  • View security advisories
  • Apply minor updates and hotfixes
  • Update history tracking

When to Use: When security advisories are published, when minor bugs require patching, or during regular maintenance windows to apply cumulative updates.

Related Documentation: PLACEHOLDER - Patch Management Guide


Authentication, authorization, and security hardening configuration.

Purpose: System security settings including password policies, session management, encryption, and security hardening options.

Key Settings:

  • Password complexity requirements
  • Password expiration and rotation policies
  • Session timeout and concurrent session limits
  • Two-factor authentication (2FA) configuration
  • API rate limiting
  • Security headers and HTTPS enforcement
  • Audit logging configuration

When to Use: During initial deployment to establish security baseline, when implementing compliance requirements, or when hardening system against security threats.

Related Documentation:

  • System Encryption Key - Encryption key management and rotation
  • PLACEHOLDER - Security Best Practices Guide

Purpose: Management of authentication credentials used for connecting to network devices.

Key Functions:

  • Create and manage credential sets
  • Configure SSH passwords and private keys
  • Set Telnet passwords
  • Configure SNMP community strings and v3 credentials
  • Enable password configuration
  • Credential assignment to devices

When to Use: When adding new devices requiring different credentials, rotating device passwords, or organizing credentials by device groups or security zones.

Related Documentation: PLACEHOLDER - Device Credentials Management Guide

Purpose: Integration with LDAP/Active Directory for centralized user authentication and automatic user provisioning.

Key Settings:

  • LDAP server configuration (hostname, port, SSL/TLS)
  • Bind credentials for directory queries
  • Base DN for user searches
  • Authorized group for access control
  • User attribute mapping (username, email, name)
  • Password synchronization for fallback authentication
  • Connection testing tools

When to Use: When integrating rConfig with enterprise directory services for single sign-on, centralizing user management, or eliminating duplicate credential administration.

Related Documentation:


Import, export, migration, and data lifecycle management.

Purpose: Bulk data import and export functionality for devices, configurations, policies, and system data.

Key Functions:

  • CSV import for bulk device addition
  • Configuration export for backup or analysis
  • Policy definition export/import
  • Compliance results export
  • System configuration export

When to Use: When initially populating device inventory, migrating data between rConfig instances, creating data backups, or exporting data for external analysis.

Related Documentation: PLACEHOLDER - Import/Export Guide

Purpose: Migration tools for upgrading from previous rConfig versions or moving between deployments.

Key Functions:

  • Database migration from older versions
  • Configuration file migration
  • User account migration
  • Policy and compliance data migration
  • Integration configuration migration

When to Use: When upgrading from rConfig V6 or V7 to V8, migrating to new infrastructure, or consolidating multiple rConfig instances.

Related Documentation: PLACEHOLDER - Migration Guide

Purpose: Permanent deletion of old data to manage database size and comply with data retention policies.

Key Settings:

  • Configuration retention policies (keep configurations for X days/months)
  • Compliance result retention
  • Log retention policies
  • Archived data purging
  • Purge scheduling and automation

When to Use: When implementing data retention policies, managing database growth, complying with data privacy regulations, or reclaiming storage capacity.

Related Documentation: PLACEHOLDER - Data Retention and Purge Guide


Logging, monitoring, and diagnostic configuration.

Purpose: Configuration of logging levels, debug modes, and diagnostic tools for troubleshooting.

Key Settings:

  • Log level configuration (emergency, alert, critical, error, warning, notice, info, debug)
  • Debug mode enabling for verbose output
  • Log file rotation settings
  • Performance profiling tools
  • Query logging for database optimization

When to Use: When troubleshooting system issues, investigating performance problems, or gathering detailed diagnostic information for support requests.

Related Documentation:

Purpose: Access to database-driven application event logs for operational monitoring and troubleshooting.

Key Functions:

  • View and filter application events
  • Search log descriptions by keyword
  • Filter by severity level
  • Export logs for external analysis
  • Configure log archival policies

When to Use: When investigating device connection issues, reviewing user activity, monitoring scheduled task execution, or troubleshooting application-level errors.

Related Documentation:

Purpose: Management and monitoring of scheduled background tasks including configuration downloads, compliance checks, and maintenance operations.

Key Functions:

  • View task execution history
  • Monitor task success/failure rates
  • Configure task schedules
  • Enable/disable tasks
  • Task performance metrics

When to Use: When reviewing task execution status, troubleshooting scheduled task failures, or optimizing task scheduling for performance.

Related Documentation:


API access and developer resources for integrations and automation.

Purpose: Configuration and management of REST API access including authentication tokens, rate limiting, and endpoint documentation.

Key Functions:

  • Generate API authentication tokens
  • Configure API rate limits
  • View API endpoint documentation
  • Test API endpoints
  • Monitor API usage and statistics
  • Revoke compromised tokens

When to Use: When integrating rConfig with external systems, automating operations via API, or developing custom applications leveraging rConfig functionality.

Related Documentation: PLACEHOLDER - REST API Documentation

Purpose: Developer resources, tools, and utilities for extending rConfig or building integrations.

Key Resources:

  • API schema documentation
  • Webhook configuration
  • Custom integration examples
  • Developer SDK and libraries
  • Code samples and tutorials

When to Use: When building custom integrations, developing automation scripts, or extending rConfig functionality for specific organizational requirements.

Related Documentation: PLACEHOLDER - Developer Guide


System information and version details.

Purpose: System information display including version, license status, system health, and credits.

Information Displayed:

  • rConfig version and build information
  • License status and expiration
  • System health metrics (uptime, resource usage)
  • Installed modules and features
  • Credits and open source licenses
  • Support contact information

When to Use: When verifying system version for support requests, checking license status, reviewing system health at a glance, or accessing support contact information.

Related Documentation: PLACEHOLDER - About rConfig


  1. Log in to rConfig with an account having Admin role
  2. Navigate to Settings from the main navigation menu (typically gear icon)
  3. Settings sections are organized by category in the left sidebar
  4. Click any section to view and modify its configuration

Many System Settings sections include search functionality:

  • Use search fields to quickly locate specific settings
  • Search operates on setting names, descriptions, and values
  • Filters narrow results by category or status

Document changes: Before modifying settings, document current values and business justification for changes. This aids troubleshooting and audit compliance.

Test in non-production: When possible, test setting changes in development or staging environments before applying to production systems.

One change at a time: Modify one setting at a time to clearly identify impact of each change. Multiple simultaneous changes complicate troubleshooting.

Review after updates: After rConfig version updates, review System Settings to identify new options or deprecated settings requiring attention.

Backup before major changes: Create system backup before making significant configuration changes enabling rapid rollback if issues arise.

Initial deployment configuration:

  1. System → Configure application name, timezone, defaults
  2. Security → Establish password policies, session timeouts
  3. Backup Settings → Configure automated backups
  4. LDAP Setup → Integrate with directory services (if applicable)
  5. Logging & Debugging → Set appropriate log levels

Regular maintenance review (quarterly):

  1. Security → Review and rotate credentials
  2. Backup Settings → Verify backups executing successfully
  3. Data Purge → Execute retention policy enforcement
  4. System Optimization → Review performance metrics and adjust
  5. About → Check for available updates

Troubleshooting workflow:

  1. Application Logs → Review recent errors and warnings
  2. Logging & Debugging → Temporarily increase log verbosity
  3. Scheduled Tasks → Check task execution history
  4. Help & Support → Access documentation and support resources

The System Settings interface provides centralized access to all rConfig V8 configuration, security, maintenance, and administrative functions. This reference guide maps settings sections to their purposes and detailed documentation, enabling efficient navigation and consistent administrative practices.

Key takeaways for effective settings management:

  • Settings are organized by functional area - System Management, Security & Access, Data Management, Monitoring & Debugging, Developer Tools
  • Many sections have dedicated documentation - Follow links to comprehensive guides for detailed implementation procedures
  • Changes require Admin role - Most System Settings sections are restricted to users with administrator privileges
  • Document configuration changes - Maintain records of what changed, why, and when for troubleshooting and compliance
  • Test before production - Validate setting changes in non-production environments when possible

Regular review of System Settings ensures configuration remains aligned with organizational standards, security requirements, and operational needs as deployments evolve and scale. Use this reference as a navigation tool for locating specific configuration areas and accessing detailed implementation documentation.