Skip to content

Settings reference

Every control on the Settings page, what it does and when to use it.

Settings holds sign-in, backup storage, encryption, background backups, notifications, PDF branding and updates for this computer. Open it from the bottom of the sidebar.

Choose a section in the list on the left to open it: Sign-in, Services and permissions, Storage and recovery, Background runner, Notifications, PDF branding, Updates, Appearance and About. One section shows at a time, starting with Sign-in. When no tenant on this computer is on Pro or MSP, Notifications and PDF branding carry a Pro badge in the list; both sections still open. Notifications links to the Alerts page in the sidebar, where alerts, channels, change watching and deliveries are set up. On a narrow window the list becomes a row above the section.

Settings apply to this computer only. Other admins who use TenuVault have their own settings.

The Appearance section sets the color theme.

OptionEffect
Use system settingFollows the light or dark mode of Windows or macOS, and switches when it changes. Default.
LightAlways light.
DarkAlways dark.

The Tenants card shows, for each connected tenant, who you are signed in as and where its backups are stored, for example Signed in as admin@contoso.com · Backups: This device (encrypted) or the name of the Azure storage account. Not signed in means TenuVault has no valid sign-in for the tenant.

If no tenant is connected, the card shows No tenants yet. with a link to Set up your first tenant.

ControlWhat it does
Sign in / Sign in againOpens a Microsoft sign-in for the tenant, pre-filled with the account last used. You must sign in to the same tenant; otherwise TenuVault shows You signed in to a different tenant. Sign in with an account from this tenant. Signing in again also rechecks the tenant’s license.
Change storageOpens Backup storage for <tenant>, where you choose between This device, encrypted and Your Azure storage account. For Azure, Save is available once Check access shows Access confirmed.
  1. Select Change storage for the tenant.
  2. Choose the new location. For Azure, choose the Storage account and select Check access until it shows Access confirmed.
  3. Select Save. TenuVault confirms with Backups for <tenant> now go to <location>.

New backups go to the location you choose. Existing backups stay where they are and are only listed while that location is selected. Azure storage needs the Pro or MSP plan. For the options and errors, see Choose where backups are stored.

To add or remove tenants, use Tenants. See Manage tenants.

Shows, for each connected tenant, which services TenuVault backs up and what the tenant’s app registration allows for each one: read permissions for backups and drift detection, write permissions for restores. TenuVault reads this from the sign-in it already has, so the check sends no request to Microsoft and changes nothing. With more than one tenant, an overview at the top lists every tenant; select one to see its details.

ControlWhat it does
Check againGets a new sign-in token and checks again, for example after you granted admin consent to a permission.
Include in backupsTurns an opt-in service, such as Entra Conditional Access, on or off for the tenant. While it is off, backups leave its items out.
Open API permissions in EntraShown when a permission is missing. Opens the tenant’s existing app registration in Entra, where you add the permission and grant admin consent. That needs a Global Administrator, Privileged Role Administrator, Cloud Application Administrator or Application Administrator.
Copy Azure CLI commandsShown when only a service’s restore permission is missing. Copies the commands that add it to the existing app registration and grant admin consent.

Backup logs, Backup Details and the restore wizard link here when a missing permission leaves items out or stops a restore. For the permissions each service needs, see App registration and delegated permissions and Conditional Access backups.

This card applies to tenants that keep backups on this device. Every backup file is encrypted with AES-256-GCM; file names reveal nothing about your policies.

ControlWhat it does
Import backup ZIPImports a backup exported as a ZIP file. TenuVault shows the source tenant, backup ID and SHA-256 hash, and asks you to confirm with Import locally. The snapshots are encrypted on this device. Import never changes Intune. See Backup storage and retention.
FolderShows the current backup folder. Default: Documents/TenuVault Backups.
Change folderChooses another folder, including a network share. Changing the folder does not move existing backups; move the folder’s contents yourself to keep them visible.
Open folderOpens the backup folder in Explorer or Finder, creating it if needed.

After an import, TenuVault shows Imported <backup>. Select this device as storage for tenant <tenant id> to preview and restore it. The archive must be smaller than 128 MiB, and your license must cover the source tenant.

The backup encryption key is protected by your Windows account or macOS Keychain. It encrypts backups on this device. Backups in Azure storage are not encrypted by TenuVault and do not need it, except Azure backups that an earlier TenuVault version encrypted with it.

ControlWhat it does
Key fingerprintIdentifies the current key. The recovery key file name includes it.
Save recovery keySaves the recovery key to a text file, by default Documents/TenuVault recovery key <fingerprint>.txt. The saved bundle includes all previous keys on this device.
Import a recovery keyOpens a field where you paste a recovery key (TVK2. bundle, or a legacy TVK1. key) and select Import.

After you import a key, the imported key encrypts new backups on this device, and backups made with the previous key stay readable. Save a new bundle after importing keys, so your saved recovery key covers every key on this device.

TenuVault reads the backup inventory of each tenant connected on this device that keeps its backups in the folder, exactly as a backup would. When that inventory holds backups this device cannot read, because another installation made them with a different key or the files are damaged, the card and All tenants show This folder has backups this device cannot read, with Import recovery key and Choose another folder. Backups to an affected tenant fail until one of the two is done. See A folder with backups this device cannot read.

When local backup files exist or a tenant uses local storage, Settings and Overview show a recovery key notice if no export is recorded for the current key. Select Go to Save recovery key to reach the export action. The notice disappears after you save the key. It does not block local backups. Starting over deletes the backup encryption key from the active app state. Backups on this device become unreadable unless you exported their recovery key, and so do Azure backups that an earlier TenuVault version encrypted with it. Azure backups made by this version stay readable.

When a restore write to Intune ends without a clear answer (for example a timeout or a dropped connection), TenuVault records it and blocks an identical write until you confirm what happened. This history is where you do that.

ControlWhat it does
Restore history tenantChooses the tenant whose history is shown. Viewing it needs a current sign-in to that tenant, a license that covers it and Intune management access.
Refresh historyReloads the list. If it fails, the previous records stay visible with an error.

Each entry shows the object name, time, state, tenant and the request (method and path). Request payloads and tokens are not stored. Interrupted writes stay blocked across restarts.

StateButtonsUse them when
uncertainConfirm appliedYou checked the target tenant in Intune and the change was made. Enter the object ID in the inline form and choose Save applied ID; a retry reuses it instead of repeating the write.
uncertainConfirm not appliedYou checked in Intune and the change was not made. The next attempt sends the write again.
reconciledCorrect applied IDYou entered the wrong object ID earlier. Edit the recorded ID in the inline form and choose Save applied ID. The next retry reads and verifies the object before any follow-up writes.
reconciledAllow a new operationYou deliberately want to send the same request again, which may create another object. Do not use it while resuming a repair.

The object ID must be a GUID. Invalid IDs and failed requests show an error in the form. After a failed save, focus returns to the input. Cancel or Escape closes the form without saving while no save is in progress. Closing the form returns focus to the record’s recovery button or, if the entry is gone, to Refresh history, including after a successful save.

Always check the target tenant in Intune before you resolve an entry. See What cannot be restored and restore write history.

Automatic backups run while TenuVault is running, in the window or in the menu bar on macOS and the tray on Windows.

ControlWhat it does
Install background launchAdds a LaunchAgent for your user account on macOS or a scheduled task for your user account on Windows. The background runner can reopen TenuVault in the menu bar or tray within five minutes while you are signed in to the computer. It never brings an open TenuVault window to the front.
Remove background launchRemoves the background runner. Your backup schedules stay unchanged.
Retry checkRequests the runner status again after a failed check. Installation stays disabled until a check succeeds.

The state appears beside the install or remove button:

StateMeaning
Checking…TenuVault is checking the background runner status. The install or remove button is disabled.
InstalledThe status check reports that the background runner is installed. This does not confirm that a backup can run.
Not installedThe status check reports that the background runner is not installed.
Unable to checkThe status request failed. Could not check background startup. Try again. stays visible with Retry check until a check succeeds.

While a change is running, the button shows Installing… or Removing… and is disabled.

The background runner only helps while you are signed in to the computer. It does not run while you are signed out, or while the computer is asleep or off, and it does not wake the computer. Backups still need a valid Microsoft sign-in (or a verified Backup Reader for scheduled backups), plan access and available storage. The button is disabled with Available in installed Windows and macOS builds. when TenuVault is not an installed build.

Backups need an awake computer and a signed in session. Locking the screen does not sign you out; closing a laptop lid may put it to sleep.

To stop automatic restarts completely, select Remove background launch and turn off start at login before you quit TenuVault. If you move the app, install the background runner again.

Below the background runner card, the Backup Reader card sets up the optional read-only identity that keeps scheduled backups running when a Conditional Access sign-in frequency policy ends your Microsoft session. It is available on Pro and MSP in the installed Windows and macOS apps, per tenant and per computer. When several tenants are connected, a Tenant selector appears at the top of the card.

Setup cannot be finished in the app alone: an Entra administrator creates the app registration with a script, and for Azure backups an Azure administrator grants the storage role. The card walks through your half in order (Set up the Backup Reader, Save certificate, copy or save the setup script and the request for your administrator, enter the application ID, Verify) and afterwards shows the application ID, the certificate with the thumbprint Entra ID shows, its expiry, the verified permissions and confidence checks (last read test, storage check and last run), with Test now, Renew certificate, Verify again and Remove. The Setup guide link at the top of the card opens the full guide in every state. From 30 days before the certificate expires, the card shows a warning.

See Backup Reader for scheduled backups for who has to do what, the exact permissions, and how these backups differ. For the options that need no application permissions, see Conditional Access and TenuVault.

On macOS, these Settings labels say menu bar. On Windows, they say tray.

OptionDefaultEffect
Start TenuVault in the menu bar/tray when I sign in to this computerOffStarts TenuVault hidden in the menu bar or tray when you sign in.
Keep running in the menu bar/tray when I close the windowOnClosing the window hides TenuVault instead of quitting, so schedules keep running. The first time, a notification says TenuVault is still running. When off, closing the window quits TenuVault on Windows; on macOS, TenuVault keeps running until you quit it.

The menu bar or tray icon menu has Open TenuVault, Back up all tenants now, the next scheduled backup (or No scheduled backups) and Quit TenuVault. When the background runner is installed, a disabled row directly above Quit says Background restart may reopen TenuVault within five minutes. Quit stops the current process, but the runner may reopen it.

Sets how long backups are kept: 7 days, 14 days, 30 days, 60 days, 90 days, 180 days, 365 days or Forever. Default: 30 days. The setting applies to every tenant on this computer.

  • Older backups are deleted after each successful backup. The newest backup is always kept.
  • If a backup is incomplete, no older backups are deleted.
  • A backup that is the newest copy of a type that later backups left out is kept.
  • Community tenants keep 30 days at most, even if you choose a longer period or Forever. Pro and MSP tenants keep what you choose.
  • When every connected tenant is on Community, periods longer than 30 days and Forever are marked Pro and cannot be chosen. If a longer period was saved earlier, Settings shows the saved choice and the 30 days that take effect on Community.

See Backup storage and retention and Schedule backups.

PDF branding puts your company name, logo and colors on every PDF report TenuVault exports: framework comparisons, policy pack assessments, CIS readiness reports and the OpenIntuneBaseline Existing Deployment comparison and Policy Validation reports. A preview of the report cover beside the fields shows the result as you edit.

ControlWhat it does
Company nameRequired. Replaces TenuVault on the cover and in the running footer, and in the document properties of framework, policy pack and CIS reports. Up to 120 characters.
Upload logo / Replace logoAdds a PNG or JPEG of up to 1 MB and at most 2048 by 2048 pixels, shown top left on the cover instead of the TenuVault mark. TenuVault checks the file, removes embedded color profiles, text, EXIF and similar data (keeping only basic color and resolution hints), and stores the logo as a PNG scaled to at most 1200 pixels on its longest side. A wide logo on a transparent background works best. Without a logo the cover shows the company name.
Remove logoRemoves the logo; the cover shows the company name.
Primary colorThe cover band and headings, as #RRGGBB. Choose it with the color picker or type it. Headings use a darker shade when the color is too light to read on white.
Accent colorThe accent bar, eyebrows and chart highlights, as #RRGGBB.
Prepared byAdded to Document control on the cover. Optional.
ClassificationAdded to Document control on the cover, for example Confidential. Optional.
Footer textReplaces the footer on every page. Defaults to the company name. Optional.
Save brandingSaves the branding on this computer, encrypted with the rest of the app state. New PDF exports use it.
Reset to TenuVault designDeletes the saved branding. Reports use the TenuVault design again. Always available, also after a plan ends.

The OpenIntuneBaseline reports print through the app’s built-in Chromium engine, so tenant and policy names in any script, such as Japanese or Cyrillic, print as recorded. Framework, policy pack and CIS reports use a built-in PDF font that prints Western European characters only.

PDF branding needs the Pro or MSP plan. It applies to the reports of tenants on Pro or MSP: TenuVault checks the plan of the report’s tenant every time it generates a PDF, so a report of a Community tenant keeps the TenuVault design even when branding is saved. When no tenant on this computer is on Pro or MSP, the section shows a Pro badge and the fields are disabled; branding saved under an earlier plan is kept but not applied until a tenant is on Pro or MSP again.

Branded reports are fully white label: they carry no TenuVault name or logo. What stays as published is license and attribution text, such as the Elastic License 2.0 notice of the framework mappings, publisher terms (CC BY 4.0, Open Government Licence, NIST) and the OpenIntuneBaseline GPL-3.0 attribution. Tenant data is always printed exactly as recorded: a policy, group or setting value that contains the word TenuVault keeps it. Report notices that name the tool, such as Independent TenuVault configuration comparison, name your company instead, and the OpenIntuneBaseline reports leave out the Generated by row.

For screenshots and a walkthrough of switching from stable to nightly, see Try nightly builds from stable.

ControlWhat it does
Download and install updates automaticallyOn by default. TenuVault checks 15 seconds after start and every 6 hours, downloads updates in the background and installs them when it restarts. Turning it off prevents installation of a pending update.
Get nightly buildsOpt into previews between stable releases. A stable release newer than the latest nightly is offered too. Turn it off to return to the current stable release, even if it is older than the installed nightly.
Check nowChecks immediately. Disabled while automatic updates are off.
Restart and updateAppears when an update has downloaded. Restarts TenuVault and installs it.

While an update downloads and once it is ready, a green Update available label at the bottom of the sidebar installs it too: select it and TenuVault restarts as soon as the download finishes.

The status line shows the current state:

StatusMeaning
Checking for updates…A check is running.
TenuVault is up to date.No newer version on your channel.
Downloading version <version> (<n>%)…An update is downloading.
Version <version> is ready to install.Select Restart and update, or it installs when you next quit.
Could not check for updates: <reason>The check failed, for example because GitHub is blocked. TenuVault keeps working.
Automatic updates are off.You turned automatic updates off.
Your organization manages updates for TenuVault.An administrator turned updates off by policy. The checkbox is locked. See Deploy TenuVault in your organization.

Stable installs follow stable by default. Enable Get nightly builds to receive previews between stable releases, plus any stable release that is newer than the latest nightly. Turn it off to download the current stable release, even if it is older than your installed nightly. Changing channels replaces a pending update and checks the selected channel immediately. See Install and update TenuVault.

ItemShows
VersionTenuVault Desktop <version>
Network summaryWhich services TenuVault talks to: Microsoft for sign-in, Graph and Azure; GitHub for the Open Intune Baseline catalog and updates; tenuvault.com for license checks and for feedback you choose to send. No tenant configuration or backup is ever sent to TenuVault, apart from feedback you choose to send: the text you write and, only if you tick it, a screenshot that may show tenant, policy or user names.
LicenseOpens the License page. See Activate and manage your license.
Website and supportOpens tenuvault.com/desktop in your browser.

Hygiene scan findings and health review finding reconciliation are saved together before returning, reducing repeated encryption and disk writes. A failed batch leaves the previous records intact.