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

Organizations

Use Organizations to separate work by client, department, or business unit.

Overview

Organizations are the primary containers for separating work in Transform. They prevent cross-client mixing and support scoped access control.

Key Concepts

  • Organization scope: container for Projects, Segment Types, and Segments

  • Organization naming: stable identifiers used across reporting and search

  • Access at Organization scope: shared access across multiple Projects

How It’s Used

Create one Organization per client or department. Create Projects inside the Organization for each initiative.

Organizations are also the home for segmentation:

  • Segment Types and Segments are managed at the Organization level.

  • Segmentation

Benefits

  • Clear separation of work and governance boundaries

  • Cleaner access control for multi-Project delivery teams

  • Consistent reporting across Projects within a business boundary

Setup Steps

1

Create an Organization

2

Create Projects inside the Organization

3

Configure Organization-level structure (optional)

Define segmentation and standard reporting fields.

Best Practices

  • Keep Organization names stable and human-searchable.

  • Avoid abbreviations in Organization names unless required by policy.

  • Use segmentation only for real business dimensions that drive reporting.

Summary

Organizations separate work and define an access and reporting boundary. Projects inside an Organization contain delivery work items.

Related:

Last updated