Projects and Jobs
Projects give PA a central place for work that spans more than one document or client contact.
What a Project Can Hold
- Primary client or organization
- Additional clients
- Department context
- Quotes, contracts, invoices, and project invoices
- Files and external links
- Project notes and status
- Public project access settings
- One primary Project Manager and a Project Team
- Optional work planning (currently paused with the workforce workflows)
Project Manager and Team
Each Project may have one primary Project Manager. Selecting a manager keeps that user on the Project Team. Replacing a manager leaves the former manager as an ordinary Team member until an administrator ends that membership.
PA no longer asks for an internal Business Unit or Division when creating or editing a Project. New projects do not inherit an internal division from the manager or a global default. Customer organizations and their departments remain separate and unchanged. Historical internal division IDs are retained as compatibility data until connected integrations complete their authority transition; editing a project does not reassign that historical scope.
The experimental Team & Work workforce workflow is paused. Its stored Team, Operation, and Task data is preserved. Operation and Task assignees must be active Project Team members. Open assignments must be resolved before a Team member can be removed.
Public Project Links
Project links are long-term public links. They can be view-only or allow limited actions such as uploads, depending on ACL settings. A project link can also be protected by a single password set in project settings.
Organizations and Departments
If an organization has no departments, PA can use the overall organization folder. When departments exist, PA switches to department-specific linking so records stay in the right place.
When to Use Projects
Use a project when work has multiple documents, shared files, multiple contacts, or a job code that should stay visible across the workflow.