# Clients and client reports > Clients, what they owe you, dated updates, report editions and private portal links. Source: https://docs.crossbot.io/pmo/cli/reference/clients Product: pmo · Kind: reference · Status: live · Last verified: 2026-10-21 {/* Generated by scripts/gen-pmo-cli-reference.mjs from `pmo help`. Do not edit by hand. */} Clients, what they owe you, dated updates, report editions and private portal links. On your own computer, `pmo help ` prints the same text, for example `pmo help client list`. ## `pmo client list` Every client: engagements, projects, modules, open activities, worst health. ```sh pmo client list [] [--q ] [--all] [--json] ``` **Example** ```sh pmo client list --json `pmo help filters` prints these filters in full, and the bare-word search. ``` ## `pmo client show` One client: its contacts, every engagement with its counts, and the totals. ```sh pmo client show [--all] [--json] ``` **Example** ```sh pmo client show cross-systems ``` ## `pmo client create` Register a client — who an engagement is for. ```sh pmo client create --name "" --kind internal|external|pursuit [--industry ""] [--primary-contact ""] [--notes ""] --as person: ``` ## `pmo client set` Correct a client's name, kind, industry, contact or notes. ```sh pmo client set ... --as person: ``` ## `pmo client contact add` Record one of a client's people — who its reports are addressed to. ```sh pmo client contact add --name "" --role "" [--email ] [--github ] --as person: ``` **Example** ```sh pmo client contact add cross-energy --name "you Farias" --role "Chairman and chief executive" \ --github you --as person:you A write: it needs an identity (--as, or PMO_ACTOR) and PMO_WRITES=1. `pmo whoami --grants` prints what this actor may do above the activity. ``` ## `pmo client contact remove` Take one of a client's people off its contacts. ```sh pmo client contact remove --name "" --as person: ``` **Example** ```sh pmo client contact remove cross-energy --name "you Farias" --as person:you A write: it needs an identity (--as, or PMO_ACTOR) and PMO_WRITES=1. `pmo whoami --grants` prints what this actor may do above the activity. ``` ## `pmo client partner add` Record somebody working on a client's behalf. ```sh pmo client partner add --name "" --role "" [--email ] [--github ] --as person: ``` **Example** ```sh pmo client partner add cross-systems --name "FanHero" --role "Network partner on Reef" --as person:you A write: it needs an identity (--as, or PMO_ACTOR) and PMO_WRITES=1. `pmo whoami --grants` prints what this actor may do above the activity. ``` ## `pmo client partner remove` Take somebody off a client's partners. ```sh pmo client partner remove --name "" --as person: ``` **Example** ```sh pmo client partner remove cross-systems --name "FanHero" --as person:you A write: it needs an identity (--as, or PMO_ACTOR) and PMO_WRITES=1. `pmo whoami --grants` prints what this actor may do above the activity. ``` ## `pmo request remove` Take a request recorded by mistake off the record; close one the client answered. ```sh pmo request remove --eng ``` **Example** ```sh pmo request remove pend-024 --eng example-client --as person:you A write: it needs an identity (--as, or PMO_ACTOR) and PMO_WRITES=1. `pmo whoami --grants` prints what this actor may do above the activity. ``` ## `pmo request followup remove` Take one follow-up date off a request. ```sh pmo request followup remove --date --eng ``` **Example** ```sh pmo request followup remove pend-007 --eng example-client --date 2026-09-29 --as person:you A write: it needs an identity (--as, or PMO_ACTOR) and PMO_WRITES=1. `pmo whoami --grants` prints what this actor may do above the activity. ``` ## `pmo request followup set` Correct a follow-up: the day it was sent, or what it chased. ```sh pmo request followup set --date [--on ] [--note ""] --eng ``` **Example** ```sh pmo request followup set pend-007 --eng example-client --date 2026-09-29 --on 2026-09-30 --note "Asked for the written sign-off." --as person:you A write: it needs an identity (--as, or PMO_ACTOR) and PMO_WRITES=1. `pmo whoami --grants` prints what this actor may do above the activity. ``` ## `pmo request list` What the engagement is waiting on the client for — open requests, or --all. ```sh pmo request list --eng [--module ] [--all] [--json] ``` **Example** ```sh pmo request list --eng example-client --module parser `pmo help filters` prints these filters in full, and the bare-word search. ``` ## `pmo request add` Record something asked of the client. ```sh pmo request add --eng --ask "" [--module ] [--requested ] [--to ""] [--blocker] ``` **Example** ```sh pmo request add --eng example-client --module appraisal-import-module \ --ask "A sample Lido export to build and test against." --requested 2026-09-28 --as agent:rag A write: it needs an identity (--as, or PMO_ACTOR) and PMO_WRITES=1. `pmo whoami --grants` prints what this actor may do above the activity. ``` ## `pmo request set` Correct a request: its words, its date, who it went to, its module, its number, how and by which update it was resolved, or reopen it. ```sh pmo request set ask=… | requested= | to=… | module= | ref=… | resolution=… | resolved_by= | closed= --eng ``` **Example** ```sh pmo request set pend-009 --eng example-client resolution="the client confirmed the dataset on a call." --as agent:rag A write: it needs an identity (--as, or PMO_ACTOR) and PMO_WRITES=1. `pmo whoami --grants` prints what this actor may do above the activity. ``` ## `pmo request followup` Record that the client was chased again. ```sh pmo request followup --eng [--date ] ``` **Example** ```sh pmo request followup pend-007 --eng example-client --date 2026-09-29 --as agent:rag A write: it needs an identity (--as, or PMO_ACTOR) and PMO_WRITES=1. `pmo whoami --grants` prints what this actor may do above the activity. ``` ## `pmo request close` Close a request — the client answered, or it no longer applies — and say how. ```sh pmo request close --eng [--date ] [--note ""] [--by ] ``` **Example** ```sh pmo request close pend-001 --eng example-client --date 2026-10-01 --note "example granted access to the sandbox." --as agent:rag A write: it needs an identity (--as, or PMO_ACTOR) and PMO_WRITES=1. `pmo whoami --grants` prints what this actor may do above the activity. ``` ## `pmo portal link create` Make a private link a client opens without an account — or reuse the scope's live one. ```sh pmo portal link create (--client | [--project | --module ]) --label "" [--expires ] [--reports tracker,scope] [--new] [--note ""] --as person: ``` **Example** ```sh pmo portal link create --client example --label "Jane Smith" --as person:you pmo portal link create --client example --label "John Doe" --new --as person:you pmo portal link create example-client --module data-lakehouse-sandbox --label "Jane Smith" --as person:you # one link per person, labelled with their name: each revokes on its own and every open is logged against it # a second create for the same scope returns the same link unless --new A write: it needs an identity (--as, or PMO_ACTOR) and PMO_WRITES=1. `pmo whoami --grants` prints what this actor may do above the activity. ``` ## `pmo portal link list` An engagement's or a client's links, with when each was last opened. ```sh pmo portal link list ( | --client ) [--all] [--json] ``` **Example** ```sh pmo portal link list example-client pmo portal link list --client example --all `pmo help filters` prints these filters in full, and the bare-word search. ``` ## `pmo portal link show` One link, its history and its last opens. ```sh pmo portal link show [--hits ] [--json] ``` **Example** ```sh pmo portal link show pl-3k9x2m7q --hits 50 ``` ## `pmo portal link copy` Print a link's URL again — logged. ```sh pmo portal link copy [--note ""] --as person: ``` **Example** ```sh pmo portal link copy pl-3k9x2m7q --as person:you # the same URL, again A write: it needs an identity (--as, or PMO_ACTOR) and PMO_WRITES=1. `pmo whoami --grants` prints what this actor may do above the activity. ``` ## `pmo portal link set` Change a link's label, expiry or reports. ```sh pmo portal link set label="" | expires=|none | reports=tracker,scope [--note ""] --as person: ``` **Example** ```sh pmo portal link set pl-3k9x2m7q expires=2027-03-31 --as person:you pmo portal link set pl-3k9x2m7q reports=tracker --as person:you # scope analysis off: an Owner's A write: it needs an identity (--as, or PMO_ACTOR) and PMO_WRITES=1. `pmo whoami --grants` prints what this actor may do above the activity. ``` ## `pmo portal link revoke` Stop a link working on its next request — with --children, every link below it too. ```sh pmo portal link revoke [--children] [--note ""] --as person: ``` **Example** ```sh pmo portal link revoke pl-3k9x2m7q --children --as person:you A write: it needs an identity (--as, or PMO_ACTOR) and PMO_WRITES=1. `pmo whoami --grants` prints what this actor may do above the activity. ``` ## `pmo portal hits` The portal log, newest first: which link opened which page, and when. ```sh pmo portal hits ( | --client ) [--link ] [--since ] [--limit ] [--json] ``` **Example** ```sh pmo portal hits --client example --since 2026-10-01 ``` ## `pmo portal people add` Let a client person open a link — they sign in with their email and a code. ```sh pmo portal people add --name "" --email
[--note ""] --as person: ``` ## `pmo portal people remove` Take a client person off a link; off their last link, they are removed and signed out. ```sh pmo portal people remove [--note ""] --as person: ``` ## `pmo portal people list` The client people who may open a link, and when each last signed in. ```sh pmo portal people list [--json] ``` ## `pmo cycle list` The editions of an engagement's client report, newest first. ```sh pmo cycle list --eng [--json] ``` **Example** ```sh pmo cycle list --eng example-client `pmo help filters` prints these filters in full, and the bare-word search. ``` ## `pmo cycle add` Record the date a client report is as of, who it is for and how it is marked. ```sh pmo cycle add --eng --as-of [--audience customer|internal] [--classification "