--- title: "About company structure & organizational hierarchy" slug: "about-company-structure-and-organizational-hierarchy" updated: 2026-05-20T22:11:11Z published: 2026-05-20T22:11:11Z canonical: "help.wrapbook.com/about-company-structure-and-organizational-hierarchy" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.wrapbook.com/llms.txt > Use this file to discover all available pages before exploring further. # About company structure & organizational hierarchy > [!NOTE] > Organizational Hierarchy is available by request > > Organizations, organizational hierarchy, and production entities are available by request. If you don't see these settings in your Company settings, contact your Customer Success Manager or the [Wrapbook Support Team](/v1/docs/how-to-get-help-using-wrapbook). ## Overview If your company has a complex structure, Wrapbook's *Organizational Hierarchy* helps you set it up correctly. It includes: - **Organizations (Organizational Units, or OUs)**: used to manage *visibility and access* (who can see/do what) - **Production Entities (PEs)**: used to represent *legal and financial entities* (who is legally employing/payrolling workers) Many companies only need a simple structure (one company with a single legal entity and no additional organizations). Organizational Hierarchy is intended for companies that are **one parent company** with **multiple divisions and/or multiple legal entities**. ## Key definitions ### Company (your Wrapbook company) Your Wrapbook company is the top-level account that contains your projects, people, organizations (OUs), and production entities (PEs). ### Organization (OU) An *Organizational Unit* is a division or business unit inside your company. Organizational units help you: - Establish well-defined access controls that govern which team members can view and interact with projects within each organizational unit - Model internal structure (for example, division heads) - Assign org-specific settings in Wrapbook where available (for example, approval workflows may be scoped to an organizational unit so that the workflow is only available to projects within that organizational unit) ### Production Entity (PE) A *Production Entity* is a **legal entity** (typically with its own EIN/FEIN and address, and often separate banking) that can be assigned to projects for payroll and legal responsibility. Production entities help you: - Ensure the correct **legal employer** appears in the right places - Route payroll and certain project-related transactions under the correct entity ## The simplest way to remember the difference - **Organizations (OUs) = "who sees what"** - **Production Entities (PEs) = "who legally pays whom"** Organizations control access and structure. Production entities control legal/financial identity. ## How projects use OUs and PEs Each **project** can use both concepts: - A project is typically **assigned to one Production Entity** (for legal/employer context) - A project can also be **associated with an Organization** (for access/visibility and grouping) This means you can, for example: - Keep two divisions from seeing each other's projects using Organizations - Still run payroll under multiple different legal entities using Production Entities ## Common scenarios ### One company with multiple divisions (access control is the goal) **Example:** A studio has separate teams (Commercials vs. Unscripted) and wants each team to see only their own projects. **Use:** Organizations (OUs) - Create an organization for each division - Assign projects to the right organization - Assign users to the organization(s) they should access ### Scenario: Multiple EINs/legal entities (legal + payroll routing is the goal) **Example:** A studio operates multiple legal entities and needs each show's payroll under the correct EIN. **Use:** Production Entities (PEs) - Create a production entity for each legal entity - Assign each project to the correct production entity ### Scenario: Both divisions and multiple legal entities **Example:** A parent company has multiple divisions, and each division operates multiple legal entities. **Use:** Both - Organizations: set who can see/manage which projects - Production Entities: set which legal entity is responsible for payroll on each project ## What Organizational Hierarchy is *not* Organizational Hierarchy is not designed for: - Combining **unrelated businesses** into one Wrapbook company - Creating complete "isolation" like separate companies across entirely separate clients If productions do not roll up to one parent company, you may need **separate Wrapbook companies**. ## Where to manage these settings ### Manage Production Entities Navigate to **Company settings** and look for **Production entities**. To learn more, see [About production entities](/v1/docs/about-production-entities#access-production-entities). ### Manage Organizations (Organizational structure) Navigate to **Company settings** and look for **Organizations** under Permissions and Access Control. To learn more, see [About organizations](/v1/docs/about-organizations#access-organizations). Employer Identification Number: Federal tax identifier used to identify a business (Federal Tax Identification Number) Official identification number, often a Social Security or Federal ID number, used for tax reporting.