Documentation Projects Edit Project
Detailed guide

Edit Project

The project maintenance form for correcting setup details without losing the project history around it.

Use this form to create a clean record the first time or safely update an existing one without guessing which field drives downstream behavior.

Open demo page Back to overview
Quick summary Step by step Guardrails Troubleshooting Related workflows

Quick summary

  • Correct inaccurate dates or status values when the delivery plan changes.
  • Update client association carefully because it affects linked work and reporting context.

Put it into practice

  1. Open the edit form for the project you need to update.

    InteractionsProjects List: open the target project, then click the Edit Project action.
    Open the edit form for the project you need to update.

  2. Review & Update the current project details to reflect the revised delivery plan.

    InteractionsEdit Project form: update Project Name, description, status, date fields, and budget-related inputs as needed.
    Review & Update the current project details to reflect the revised delivery plan.

  3. Pick the client for this project.

    InteractionsEdit Project form: use the Client dropdown at the top of the form.
    Pick the client for this project.

  4. Change the client only when the project should be reassigned.

    InteractionsEdit Project form: use the Client dropdown. If the client is missing, use Quick Add Client to create and select it.
    Change the client only when the project should be reassigned.
    Open workflow: Create Client

  5. Save the project updates.

    InteractionsEdit Project form, bottom actions: click Update.
    Save the project updates.

What to review

Page header and breadcrumb

Confirms whether you are creating or editing, gives you the back path, and is the quickest way to avoid updating the wrong record.

Primary form sections

The form is grouped so you can complete one block at a time instead of hunting for every field in a single long screen.

Required inputs and field labels

Every required label tells you what must exist before the record can be saved; blank or invalid values should be corrected before moving on.

Validation and inline errors

Use these messages as instructions, not warnings to dismiss. They tell you exactly which field blocks save and why.

Primary save action

Commits the record only after the form validates. Use it after reviewing every section because it is the action that changes workspace data.

Cancel or return action

Leaves the form and takes you back without finishing the workflow. Use it when you opened the wrong record or need to check related data first.

Current project values

Read the current values first so you know whether you are correcting data or changing the delivery plan.

Editable project details

These fields update how the project appears in operational and commercial views.

Quick Add Client modal

Use the modal only if the project genuinely needs to move to a brand new client record.

Guardrails

  • Existing linked records do not remove the need for valid required fields; incomplete edits should still fail cleanly.
  • Edit rights are separate from simple view rights on many teams.

If it starts drifting

  • If fields appear locked or save is unavailable, confirm you have edit permission rather than assuming the page is broken.