Before you start
Use an authorised account in your company’s installation. Confirm your service and location scope. Test configuration changes with fictional records before publishing them for employees.
This guide describes the project controls in the current local build. A dedicated project screenshot is not included; unrelated screens are not presented as this module.
Step-by-step walkthrough
Open IT projects
Use Projects to open the internal project directory. This is a separate place for delivery work rather than another ticket status.
Check your permissions
Confirm that your role can create or edit projects. Project directory content and exports are intended for IT staff; publication does not grant general employee access.
Add a project
Choose Add project. Give the project a clear name and describe the work so colleagues can find it later.
Set its delivery status
Use the appropriate phase: planned, in progress, completed or on hold. Update the phase when delivery changes, not just when the description is edited.
Describe the project story
Record the challenge, work and results in the available project sections. Distinguish planned benefits from achieved outcomes.
Maintain milestones
Add milestone titles, dates and statuses. Use milestones for meaningful checkpoints that help colleagues understand delivery progress.
Record supporting outcomes
Maintain the available metrics and supporting project information. Add a website link only where it is relevant to the project.
Submit for review
Use Submit for review when the draft is ready. An authorised publisher can then Publish to directory; publication records the reviewed version.
Manage changes with a reason
Use the revision history to trace edits. Archive project when it should leave the active directory, or Restore draft when the available workflow requires further revision.
Find and maintain the portfolio
Use Find a project and the available filters. For bulk edits, select projects, set only the fields to change, preview the changes and supply a reason before confirmation.
Check the result
Repeat the journey as the intended user, including a user outside the permitted scope. Confirm the visible choices, saved record and history match the policy. If an action is absent, check the user’s permissions and the published configuration before changing the workflow.
Configuration labels and available actions depend on the installed version and your role. These instructions describe the current local build.