Projects

Projects and their members.

Who can use this page

Everyone who is signed in can open Projects. You only see projects you’re a member of.

Seeing every project: View projects (view_project). By default that is the Project Administrator.

Creating a project: Add projects (add_project), held by the Project Administrator.

Managing a project: Edit projects (change_project), or being that project’s project manager. Only the project manager can wind a project up.

Superusers can do everything. Your administrator can also give the permissions to a custom role.

Projects record who owns a piece of work, who is on the team, its timeline and where team standups are sent. A project can be a Project or a Product, and internal or external.

Why projects matter for standups

When someone on a project submits their standup, Peoplance also posts it to that project’s Slack channel, so the team can follow along. This only happens when:

• the project is Active,
• the project has a Slack channel connected, and
• the person is a member of it on the date of the standup.

A person who is on several projects is posted to each project’s channel. If a standup is changed later, its Slack message is updated. A Slack channel can belong to only one active project at a time. See My standup.

The project list

Each row shows the project name and status, its project ID, the manager, how many members it has, and the due date (or “No due date”). Select a row to open the project.

Use Find a project to search by name, ID or manager, and the Status filter to show All statuses, Active or Closed.

If you’re not on any project, the page says there are no projects yet. Project administrators can create the first one.

Open a project

The project page shows:

• The name, project ID, whether it is Internal or External and its type.
• Project manager, Team, Due date and Slack delivery at a glance.
• About this project: the description.
• Team: each current member. Project managers and administrators can Add members.
• Timeline: the start date, the due date and, for a closed project, when it was closed.
• Slack delivery: the connected channel, or “No Slack channel is connected yet”. Managers can Connect a channel or Change Slack channel.
• Record information: the project ID, a legacy identity code (for imported projects), and when it was created and last updated.

If you open a project you don’t belong to, you’ll see “Couldn’t find this project, or you don’t have access to it.”

Create a project

For project administrators.

1. Select Create project.
2. Enter the Project name. This is required.
3. Choose the Type: Project or Product.
4. Tick Mark as internal if it is internal work. Leave it unticked for external client work.
5. Leave Legacy code blank. It is only for imported projects, and a code is otherwise generated for you. The Generated project ID is shown for reference.
6. Add a Description if you like.
7. Choose the Project manager. This is required.
8. Set the Start date, which is required, and an optional Due date.
9. Add Additional members if you want. You choose them from a list of people.
10. Save the project.

Manage a project

Open the row’s Actions menu (project administrators and the project’s manager, on active projects only):

• Manage project opens the same form to edit the details and the members.
• Connect Slack or Change Slack picks the project’s Slack channel. Choose Do not send project standups to disconnect it.
• Wind up project closes it (project manager only).

Add members

On the project page, select Add members, tick the people to add and confirm. A message tells you how many were added. Memberships have dates, so a person’s history on the project is kept.

Wind up a project

Winding up closes a project for good. Select Wind up project, then type the project’s name exactly to confirm.

When a project is wound up:

• Future standups stop being sent to its Slack channel.
• All memberships end, as of that day.
• The project becomes read-only.
• Existing records stay available.

A closed project shows Closed in the list and no longer has actions.

Default standup project and optional updates

A person may belong to several projects while sending their daily standup to one Default standup project. One active assigned project with a configured Slack channel is selected automatically. If several are eligible, a person manager must choose; if none are eligible, ask a person manager to check membership dates, project status and Slack configuration. Saving an update still works while routing is unresolved; it is not broadcast to all projects.

Person managers can review these settings in the person's detail view and in the project's team list. Manage standup settings opens the controls; Review changes names the person, current destination and new destination before Save standup settings applies the change. Cancel leaves the saved policy untouched. Project management alone does not grant permission to override another project's default. Employees cannot exempt themselves.

Standup required → Optional makes updates optional from today in the organization's timezone. Time tracking and attendance hour thresholds still apply. When ending the day, choose Submit update & end day or Skip update & end day. Blank skips create no standup; skipping a written draft requires discard confirmation. Failed requests preserve the draft. Voluntary updates remain visible and use the same validation and default-project routing as required updates.

Optional dates are Not required, rather than missing, in the team overview and are excluded from missing-standup alerts and reminders. Earlier dates retain their expectations. Requiring updates again starts from the change date. Changes record the editor, prior policy and effective date; a stale edit must be reloaded and reviewed again. Open tabs refresh policy on focus and periodically.

Changing a default does not replay earlier updates or redirect an already queued delivery. Each saved standup keeps its original destination (including unresolved routing); retries use that recorded destination. Existing memberships are preserved on upgrade, and unambiguous single-project defaults are initialized without sending Slack messages. A default that becomes unavailable falls back only to a sole eligible project; otherwise a manager must choose a replacement.

When Slack is disconnected, the settings show a warning asking an integration administrator to reconnect it. Saving an update remains available.