Settings
DevOps environments
Add other Azure DevOps environments you manage. Each uses its own Personal Access Token, stored securely (Azure Key Vault) and scoped to your account — tokens are never shown again after saving, only their last 4 characters.
Add an environment
Integrations (optional)
Board vocabulary (advanced)
Calendars
Fold in calendars from your other organizations so they all show in one view. Paste the calendar's ICS feed URL (in Outlook: Settings → Calendar → Shared calendars → Publish a calendar → ICS link; Google: Settings → your calendar → “Secret address in iCal format”). The link is read-only and stored securely (Azure Key Vault), scoped to your account — never shown again after saving.
Add a calendar
Calendar reminders
Get a heads-up before a calendar event starts. Reminders fire while the dashboard is open (including the installed app running in the background). They can't wake a fully-closed app.
Clients
The canonical client list that billing groups by. Techs pick from this list when promoting meetings, so the same client can't sprout different spellings. Adding a client is a governed action — keep this list tidy. Use Import from board once to pull in the clients already in use, then curate.
Move clients out of tags
A card’s client used to be its first tag. This writes that client into the client field instead and removes the tag, so tags go back to being tags. Preview first and read it — anything this can’t decide safely is listed for you rather than guessed at, and a card whose client tag isn’t first is never moved automatically, because that would change what it bills to.
Company links
Shared links shown in the header Company Links menu. Pick or type a folder (a company, a vendor, whatever groups them), add labeled URLs (e.g. “Firewall admin”, “M365 admin”), and Save. Everyone on the team sees the same links.
Add a folder
Connections — credential health
The health of every credential your environments authenticate with — the Azure DevOps token, NinjaOne, CrowdStrike, your Microsoft 365 calendar, and the Anthropic key. A credential that expires or is revoked shows here, and you'll get a notification on the bell the moment one starts failing. Checked automatically; use Re-check now to probe on demand.
Board vocabulary
The work-item type and state names this instance is configured with, checked against what the board actually has. A wrong name fails silently — pickers and the planning board simply come up empty — so anything that doesn't match is called out here along with the setting to change.
People — identity map
Links each person's identity across orgs so the Management dashboard can roll a person's work up everywhere they work. This builds itself: whoever configures an environment is auto-linked. Use this to rename people, merge duplicates, or assign identities seen on a board that couldn't be auto-linked (client-side staff, or a teammate who hasn't added that org). It stores who-is-who only — never another org's card data.
Branding
How this instance presents itself — the name, the images and the brand colours. Changes apply on the next page load; no redeploy needed.
Images
Pick a PNG, JPEG or GIF. Large images are scaled down in the browser before upload, so a full-size logo is fine to choose.
Identity
Brand colours
The colours that carry the brand, for each theme. The surface colours (backgrounds, text, borders) stay in deployed config — they are the ones that make the app unreadable if they go wrong.
Preview
The preview shows the light and dark values you have chosen applied to the shell; the rest of the app follows the same variables.