Developer mode · Entra configuration required
CHRP-INDIAMenu

HELP & TUTORIAL

Learn how Workstream works

A practical guide based on the access currently assigned to you.

Back to overview
YOUR ACCESS

Checking your workspace…

Only guides and destinations available through your permissions are shown here.

Before you beginViews follow organization, department and project scope.Important changes may require confirmation and a reason.

YOUR DAILY WORKSPACE

Complete your everyday work in one place

Track attendance, delivery work, leave and time without switching between separate systems.

  1. 1

    Start with Overview

    Review assigned work, deadlines, project progress and current workforce status.

    Open overview →
  2. 2

    Record attendance

    Check in and out, then review your daily attendance history and exceptions.

    Open attendance →
  3. 3

    Work on projects

    Open accessible projects, update tasks, add activity and collaborate with participants.

    Open projects →
  4. 4

    Submit leave and time

    Request leave, check balances and complete weekly timesheet entries before submission.

    Manage leave →
  5. 5

    Keep your profile current

    Review your employee identity, job context and notification preferences.

    Open profile →

PROJECT DELIVERY PROCESS

From business outcome to completed work

Create the delivery lifecycle first, place functional modules inside each phase, and then break modules into executable tasks and subtasks. Portfolio and release mappings remain optional.

ProjectEpic / DeliverableFeature / Work packageTaskSubtask

Execution hierarchy: Project → Phase → Module → Task → Subtask. Sprints, milestones, assignees and dependencies provide additional tracking.

  1. 1

    Create the project

    Choose the owning department, participating departments, dates, priority and client profile when it is client work.

  2. 2

    Define outcomes

    Add an Epic / Deliverable for each major business outcome, then place Features / Work packages under the relevant epic.

  3. 3

    Plan delivery

    Create Sprints / Releases for time-boxed delivery and Milestones for important target dates or approvals.

  4. 4

    Build the delivery structure

    Create lifecycle Phases first, then add Modules inside the relevant phase before planning tasks and subtasks.

  5. 5

    Assign the team

    Add team leads with Manage or Contribute access and add delivery members for assigned work. A newly assigned member receives a bell notification and email with the project link.

  6. 6

    Delegate scope ownership

    The project manager assigns each Module or Feature to an active project member, normally the responsible team lead. Every reassignment requires a reason and is retained in ownership history.

  7. 7

    Break down work

    Create Tasks inside the selected Phase and Module, then add Subtasks. Epic, feature, sprint and milestone mappings remain optional.

  8. 8

    Track execution

    Maintain status, priority, assignee, activity, dependencies, estimates, due dates, comments and actual time.

  9. 9

    Close with evidence

    Complete open child work, review history and progress, then move the project through its controlled lifecycle.

WORKED EXAMPLE

Employee Training Platform

Phase
Development
Module
User management
Task
Build registration workflow
Subtasks
Registration UI · API validation · Unit tests

OPTIONAL MAPPINGS

Epic
Employee onboarding
Feature
Self-service registration
Sprint
Sprint 03
Milestone
Internal beta

PM → TEAM LEAD → TEAM

Controlled delegation and assignment

The project manager remains accountable for the complete project while team leads control only the delivery scope assigned to them.

Project ManagerModule / Feature ownerTeam task assigneesStatus & activity updates
  1. 1

    Add the team lead

    Open Team and add the DXF team lead with Contribute access for scoped delivery or Manage access when they must manage project membership. The lead receives an in-app alert and email.

  2. 2

    Create the phase

    Create the lifecycle stage first—for example Development, Testing or Deployment—and provide its planned dates.

  3. 3

    Create and assign the module

    Create User Authentication inside Development, then select the active team lead as Scope owner. A person outside the project team cannot own it.

  4. 4

    Plan team work

    The module owner creates Tasks and Subtasks in the owned module and assigns them only to active project members. Each task retains its phase and module context.

  5. 5

    Track and audit delivery

    Members update status, activity and time. The project manager monitors progress, blocks and overdue work; administrators review organization-wide detail and ownership history.

EXAMPLE

DXF delivery

Project manager
Akash Rai
Phase
Development
Module
User Authentication
Module owner
Sandeep Yadav · Lead Full Stack Developer

ACCESS RULE

Clear accountability

Project Manager
Plans and manages the complete project
Team Lead
Creates and assigns work within owned scope
Team Member
Updates assigned work and activity
Administrator
Views organization-wide delivery and audit evidence
Open projectsProject managers configure the plan; members update assigned work within their access.

GOOD TO KNOW

Access looks different for every person

If a menu or action is missing, your current role or scope does not grant it. Contact an administrator when your responsibilities change.

Review my profile