Project Hub

How to structure your projects, sites, and sub-sites — and who can access what.

The hierarchy

Pranaalika Nirman organizes work in a three-level structure:

  • Organization — your company, the top-level container
  • Project — a single contract or development (e.g., "Krishna Heights")
  • Site — a physical location within a project (e.g., "Block A")
  • Sub-site — a structural unit within a site (e.g., "Tower 1, Floor 3")

You do not need to create all four levels for every project. A single-site contract can have just Project → Site. Use sub-sites when you need to track work at a finer granularity (per tower, per floor, per zone).

Creating a project

  1. Go to Projects from the main navigation
  2. Click Add Project
  3. Fill in: name, type, location, scope, expected timeline, estimated budget
  4. Save — the project is created and shows up in the Projects list
Project metadata
Estimated budget at this stage is just a marker. Detailed budget setup happens inside Cost Control (coming soon).

Adding sites and sub-sites

From inside a project, go to the Sites tab and click Add Site. For each site, you capture:

  • Site name (e.g., "Block A")
  • Site address or coordinates
  • Site type (e.g., Residential, Commercial, Infrastructure)
  • Site supervisor (assigned from your organization users)

To add a sub-site, open the parent site and click Add Sub-site. Sub-sites inherit the parent site's metadata by default but can be customized.

Files and documents

Each project has a Files tab where you can upload drawings, contracts, approvals, and other reference documents. Documents are scoped to the project — everyone with access to the project can see them, subject to their role.

Site-specific documents (e.g., site-level drawings, site survey reports) live at the site level and are visible only to users with access to that site.

Roles and access

Pranaalika Nirman uses four roles at the organization level:

  • Admin — full access to everything in the organization, including billing and user management
  • Manager — full read and write across all projects; can manage projects but not billing
  • Engineer — read and write within projects they are assigned to; can create DPRs, log issues, manage attendance
  • Viewer — read-only access across the projects they are added to

Roles can be assigned organization-wide, and you can further refine access per project. For example, a manager may have access only to projects in a specific region.

A note on AI access
AI Reports and AI Assistant access follows the same role model. A Viewer cannot generate a Cost Control report. AI Insights for budget anomalies are visible only to Admins and Managers by default. (This will be configurable in a future release.)

Archiving and closing projects

Projects you are no longer working on can be archived. Archived projects no longer count toward your plan's "active project" limit (see pricing). Archived data remains accessible — you can read DPRs, reports, and files from any archived project.

Closing a project is a stronger action that prevents any further data writes. Use this when a contract is fully done and you want to preserve the final state.

What is next