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

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Strategic Portfolio Management

ft:clusterId :

    - itbm

bundleId :

    - itbm

workflow :

    - Technology


---

# Project types in Project Workspace

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

Release version: Brazil  
Updated November 5, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
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/D2h7t7Nt18swQ~Cn4ikzfA "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/exEpOAPYt2JHMOhjlVSHkg "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/BNSe1RBsM4aNpdl3me1dbA "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/xg1~9sool6DH9gMAYsL_Bw "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/D2h7t7Nt18swQ~Cn4ikzfA "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/w2B~zDUncR47i7N2ItqxuA "You can install the SPM Enterprise-Wide Deployment application (sn_spm_ewd) if you have the admin role.")