Page tree
Skip to end of metadata
Go to start of metadata

Title: Organization Naming Conventions

Brief description:

This document illustrates the use of organizations in Unanet and best practices to use an Organization Naming Convention in Reporting and Organizational Access.

What’s covered in this document:

Organization Purposes

Organizations are used in Unanet to structure people and projects. They can be thought of as a hierarchy level that sits above the Person or the Project Code. Organizations can be leveraged for two basic functions:

  1. Reporting - Project, People, and Resource Reports can be filtered using Organizations to run reports across multiple projects, clients, or teams.
  2. Access - Unanet Organizational Access allows an administrator to give access to People, Projects, and Resources across multiple projects, clients, or teams.

Examples and steps to set up Organizations

  1. Set up Organization Types to separate people-based organizations from project-based organizations. (Admin > Project > Organization Types)
    1. Examples or Organization Types:
      1. Employee (people) and Project (projects)
      2. People (people) and Clients (projects)
      3. Employee (people) and Customer (projects)
  2. Consider naming conventions that would help your company use Organization for Reporting and Access. Examples:
    1. Begin Government client project orgs with GOV_ and Commercial with COMM_
      1. GOV_USDA, GOV_DOE, GOV_Dept_of_Education
      2. COMM_Unitil, COMM_Raytheon, COMM_Acme_Company
    2. By beginning an Organization name with a standard such as GOV or COMM or the name of a client with multiple projects in Unanet, reports can be filtered by Organization using a wildcard search, e.g., MYCO%. The % symbol represents a wildcard in Unanet.



  3. Set up Organizations with the appropriate Org Type and naming convention.
    Note: If Parent Org is going to be used, Parent Organizations will also need to be set up.
    Note: Parent Org is not available in all Unanet reports, so a standard naming convention for clients/customers or client types can be helpful in using Project Org or People Org to filter report criteria.



  • No labels