Settings

Company Settings

This article explains the basic options available in the Company tab of the Nymble settings page.

Overview

The Company settings tab allows you to configure your organization's basic information and address details. These details are essential for proper system operation and may be used in various parts of the application, such as reports and documents.

Available Settings

Company Information

• Company Name: Your organization's official name as it should appear throughout the system
• Address: Your company's primary business address
• Country: Select your company's country of operation
• State/Region: Select your company's state or region
• City: Your company's city of operation
• Postal Code: Your company's postal/zip code

Best Practices

1. Keep your company information up to date, as it may be used in official documents and communications
2. Ensure the address is formatted according to your country's postal standards
3. Double-check all fields for accuracy before saving changes

How to Save Changes

After updating any field in the Company settings:

1. Review your changes for accuracy
2. Click the "Save changes" button at the bottom of the form
3. Wait for the confirmation that your changes have been saved successfully

Finance Settings

This article explains the basic options available in the Finance tab of the Nymble settings page.

Overview

The Finance settings tab allows you to configure email addresses for accounts payable and accounts receivable communications. These settings are crucial for managing financial communications and ensuring that billing-related correspondence reaches the appropriate departments.

Available Settings

Email Addresses

• Accounts Payable Email Address: The email address where vendor invoices and payment-related communications should be sent
• Accounts Receivable Email Address: The email address used for sending invoices and receiving payment-related communications from clients

Best Practices

1. Use department-specific email addresses (e.g., [email protected], [email protected]) rather than individual email addresses
2. Ensure the email addresses are monitored regularly
3. Consider setting up email forwarding rules to relevant team members
4. Verify email addresses are correctly spelled before saving

How to Save Changes

After updating any email address in the Finance settings:

1. Double-check the email addresses for accuracy
2. Click the "Save changes" button at the bottom of the form
3. Verify that the changes have been saved successfully

Important Notes

• These email addresses may be used in automated communications
• Make sure to update these settings if your financial contact information changes
• Consider notifying vendors and clients when changing these email addresses

Timesheet Settings

This article explains the basic options available in the Timesheets tab of the Nymble settings page.

Overview

The Timesheet settings tab allows you to configure how timesheets function in your organization, including when weeks start, when timesheets are due, when they get locked, and what attestation statement users must acknowledge when submitting timesheets.

Available Settings

Week Configuration

• Week Starts On: Define which day of the week your timesheet period begins (default: Sunday)

Timing Settings

• Timesheets Due Offset:
  • Specifies how many hours before or after the end of the week timesheets should be due
  • Example: For timesheets due at 5pm on Friday with weeks ending on Saturday, enter -32 hours
  • Current setting: 0 hours
• Timesheets Lockout Offset:
  • Determines how many hours after the week ends that timesheets become locked
  • Example: For a two-week lockout period, enter 336 hours (14 days × 24 hours)
  • Current setting: 336 hours

Attestation Configuration

• Attestation Statement:
  • Customizable text that users must acknowledge when submitting timesheets
  • Rich text editor available for formatting (bold, italic, underline)
  • Can include bullet points and numbered lists
  • Default statement emphasizes:
    • Hours must be defendable
    • Work reported should withstand scrutiny
    • Importance of maintaining service integrity
    • Building trust with clients and colleagues

Best Practices

1. Set due dates that align with your organization's billing cycles
2. Choose lockout periods that allow sufficient time for corrections while maintaining timely submissions
3. Keep the attestation statement clear, professional, and aligned with your company's policies
4. Consider your team's time zones when setting due dates

How to Save Changes

After updating any settings:

1. Review all changes for accuracy
2. Click the "Save changes" button at the bottom of the form
3. Verify that the changes have been saved successfully

Important Notes

• Changes to week start days may affect reporting and analytics
• Due and lockout offsets are calculated from midnight on the last day of the week
• The attestation statement appears each time a user submits their timesheet

Availability Settings

This article explains the basic options available in the Availability tab of the Nymble settings page.

Overview

The Availability settings tab allows you to configure how users report their availability during timesheet submission. These settings help ensure accurate project assignments and resource allocation by collecting standardized availability information from team members.

Available Settings

Form Configuration

• Enable Availability Form: Toggle to enable/disable the availability form during timesheet submission
  • When enabled, users will be prompted to update their availability when submitting timesheets
  • When disabled, availability updates must be made through other means

Message Configuration

• Availability Preamble:
  • Customizable text shown to users when updating their availability
  • Includes dynamic placeholder {{timezone}} which displays the user's current timezone
  • Default text explains:
    • Importance of keeping availability up to date
    • How availability affects project assignments
    • Standard week vs. specific week availability
    • Using Time Off feature for complete unavailability
    • Current timezone context
• Availability Summary:
  • Customizable text shown after availability is entered
  • Includes dynamic placeholder {{total}} which shows calculated weekly hours
  • Allows users to specify reduced weekly maximum hours if needed
  • Default text summarizes total available hours per week

Best Practices

1. Keep the preamble clear and concise while emphasizing the importance of accurate availability
2. Explain the difference between standard weekly availability and specific time-off requests
3. Ensure users understand how to interpret and adjust their total available hours
4. Consider including guidelines for minimum expected availability in the preamble

How to Save Changes

After updating any settings:

1. Review the preamble and summary text for clarity
2. Verify that placeholders ({{timezone}} and {{total}}) are preserved
3. Click the "Save changes" button at the bottom of the form
4. Test the form during timesheet submission to ensure proper display

Important Notes

• The {{timezone}} placeholder automatically updates based on each user's settings
• The {{total}} placeholder calculates hours based on the availability grid input
• Changes to these settings affect all users during timesheet submission
• Consider multi-timezone teams when writing availability instructions

Project Health Settings

This article explains the basic options available in the Project Health tab of the Nymble settings page.

Overview

The Project Health settings tab allows you to configure how project health is calculated and displayed across your organization. These settings help maintain consistent project monitoring and early warning systems for potential issues.

Available Settings

Health Calculation Settings

• Health Check Period:
  • Number of days to look back when calculating project health
  • Affects trending calculations and historical data analysis
  • Default: 30 days

Threshold Configuration

• Budget Warning Threshold:
  • Percentage of budget consumed that triggers a warning status
  • Example: 75% means projects will show warnings when 75% of budget is used
  • Helps prevent budget overruns through early notification
• Budget Critical Threshold:
  • Percentage of budget consumed that triggers a critical status
  • Example: 90% means projects will show critical status when 90% of budget is used
  • Enables immediate action on projects approaching budget limits

Schedule Settings

• Schedule Warning Threshold:
  • Percentage of schedule variance that triggers a warning status
  • Example: 10% means projects running 10% behind schedule will show warnings
  • Helps identify timeline risks early
• Schedule Critical Threshold:
  • Percentage of schedule variance that triggers a critical status
  • Example: 20% means projects running 20% behind schedule will show critical status
  • Enables proactive schedule management

Best Practices

1. Set warning thresholds to allow enough time for corrective action
2. Align critical thresholds with organizational risk tolerance
3. Consider project complexity when setting schedule variance thresholds
4. Review and adjust thresholds periodically based on historical data
5. Document threshold changes and their rationale

How to Save Changes

After updating any settings:

1. Review all threshold values for accuracy
2. Consider the impact on existing projects
3. Click the "Save changes" button at the bottom of the form
4. Verify that the changes have been saved successfully

Important Notes

• Changes to thresholds affect all projects immediately
• Historical health calculations use the look-back period setting
• Warning and critical thresholds should have sufficient gap between them
• Consider notification settings when adjusting thresholds
• Project managers can override health status with proper justification

System Settings

This article explains the basic options available in the System tab of the Nymble settings page.

Overview

The System settings tab provides configuration options for core system functionality, including debugging, caching, and performance settings. These settings affect the overall behavior and performance of your Nymble installation.

Available Settings

Debug Settings

• Debug Mode:
  • Toggle to enable/disable detailed error messages and debugging information
  • When enabled, shows full stack traces and query information
  • Should be disabled in production environments
  • Useful for troubleshooting issues in development/staging

Cache Configuration

• Cache Duration:
  • Time (in minutes) that cached data remains valid
  • Affects system performance and resource usage
  • Default: 60 minutes
  • Lower values provide more frequent updates but increase server load

Performance Settings

• Pagination Limit:
  • Maximum number of items displayed per page in lists and tables
  • Affects loading times and memory usage
  • Default: 25 items
  • Consider browser performance when adjusting

Logging Configuration

• Log Level:
  • Determines the detail level of system logs
  • Options: Emergency, Alert, Critical, Error, Warning, Notice, Info, Debug
  • Default: Error
  • Higher levels include more detailed information but use more storage

Session Settings

• Session Lifetime:
  • Duration (in minutes) before user sessions expire
  • Affects security and user experience
  • Default: 120 minutes
  • Balance security needs with user convenience

Best Practices

1. Keep Debug Mode disabled in production environments
2. Adjust cache duration based on data update frequency
3. Monitor log storage when using detailed log levels
4. Set appropriate session timeouts for security compliance
5. Test performance impact of pagination changes

How to Save Changes

After updating any settings:

1. Review changes carefully, especially security-related settings
2. Consider impact on system performance
3. Click the "Save changes" button at the bottom of the form
4. Test system functionality after significant changes

Important Notes

• Debug Mode significantly affects system performance
• Cache settings impact server resource usage
• Log levels affect storage requirements
• Session settings may have security implications
• Some changes may require system restart
• Consider regulatory requirements when configuring security settings

Integration Settings

This article explains the basic options available in the Integrations tab of the Nymble settings page.

Overview

The Integrations settings tab allows you to configure connections with external services and third-party applications. These settings enable seamless data flow and functionality extensions through various integrations.

Available Settings

Authentication Settings

• API Keys:
  • Manage API keys for external service authentication
  • Generate new keys for integration partners
  • Revoke existing keys for security
  • View key usage statistics

Service Connections

• Webhook Configuration:
  • Define webhook endpoints for event notifications
  • Configure retry policies for failed deliveries
  • Set security headers and authentication
  • Test webhook connectivity

Email Integration

• SMTP Settings:
  • Configure email server connection details
  • Set default "From" address
  • Test email connectivity
  • Configure email encryption settings

Calendar Integration

• Calendar Sync Settings:
  • Configure calendar service connections
  • Set sync frequency
  • Choose events to sync
  • Map calendar categories

File Storage

• Storage Provider Settings:
  • Configure cloud storage connections
  • Set file retention policies
  • Configure backup settings
  • Manage storage quotas

Best Practices

1. Regularly rotate API keys for security
2. Test webhook endpoints after configuration
3. Monitor integration health and error rates
4. Document integration dependencies
5. Maintain backup communication channels
6. Regular testing of email connectivity

How to Save Changes

After updating any settings:

1. Test the integration connection
2. Verify data flow is working
3. Click the "Save changes" button
4. Monitor for any integration errors

Important Notes

• Keep API keys secure and never share them
• Document all integration endpoints
• Monitor webhook delivery success rates
• Maintain updated contact information for service providers
• Regular backups of integration configurations
• Consider rate limits and quotas
• Test in staging environment first