# Celest Helpdesk Triage security

> Nothing runs outside your tenant.

The package is client-side code inside your SharePoint and Microsoft 365
Copilot. There is no Celest server, connector, secret or database in the path,
so the security boundary is your tenant’s boundary. **Limited preview —
enrolling by conversation.**

## Where it runs

The package runs as the signed-in user with that user’s existing SharePoint
permissions and asks for none of its own. It calls SharePoint’s REST API from
the page; it stores no credential and uses only the short-lived SharePoint token issued
to the signed-in user, as any SPFx solution does; it never runs unattended and
never calls a Celest endpoint. Microsoft 365 Copilot reads the queue the card shows it and
proposes; Microsoft’s controls govern that step.

## What a change needs

A change to a ticket is proposed, then applied only after a person approves it
in the card. The write carries the ticket’s version, so a ticket that changed
underneath is refused and the receipt reads stale. After the write the package
reads the ticket back and records verified, stale, diverged, indeterminate or failed on the run row,
with who decided and when.

## What it never does

- No mail.
- No closing tickets, and no creating tickets during triage; the only tickets it creates are the optional fictional samples.
- No change an operator did not approve, and no “while you are there” changes.
- No approvals delivered through Teams or Agent 365 in this release.
- No data sent to Celest.

## What setup creates, and how to remove it

Three lists, optional sample tickets, the site agent file, the list command and
the site’s main-agent setting, each on your click and each reversible; the main-agent setting comes with the
agent install, when the site had no main agent. The
[privacy notice](https://celest.dev/helpdesk-triage/privacy) lists them and the
[uninstall page](https://celest.dev/helpdesk-triage/uninstall) gives the removal
step for each.

## Reporting a concern

Email [support@celest.dev](mailto:support@celest.dev) with “security” in the
subject and the minimum context needed to route it. Do not send secrets, tokens
or ticket contents; the [support page](https://celest.dev/helpdesk-triage/support) explains what to include.