Manage a project-space summary and status
Edit the authorized summary, follow saving, and distinguish a draft from an applied change.
In this article
Open the project space and confirm the active private or shared side.
Review name, code, status, dates, and summary before editing.
Make a focused change and add the comment required by the displayed workflow.
Save or submit according to the offered action; do not assume a draft is already approved.
Wait for processing state or notification, then refresh the data.
Practical guidance
Check the selected private or shared scope before editing the summary. Narrative changes and a status transition can follow different save paths: a requested status change may start a workflow. Read the returned state and any notification instead of assuming that closing the editor means the transition was approved.
Advanced tips
If another person changed the project while your editor was open, reload the current version and reconcile your changes before saving again. Separate a save failure from a refresh failure by reopening the project and checking the actual stored values.