How changes and confirmations work

Your AI app can read freely, but it treats anything that changes your data with care. You stay in control of every change.

Reads and changes

Reading (listing partners, showing a brief, showing revenue) is safe, so the app does it straight away.

Changing covers logging revenue, starting or updating a brief, generating, approving or regenerating, dispatching, promoting with social posts, and saving a dormant partner diagnosis. For all of these, HockeyStick tells the app to:

Show you the exact values it is about to send.
Act only after your clear confirmation.
Never invent facts such as transcripts, source material, speaker details or strategy consent. It asks you instead.

Extra safety switches in your app

Codex: keep per-tool approval on, so Codex asks before each change. For read-only use, sign in with read access only.
Claude: you can turn off HockeyStick's write tools for a conversation where you only want to read.

When something is refused

If HockeyStick refuses a request, the app passes on a short code and an explanation, for example that your Story needs branding saved in Activate first, or that a setup answer needs correcting. Nothing was saved. Fix what it describes and ask again. A refusal never means the app should keep retrying.

When the outcome is unclear

If a change times out or the response is lost, the change may still have gone through. The app does not repeat it. It gives you the brief ID and request ID instead. Ask the app to read the record back, and share those IDs with your consultant if it needs sorting out.

What the app cannot do

Change PartnerStack partner figures. Partner revenue, leads, trials and activations are read-only everywhere in HockeyStick.
See other organisations. You only see the clients your login can see.
Do staff-only tasks such as programme go-live or publishing the Riley pack.
Regenerate an Event. Do that in your portal.
Change settings outside its tools, such as finance settings, Zoom or asset approvals.