Help center Core configuration Projects Configure projects and release versions Updated Thursday, October 29, 2026 · Marc Staine Projects group related support work, and versions track planned or released milestones. Use clear project ownership and dates to give agents a shared reference for ongoing work. Applies to: Supportbench Core. Location: Settings → Projects → Projects. Editing Projects and their Versions requires Administer projects. Before you begin You need Administer projects and access to the intended Division scope.Agree the project identity, type and milestones. A project version is maintained separately from the project profile.Reopen the saved result and test a representative consuming workflow. A successful save alone does not verify every reader, assignment or rendered result. Configure and verify Open Settings → Projects → Projects and choose New Project or open the intended project.Enter Name/Description and review Active, Divisions and Type using the field reference.Choose Save Changes and reopen the project profile.Open the project’s Versions section and choose New Version. Enter Version name/Description and the intended Start, Target and Released dates and Active value.Choose Save Version. Reopen that version and verify its dates independently of the project profile.Check the relevant project/version selections in a controlled consuming record. Confirm the meaning of planned versus actually released dates before using them in operational reporting. Settings reference ProjectSettingWhat it controlsHow to chooseName / DescriptionIdentifies and explains the record.Use terminology your team recognizes.ActiveControls normal availability.Review references before deactivating.Name / Description limitsName up to 50 and description up to 250 characters.Describe the project’s scope.DivisionsAuthorized project scope.Choose the teams’ intended divisions.TypeOptional active project type.Use a consistent classification. VersionsSettingWhat it controlsHow to chooseVersion name / DescriptionName up to 50 and description up to 250 characters.Use a version label your team recognizes.Start / Target / Released datesPlanned and actual milestone dates.Distinguish the target from the actual release date.ActiveVersion availability.Review existing uses before deactivation. Behavior to knowNew projects start Active with the permitted starting division, no type and no versions.Versions are saved separately from the main project. Recommended use Choose dates and version names that the team can interpret consistently.Maintain project profile changes and version milestones deliberately through their separate save actions.Review references before deactivating a project or version. Worked example: track a customer rollout and its planned release separately A B2B team is coordinating an illustrative Northstar controller rollout. Create the Project with a description of the agreed scope, intended Divisions and an already-configured active Project Type where needed. Review Active and choose Save Changes.Reopen the project and verify its profile before adding a Version. Use New Version for a meaningful milestone such as Site 1 pilot. Set Start and Target to the actual agreed plan; leave Released unset until the milestone was actually released.Choose Save Version and reopen that Version separately. Saving the project profile does not save an unfinished Version editor. Confirm the planned Target has not been mistaken for evidence of an actual release.In a controlled consuming record, verify the saved Project and its Version appear in the intended context. If the Version is absent, check its Active state, saved project relationship and Division context before creating a duplicate.Keep the support owner and customer commitments explicit in the ordinary Case process. A project label, type or target date does not automatically route support work or replace an agreed next update. Troubleshooting ProblemWhat to checkThe version was not saved with the projectVersions use their own Save Version action.A project or version is absent from a selectorCheck its Active value, applicable project/Division context and the saved record.The Type is missingReview the separately configured active Project Type.A date implies the wrong milestoneCheck Start, Target and Released separately; a planned target is not proof of actual release.I cannot edit a project/versionCheck Administer projects. Related configuration Projects → Configure project typesOrganization → Configure divisionsWork a case from first response to resolutionBuild views that turn case data into an action list Was this article helpful? Yes No Thank you for your feedback.