Service Desk & Project Sync — Setup Guide

Install once, configure in Settings, and you're live. Your team signs in with GitHub; customers sign in with email, Google, or GitHub.

Open your Service Desk →

Just installed? Open your portal

Your Service Desk is live at desk.woden-ai.com — sign in with the GitHub account that installed the app and you become the first admin. This is where you and your customers will work, so bookmark it.

1. Install (if you haven't already)

Not installed yet? Install on GitHub and choose the repositories it can access, then head to desk.woden-ai.com and sign in with the GitHub account that installed it.

2. Configure in Settings

Work through Settings in this order:

  1. Branding & portal URL — display name, logo initials, and your personalised URL slug (e.g. /acme/portal).
  2. Estimation unit — hours, days, or story points (drives the dashboard's delivery metrics).
  3. Team — invite admins and agents by GitHub login; scope agents to service desk and/or development.
  4. Projects — classify each GitHub Project as service desk and/or development, pick the desk destination project, and on development boards mark the Done and Active Status columns so delivery reporting (throughput, cycle time, estimate split) is accurate.
  5. Repositories — choose which connected repos are in scope.
  6. Knowledge base & Release notes — publish markdown from a repo (pick files or auto-publish a folder).
  7. Intake form — build the customer ticket form and map select options to GitHub labels.
  8. End users — invite customers by email.
  9. SLA policy — first-response and resolution targets, business hours, and the label→priority map.

3. Invite & test

Invite your team by GitHub login, and share the personalised sign-in link with your customers (/<your-slug>/login/support). Raise a live test ticket and confirm it lands in the right repository, project, and board column.

Customer sign-in

Customers sign in with email/password (via Microsoft Entra External ID), Google, or GitHub, and are matched to their invited email — no GitHub account required for the local/social options. Authentication is handled by Azure Static Web Apps with Entra External ID as the customer identity provider; configure each provider's client id/secret in your Static Web App settings.

Plans

Every feature — including custom branding — is available on every plan. Paid tiers differ only by the limits.

PlanPriceProjectsReposAdminsCustomersNotes
Free$01125Custom branding included
Pro$15/mo22525
Unlimited$50/moLocal & Microsoft sign-in (soon)
Advanced$150/mo+ Azure SSO, AI & automation (soon)