AIUNIFY CRM allows authorized Project users to manage the members participating in a Project and the Project-specific features available for the work.
These controls apply to the individual Project. They are not a replacement for organization-wide user or role management.
The Project view includes a Project Members workflow.
Members should represent the staff users who actually participate in or require access to the Project according to your organization's operational process.
Before changing membership:
Project membership can affect which staff members participate in Project work and how related Tasks, time, discussions, files, and other Project activity are coordinated.
Do not add users merely to make information easier to find if they do not require Project participation.
The Project model contains a defined set of Project features that can be made available within the individual Project.
Depending on the Project and the controls presented to your user account, available feature areas include:
Later chapters explain the major Project workspaces in detail.
The Project also defines task-related customer collaboration options that can include:
These options are Project-specific customer collaboration controls and should match what the Customer is intended to see or do within that Project.
The interface links several Task options to the broader View Tasks choice.
If Task viewing is disabled for the Project's customer-facing experience, related customer Task creation, editing, commenting, attachment, checklist, upload, and logged-time options are correspondingly restricted by the Project form.
This prevents a dependent Task capability from remaining enabled when the underlying Task view is unavailable.
The Project feature set includes the ability to expose supported Project file functionality where applicable.
Before sharing Project files, verify that they belong to the correct Customer and are appropriate for the intended Project participants.
Projects can expose a discussion area when that feature is available.
Use Project Discussions for collaborative conversation that should remain associated with the Project instead of moving Project context into unrelated records.
The Project can expose Milestones to represent significant stages or target points in the work.
Milestone operations are covered in the next Project chapter.
The Project feature model includes Gantt visibility where enabled.
The Gantt view provides a time-oriented representation of Project work and is covered with Project planning operations in the next chapter.
Timesheet visibility can be made available as part of the Project feature set.
Project time tracking and Timesheets are covered in a dedicated later chapter.
The Project feature set can include a financial overview where applicable to the Project's workflow.
Only users with the appropriate access should rely on Project financial information. Detailed Project Expense and Invoice workflows are documented later in this manual.
The Project can expose its activity history so authorized participants can review significant Project events.
Use the activity history as supporting context. Make corrections in the underlying Project, Task, file, time, or financial record rather than trying to alter history indirectly.
The Project feature set can include team-member visibility for the customer-facing Project experience.
Enable or retain that visibility only when it matches the intended collaboration model for the Project.
Before sharing Project access or relying on the customer-facing Project workflow:
Operational principle: Give Project participants access to the information and collaboration features required for the work while keeping unrelated or sensitive Project information outside their intended visibility.