Ctrlk
HomePricingBlogContactSign In
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Account Settings

Configure default backup settings for your repositories in Cloudback, including timezone, schedules, storage options, and repository naming patterns.

The Account Settings page allows you to configure default backup settings for repositories linked to your connected accounts across all supported platforms.

Default Configuration

When you connect a new account or add new repositories, Cloudback applies these defaults:

  • Schedule: Daily automated backups

  • Storage: Cloudback Managed Storage

  • Retention: 30-day retention policy

  • Notifications: Daily email summary for failed backups

You can customize all of these per account or per repository.

How to Configure Account Settings

To access and modify account settings, navigate to the Account Settings page from the sidebar. Use the account selector at the top of the page to switch between your connected platform accounts - each account is shown with its platform badge and avatar.

Here, you can set the default backup schedule, storage location, retention policy, and other settings for all repositories associated with the selected account. The settings also affect new repositories and new linked accounts added in the future.

Account Settings

Available Settings

All settings in the Account Settings page are applied to the selected account. The timezone is applied to all existing repositories and new ones. The other settings will be applied to all new repositories of the account selected above. If you want to apply settings to already existing repositories, use Bulk Operations.

You can configure the following settings:

Timezone

  • Determines the timezone used for scheduling backups.

  • The selected timezone applies to all existing repositories and new ones added under the account.

Default Schedule

  • Sets the default backup schedule for new repositories.

  • Options include predefined schedules such as Daily at 1 PM, and schedules created by the user. For more information, see Backup Schedules.

Default Storage

  • Specifies the default storage location for backup archives for new repositories.

  • You can choose Cloudback Managed Storage or a custom storage created by the user.

Default Retention Policy

  • Defines how long backup archives of new repositories are retained before being deleted. For more information, see Backup Retention Policy.

  • Example: Last 30 days.

Archived Repository Handling

GitHub only. Determines how archived repositories are treated in Cloudback.

  • Options:

    • Hide from dashboard and skip backup (default).

    • Display on dashboard and backup.

This setting is only available for GitHub accounts. Other platforms do not have this option.

Auto-Enabling New Repositories

New repositories are automatically enabled for backup across all supported platforms, as long as the subscription plan has available slots. If the plan limit has been reached, newly discovered items remain disabled until you upgrade or free up a slot. For Azure DevOps, GitLab, and Linear accounts, all newly discovered items are automatically enabled without pattern filtering.

GitHub accounts additionally support wildcard pattern filtering, allowing you to control which new repositories are automatically enabled based on naming patterns.

Repository name pattern accepts wildcard characters and a comma character to join multiple queries.

Wildcard characters:

  • * - zero or more characters

  • ? - exactly one character

  • , - specify multiple queries separated by a comma

Examples:

Considering the selected account has 4 repositories awesome, awesome-repos, book and static-website-example, the given patterns will match the following repositories:

  • * - matches all repositories

  • awe* - matches awesome and awesome-repos

  • awe*,book - matches awesome, awesome-repos and book

  • *b* - matches book and static-website-example

Backup Encryption

  • Specifies the default encryption provider used when creating backup archives for new repositories.

  • The dropdown lists all encryption providers you have access to:

    • Secure Random Key (built-in) - Cloudback generates and manages a unique random password for each backup. You don't need to provide anything extra during restore or download.

    • RSA Lockbox (customer-managed) - You provide your own RSA public key. During restore or download, you'll need to paste your private key so Cloudback can decrypt the backup password.

    • Additional provider types (External KMS, External Password API) will be added in future releases.

  • To create a custom encryption key, see Encryption Overview.

  • For details on how archive encryption works, see Password-Protected Archives.

Note: Changing the encryption provider only affects new backups. Existing backups retain the encryption provider that was active when they were created.

Danger Zone

The Danger Zone section at the bottom of the Account Settings page contains destructive actions.

To remove a connected account from Cloudback:

  1. Navigate to the Account Settings page for the account you want to remove

  2. Scroll to the Danger Zone section

  3. Click Delete Cloudback Account

  4. Confirm the deletion in the confirmation dialog

Warning: Deleting an account is a permanent, destructive operation. This will permanently remove the account and all associated backup archives. This action cannot be undone.

Learn More

PreviousBackup Retention PolicyNextBulk Operations

Last updated

Was this helpful?