Dimensions
Screen reference
Dimensions are the classification structures that give records their business context in EVX Software.
A task tells the system what work has to happen. A time entry tells the system how much work was logged. An expense tells the system what cost was recorded. A document stores supporting information. Dimensions tell EVX Software where those records belong.
Clients, projects, workspaces, and tags are common dimensions. Other configured structures can also behave as dimensions, such as sites, job phases, project managers, labor categories, regions, departments, or service lines.
What a dimension does
A dimension gives users a shared way to organize records across modules.
| Dimension role | What it means |
|---|---|
| Classification | The record is assigned to a client, project, workspace, tag, or other configured structure. |
| Navigation | The same structure appears in the left navigation so users can choose a context. |
| Filtering | The selected dimension member limits what appears in the active module. |
| Reporting | Reports can group, filter, or calculate from the same classification data. |
| Permissions | Access can depend on which dimension members a user is allowed to see. |
The important point is that dimensions work across modules. A project is not only a field on a task. It can also be the context for documents, expenses, time entries, invoices, notes, and reports.
Dimension members
A dimension is the structure. A dimension member is one selectable item inside that structure.
For example:
| Dimension | Dimension members |
|---|---|
| Clients and projects | A client, a project under a client, or a project group. |
| Workspaces | A department, operating area, team, or internal work area. |
| Tags | A label such as Draft, Review, Internal, or Urgent. |
| Sites | A field location, facility, parcel, or survey area, when configured. |
| Job phases | Planning, field work, lab review, reporting, billing, or other account-specific phases. |
| Labor categories | Project manager, engineer, scientist, technician, administrator, or other billing categories. |
A record can be connected to one or more dimension members, depending on the object type and account configuration.
Dimensions and the left navigation
The left navigation exposes dimensions as selectable panels. Selecting a member in the left navigation sets the context for the main area.
For example, selecting a project limits the main area to records that belong to that project. The user can then switch between modules without losing the project context.
This is different from a simple menu. A menu only changes the page. The left navigation in EVX Software also filters the data shown on that page.
Dimensions and modules
Modules describe the type of record a user is working with. Dimensions describe the business context for that record.
A time entry belongs to the Time module. It may also belong to a project, task, labor category, workspace, and date range. A document belongs to the Documents module. It may also be classified to a project, a workspace, and one or more tags.
This separation lets EVX Software answer practical questions from different angles:
| Question | Dimension context | Module detail |
|---|---|---|
| What work is open for this project? | Project | Tasks, Status, Assigned to, Due date. |
| What time was logged for this client? | Client | Time entries, User, Date range, Labor category. |
| What costs belong to this job phase? | Job phase | Expenses, Product type, Budgeted or actual. |
| What supporting files belong to this site? | Site | Documents, File type, Last update, Status. |
| What should appear on the invoice? | Project and billing context | Tasks, Time, Expenses, Rates, Taxes. |
Multiple dimensions at the same time
When records are classified in more than one dimension, users can narrow the working set by combining contexts.
For example, a record can be connected to a project and a workspace. A user looking at that project sees the record from the project view. A user looking at that workspace sees the same record from the workspace view, if permissions allow it.
The same idea applies when a project is selected on the left and a module filter is applied at the top of the module. The dimension sets the context. The module filter narrows the records inside that context.
Environmental consulting example
A wetland delineation project may need to organize work by client, project, site, job phase, staff member, and labor category.
The field team may care about site and task assignment. The project manager may care about project, status, due date, and budget. The billing team may care about labor category, billable status, rate schedule, and invoice status. The executive team may care about project status, margin, utilization, and billing status.
Those are not separate systems. They are different views of the same underlying records. Dimensions make that possible by carrying context across modules.
Dimensions and permissions
Permissions often depend on dimensions. A user may have access to one project but not another, or one workspace but not another. That affects what the user can see in every module.
This means two users can open the same module and see different records. The module is the same. Their dimension access is different.
Administrators should review dimensions and permissions together. Adding a dimension without reviewing access can make records hard to find or expose records to the wrong users.
What you can do next
- Review navigation and filters to see how dimensions affect daily use.
- Review modules to understand how modules and dimensions work together.
- Review objects and classification to understand how records are assigned to dimensions.
- Review permissions overview before changing user access.