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

# Service commands

> Manage organization-shared service commands and copy a validated preview from a stored service row.

# Service commands

Open **Service commands** in dashboard navigation to browse your organization's library. **Permission required:** Operator-and-above tool access to read, preview or copy; **Manage Playbooks** to create, edit, archive or restore. An active read-only engagement membership prevents organization-wide library changes; it does not grant or replace an organization role.

Commands are grouped by trimmed, lowercase service name and protocol, independently of port number. Several commands can share the same key. Use Active, Archived or All browsing and the service/protocol filters. A command has a title (1–160 characters), service (1–120), protocol (1–32) and nonblank plain text (at most 10,000 characters). Service and protocol start with a letter or number and use only ASCII letters, numbers, dots, underscores, plus signs or hyphens. The command text retains whitespace.

## Manage the library

**Permission required:** Manage Playbooks. Choose **New command** or **Edit**, change the draft and explicitly **Save command**. **Cancel draft** leaves saved data unchanged. Archive retains the command; choose Archived or All and **Restore** to return it to active use. Archived entries cannot be previewed.

A new command is bound to the organization that opened its draft; an organization change requires a fresh page before saving. A failed or conflicting save retains your draft. **Refresh saved data** obtains the current saved command without replacing your text. **Use refreshed saved command (discard draft)** deliberately adopts that version. An unconfirmed result does not establish whether a commit occurred. For an unconfirmed create, another create is blocked while your draft is retained. **Refresh catalog to reconcile create** loads current saved commands without replacing the draft. Deliberately **Adopt** an active saved command and its revision, or review the catalog and choose **I reviewed the catalog; retry this create** before saving again. No matching record is inferred automatically; refresh failure keeps the retry blocked.

## Preview from a service row

**Permission required:** Operator-and-above tool access and access to the engagement. Choose **Commands** on an engagement's service row. The server resolves the stored engagement, endpoint, address and port under your current access; URL parameters carry their identity, not trusted display values. The stored service and protocol must match the active command. A command for `https/tcp` can therefore be used on either port 443 or 8443.

Choose a command and **Render preview**. Only these exact tokens are supported:

| Token | Stored value |
| - | - |
| `{{address}}` | Bounded unscoped IP address or ASCII hostname |
| `{{port}}` | Decimal port between 1 and 65535 |
| `{{service}}` | Normalized service atom |
| `{{protocol}}` | Normalized protocol atom |

```text theme={null}
probe --target {{address}} --port {{port}}
```

Substitution runs once. Unknown or malformed tokens, unsafe stored values and missing/unavailable context produce a visible error; they do not expand to arbitrary context. HTML remains literal, selectable text. Context or command-revision changes invalidate the displayed preview. Switching the selected command cancels its pending preview and ignores an obsolete response or error, so a new selection can be rendered. IPv6 zone suffixes containing `%` are unsupported; stored addresses are not rewritten.

**Copy displayed command** copies exactly the preview. Clipboard rejection keeps the text available for manual selection/copy. Strikepoint does not execute commands, resolve destinations, launch terminals or record copy events. Library lifecycle audits omit command content and context.

The migration file accompanies this feature branch; database rollout and hosted availability require their separate delivery gates.


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