About Projects

A project is a process for attaining a specified goal or objective. This section describes how to create and work with projects, including working with project concepts, dashboards, and project visibility.

This page discusses:

Project Security

There are various levels of security associated with projects and their tasks that determine who can view project and task information. Security is controlled at the project level. When Project Leads create a project, they use the Project Visibility option to define whether the project is visible to all employees of their company or only to project members.

A higher level of security is Project Ownership security. The person who creates the project is the project owner. Only one user can own the project. The project owner has all access, including the ability to delete the project and reassign ownership to another user.

The Project Lead for a project can delete the project and change its ownership.

Project Membership is the higher level of security. Being a project member means:

  • The project is listed on your Projects page (unless you are a member only because you are assigned to a role or group that is a member). As a member of a project you get access to tasks in the project.
  • For app-specific users, you can be assigned a role that lets you edit certain attributes of a project. For example, a Project Lead can create/edit the project task. For projects with Member visibility, you and other explicitly added members to the project are the only people who can access project information.
  • For baseline users, if a member-visible project is created when you are logged in with a organization/collaborative space, the project is stamped with that organization/collaborative space. All users belonging to that organization/collaborative space are given access to the project according to the user's access in that collaborative space.

A task can be assigned to a nonmember of the project or to any member of the project. Task assignees have the following access:

  • View their task and the task parent (project).
  • Add subtasks. The assignee may or may not be the owner of the task.
  • Remove subtasks. The assignee is the owner of the task or has lead access in the project.
  • Create on-demand routes on their tasks.
  • Delegate their assignment to someone else in the project membership. The assignee has lead access in the project.
    Note: Assignees cannot delete the top-level task assigned to them.

Project Scheduling

You can schedule a project by estimated or actual dates.

When you create a project, calculates the finish date based on the project's start date and the schedule.

Some projects may require a specific finish date that does not slip. For example, in the apparel industry, cloths must be available in retail stores on predetermined dates that must be met.

Both methods of scheduling are supported.

Calendars

A project can have multiple calendars used to accommodate different work schedules and locations. Only one project calendar is the default calendar, which is used for project scheduling. A task can have only one calendar associated with it.

Below is the priority level for evaluation of calendars (from the lowest level up):

  • Calendar connected to the task
  • If the task has a single assignee, the calendar connected to the assignee’s location is considered for scheduling (if defined).
  • Default project calendar (if defined)
  • System default calendar (8-hour day with Sat/Sun as nonworking days)