> ## Documentation Index
> Fetch the complete documentation index at: https://docs.photon.codes/docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Use Stable documentation by default. Honor an explicit Beta request or a URL under /docs/beta/. If the requested version conflicts with the installed CLI package or API origin, clarify the target before writing integration code.
> Pages under /docs/beta/ document Beta; other product pages document Stable. Keep the CLI package, commands, API origin, and credentials within the selected version. State the documentation version in your answer.
> For MCP search, always pass version: Stable or version: Beta. Unfiltered search mixes both versions. For filesystem reads, keep Beta queries under /beta/ and exclude /beta/ from Stable queries; discover paths before reading them.
> The public docs base is https://photon.codes/docs. Convert MCP page paths to public URLs under that base, preserving /beta/ when present. Read https://photon.codes/docs/skill.md for version selection and https://photon.codes/docs/llms.txt for the version indexes.

# Photon support access

> How Photon support can sign in as an account in your organization to troubleshoot a problem, and what that session can do.

> [!WARNING]
>
> **Beta is a preview.** The Beta (2.0) platform does not have all the features
> of [Stable](https://docs.photon.codes/docs/spectrum-ts/introduction.md) yet. For example, iMessage on Beta
> supports only text and images, so tapbacks, polls, message effects, and voice
> notes are [only on Stable](https://docs.photon.codes/docs/spectrum-ts/providers/imessage/messaging-features.md)
> for now. Use Stable for production agents, and confirm that Beta supports the
> features you need before you buy a plan.

Photon support can sign in to the Dashboard as a specific account in your
organization to reproduce and troubleshoot a problem. This page explains how a
support session works and what it can do.

## How a support session works

Support sessions are started through WorkOS, the identity provider Photon uses
for sign-in.

* **One account.** A session signs in as one existing account. It doesn't
  create a user or add anyone to your organization.
* **A recorded reason.** The staff member must enter a reason before the session
  starts. WorkOS records the reason with the session.
* **60 minutes at most.** The session ends automatically after 60 minutes. Staff
  can end it sooner by signing out.
* **No more access than the account.** The session has exactly that account's
  role and permissions, so it can't do anything the account can't.
* **Attributed to the staff member.** Every request in the session carries the
  staff member's identity alongside the account's.
* **Clearly marked.** While the session lasts, the staff member's Dashboard
  shows a banner on every page that names the account they're signed in as.

## What a session can see and change

A support session sees what that account sees in the Dashboard. Photon shows
secrets such as API key secrets and webhook signing secrets only when they're
created or rotated, so a support session can't read your existing ones.

Because the session has the account's permissions, it can change anything that
account can change. A session as an account with **Can view** can only read.
See [Roles and invitations](https://docs.photon.codes/docs/beta/security/hardening.md#roles-and-invitations) for
what each role can do.

## What you control

* **Remove an account to end its access.** A support session uses an existing
  account's access. If you remove that account from **Members**, a session as
  that account can no longer reach your organization.
* **Ask us.** There's no Dashboard setting to turn support access off or to
  approve each session. For questions about support access to your
  organization, email [support@photon.codes](mailto:support@photon.codes) from
  an Owner or Admin address.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.