# Service directory: approved destinations, not shared access

> Checked · 20 October 2026 · Wiki version 2026.10.20.2

This directory names the approved service destinations used around Co.Property. Every destination requires an existing authorised account or approved auth; the wiki never stores tokens, credentials, or private logs.

## Purpose
Provide a concise, safe index of services and explain which ones are staff views, provider consoles, deployment consoles, private admin surfaces, or authenticated APIs.

## Diagram text alternative
Staff and public web surfaces, provider consoles, infrastructure consoles, the authenticated source API, and loopback mini viewer paths have different access and action boundaries.

## Current / proposed status
- Current: Checked — destinations are documented; an available URL is not proof of access, ownership, freshness, or approval.
- Proposed: Keep links current through reviewed documentation changes and never add credentials or private administrative material.

## Safe example
### A safe directory use
Open the staff PWA only with an approved account. If a dashboard issue needs investigation, use the directory to identify the relevant provider or console, then follow its current approved access procedure. Do not paste tokens into the wiki or a drafted prompt.

## Responsibilities
- Each service owner controls access through its approved account and permission model.
- A contributor uses their own approved identity and does not share or request secrets in documentation.
- The source API requires approved authentication and must not be probed anonymously.
- The mini viewer remains loopback-only through a secured SSH tunnel.

## Checklist
- Use an existing authorised account; ask for access through the owner/admin route.
- Never publish, paste, or request tokens, private keys, credentials, or private logs.
- Treat authenticated API and provider consoles as controlled surfaces, not documentation examples to call.
- Use a secured tunnel for mini viewer paths; do not expose loopback endpoints publicly.

<a id="directory"></a>

## Find the right service by the work it supports

**Status:** Checked

Project and staff surfaces: GitHub repository, staff PWA, Co.Property website, and Academy. Infrastructure and access consoles: Cloudflare dashboard, Vercel dashboard, and Tailscale admin. Provider and communications consoles: Hospitable, Turno, PriceLabs, LINE manager, and LINE developers console.
The source API is `https://coproperty-office-api.coproperty-office.workers.dev` and requires approved authentication. The directory lists it as a controlled source, not an endpoint to call from this static site.

**Current / proposed status**
- Current: Checked — links are a navigation aid; every destination still requires existing authorised access.
- Proposed: Review link ownership and access wording whenever a service changes.

**Expected outcome**
A reader can identify the relevant authorised surface without treating the wiki as a credential vault.

**Meaningful tests**
- Check service URLs exactly match the approved directory and use HTTPS.
- Check all external link elements include rel="noreferrer" or equivalent safe handling.

<a id="access-condition"></a>

## A reachable sign-in page is not an approval to act

**Status:** Checked

Existing authorised accounts are required for every listed service. An installed CLI, an open browser session, or a familiar dashboard does not prove a teammate is the approved identity for a task. This is especially important for Codex on the mini, provider consoles, and deployment dashboards.
The wiki deliberately avoids tokens, credentials, API probes, and private evidence. If a task needs access, use the owner or admin approval route and record only the safe outcome in the appropriate authorised system.

**Current / proposed status**
- Current: Checked — the access condition is explicit and no secret material is included.
- Proposed: Keep privileged actions outside static documentation and require individual approved authentication.

**Expected outcome**
Links help navigation without leaking access material or implying authority.

**Meaningful tests**
- Search static exports for credential-like terms and confirm no values are present.
- Check source API text says approved auth is required and makes no unauthenticated request.

<a id="do-not-publish"></a>

## Keep operational paths useful without publishing private material

**Status:** Checked

The loopback mini viewer can be reached through an approved SSH tunnel at port 8790 for `/admin`, `/planning`, `/health`, `/reports`, and `/tv`. Keep it described as a secured operator path, not a public web service.
Do not add runtime databases, credentials, private logs, internal QA evidence, or an endpoint that executes a contribution request to the wiki. The static site’s role is orientation and safe drafting.

**Current / proposed status**
- Current: Checked — the directory is intentionally bounded to safe links and explanations.
- Proposed: Reject documentation additions that would turn the wiki into a credential, runtime, or execution surface.

**Expected outcome**
The shareable static wiki remains useful without expanding the exposure of internal systems.

**Meaningful tests**
- Check generated files contain no API client, execution endpoint, or runtime database artifact.
- Check mini viewer paths are paired with the SSH-tunnel requirement.

## Related pages
- [Personal access: choose the least-privileged path](/contribution/access/) — Most staff should use approved dashboard access. Technical operators use their own Tailscale identity and SSH key to reach the office mini only after owner approval.
- [Provider → data → replica: one writer, protected projections](/systems/data-replicas/) — Providers remain authoritative for their own transactions. The main mini writes internal company state; Cloudflare protected replicas and the Vercel staff PWA consume projections rather than replacing the master record.
- [Screenshots tour: dated examples, safer next questions](/reference/screenshots-tour/) — These sanitized screenshots are a visual orientation to the installed app captured on 20 October 2026. They are not mockups, credentials, or current operational proof.

## Source pointers
- Handoff / pages/infrastructure.html
- Handoff / pages/access.html
- Handoff / START-HERE.html

## Context export
- Page context: ./exports/reference--service-directory.context.json