PMO · PSA · ITSM — deliver projects, services & support in one hive.
| Country | Client | Month/Year | Value ($) | Actions |
|---|
| Location | Department | Client | Project | Milestone | Payment Due Date | Days Overdue | Value ($) | GP ($) | Risk |
|---|
| Country / Client | Avg Days |
|---|
| Country | Customer | Start Date | End Date | Jan | Feb | Mar | Apr | May | Jun | Jul | Aug | Sep | Oct | Nov | Dec | Grand Total |
|---|
| Country | Customer | Start Date | End Date | Jan | Feb | Mar | Apr | May | Jun | Jul | Aug | Sep | Oct | Nov | Dec | Grand Total |
|---|
| Country | Customer | Pln Comp Date | Jan | Feb | Mar | Apr | May | Jun | Jul | Aug | Sep | Oct | Nov | Dec | Grand Total |
|---|
Track resources, hours, and ad-hoc work per project across January, February & March
| Country | Client | Project | Estimated Time | Total | January | February | March | April | May | June | July | August | September | October | November | December | Total MD Cost | Total GP | GP vs Cost | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Mgmt MD | Tech MD | Mgmt MD | Tech MD | Mgmt MD | Tech MD | Mgmt MD | Tech MD | Mgmt MD | Tech MD | Mgmt MD | Tech MD | Mgmt MD | Tech MD | Mgmt MD | Tech MD | Mgmt MD | Tech MD | Mgmt MD | Tech MD | Mgmt MD | Tech MD | Mgmt MD | Tech MD | ||||||||
Hours allocated per project per month — syncs to Team Effort
| Country | Client | Project | Estimated Time | January — Hours | February — Hours | March — Hours | April — Hours | May — Hours | June — Hours | July — Hours | August — Hours | September — Hours | October — Hours | November — Hours | December — Hours |
|---|
Individual resource hours per project per month — resources auto-populated from Settings
| Resource Name | Department | Project | Jan | Feb | Mar | Apr | May | Jun | Jul | Aug | Sep | Oct | Nov | Dec | Total | Actions |
|---|
Submit weekly project and SLA hours for manager approval
Pending submissions from resources reporting to you
Activity effort by project and role level
Fill and review weekly timesheets per resource
Open a project to manage its task board. Active projects are listed automatically (SLAs excluded).
Everything scheduled across your projects. Click any day to add a task — managers can assign it to their team, and public holidays show per country.
Track potential projects currently being negotiated
| Location | Department | Client | Project | Assigned To | Description | Est. Value ($) | Probability (%) | Expected Close | Status | Notes | Actions |
|---|
Your account details and access. To change your password, enter your current one first.
Choose a strong password of at least 8 characters. Changing it signs out your other devices.
Upload your signature once. It is applied automatically when you approve an expense and when you issue a completion certificate, so you don't have to attach it each time.
The name shown in the browser tab and as the app title.
Enable the sellable modules available in this installation. Disabled modules are hidden from navigation and blocked at the API layer.
At least one module should remain enabled so users have a landing page.
Toggle columns on/off for the milestones table.
Select the last column that should remain visible when scrolling horizontally.
Add custom columns to the milestones table.
Add or remove departments used across projects and resources.
Add or remove countries/locations used across projects and resources.
Add, rename or remove the categories shown in the Expenses entry form. Categories already used on existing expenses always remain selectable.
Each client's Account Manager automatically receives SLA renewal reminders. AM email is pulled from their resource profile. The Contact Email is used in Support Tickets to send emails to the client. You can also define the organization and whether portal updates can be shared with additional contacts.
Add team members with their details.
Users who sign up with these email domains are added to the Resource Directory automatically.
Configure which day the work week starts. Used for the Weekly Timesheet.
Categories used for project activities (one per line, order preserved). Only managers and administrators can edit.
Activities automatically added to every project — existing and newly created (one per line). Only managers and administrators can edit.
Click any cell to edit inline. Changes are saved automatically on blur.
| Name | Department | Location | Phone | Job Title | Level | Actions |
|---|
Select a resource to view and edit their project allocations.
Create support groups (like departments) and assign resources to each group. Groups can be assigned to tickets for better routing and filtering.
Build the reporting tree from the regular users list.
Public holidays are per country, because a task is only moved by holidays for its own project's country — an Omani holiday never shifts a Lebanese task. Leave the country blank to make a holiday apply everywhere. When a task you create or edit would start or finish on a holiday or a weekend, it slides to the next working day and keeps its duration. Tasks you don't touch are never rewritten.
| Date | Name | Country |
|---|
The Gulf works Sunday–Thursday; Lebanon works Monday–Friday. These days are treated as non-working when a task's dates are pushed.
Configure the kanban stages used on every project's task board (same idea as the support ticket stages). The Done stage is fixed as the last stage — it drives the completion percentage.
Rename the standard folders every project gets, or add your own. Renaming moves the folder on disk for every project; generated documents (MOM, Weekly Report, Certificates) keep landing in the right folder after a rename. Standard folders can be renamed but not removed; removing a custom folder only hides it (files stay on disk).
The Weekly Report and Minutes of Meeting project lists show active, non-SLA projects only. Add exceptions here to force-include a specific SLA or project (e.g. a closed project, or an SLA you report on).
All outbound email settings are managed here. Each tab corresponds to a specific module.
Configure your outgoing mail server. Reminders are sent automatically to management and the account manager of each expiring SLA milestone.
The email goes to the resource's address (from the Resources directory). Requires SMTP above to be configured.
Define SLA service items that can be linked to milestones.
Configure the outbound SMTP server used to send ticket emails.
Configure your IMAP inbox to automatically create tickets from inbound emails and route client replies back into the correct ticket's chatter.
[TKT-XXXXXXXX-XXX]) → threaded into the ticket's chatterSet a separate account to send Forgot Password & Email Verification emails. Uses the same SMTP host/port as the SLA config but authenticates as this account. Leave blank to use the main SMTP account.
Recent changes made to milestones and project data.
| Timestamp | Username | Action | Table | Record ID | Field | Old Value | New Value |
|---|
Recipients for the automated weekly summary (Mondays 08:00) and daily payment-due reminders (09:00). Leave recipients blank to keep automatic sending OFF.
Set the monthly GP target used in the Weekly PMO Report (Budget Status table).
Everything still sitting in a Deleted stage — Projects-module tasks and Support tickets. Select items (or use Select All) and purge them permanently. This cannot be undone.
Export your data for backup or transfer, or import a previously exported file.
Set the monthly GP target used in the Weekly PMO Report (Budget Status table).
These actions are irreversible. Please make sure you have a backup before proceeding.
Add, remove and reorder the stages used in the Support Tickets module. Drag the ⠿ handle to reorder.
Configure the automatic email sent when a ticket reaches each stage. Type / inside a subject or template to insert ticket objects like person name, ticket number, client, and project.
Add, remove and reorder the ticket types used when creating or classifying tickets (e.g. CR, Bug, Issue, New Request).
Manage the request types shown in the support catalog and the dynamic fields users complete when creating tickets.
Define who must approve this request type before work can continue.
Types: text, textarea, select, number, date, datetime-local, checkbox.
Register business services, model service dependencies, and maintain linked support assets.
Configure the embeddable support widget that accepts website messages and creates support tickets automatically.
Paste this script on any website where you want the support launcher to appear.
Configure the customer-facing login portal used to create tickets, track all requests, and reply inside one workspace.
Send this to new customer contacts so they land on the login and signup page with the join request link already applied.
Send the first-time join link directly to a customer contact so they can create a portal account.
Create support articles that can be suggested automatically in the customer portal.
Define response and resolution time targets per priority level. These are applied automatically when a new ticket is created.
Create shortcut responses that agents can insert by typing /shortcut in the ticket chatter.
Automatically escalate tickets based on inactivity. Rules run every 15 minutes.
Configure global options for the support portal.
Example: https://support.yourcompany.com
Configure automated email reminders for expiring milestones. Each tab manages rules for a different milestone type.
Automated reminders are sent when an SLA milestone is within the specified days of expiry. The 3 default rules below are always active.
Automated reminders are sent when an Outsource milestone is within the specified days of its planned completion date. Configure your rules below.
Approve or reject pending user registrations and manage existing users.
Control what each role can see and do across the system.
| Permission |
Super Admin
|
Admin
|
Manager
|
User
|
|---|
Fill in the project details and add its milestones below.