Open topic with left hand navigation

About Projects

In Proliance, a project is grouping of Proliance documents that encompass tasks that are more limited in scope than a Proliance workspace. Compared to standard Proliance workspaces, projects typically involve fewer resources and are completed over a shorter period of time.

Proliance documents become part of a project when they are linked to a project document. In the same way, Proliance users also become part of a project by being linked to a project document. Depending on their security settings, only users who are part of a project can work with the documents in that project. Access to projects can also be further qualified by project team roles.

Projects do not have their own work area. Instead, projects are managed within a Proliance workspace. A standard Proliance workspace can contain one or more projects. Only managed workspaces (workspace within a portfolio) can use projects.

By default, project functionality is disabled. To enable project functionality in Proliance, create the first project document in the Projects register.

Project Linking and Access Permissions

Access to project documents is controlled by a user's link to that project, set on the Projects tab of the user's contact document. The Project tab on a user's contact document controls whether the user has Project security applied to them. If they do, they can only work with documents that are linked to the same projects they are linked to. For more information about the Project tab on staff and contact documents, see About Contacts and the Projects Tab.

Project security is a subset of a user's overall account permissions, which takes precedence. For more information about project security, see About Project Security Permissions.

Project Linking and Documents with Child Documents

In Proliance, many documents have a number of related child documents. For example, company documents have related insurance, location, bond and certification documents. In these cases, the child documents must have a project link in common with the parent document. For example, if a location document has a link to a particular project, the parent company document must also have a link to the same project.

Project Linking and Documents with Related Items

Some Proliance documents have tightly coupled business logic that requires that they have projects in common. For example, contract and invoice documents, by the nature of their relationship, must be part of the same set of projects: an invoice cannot be part of a project without the related contract also being linked to the same project. Likewise, their allocation line items must also be linked to the same project.

Project information is organized under the following pages:

• Main: Contains a general overview of the project, details, its classifications, important dates, document information, and user defined fields. For more information, see "Projects - Main".
• Properties: Contains the properties of the project document. This includes the name of the user who created the project and the date when it was created. For more information, see "Document Properties".

Additional workspace information is also available on the following tabs:

• Workflow: Enables you to see where the document is in its lifecycle, who has already performed actions on the document, and who will receive notification when the document changes to a specific state. For more information, see "About the Workflow Tab".
• Activity Log: Records all the activities of a workspace properties document, such as when it was saved, imported, exported, forwarded, or received. For more information, see "Activity Log Tab".
• Attachments: Contains a list of all the documents related to this workspace properties document. For more information, see "Attachments Tab".

To open a Project document

1. Open the Projects register.
2. Select the project you wish to view.

Proliance opens the document in Read Mode.