For the complete documentation index, see llms.txt. This page is also available as Markdown.

Create Projects and the Details Page

Create a Project, update key fields on the details page, and locate deeper settings.

Overview

Project details contain the basic fields used for naming, timeline, and reporting. Project Settings contains deeper configuration such as roles, fields, and connectors.

Key Concepts

  • Project details: name, dates, status, and other high-level metadata

  • Project Settings: access control, fields, templates, automation, connectors

How It’s Used

Use Project details for quick metadata updates. Use Project Settings for governance and workflow configuration.

Benefits

  • Cleaner reporting through accurate dates and status

  • Reduced configuration drift by separating details from settings

Setup Steps

1

Create a Project

Use this guide when a Project does not exist yet:

2

Open Project details

Open the Project. Open Project details (or the Project name menu), depending on UI configuration.

3

Update core fields

Keep these fields accurate:

  • Name

  • Description

  • Start date / end date

  • Status

4

Locate deeper configuration

Use Project Settings for configuration changes:

Best Practices

  • Keep start and end dates aligned to the delivery plan.

  • Use consistent naming patterns across Projects.

  • Treat Project Settings changes as governed updates.

Troubleshooting

Project details cannot be edited

This is usually a permissions issue. Project Admin access may be required.

Summary

Project details are used for quick metadata updates.

Project Settings is used for access control and workflow configuration.

Related:

Last updated