Help
Go to aliteo.com
Notifications > Notifications > Project and team notifications

Project and team notifications

Notifications at the project and team level provide an overview of key changes, new tasks, documents, and meetings within the given unit. All notifications generated by a project or team are delivered exclusively in-app to the right notification panel – email and Push notifications are never sent for project and team activities.

Activation and general conditions

  • Manual activation (bell icon) – detailed notifications on a project or team are never enabled automatically. Each member must activate them manually by clicking the bell icon in the top-right corner of the project or team header.
  • Projects in Plan status – while a project is in the Plan status, the system suppresses routine operational notifications (with the exception of notifications regarding changes to the project status itself).
  • Automatic removal upon member removal – if a user ceases to be a member of a project or team (and is not a member through any user group), their detailed notification subscription is automatically turned off.

Notifications without detailed notifications enabled

If a user does not have the bell icon enabled on a project or team, they do not receive routine project notifications. Two system events delivered based on role responsibility are exceptions:

  • Subteam connection or disconnection request – the administrator of the parent project receives an in-app notification regarding requests to link or unlink a subteam.
  • Gantt planning conflict – users with project planner permissions receive an alert when a scheduling conflict arises in the Gantt chart.

Notifications with detailed notifications enabled

Project or team members (both internal and external) who have enabled detailed notifications (the bell icon) receive in-app notifications in the right panel for the following events – provided they have access permissions to view the given object or task:

  • New task creation – notification when a new task is created in the project or team. If the user has already been notified directly at the task level (for example, as the assigned solver), a duplicate project notification is not sent.
  • Task closure, cancellation, or reopening – notification when a task transitions to or from the Closed or Canceled status.
  • Task archiving, deletion, restoration, or move – notification when a task is moved into or out of the project, or when it is archived, restored, or deleted (in a team, also when a task is linked or unlinked).
  • Expected reaction from the project or team – notification when a task is set to Waiting for reaction directed at the entire project or team.
  • Project documents – notification when a project document is added, archived, or deleted in the project documents tab (this does not apply to regular attachments uploaded to individual tasks).
  • Project meetings – notification when a meeting is created or deleted within the project.

Events reserved for project and team administrators

Certain configuration changes require higher permissions, and notifications for them (with the bell icon enabled) are delivered exclusively to project or team administrators (external users cannot be project administrators and therefore never receive these notifications):

  • Membership and permission changes – adding or removing a project or team member, changing Administrator or Supervisor privileges, and changing member type.
  • Project settings and property changes – changing the project owner (manager), visibility, project status, and risk evaluation (deadline, quality).
Was this information helpful?

Can't find what you were looking for? Contact us

4986

Copyright 2024 KARAT Software. All rights reserved