Skip to main content
Most contractors run one procurement manager for the company and a buying team per project. Project teams let you record that structure so notifications land on the person actually responsible for the site, instead of every PM in the organization. Two things are set per project, in Settings → Organization → Projects:
  • Responsible PM — the manager who owns that site.
  • Team members — the buyers and PMs attached to it. Somebody can be on several projects.

​
What the responsible PM changes

When something on a project needs a PM’s attention, the notice goes to that project’s PM rather than to everyone.
This affects who gets notified, not who is allowed to approve. Approval authority is unchanged: any active PM can still sign off on anything, exactly as described in Approvals. Naming a responsible PM narrows the noise, not the permissions.

​
What team members change

Membership is used for convenience, in two places:
  • Suggesting who to assign work to on that project.
  • The My projects filter in the trackers, which narrows the list to the sites you’re on.
It does not restrict anything. A buyer who is not a member of a project can still see and act on its records if their role allows it — the filter is a shortcut, not a wall.

​
Rules

  • Only buyers, PMs and admins can be on a team. Requestors are not team members.
  • The responsible PM must hold the PM or admin role.
  • Only active users count. Deactivating someone removes them from the team’s effective membership without you having to edit each project.
Project teams are entirely optional. With no PM named and no members added, Seloria behaves exactly as it did before — every PM is notified about everything.

​
Where to see it

Settings → Organization shows the organizational tree with each project, its responsible PM and its members, and lets you edit a team from there.