---
sourceDocument: Australia Strategic Portfolio Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-business-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Strategic Portfolio Management

ft:clusterId :

    - itbm

bundleId :

    - itbm

workflow :

    - Technology


---

# Project types in Project Workspace

# Project types in Project Workspace {#ariaid-title1}

Release version: Australia  
Updated November 5, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Project types in Project Workspace

Project Workspace allows administrators to define custom configurations for different project types without impacting default settings or other types.
This capability requires the SPM Enterprise-Wide Deployment (EWD) application, which is installed automatically starting with Project Workspace version 7.3.0.
Each project type configuration includes a dynamic category for custom fields, a form view for layout, and module visibility settings.
Show full answer Show less  

## Key Features

* **Dynamic Category:** Defines custom fields specific to a project type. These fields are scoped to only appear on projects of that type, preventing cross-type interference. Dynamic categories can inherit attributes from parent categories, allowing reuse of shared fields alongside type-specific additions. Supported data types include String, Boolean, Date, Date/Time, Integer, Decimal, Floating point, Choice, and Reference. Project managers can view and update these fields within Project Workspace and playbooks.
* **Form View:** Establishes a unique, dynamic form layout rendered based on the assigned project type, enhancing user experience by tailoring the interface.
* **Module Visibility:** Controls which modules (Planning, Details, Financials, RIDAC, Resource, Analytics, Docs, Status Report) appear in the Project Workspace menu per project type. By default, all modules are visible, but this setting allows customization. Role-based access remains enforced regardless of module visibility settings.

## Practical Considerations

* The project type can be set only once per project and cannot be changed afterward.
* Project types function independently from EWD partitions; partitions govern access to projects and dashboards, while project types govern the project's appearance and navigation.
* When both partitions and project types are configured, users see only projects they have access to through partitions, and each project displays modules and fields according to its project type, subject to role permissions.

## What This Enables for ServiceNow Customers

ServiceNow customers can customize project management experiences at a granular level by defining unique fields, layouts, and navigation modules per project type. This flexibility enhances project tracking and management tailored to different business needs without disrupting other projects or default settings. Combining project types with EWD partitions ensures secure, role-based access alongside a customized interface, improving usability and governance.  
Administrators can define custom fields, a form view, and visible modules for each project type in Project Workspace without affecting default settings or other project types.

Project types require the SPM
Enterprise-Wide Deployment (EWD) application (sn_spm_ewd). Starting with Project Workspace version 7.3.0, the application is installed automatically.{#project-types-in-pw__section_project_types-para-1}

Each project type configuration consists of three components: dynamic category, form view, and module visibility.{#project-types-in-pw__section_project_types-para-2}

Dynamic category

:   Defines the custom fields for a specific project type. A dynamic category belongs to the Default SPM Dynamic Namespace and groups the dynamic attributes that appear as custom fields on project records of that type.
    Custom fields are scoped to a specific type and don't appear on records of other types or affect default fields.

    * A dynamic category can have a parent category. A child category inherits the attributes of its parent, so you can define shared fields once and add type-specific fields in each child category.
    * Custom fields support the String, Boolean, Date, Date/Time, Integer, Decimal, Floating point, Choice, and Reference data types.
    * Project managers view and update custom fields in Project Workspace and in playbooks for projects of that type.

    For details, see [Create a dynamic category for a project type](https://www.servicenow.com/docs/xlfTetqvKfjYHkS1uCTFXA "Create a dynamic category to define the custom fields that appear on project records of a specific project type in Project Workspace.").

Form view
:   Defines a unique form layout for each project type. The form view is dynamically rendered based on the project type assigned to a record.

Module visibility
:   Defines which modules appear in the Project Workspace menu for projects of a specific type. You can show or hide the Planning, Details, Financials, RIDAC, Resource, Analytics, Docs, and Status Report modules. All modules are shown by
    default, and projects without a project type show all modules. Role-based access still applies: users need the required role to access a shown module.

You can set the project type of a project only once. After the project type is set, you can't change it.{#project-types-in-pw__section_project_types-para-4}

## Project types and partitions {#project-types-in-pw__section_project_types_partitions}

EWD partitions and project types are two independent, complementary layers. Partitions control who can see a project and its dashboards. Project types control what a project
looks like and how it's navigated after you have access to it. Partitions don't determine the form fields, form layout, or modules of a project. Those are controlled by the project type. For the full EWD concept, see [Exploring SPM Enterprise-Wide Deployment](https://www.servicenow.com/docs/vWukTR_Sj3ptliNdL44~0A "SPM Enterprise-Wide Deployment (EWD) partitions SPM tables data so that you can restrict record access by department, business unit, or other function.").

The Project \[pm_project\] table is one of the tables EWD supports for partitioning. You define a partition criteria field on the Project table, such as Department, and create a partition for each value.
When a project is created, it's automatically assigned to the partition that matches its criteria field. A user then sees only the projects that belong to a partition their role grants them access to, across Project Workspace, list views, search results, and dashboards. For the full list of supported tables, see [Supported tables for partition](https://www.servicenow.com/docs/xSUbN9ilEuJYpcQOF9yCEg "Several tables are supported for partition using Enterprise-Wide Deployment, including direct and indirect related tables for each entity.").

When partitions and project types are both configured, a user sees:

* Only the projects that belong to their assigned partitions, in list views, search results, and dashboards.
* For each of those projects, only the modules that are shown for the project's type, subject to role-based access.
* The custom fields and form layout defined for the project's type.
{#project-types-in-pw__ul_project_types_partitions}
**Related tasks**   

* [Configure project type fields and layouts](https://www.servicenow.com/docs/uNQb_b7VW1evkLQHdZhSng "Define custom fields, a unique form layout, and the visible modules to support configuration independence across different types of projects.")
* [Create a dynamic category for a project type](https://www.servicenow.com/docs/xlfTetqvKfjYHkS1uCTFXA "Create a dynamic category to define the custom fields that appear on project records of a specific project type in Project Workspace.")
* [Install SPM Enterprise-Wide Deployment](https://www.servicenow.com/docs/lROZznqngPs9pEIoT2Cv9A "You can install the SPM Enterprise-Wide Deployment application (sn_spm_ewd) if you have the admin role.")