Understanding Organizations and Projects

Learn how Organizations and Projects structure delivery work and access scope.

Overview

Organizations and Projects define how work is structured in Transform. This structure also defines the scope for access control and reporting.

Key Concepts

Organization

An Organization is a container for work belonging to a client, department, or business unit. Organizations contain Projects.

Project

A Project is a delivery container for a single transformation initiative. Projects contain requirements, tasks, tests, and artifacts.

Access scope

Access is assigned at Account, Organization, and Project scope. Scope determines what a Teammate can see.

• Understanding Access Levels

How It’s Used

Use Organizations to separate clients or internal divisions. Use Projects to separate initiatives and delivery timelines.

Benefits

• Clear separation of work by client or department
• Cleaner access control through scope-based permissions
• More consistent reporting across Projects

Setup Steps

Follow the common setup path.

1

Create an Organization

Create an Organization for a client, department, or business unit.

• Create an Organization

2

Create a Project

Create a Project for one transformation initiative.

• Create a Project

3

Configure the project

Set defaults, roles, fields, and integrations.

• Project Settings and Configuration

Best Practices

• Keep Organization names stable.
• Use consistent Project naming, such as {Organization} {initiative}.
• Start with least-privilege access and expand only when needed.

Summary

Core pages:

• Organizations
• Projects
• Project Settings and Configuration

Related:

• Start Here
• Understanding Access Levels