Change mission settings safely

Edit criteria, involvement and research depth, check continuation notices and reconcile what was actually saved.

Change a mission deliberately: keep the business goal clear, save one setting at a time and check what Kite actually confirmed.

Start with the right mission#

Open Missions, select the mission and choose Settings. Check your workspace, the mission name, objective and current state before opening an editor. Read recent Activity and Outreach if you need to understand work already in progress.

You need permission to change the selected setting when you save. If access is refused, ask your workspace owner to check your role.

Write down the change you want and why. “Make timing a preference because it is useful context” is clear. “Get more Introductions by removing the difficult requirements” can change the business standard you actually need.

If you need work held while you decide, use the separate Pause mission workflow. Editing a setting is not a substitute for checking the mission and campaign states.

Choose a setting you can change#

Your change	Where to look	What to check
Required conditions or useful preferences	What qualifies	Each condition still represents your real Introduction standard.
How much review you provide	Your involvement	Your plan and account permissions allow the choice; read any continuation notice.
How thoroughly company fit is checked	Research depth	Your plan allows the depth; read any continuation notice.
Monthly sourcing allocation	Share of Monthly Reach	Check the account's allocation and available resources; it is not an Introduction target.
Delivery destination	Where opportunities go	The destination and required connection are ready.

A row can be locked or unavailable. Read its explanation. A mission started through setup currently locks its name and decision-maker roles; company fit, offering, channels and priority also have no supported change control on that started mission. Earlier missions and ended missions can have different restrictions. A failed readiness read does not mean a setting is available.

For a materially different objective, offer or audience, prepare a new mission direction and review its setup in Kite. Do not use an agent or an older address to bypass a locked control.

**Respect a locked setting**
The started mission shows a locked Name row and explains that its name cannot be changed now.

Edit required conditions and preferences#

Select What qualifies. Read What must be true for an introduction.
Keep each condition concrete. Required means a recorded failure rules the person out and an unconfirmed fact must be confirmed on the call; Preferred adds useful context and does not block an Introduction by itself. Select its label to switch between the two.
To add a condition, type it in the field and select Add. This stages a change in the open editor. It does not save it.
Use the remove control to remove a condition from the staged list. To replace its wording, add the replacement and remove the old row before saving. Check the complete staged list before Save and follow any limit or validation shown in your workspace.
Keep conditions concise and follow the current editor’s validation. Combine duplicates and avoid a long paragraph containing several unrelated tests. This saved-standard editor requires at least one condition. Initial baseline setup, where you may add no extra condition, is a separate flow.
Read the complete final list. Keep any real must-have requirement Required; do not relax it simply to obtain a booking or fill a month.

An Introduction still needs a relevant person, willingness to talk, no required criterion recorded as not met and an actual handoff with context and a next step. Changing a preference does not establish interest or turn an unknown required fact into a satisfied one.

**Read the Introduction standard**
The saved-standard editor shows Required and Preferred conditions before an edit.

Save one change and read it back#

When the staged list is right, select Save once and stay on the selected mission while the result is checked. Cancel, the close control or Escape abandons the staged edit before Save.

After a confirmed save, reopen the setting and compare the current conditions with what you intended. Check that the full wording and Required/Preferred choices are correct, then read the mission's latest state and relevant activity. Repeat this process separately for each setting you change.

Do not treat pressing Save, a spinner or the drawer closing as your account evidence. Keep an unconfirmed result open for reconciliation. Closing a drawer after a Save request was dispatched does not undo that request.

If the mission has no attached Introduction standard, saving criteria can create and attach one. Review the intended mission and full staged list before saving, then read the attached standard back. If the existing standard or save outcome is unclear, stop and get help with useful context before trying another tool or repeating the change.

Review involvement before changing it#

Open Your involvement and read the choices offered for this mission. All paid plans offer Run it; Free does not. Availability alone does not change your saved involvement, start work or broaden account permissions.

Choose the level of review you intend to provide. If a finished mission is changed to Run it, the editor can warn that remaining work for its existing goal may continue. Read Before you save, then make the choice only if that continuation is intended.

Save this setting on its own. Afterwards, check both the saved involvement and the mission's current state. A pending outcome, an ended mission, an earlier unsupported mission or unreadable controls can prevent a change. Resolve the stated reason rather than guessing that the choice was saved.

**Check the account permission ceiling**
Run it is unavailable under this account permission ceiling; the existing Review everything choice remains selected.

Review research depth before changing it#

Open Research depth and read the choices your plan permits. Fast uses filters and available data. Verified adds one front-page read and can rule out a clear mismatch; a silent or unreadable page does not independently confirm fit. Deep researches the relevant criteria and leaves what cannot be proved for a decision.

If the mission finished building its Fast list, changing to deeper research can continue its search. Read Before you save, save only when that is intended and inspect the current state afterwards. Your existing permissions and limits still apply.

Researching company fit does not establish the person's willingness to talk. Use Choose the right research depth for the deeper comparison.

**Review the research depth choice**
Verified is staged for a completed Fast mission. Save is enabled and unpressed; no continuation notice is shown in this demo.

Keep resources and restrictions in view#

A criteria or audience change does not restore Reach already consumed, create an unlimited sourcing allowance or remove suppression. One unique person sourced into a mission uses one Reach for that sourcing event. Later messages, replies and the Introduction do not repeatedly consume it. Unused Reach does not roll over.

Review any allocation, funding, credit, permission or connection requirement the product shows before work continues. Do-not-contact rules and opt-outs still apply. A new setting does not recall a sent message, erase a conversation or give an agent permission to act.

Preserve history and inspect current qualification#

An earlier handoff remains part of the recorded history. Changing the standard does not create another Introduction from that same historical event. Its recorded qualification context should be read alongside the current state.

Current qualification may need checking against the changed standard. Treat stale or unknown evidence as unresolved; do not assume every previously reviewed person still meets the new criteria. Review the person, conversation, required facts and next step in your Introduction workspace.

Recover an unconfirmed change#

If the page says the conditions save could not be confirmed, record the exact message, setting, mission and time. Refresh and read the current conditions and mission state before another attempt.

If the current values match your intended change, keep that observed state and investigate any remaining warning. If they differ, or cannot be read, resolve the discrepancy before saving again. Another action or teammate may have changed the mission; do not overwrite that later choice blindly.

Involvement, research depth and allocation can use a retained settings request. If Kite specifically tells you an earlier change was recovered or asks you to preserve the original session/request, follow that instruction and reread the current state before choosing different settings. A recovered earlier result is not permission to overwrite a later change. Criteria-save uncertainty instead calls for current-state reconciliation; do not assume every editor has the same retry contract.

Do not clear browser storage, duplicate the mission, restart it, change funding or disable a restriction to make an uncertain result disappear. For unresolved state, use Get help with useful context.

Watch the settings controls#

Use the walkthrough to locate the criteria editor, staged choices, locked settings, an account permission ceiling and the research-depth choices. Read any continuation notice shown in your workspace. Follow the written save/readback steps in your own workspace and check the actual result there. The walkthrough shows where to look; it does not save your account settings.

48 sec · Captioned, no audio

Change mission settings and check the result

Work with your agent#

Ask your agent to prepare the change and its readback checklist from authorised current context. Give it the business reason and the proposed standard. A public guide supplies instructions; it does not reveal your private mission state or authorise a mutation.

Keep missing account facts explicit. Have your agent distinguish a proposed setting, a saved setting, a confirmed current mission state and historical Introduction evidence.

Work with your agent

A clear task to copy

Prepare a read-only mission-change review. Discover the currently available authorised Kite tools and exact arguments. Where supported, find the mission through list_missions and use its returned market_id with get_mission. Read current settings, activity and relevant campaign state only through supported read tools. Check the workspace, objective, current state, required criteria, preferences and saved involvement/depth. Compare my proposed change with those observed facts; keep missing fields unknown and explain any locked control or continuation notice. Separate historical handoff evidence from current qualification and stale verdicts. Give me the exact in-app setting, one proposed change and a readback checklist, citing the current University guide, stable section and version.

Prepare only. Do not save or attach qualification standards, change mission controls or allocation, change permissions/connections/suppression, start/resume/pause/archive a mission or campaign, source or enroll people, send messages, book a meeting, generate paid work or spend money. Public University tools do not reveal private account state or authorise mutations. If an earlier outcome is uncertain, preserve the original request/session where Kite instructs it and reconcile current state before another action.

This prepares guidance. Use the controls in your Kite workspace for account changes and starting work.

Before you move on#

Confirm the saved values and current state for each setting you actually changed. Leave unresolved results for reconciliation. Completing the checklist below records your own readiness notes; it does not save, pause or resume a mission.

Your readiness check

0 of 7 checked

I checked the correct workspace, mission, objective and current stateThe change preserves my real required Introduction standardI read locked-control explanations and continuation noticesI saved each setting separately and compared its current valuesI checked mission and relevant campaign state after confirmed changesI retained any unconfirmed message and reconciled it before retryingI kept Reach, permissions and contact restrictions in forceThese checks stay in this browser. These are your notes; Kite’s actual account state and start checks decide readiness.