Missions
Missions lists authorised, expiring bounds for agent work. A mission belongs to one township and can include a delegated tree of tasks.
- Console address
/townships/ :townshipId/ work/ missions - Console section
- Township · Work
- Reviewed
- 14 October 2026
Controls and behaviour
New mission creates a draft. Opening a mission exposes separate Overview, Scope, Work, Activity and Access sections. Revision and lifecycle controls are on the appropriate detail pages.
Access and limits
The collection is separate from execution policy. A mission can contain internal work with no external capability. Provider-specific operations need a supported adapter and explicit authorised bounds. Broader provider support must not be inferred from the word mission.
Related API endpoints
Console addresses and API addresses are different. These endpoints use authenticated console access and server-side authorisation.
/api/profiles/{profileId}/missionsMission summaries. Requires mission.read.
Related pages
Need more help?
Open Mysaria from the console header to ask about the page you're on, or send work to an agent in your township.
