Site Settings
Configure your Completix environment from a single place. Site Settings control which features are active, how the platform behaves, what labels and taxonomies are available, and how warnings, approvals, and dashboards are configured across every project.
Site Settings is the central administration area for your Completix environment. It is accessible to site administrators from the main navigation and contains eight sections, each governing a distinct aspect of how the platform behaves across all projects and users.
The left-hand sidebar lists all available sections: General, Features, Options, Labels and Categories, Dashboard, Custom Fields, Trigger Warnings, and Policies. Clicking any item opens its configuration panel on the right without leaving the settings modal.
Changes saved in Site Settings apply immediately and site-wide. Individual projects can override some defaults (such as label colours and field structure) for their own context, but the values defined here serve as the baseline for every new project created on the site.
Features
The Features panel lets administrators turn product capabilities on or off across the entire site. Disabling a feature removes the associated tabs and UI elements from every project, keeping the interface focused for your team's workflow.
Each feature card shows a toggle and a short description of what it controls. Available features include Capex/Opex, Governance, Change Requests, Expenses, Resource Forecast, Resource Allocation, Project Intake, Timesheets, Budget Fiscals, Financials, Outstanding Approvals, Lesson Learned, Portfolios, and the Executive Dashboard.
Options
Options set platform-wide defaults that affect every project and user. Settings are grouped into three areas: General, Timesheet, and Financials.
General
These settings control core platform behaviour:
| Setting | Description |
|---|---|
| Allow users to update their name | When enabled, users can modify their own display name in the system. |
| Currency | Sets the default currency for all financial calculations and reports. Defaults to USD. |
| Typical hrs/week | Expected working hours per week, used for allocation planning. Defaults to 40 hrs. |
| Working week | Defines which days constitute a working week. Defaults to Mon-Fri. |
| Forecast Mode | Determines how forecast effort is computed across projects. Set to Project-determined to let each project define its own mode. |
Timesheet
Controls how timesheets are submitted, approved, and counted:
| Setting | Description |
|---|---|
| Submission period | How frequently team members submit timesheets for approval. Options include Weekly and Monthly. |
| Simplified timesheet | When enabled, team members log hours at the project level rather than per task. |
| Count actuals only when approved | Restricts budget actuals to approved timesheet entries only. |
| Approve without submission | Allows approvers to approve time entries without waiting for a formal submission from the team member. |
| Allow time outside project dates | Lets individual projects opt in to logging time entries outside their defined start and end dates. |
Financials
The Fiscal Year setting defines the start date of your financial year. The platform uses this date to compute fiscal period breakdowns across budgets and dashboards. The default is Jan 01, yielding a Jan 01 to Dec 31 fiscal year.
Labels & Categories
Labels and Categories lets you edit all of the reusable lists used across the platform. Changes made here propagate to every project on the site, providing consistent taxonomy without manual duplication.
The following lists are configurable from this panel:
| List | Purpose |
|---|---|
| Project Type | Classifies projects as billable or non-billable and defines the type of work (Client Project, Internal Project, R&D, Maintenance/Support, Change Request, and so on). |
| Governance Tags | Phase labels used in the governance process, such as Initiation, Planning, Execution, Monitoring and Control, and Closure. |
| Project Priority | Priority levels shown on project cards and dashboards, for example Critical, High, Medium, and On Track. |
| Teams / Dept | Department or team names used when assigning resources and filtering reports. |
| Titles | Resource job titles available when configuring the project team, such as DBA. |
| Sponsorship | Sponsorship roles available on projects, including Business Sponsor, Technology Sponsor, and Project Owner. |
| PM Role | Project manager role types, such as Lead PM, Infrastructure PM, and Business PM. |
| Locations | Office or site locations that can be associated with resources and projects. |
| Task Status | Status values available on tasks. Open and Closed are reserved and cannot be removed, as they power dashboard counters. |
| Risks Status | Status values available on risk log entries, with the same Open and Closed restrictions as task status. |
Each list supports adding new entries using the + icon next to the list heading. Existing entries can be renamed or recoloured directly in the list. The RAID status values you define here are reflected in the RAID log for each project.
For added flexibility, individual projects can override the default colours and structure defined here to suit their specific needs without affecting the site-wide defaults.
Dashboard
The Dashboard settings page controls what is displayed on the Executive Dashboard. Configuration is split across three tabs: Metrics, Panels, and Columns.
Metrics tab
Metrics are the individual KPI cards shown at the top of the Executive Dashboard. They are grouped into four categories:
| Group | Available metrics |
|---|---|
| General | Rating, Projects, Project Type, Tasks, Issues, Open Risks, Warnings |
| Delivery | Schedule Variance, Avg. Duration, Avg. Delay |
| Budget | Avg. Budget, Avg. Variance, Budget, Current FY |
| Warning Triggers | Project Budget Forecast, Project Budget Actuals, Project Budget FY Forecast, Project Budget FY Actuals, Schedule Finish, Project Scheduled End, RAID Task Due, RAID Issue Due, Milestone Due, Schedule Actuals, Capacity, Capacity Effort Actuals |
Use the checkbox next to each metric to include or exclude it. The Deselect All button at the top right of each group clears all selections in that group at once.
Custom Fields
Custom Fields lets you define additional data points that appear on project home pages and in the budget component. Two separate lists are available:
Project Custom Fields appear on each project's overview page and can capture any supplementary information relevant to your organisation. Available field types include Text, Date, Date and Time, Currency, Tag, Percent, Number, People, Progress, and Checkbox. The first custom field is mandatory and serves as a key identifier visible across dashboards and reports, though it can be renamed to match your terminology.
Budget Custom Fields are part of the budget component and allow you to define your own budget KPIs beyond the standard fields. These fields are also surfaced in the dashboards and can be configured in the Dashboard settings to appear in the relevant metrics and columns.
Each custom field has an enable toggle. Only enabled fields are visible on projects and in the dashboards. New fields can be added using the + icon at the top of each list.
Trigger Warnings
Trigger Warnings define the thresholds at which warning colours and indicator icons are applied throughout the platform. When a project or task reaches a configured threshold, the relevant fields and dashboard icons change colour to reflect the new status.
Triggers are organised into six groups, each expandable to reveal its detailed settings:
| Trigger Group | What it controls |
|---|---|
| RAID Triggers | Colour coding for risks, actions, issues, and decisions in the RAID log. Includes To-Do and To-Do Actuals sub-groups with separate thresholds for low, medium, and critical states, as well as at-risk and off-track conditions. |
| Schedule Triggers | Colour rules based on schedule health and how close a project is to its deadline. |
| Allocation Triggers | Colour rules for resource allocation levels, helping identify over-allocated or under-used resources. |
| Effort Triggers | Colour coding based on effort tracking and utilisation percentages. |
| Project Summary and Status Triggers | Indicator colours for project health summaries displayed in status reports and the Executive Dashboard. |
| Success Rating | Defines the rating scale options and the colour thresholds that affect the overall project rating score. |
Each individual trigger has an enable toggle. Disabled triggers are not evaluated, so no warning will be raised for that condition regardless of the actual values.
For RAID Triggers, threshold conditions combine a completion percentage with a days-away value, for example triggering an At Risk warning when a task is less than 50% complete and the due date is two or fewer days away.
Policies
Policies define site-wide approval routing rules and control how project risk trends are calculated. Each policy type can have multiple rules that route requests to different approvers based on request attributes.
Four policy types are available:
| Policy | Description |
|---|---|
| Project Intake Approval | Routes new project requests to the appropriate approvers based on request attributes such as proposed budget or priority. Supports multiple rules and a default approver fallback. |
| Governance Approval | Routes project phase gate approvals to the right reviewers based on phase attributes. |
| Timesheet Approval | Routes submitted timesheets to approvers based on project attributes. |
| Risk Trend | Configures how project risk trends are calculated and aggregated across the site. |
Each policy shows its current status (Active or inactive) and can be expanded to view and manage its rules. Click the chevron to expand a policy.
Adding and managing rules (Project Intake Approval example)
Within the Project Intake Approval policy, the Default Approvers section defines who receives all requests that do not match a specific rule. Individual rules are added using the Add Rule button and use an attribute, operator, and value format, for example "Proposed Budget is greater than $200,000" or "Priority is Critical". Each rule specifies which members or groups are required to approve requests that match the condition.
The date and name of the last person to modify the policy is shown at the bottom of the expanded view.