What it connects to, and what is running today.
Three labels are used on this page and nothing is sold before it runs: what is on every instance, what we configure with you at onboarding, and what is in build and shown at preview stage. If an item matters to a decision, ask us for its current status in writing.
The desk sits in the middle; nothing is duplicated.
Requests come in from wherever people already are, records stay in one place, and anything that needs a credential gets it server-side — never in a page a browser can read.
Connections, and where the secrets live
Integration credentials are issued per integration, held server-side, and never placed in a page, a URL or a download.
Every item, labelled.
Identity & access
Single sign-on (SAML / OIDC) Configured with you at onboarding
Connect your existing directory so people use the account they already have. Entra ID, Google Workspace and Okta are the usual starting points; others are wired up case by case.
Multi-factor authentication Runs on every instance
Enforced for every account, including administrators. There is no bypass role.
Role-based access Runs on every instance
Roles decide what a person can see and do. Access is scoped to the tenant, so the role travels with the person, not with the browser.
Session review & revoke Runs on every instance
Administrators can see active sessions and end one immediately.
Getting requests in
Staff portal Runs on every instance
A branded self-service page per tenant: raise a request, track it, read the knowledge base, reserve equipment.
Email to ticket Configured with you at onboarding
An address people already know. Mail is turned into a ticket with the sender's details, and replies thread back to the requester.
Assistant (text & voice) Preview — in build, shown in a demo
Ask a question in writing or by speaking to it; the assistant answers from your own records and drafts the reply when it cannot.
REST API & webhooks Configured with you at onboarding
Create tickets, read assets and receive change notifications from your own systems. Credentials are issued per integration and never exposed in a page.
Records & assets
CSV import & export Runs on every instance
Bring your existing user, asset and ticket lists in, and take everything out again whenever you want. Your data is yours.
Asset discovery records Configured with you at onboarding
Where you already have a discovery tool, its inventory is reconciled into the asset register rather than typed in twice.
Finance & procurement spreadsheets Runs on every instance
Warranty, purchase date and cost export cleanly for the budget cycle.
Where your team already works
Microsoft Teams Preview — in build, shown in a demo
Notify a channel when a priority ticket lands, and work a summary of a meeting into the knowledge base.
Microsoft 365 & Google Workspace Configured with you at onboarding
Account and licence records are reconciled with the desk so joiners and leavers are complete on both sides.
Copilot / agent access Preview — in build, shown in a demo
A published agent definition so your own assistant can raise and read support requests through a defined, permissioned interface — never a shared password.
Keys stay on the server.
- No credential is placed in a web page, a URL, a download or a public repository.
- Integration credentials are issued per integration and held server-side, injected at run time rather than shipped.
- Anything an integration can do is bounded by a role, so a connection is never more powerful than the person who authorised it.
- Credentials can be revoked without disturbing anything else, and revocation is recorded.
Sign in the way you already do.
- Multi-factor authentication is enforced for every account, including administrators.
- Single sign-on connects to your existing directory — Entra ID, Google Workspace and Okta are the usual starting points.
- Active sessions can be reviewed and ended immediately by an administrator.
- Access is scoped to the tenant, so a role grants what it grants only inside the organisation it belongs to.
What we are building next.
Published so you can plan around it, with a status against every item. Nothing moves to “available” before it runs on a live instance.
In build. The portal is fully responsive on a phone today, and that is what we will show you rather than a promise.
Where records overlap we reconcile them. We do not run a second, parallel copy of your directory or your finance system.
We will never ask for a personal credential. Access is granted through a role, a key we can revoke, or an approval you keep control of.