Skip to content

Projects

Who can use it: Super Admin and Project Manager create and manage projects. Everyone sees the projects they’re on.

A project is a piece of work for one client. It has its own team, docs, features and settings.

Ravi creates the Harbor Ordering App for Harbor Foods, adds Meera, Arjun, Lena and Tom to the team, and sets up three modules: Catalogue, Cart and Orders. Six months later the app goes live, and Ravi marks the project Completed. Every AI token for the project stops working at that moment.

flowchart LR
    N["Create project"] --> T["Add the team"]
    T --> D["Docs created<br/>automatically"]
    T --> M["Set up modules"]
    D --> F["Write features"]
    M --> F
  1. Go to Projects and select New project, or start it from the client’s Projects tab.
  2. Pick the client, name the project and fill in the details.
  3. Save. NorthFloe takes you to the project’s team, and the eight project docs are ready to fill in.

Open the project’s Team page to add or remove people.

Who Added to projects?
Architects, Developers, QA Yes: they only see projects they’re on
Client users Yes, from this project’s client only
Super Admins, Project Managers No: they already see every project

Settings → General (Super Admin and PM) holds the name, description, start date, budget and status.

stateDiagram-v2
    direction LR
    [*] --> Active
    Active --> OnHold: Pause
    OnHold --> Active: Resume
    Active --> Completed: Finish
    OnHold --> Completed: Finish
    state "On hold" as OnHold

Completing a project revokes every AI token for it.

Modules are the product areas of a project, such as Catalogue, Cart or Orders. Tag each feature with one or more modules, then filter the feature list by module.

  1. Go to Settings → Modules and add a module with a name and short description.
  2. On a feature, select Add modules and tick the ones it touches.
  3. On the feature list, filter by module, or by “no module” to find untagged features.

In the example, REQ-4 Reorder a past order is tagged Orders and Cart. Tagging never changes a feature’s requirement or sign-offs. An archived module stays on the features that already have it, but you can’t use it for new tags.