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

More Options

The More Options menu is available for each project in the Projects list. It provides additional actions that allow users to access project-level configurations and detailed information.

Click on the three-dot (⋮) icon next to a project name to view the available options.

The options include:

  • Project Details

  • Setting

These options help users manage project-specific configurations and view complete project information without leaving the project workspace.

Project Details

The Project Details option provides a consolidated view of all information related to the selected project. It allows users to review configured project attributes, ownership, workflow, and other associated details.

The top panel in the Project Details view provides a quick summary of key project attributes. It allows users to identify the project, view ownership details, and understand the project configuration at a glance.

What you see on the screen

Project Details | Top Panel

Label
Action
Description/ Example

Project Name

Click to update project name or basic details.

Displays the name of the project. Example: ITSM Web application

Project Code

View only field, no actions can be taken

Displays a unique project identifier.

Example: 190

Type

Displays the project methodology/type

Waterfall

Version

View the current project version. The version is automatically updated when the project's Baseline Start Date or Baseline End Date is modified.

Displays the current version of the project schedule. Version updates help track baseline changes and maintain project history. All version changes are recorded in the Recent Activity panel. Example: 1.1, 1.2, 1.3

The top panel provides a read-only summary of project metadata. Any updates to these fields (if permitted) are reflected immediately and tracked in audit logs.

Summary

The Summary section provides an overview of the project’s basic information, including description, timeline, and status. This section allows users to review and update key project attributes required for tracking and planning.

All fields in this section support inline editing. Changes are saved automatically when the user modifies a field and leaves it.

What you see on the screen

Project Details | Summary

Label
Action
Description/ Example

Project Description

Enter or update project details using a rich text editor

Example: Implementation of ITSM modules, including Incident and Change Management

Baseline Start Date

Displays or selects the planned project start date

Example: Feb 26, 2026 06:30 PM

Baseline End Date

Displays or selects the planned project end date

Example: Mar 30, 2026 06:30 PM

Revised Start Date

Update revised start date if schedule changes

Example: Feb 27, 2026 06:30 PM

Revised End Date

Update the revised end date based on the updates

Example: Mar 30, 2026 06:30 PM

Actual Start Date

Select the actual project start date

Example: Select Date

Actual End Date

Select the actual project completion date

Example: Select Date

Status

Displays and updates project status

**Example:**Draft → Initiation

Ensure that date fields are updated correctly, as they impact project scheduling and reporting.

Business Case

The Business Case tab is used to define the project's justification, expected benefits, return on investment, and approval details. This section helps project stakeholders understand the business value and expected outcomes associated with the project template.

The Business Case section also includes additional sub-tabs such as Impact, Objectives, Assumptions, Scope, Deliverables, and Constraints, allowing users to configure complete project planning, impact analysis, goals, assumptions, scope definitions, deliverables, and project limitations within a structured workflow.

Business Case | Configuration Details

Label
Action
Description / Example

Summary

Enter the project business summary

Provides a high-level overview of the project purpose and business requirements. Example: Implement centralized network monitoring across branch locations.

Benefits

Enter the expected project benefits

Defines the operational, financial, or strategic advantages expected from the project. Example: Improved monitoring visibility, reduced downtime, and faster incident response.

Expected ROI

Enter the expected return on investment value

Specifies the estimated return or measurable business value expected after project completion. Example: 25% reduction in operational overhead within one year.

Approver

Select the project approver

Specifies the stakeholder or authority responsible for approving the business case. Example: IT Director, Project Sponsor, or Business Head.

Once the required Business Case details are added, click Next to navigate to the Impact tab while retaining the configured information.

Impact

The Impact tab is used to capture the project's potential impact across Customer, Business, and Technology. Users can select predefined impact categories from the dropdown fields and provide detailed comments for each selected impact type. This helps stakeholders evaluate how the project affects customer experience, business operations, and technical infrastructure before project execution.

The tab supports structured impact assessment by allowing users to define impact values along with supporting remarks or analysis for each section.

Impact | Configuration Details

Label
Action
Description / Example

Customer

Select the customer impact type from the dropdown list.

Defines how the project impacts customers or end users. Available Options: Customer, Productivity, Financial, or Operational.

Customer Comment

Enter comments related to the selected customer impact.

Used to describe the expected customer-related impact in detail. Example: Improves the customer onboarding process and reduces response time.

Business

Select the business impact type from the dropdown list.

Defines the project's operational or organizational impact.

Available Options: Operational, Financial, Customer, or Productivity.

Business Comment

Enter comments related to the selected business impact.

Used to provide additional business impact details.

Example: Reduces operational overhead and improves workflow efficiency.

Technology

Select the technology impact type from the dropdown list.

Defines the technical impact area associated with the project.

Available Options: Infrastructure, Application, Database, or Security.

Technology Comment

Enter comments related to the selected technology impact.

Used to explain the technical impact or implementation considerations.

Example: Requires database optimization and additional security validation.

Once the required Impact details are added, click Next to navigate to the Objectives tab while retaining the configured information.

Objectives

The Objectives tab is used to define measurable project goals and expected targets. Multiple objectives can be added to track different project outcomes and performance metrics.

Objectives | Configuration Details

Label
Action
Description / Example

Objective

Enter the project objective

Defines the project's primary goal or outcome. Example: Improve network uptime across all data centers.

Metric

Select the measurement type

Defines the unit used to measure the objective progress. Available options include:

  • Percentage (%)

  • Count

  • Currency ($)

Start

Enter the initial value

Specifies the starting measurement value before project execution. Example: 60

Current

Enter the current progress value

Displays or defines the current progress value for the objective. Example: 75

Target

Enter the target value

Defines the expected target to achieve after project completion. Example: 100

Description

Enter objective details

Provides additional information about the project objective. Example: Achieve 99.9% uptime for all production systems.

+ Add Another

Click + Add Another

Adds multiple objective sections within the same project template.

Once the required Objective details are added, click Next to navigate to the Assumptions tab while retaining the configured information.

Assumptions

The Assumptions tab is used to document project assumptions and associated risks if those assumptions are violated during project execution.

Assumptions | Configuration Details

Label
Action
Description / Example

Category

Select the assumption category

Defines the assumption classification. Available options include:

  • Resources

  • Technical

  • Operational

  • Budgetary

  • External

  • Other

Assumption

Enter the project assumption

Specifies the assumption considered during project planning. Example: Required infrastructure resources will be available during deployment.

Risk if violated

Enter the associated risk

Defines the potential impact or risk if the assumption is not met. Example: Deployment delays due to unavailable resources.

+ Add Another

Click + Add Another

Adds multiple assumption entries within the project template.

Once the required Assumptions details are added, click Next to navigate to the Scope tab while retaining the configured information.

Scope

The Scope tab is used to define project scope items, their execution status, and whether each activity is in or out of scope for the project.

Scope | Configuration Details

Label
Action
Description / Example

Scope

Enter the scope definition

Defines the project activity, feature, or deliverable included in the scope planning. Example: Deployment of monitoring agents across branch offices.

Status

Select the scope status

Defines the current execution status of the scope item. Available options include:

  • New

  • In-Progress

  • Completed

  • On Hold

Scope Type

Select the scope type

Specifies whether the activity belongs within the approved project scope. Available options include:

  • In Scope

  • Out of Scope

+ Add Another

Click + Add Another

Adds multiple scope entries within the project template.

Once the required Scope details are added, click Next to navigate to the Deliverables tab while retaining the configured information.

Deliverables

The Deliverables tab is used to define the expected project deliverables and track their execution status within the project template.

Deliverables | Configuration Details

Label
Action
Description / Example

Deliverable

Enter the deliverable name

Defines the expected output or result of the project. Example: Finalized network deployment report.

Status

Select the deliverable status

Defines the deliverable's current status. Available options include:

  • New

  • In-Progress

  • Completed

  • On Hold

+ Add Another

Click + Add Another

Adds multiple deliverable entries within the project template.

Once the required Deliverables details are added, click Next to navigate to the Constraints tab while retaining the configured information.

Constraints

The Constraints tab is used to define project limitations, restrictions, risks, and operational boundaries that may affect project execution.

Constraints | Configuration Details

Label
Action
Description / Example

Constraint Type

Select the constraint category

Defines the type of project limitation or restriction. Available options may include:

  • Cost Budget

  • Scope

  • Resources

  • Technology

  • Quality Standards

  • Legal & Compliance

  • Location (Geographical)

  • Others

Constraint

Enter the constraint details

Defines the limitation or restriction applicable to the project. Example: Limited budget allocation for infrastructure upgrades.

Impact

Select the impact type

Defines the operational or business impact caused by the constraint. Available options may include:

  • Operational

  • Financial

  • Customer

  • Productivity

Remark

Enter additional remarks

Provides additional notes or comments related to the constraint. Example: Additional approvals required for budget expansion.

+ Add Another

Click + Add Another

Adds multiple constraint entries within the project template.

Once all required constraint details are added, click Save to save the Project with all configured Business Case information.

Teams

The Teams section allows users to associate project teams and manage team members involved in the project. It provides visibility into who is working on the project, their assigned roles, and the distribution of tasks.

What you see on the screen

Project Details | Teams

Label
Action
Description / Example

Select Team

Select a team

Allows users to choose and associate a team with the project (e.g., ITSM Team).

Username

View team members

Displays the list of users in the selected team along with their email IDs.

Projects

View associated projects

Shows the projects each user is part of (e.g., ITSM Web application).

Role

View/manage roles

Displays assigned roles such as Project Manager, Dev Team, or Test Team. Roles can be updated based on project needs.

Tasks

Monitor task count

Displays the number of tasks assigned to each user to track workload distribution.

+ Add

Add team or members

Allows users to add new teams or include additional members to the project.

Teams / Roles Tab

Switch view

Enables switching between the team-based and role-based views of users.

Business Hours

The Business Hours section is used to associate a predefined business hours profile with the project. This defines the project's working schedule and is used for time-based calculations, such as SLAs and task timelines.

To create or update hours, navigate to the Business Hours module.

What you see on the screen

This section displays the selected business hours profile along with its configuration details, including:

  • Profile Name – Name of the selected business hours profile

  • Description – Additional details about the profile

  • Timezone – Timezone configured for the business hours

  • Schedule Type – Indicates whether it is set to 24×7 or specific working days/hours

  • Working Days and Time – Defined working days along with start and end times

  • Exclude Hours – Configured non-working periods such as holidays or excluded time ranges

Workflow

The Workflow section is used to view and configure the project's workflow. This workflow defines the different stages of the project lifecycle and the transitions between them.

Users can view a predefined workflow from the available options. This section is read-only for configuration, and users cannot create or modify workflows here.

To create or update workflows, navigate to the Workflow module.

What you see on the screen

This section displays the selected workflow along with its structure and stages, including:

  • Workflow Name – Name of the selected workflow (e.g., Default Project Workflow)

  • Stages – Different phases of the workflow, such as Initiation, Hold, Close, etc.

  • Statuses – Statuses within each stage (e.g., Draft, Not Started, Paused)

  • Transitions – Visual flow showing how tasks move from one stage/status to another

  • Workflow Diagram – Graphical representation of the workflow with nodes and connections

Risk

The Risk module helps project teams identify, assess, and manage risks that may affect project objectives, timelines, resources, or deliverables.

Project risks can be recorded and monitored throughout the project lifecycle to help teams evaluate potential impacts and define mitigation strategies. The module provides access to both Risk Records and Risk Assessment, allowing project managers to track identified risks and assess their severity and likelihood.

From the Project Details page, users can create project-specific risks, associate them with the project, and monitor them as part of overall project governance.

What You See on the Screen

Project Details | Risk

Label
Action
Description / Example

Risk Records

Click to view

Displays all risks associated with the selected project. Users can create, view, edit, and manage project-specific risk records.

Risk Assessment

Click to view

Displays risk assessment information used to evaluate the impact, probability, and overall severity of identified project risks.

+ New Risk

Click to add

Opens the New Risk panel to create and associate a risk record with the current project.

Risk Records and Risk Assessment in Project Management use the same functionality as Change Management. For detailed instructions, refer to the Risk Records and Risk Assessment documentation in Change Management.

Project Health

The Project Health module enables project managers to monitor and record the overall health of a project across key operational areas, such as Schedule, Resource, Budget, Quality, and Risk. It provides a centralized view for tracking project health records, documenting action plans, and identifying areas that require attention throughout the project lifecycle.

Each health record captures the current health status of a specific project area, along with supporting details.

Add New Health

Click + New Health at the top-right corner of the Project Health page to create a new health record for the project.

Enter the details described in the following table.

Add New Health | Project Health

Label
Action
Description/ Example

Name*

Enter a unique name for the health record.

Specifies the title used to identify the project health record. Example: Resource Availability

Health Type*

Select a health category from the drop-down.

Specifies the project area to which the health record applies. Available options include:

  • Schedule

  • Resource

  • Budget

  • Quality

  • Risk

Action Plan

Enter the corrective or improvement plan.

Specifies the actions planned to improve or maintain the health of the selected project area. Example: Hire two backend developers within the next two weeks to address resource shortages

Description

Enter additional information about the health record.

Specifies the reason, observations, or current condition related to the project's health. Example: Current sprint delivery is delayed due to insufficient development resources.

Once all required details are entered, click Save to create the project health record.

The newly added record is displayed in the Project Health grid, where it can be edited or deleted as required.

Project Health

The Project Health Check allows project managers to assess a project's overall health using a predefined Health Template. The selected template presents a set of assessment questions to evaluate various aspects of the project. Based on the selected responses, the system automatically calculates the project health score and displays the corresponding health indicator.

Health Templates must be created before performing a Project Health Check. For more information, see Health Template.

To perform a project health assessment:

  1. Open the required Project.

  2. Navigate to Project Health.

  3. Click the Project Health Check tab.

  4. Select a Project Health Template from the drop-down list.

  5. Answer the assessment questions displayed for the selected template.

  6. Review the Health Meter, which updates automatically based on your responses.

  7. Click Submit to save the assessment.

What you see on the screen

Section
Description

Project Health Template

Select the Health Template that contains the assessment questions. Only configured Health Templates are available for selection.

Project Health Check Template Question

Displays the questions defined in the selected Health Template. Choose the appropriate response for each question.

Health Meter

Displays the calculated project health score as you answer the assessment questions. The meter updates dynamically based on the selected responses.

Submit

Saves the completed project health assessment.

Health Score

The project health score is calculated based on the responses provided during the assessment.

Score Range
Health Status

0 – 40

🔴 Red (Critical)

41 – 70

🟡 Amber (Moderate)

71 – 100

🟢 Green (Healthy)

Milestone

The Milestone section displays all project milestones. It provides a consolidated view of milestone details, including ownership, timelines, status, and task progress, allowing users to track project progress at key checkpoints.

Click here for detailed information about Project Milestone.

What you see on the screen

Label
Action
Description / Example

Search

Search milestones

Allows users to search milestones by name.

Filter

Apply filters

Filter milestones based on specific fields. Fields: Milestone Name, Owner, Status Conditions: in, not in, contains, not contains, equal to, not equal to

Add Milestone

Click to add a milestone

Opens a pop-up window to facilitate the creation and addition of a new milestone to the project. Please refer to the Add Milestone section for detailed instructions on adding project milestones.

Milestone

View milestone name

Displays the name of the milestone (e.g., Architecture Phase 1).

Owner

View owner

Displays the user assigned as the milestone owner.

Baseline Start Date

View start date

Displays the milestone's planned start date.

Baseline End Date

View end date

Displays the milestone's planned end date.

Status

View status

Displays the milestone's current status (e.g., To Do, Open).

Tasks

View task count

Displays the number of tasks associated with the milestone along with progress (e.g., completed vs total).

Edit

Modify milestone

Allows users to edit milestone details.

Delete

Remove milestone

Allows users to delete the milestone from the project.

Project Budget

The Project Budget section is used to define and track a project's financial allocation by recording both estimated and actual costs.

Each budget entry created in this section is linked to a Cost Center, which acts as the source of funds. The cost center defines the available budget and approval controls, while the project budget shows how the allocated budget is utilized at the project level.

In this setup:

  • The Cost Center holds and governs the total budget.

  • The Project Budget consumes or allocates a portion of that budget for specific project activities.

This relationship ensures that:

  • Project spending is aligned with approved financial limits

  • Budget usage can be tracked against the respective cost center

  • Financial control and approval workflows defined in the Cost Center are enforced at the project level.

Add Budget

On the Project Budget page, click the + Add option located at the top-right corner to create a new budget entry. This opens a side panel where you can enter the required budget details.

Refer to the table below for a structured overview of each field.

Add Budget | Project Budget

Label
Action
Description / Example

Budget Title *

Enter title

Enter a name for the budget entry Example: IT Infrastructure Setup

Cost Type *

Select type

Select the cost type from the dropdown (e.g., Hardware, Software, CapEx, OpEx).

Cost Center *

Select cost center

Select the associated cost center from which the budget will be allocated (e.g., IT Infrastructure).

Budget *

Enter amount

Enter the budget amount to be allocated for this entry (e.g., 500000).

Attachments

The Attachments section allows users to upload and manage project-related files. These files can include project documents, scope files, timelines, and other supporting materials required for project execution and reference.

Users can upload files, categorize them, and access them directly from the project for better documentation and traceability.

You can perform:

  • Upload files related to the project

  • Categorize attachments for better organization

  • Download uploaded files

  • Delete attachments when no longer required

  • View file details such as name, size, and upload date

Add Attachments

To add an attachment, click the + Add option located at the top-right corner.

You can either:

  • Drag and drop files into the upload area

  • Click Browse to select files from your system

Supported file formats include: png, jpeg, jpg, txt, doc, docx, csv, xls, xlsx, pdf, msg, eml. Maximum file size: 20 MB

Add Attachments | Project Details

Label
Action
Description / Example

File Upload

Drag & drop / Browse

Upload files by dragging them into the upload area or selecting from your system.

Category *

Select category

Select the category for the attachment (e.g., Project Charter, Scope Documents, Schedules & Timelines, Risk Register).

Description

Enter description

Add additional details about the file (e.g., Initial project charter document).

Upload

Click to upload

Upload the selected file(s) to the project.

Cancel

Click to cancel

Close the panel without uploading files.

Relation

The Relation tab allows users to associate the project with related records in the system, improving visibility and traceability across linked activities. Users can connect the project with records such as Tickets, Problems, Changes, and Requests, ensuring that all dependent or related work items are centrally accessible.

This helps track dependencies, understand the impact of changes, and maintain a unified view of all project activities.

KPIs

The KPIs tab is used to define and track Key Performance Indicators (KPIs) associated with the project. This section helps project teams monitor measurable goals, track current progress, compare target values, and evaluate overall project performance throughout the project lifecycle.

Users can configure multiple KPI entries by defining the KPI name, measurement metric, status, baseline values, current progress, and target values.

KPIs | Configuration Details

Label
Action
Description / Example

KPI

Enter the KPI name.

Used to define the measurable objective or performance indicator for the project. Example: Project Completion Rate, Customer Satisfaction Score, or Deployment Accuracy.

Metric

Select the KPI measurement type from the dropdown list.

Defines how the KPI value is measured. Available options include:

  • Percentage (%)

  • Count

  • $.

Example: Percentage (%) for completion tracking or $ for budget-related KPIs.

Status

Select the KPI status from the dropdown list.

Defines the current progress state of the KPI.Available options include: New, In-Progress, Completed, and On Hold.

Start

Enter the initial KPI value.

Used to define the starting or baseline value for KPI tracking. The default value is set to 0.Example: 0.

Current

Enter the current KPI value.

Used to capture the current measured progress or value of the KPI. The default value is set to 0.Example: 45.

Target

Enter the expected target value.

Used to define the final expected KPI value or achievement goal. The default value is set to 0.Example: 100.

Add Another

Click Add Another to create an additional KPI entry.

Adds a new KPI configuration row, allowing users to define multiple KPIs for the project.

Click Save after entering the KPI details to save the configured KPI information and successfully associate it with the project.

Procurement Details

The Procurement Details section enables you to associate project procurement records with existing Vendor, Contracts, and Purchase Orders. It provides a centralized view of procurement items used in a project while automatically retrieving related purchase order information, such as the number of items, delivery date, and procurement status.

Add Procurement

To add a procurement record to a project, click Add Procurement located at the top-right corner of the page.

In the Add Procurement panel, provide the required information as described below.

Add Procurement | Project Details

Label
Action
Description / Example

Item

Enter the procurement item name.

Specifies the item being procured for the project. Example: Dell Latitude 7450 Laptop

Vendor

Select from the drop-down.

Displays the list of active vendors available in the system. The selected vendor determines the contracts available for selection.

Contract

Select from the drop-down.

Displays only the active contracts associated with the selected vendor.

If no active contracts exist for the selected vendor, no records are displayed.

Purchase Order

Select from the drop-down.

Displays only the Purchase Orders linked to the selected contract.

Selecting a Purchase Order automatically retrieves the associated procurement details.

Number of Items

Auto-populated (Read-only).

Displays the total number of items available in the selected Purchase Order. Example: 25

Delivery Date

Auto-populated (Read-only).

Displays the delivery date defined for the selected Purchase Order. Example: 31 Jul 2026

Status

Auto-populated (Read-only).

Displays the current status of the selected Purchase Order. Example: In Progress, Delivered, or Pending

The Vendor Contract Purchase Order fields follow a cascading relationship. Available contracts depend on the selected vendor, and available purchase orders depend on the selected contract.

Once you have completed the required details, click Save to add the procurement record to the project.

The procurement entry is then displayed in the Procurement Details grid for the selected project.

Field Configuration

The Field Configuration section allows users to control how project and task fields behave based on roles and status. It defines field visibility, editability, and mandatory conditions within the project.

This configuration ensures that users see only the relevant fields based on their role and the project or task's current status.

Field Configuration in Project Management is integrated with the global Field Configuration module and applies specifically to the selected project.

What you see on the screen

Project Details | Field Configuration

Label
Action
Description / Example

Name

View

Displays the name of the field configuration

Role Name

View

Displays the role to which the configuration is applied

Status

View

Displays the status/stage where this configuration is applicable

Actions

Edit / Delete

Modify or remove the configuration

Add

Click to add

Create a new field configuration

Add Field Configuration

Click + Add to create a new configuration. This opens the Add Field Configuration panel.

Add Field Configuration | Fields

Label
Action
Description / Example

Name *

Enter text

Define the name of the configuration

Type *

Select from the dropdown

Select the configuration type (Project / Task)

Role Name *

Select from the dropdown

Choose the role for which the configuration is applied

Status *

Select from the dropdown

Select the status where this configuration should be active

Communication

The Communication section provides a centralized view of all project-related interactions. It includes emails, SMS, and comments exchanged within the project context. Users can also add internal notes for collaboration.

This section helps track communication history and ensures all stakeholders are aligned.

What you see on the screen

Project Details | Communication

Label
Action
Description / Example

All

View

Displays all communication types (Email, SMS, Comments)

Email

Filter

Displays only email conversations

SMS

Filter

Displays only SMS communications

Comment

Filter

Displays only comments

Mail

Click to compose

Send an email related to the project

Add Notes

Click to add

Add internal notes for the project

Add Notes

Users can add notes to capture important updates, discussions, or observations related to the project.

Label
Action
Description / Example

Add Notes

Enter text

Add project-related notes

Public / Private

Select visibility

Define whether the note is visible to all users or restricted

Save

Click to save

Save the note to the communication timeline

Recent Activities

The Recent Activities section provides a detailed audit trail of all changes made within the project. It tracks updates across different modules such as Summary, Teams, Workflow, Field Configuration, Attachments, and Relations.

This section helps users monitor project changes and maintain accountability.

What you see on the screen

Project Details | Recent Activities

Label
Action
Description / Example

Search Configuration

Enter text

Search for specific activity logs

Activity Timeline

View

Displays a chronological list of all activities

User

View

Displays the user/system that performed the action

Date & Time

View

Displays when the activity occurred

Activity Details

View

Displays details of changes made (e.g., field updates, associations)

Custom Fields

The Custom Fields section allows you to capture additional project-specific information that is not covered by the standard project fields. You can create fields based on the information required for a project and enter or update their values directly from the Project Details view.

Custom fields configured for a project are also reflected in the Summary tab. Changes made to custom field values are saved and remain synchronized across the applicable project views.

Add a Custom Field

To add a custom field:

  1. Open the required project.

  2. Navigate to More Options > Custom Fields.

  3. Click + Add Field. The Add Fields sidebar appears.

  4. Select the required Field Type.

  5. Enter a Label for the field.

  6. Configure the additional properties displayed for the selected field type, such as placeholder text, mandatory status, or validation rules.

  7. Click Submit.

The custom field is added to the project and becomes available for entering project-specific information.

The options displayed in the Add Fields sidebar depend on the selected field type. Use validation rules where required to control the values users can enter.

Add Field | Custom Fields

Label
Action
Description / Example

Field Type

Select

Select the type of custom field to add.

Available field types include Email, Phone Number, Text, Number, Date, Date-Time, Textarea, Dropdown, Radio, and Checkbox.

For example, select Text to create a field for entering the project's country.

Label

Enter

Enter the name displayed for the custom field.

Example: Country

Placeholder

Enter

Enter instructional or sample text to display inside the field before a value is entered.

Example: Enter name

Mandatory

Enable/Disable

Enable to make the custom field mandatory. Users must provide a valid value before an applicable save or submission can be completed.

Mandatory fields are identified with an asterisk (*).

Validation Rules – Regex

Enter

Define a regular expression to validate the value entered in the field. This is useful when the input must follow a specific pattern.

Example: ^[^\s]+(\s+[^\s]+)*$

Validation Rules – Error text

Enter

Enter the validation message to display when the value does not match the configured regex.

Example: Enter a valid country name.

Options

Add/Configure

Available for selection-based fields such as Dropdown, Radio, and Checkbox. Define the values that users can select. Configure at least two options.

Example: For a Project Region dropdown, add North, South, East, and West.

The fields available after selecting Field Type vary based on the selected input type. For example, selection-based fields require options, while text-based fields can include placeholder and validation settings.

Settings

The Settings option allows users with project configuration permission to customize the tabs and task views available for an individual project. Use these settings to display only the project information and task views required for the project.

You can configure the Project Details and Business Case tabs, as well as Task Views.

The Business Case settings are available only when the Project Management Advanced license is enabled.

To access the settings, select the Settings icon from the project options. The Settings sidebar appears for the selected project.

What you see on the screen

The Settings sidebar displays the configuration options available for the selected project. Select or clear the required options and select Submit to apply the configuration.

Settings | More Options

Label
Action
Description / Example

Project Details Tab

Select the required tabs.

Controls the tabs displayed in the project details view.

Available options can include Summary, Project Closure, Business Case, Teams, Business Hours, Workflow, Milestones, Project Budget, Risk, Project Health, Attachments, Relation, KPIs, Procurement Details, Field Configuration, Communication, Recent Activities, and Custom Fields.

Disabled tabs are hidden from the project.

Business Case Tab

Select the required Business Case tabs.

Controls the sections displayed within the Business Case view.

The available options are: Business Case, Impact, Objectives, Assumptions, Scope, Deliverables, and Constraints.

For example, disable Assumptions when it is not required for the project.

Task View

Select the task views to make available.

Controls the task views available within the project. The available views are:

Available View

Enable or disable a task view.

Determines which task views users can access. Enabled views are also available for selection in the Default View list.

Default View

Select a view from the dropdown.

Sets the task view that opens by default for the project. Only enabled task views are listed.

For example, select Table View to open the project tasks in Table View by default.

At least three Project Details tabs and one Business Case tab must remain enabled. The Business Case Tab Settings section is available only with the Project Management Advanced license.

Last updated

Was this helpful?