Trust & control

Know who acted.
Understand what changed.

Your operation needs a clear record of the activity behind its decisions. OrdexisOne brings searchable activity history, user attribution and recorded changes together with the permissions that govern access.

Review significant operational events, configuration changes and failures. Keep the responsible person, affected record and location available to the authorized team investigating what happened.

Explore Activity Logs

Searchable operational and system history

Find the relevant activity before reconstructing the story.

A customer question, an unexpected configuration result or an operating error can require more than a recollection of what happened. Activity Logs gives authorized administrators a searchable record of significant activity to investigate.

Start with the relevant period or affected record, narrow the results and open the event detail. The review stays grounded in the activity the system recorded.

One attributed activity event: the actor, the customer, the property and the service it affected, the value that changed, and the dated history around it.Activity event 4182 was recorded on 14 May 2027 at 09:42 at North Yard in the billing category with warning severity. It names the actor M. Okafor as office administrator, the affected customer A. Brennan on account C-1043, the affected property 18 Orchard Way at North Yard and the affected service S-2291, a recurring lawn programme; the recorded action is a service interval change and the description records that it was shortened after the recorded customer request. The recorded change keeps the previous value of every 28 days beside the value now recorded of every 21 days. The dated history shows six of the 128 events in the period: the service interval change and a customer sign-in on 14 May, an invoice status viewed while past due and a rejected permission change for the office role on 13 May, a completed service visit on 12 May and an activity export request for 128 rows on 11 May. The period review counts 128 events, 121 information, 4 warning, 3 error and no critical events, with an errors-only review of 3 of 128 and recorded attribution on all 128. The history is read-only and keeps recorded values as they were recorded, and no amount is printed.TRUST / ATTRIBUTED OPERATIONAL HISTORYOne recorded event names who acted, what changed and what it affects.EVENT 4182 · 14 MAY 2027 09:42 · NORTH YARD · HISTORY KEPT AS RECORDEDTHE EVENT RECORDCATEGORY BILLING · SEVERITY WARNINGACTOR · STAFF MEMBERM. Okafor · office administratorAFFECTED CUSTOMERA. Brennan · account C-1043AFFECTED PROPERTY18 Orchard Way · North YardAFFECTED SERVICES-2291 · recurring lawn programmeRECORDED ACTIONService interval changedDESCRIPTION ON THE EVENTShortened after the recorded customer requestRECORDED CHANGE · OLD AND NEW VALUEPREVIOUS VALUEEvery 28 days→VALUE NOW RECORDEDEvery 21 daysTHE DATED HISTORY6 OF 128 EVENTS IN THE PERIOD14 MAYService interval changed · S-2291WARNING14 MAYCustomer sign-in recorded · C-1043INFORMATION13 MAYInvoice status viewed · past dueWARNING13 MAYPermission change rejected · office roleERROR12 MAYService visit marked complete · S-2291INFORMATION11 MAYActivity export requested · 128 rowsINFORMATIONTHE PERIOD REVIEW128EVENTS121INFORMATION4WARNING3ERROR0CRITICALErrors only review: 3 of 128 events · attribution recorded on 128 of 128Every event is attributedActor, customer, property and service on one recordThe history is read-onlyRecorded values stay as they were recordedIllustrative activity record · references, people and counts are recorded service values · no amount is printedTRUST / ATTRIBUTED HISTORYOne event names who acted and what it affects.EVENT 4182 · BILLING · WARNING14 May 2027 09:42 · North YardActor · M. Okafor, office administratorCustomer · A. Brennan, account C-1043Property · 18 Orchard Way, North YardService · S-2291, recurring lawn programmeCustomer, property and service stay attached to the eventCHANGE RECORDED ON THE EVENT28 days → 21 daysPERIOD COUNTS128EVENTS121INFORMATION4WARNING3ERROR0CRITICALErrors only: 3 of 128 eventsThe history is read-onlyEvery event is attributedActor, customer, property and serviceThe history is read-onlyRecorded values stay as recordedIllustrative activity record · no amount is printed

Search and narrow the history

Search operational and system activity. Filter by category, affected entity and date to focus the investigation on the part of the business being reviewed.

Separate the level of the event

Filter information, warning, error and critical events, or review errors only. The severity and category help staff distinguish ordinary activity from a recorded problem.

Move from the summary into the detail

Review total and error summary counts, page through the results and open the relevant event. Investigate the record behind the count without relying on a headline alone.

User attribution and change detail

The event identifies the action and the person behind it.

Open an activity record to review its actor, user, category, action, entity, location and description. That context helps the office connect a recorded change or failure to the responsible activity.

The user and action
Review the recorded actor and user alongside the action and description. Establish which activity is being investigated and who is associated with it.
The affected record and location
The entity and location keep the review attached to the relevant business context. Category and date filters help find related activity in the history.
The recorded change
Review old and new values where the change was recorded. Read the supporting metadata to understand the context preserved with that event.

Inspect a failure with its supporting information.

Authorized staff can review recorded error and stack details where permitted. Copy the event's JSON for controlled investigation when the technical detail is needed.

Review the history without rewriting it.

Activity Logs is read-only. Access to the event and its detail remains subject to permission, retention and data-redaction policy.

Customer account and invoice activity

See the customer activity behind the follow-up.

Review recorded customer sign-ins and invoice views, including views of an overdue invoice. Keep that activity connected to the account and invoice the office is working with.

A customer returning to their account and a customer opening a particular invoice are different actions. The recorded events help the office understand that distinction when reviewing an outstanding account.

Customer account C-1043 with the sign-in event and the invoice-view event recorded separately, and the invoice status the office reads with them.Customer account C-1043 belongs to A. Brennan at 18 Orchard Way, North Yard; it holds four recorded invoices with one still open, the last sign-in was recorded on 12 May 2027 at 08:14, and 41 sign-in events were recorded in the period from 12 to 14 May 2027. The two recorded customer events are read apart: the sign-in event at 08:14 on 12 May recorded account access with no invoice opened in that event, while the invoice view event at 09:42 on 14 May recorded invoice I-2207 being opened, past due since 06 May and the third view recorded on that invoice. The invoice the office is working with is I-2207 with the status past due recorded and a reminder recorded on 09 May. What the office can see is stated as counts: 41 sign-ins, 3 views of invoice I-2207, 2 of them recorded while the invoice was past due, and 1 invoice still open. The recorded view is read with the invoice as context for the conversation, and the decision stays with the office; no amount, price or balance is printed.TRUST / CUSTOMER INVOICE ACTIVITYA recorded sign-in and a view of one invoice are different events.A. BRENNAN · ACCOUNT C-1043 · 18 ORCHARD WAY · PERIOD 12–14 MAY 2027 · SIGN-IN AND INVOICE-VIEW EVENTSTHE ACCOUNT RECORDCUSTOMER ACCOUNT · STATUS ACTIVECUSTOMER ON THE ACCOUNTA. Brennan · customer sign-inACCOUNT REFERENCEC-1043 · customer accountPROPERTY ON THE ACCOUNT18 Orchard Way · North YardINVOICES ON THE ACCOUNT4 recorded · 1 still openLAST SIGN-IN RECORDED12 May 2027 08:14SIGN-INS IN THE PERIOD41 recorded eventsTHE TWO RECORDED EVENTSSIGN-IN EVENT · 12 MAY 2027 08:14Account access recorded41 sign-ins in the period · no invoice opened in that eventINVOICE VIEW EVENT · 14 MAY 2027 09:42Invoice I-2207 openedStatus past due since 06 May · third view recorded on this invoiceTHE INVOICE THE OFFICE IS WORKING WITHINVOICEI-2207STATUS RECORDEDPast dueREMINDERRecorded 09 MayWHAT THE OFFICE CAN SEE41SIGN-INS3VIEWS OF I-22072WHILE PAST DUE1INVOICE OPENThe view is read with the invoice: recorded activity gives context for the callA sign-in is not an invoice viewTwo recorded events, read apartThe decision stays with the officeRecorded activity is context, not a decisionIllustrative customer activity · statuses and counts only · no amount, price or balance is printedTRUST / CUSTOMER ACTIVITYA sign-in and an invoice view are different events.A. BRENNAN · ACCOUNT C-104318 Orchard Way · 12–14 May 2027Sign-in · 12 May 2027 08:1441 sign-ins in the periodInvoice view · 14 May 2027 09:42Invoice I-2207 · past due since 06 MayTwo events, read apartTHE INVOICE IN REVIEWI-2207 · past duePERIOD COUNTS41SIGN-INS3VIEWS2WHILE PAST DUE1INVOICE OPEN2PAYMENTSThe office reads the view with the invoiceRecorded activity is context, not a decisionA sign-in is not an invoice viewTwo recorded events, read apartThe decision stays with the officeRecorded activity is context, not a decisionIllustrative customer activity · no amount is printed

Review the account activity.

Recorded customer sign-ins give the office visibility into account access. Invoice-view activity identifies an interaction with the invoice being reviewed, including when that invoice was overdue.

Read the event with the invoice.

Use invoice status, payment activity and customer context alongside the recorded view. The office can review what remains outstanding and the activity available before deciding how to follow up.

Keep the decision with your team.

The activity provides context for a customer conversation. Staff retain responsibility for interpreting the account position and choosing the appropriate next action.

Explore invoice and payment context

People and permissions

Access follows the role and the work.

A dedicated business environment contains different responsibilities. Customers, field staff, outreach representatives and administrators use the workflows their roles permit.

Administration access is governed by the user's role, permissions, plan and authorized locations. Staff administration maintains the role, department, employment status and termination information that belong to the person.

Which operating roles are authorized for which actions: a role-to-action table with a mark per role and action, the counts per role and per action, and what each role group uses.The role-to-action table sets five authorized roles against six operating actions with a mark for each permission. The customer as account holder is authorized for the customer account and the invoice record, two of six actions. Field staff as assigned technician are authorized for assigned work, one of six. An outreach representative is authorized for assigned work and the team schedule, two of six. Office staff are authorized for the customer account, the invoice record, assigned work, the team schedule and staff and roles, five of six. An administrator is authorized for all six including business settings. Counted per action, the customer account, the invoice record and the team schedule each carry three authorized roles, assigned work carries four, staff and roles carries two and business settings carries one, making sixteen authorized marks across five roles and six actions. Customer actions cover the account, invoices, payments and support for their own records; field-work actions cover assigned work, route and property context for the working day; office actions cover scheduling, customer accounts, invoices and staff accounts. Access follows the role, the permissions, the plan and the authorized location.TRUST / AUTHORIZED OPERATING ROLESEach role is authorized for the actions its own work requires.ORCHARD & LANE · 3 AUTHORIZED LOCATIONS · ADMINISTRATION ACCESS IS GOVERNED BY THE USER’S ROLE, PERMISSIONS, PLAN AND LOCATIONROLE TO ACTION · AUTHORIZED MARKS PER ROLEAUTHORIZEDNOT AUTHORIZEDAUTHORIZED ROLECUSTOMER ACCOUNTINVOICE RECORDASSIGNED WORKTEAM SCHEDULESTAFF & ROLESBUSINESS SETTINGSACTIONSCUSTOMERaccount holder2 of 6FIELD STAFFassigned technician1 of 6OUTREACH REPassigned visits2 of 6OFFICE STAFFinvoices and staff accounts5 of 6ADMINISTRATORconfiguration and access6 of 6AUTHORIZED ROLES PER ACTION334321WHAT EACH ROLE GROUP USESCustomer actionsAccount, invoices, payments and support for their ownrecords · 2 of 6 actions authorizedField-work actionsAssigned work, route and property context for theworking day · 1 of 6 actions authorizedOffice actionsScheduling, customer accounts, invoices and staffaccounts · 5 of 6 actions authorizedAccess follows the roleRole, permissions, plan and location govern what is usedEvery action is counted16 authorized marks across 5 roles and 6 actionsIllustrative role table · roles, marks and counts are illustrative service values · no certification is claimedTRUST / AUTHORIZED ROLESEach role is authorized for the actions its work needs.ROLE · AUTHORIZED ACTIONSCUSTOMER2 of 6FIELD STAFF1 of 6OUTREACH REP2 of 6OFFICE STAFF5 of 6ADMINISTRATOR6 of 6Customer, field-work and office recordsAccess follows role, plan and locationAUTHORIZED ROLES PER ACTIONCustomer account3 rolesInvoice record3 rolesAssigned work4 rolesTeam schedule3 rolesStaff and roles2 rolesBusiness settings1 role16 authorized marks · 5 roles · 6 actionsIllustrative role table · no certification is claimedAccess follows the roleRole, permissions, plan and locationEvery action is counted16 marks across 5 roles and 6 actions
Customer account actions
Supported customer workflows connect account information, services, invoices, payments and support to the relevant customer. Protected status lookup gives customers or candidates an appropriate way to access the specific information they need.
Staff responsibilities
Manage staff accounts and access according to roles and permissions. Assigned work and role-appropriate functions give people the operating context needed for their responsibilities.
Administrative control
Authorized administrators manage the business's commercial and operational configuration. Roles and location access determine what each user can see and do.
Relevant operating guidance
Role-aware documentation makes help available to the intended audience. Internal operating instructions and customer-facing guidance can have different readership and publishing controls.
Explore staff roles and access

Location authorization and governance

A shared organization still needs controlled boundaries.

An authorized administrator can move into a permitted location context. Cross-location navigation is denied when authorization is absent, and the current operating context remains visible.

Parent and child relationships add another layer of control over how business rules are shared. Geography, customers, staff and commercial settings retain their relevant location context.

Explore location governance

Choose the relationship and policy

Request and review a parent-child relationship, approve or reject it, and suspend or revoke it when required. Govern the supported business domains separately.

Define what is shared

Live-linked, copy-once and independent modes let the organization choose which standards continue from the parent and which are managed locally. Supported controls can lock child editing or allow local and fork-on-edit behavior.

Review changes and their delivery

Review proposals, comparison evidence, warnings and audit information. Publish parent change sets and review rollout and delivery history under the configured server policy.

Evidence inside the workflow

Keep the decision with the work it affects.

The central activity history is part of a wider operating record. Specific workflows also retain the policy, document or outcome information needed to review their decisions.

Billing policies and engine outcomes

Configure invoice timing and lifecycle rules, simulate policy outcomes and review engine runs. Generated outcomes, warnings and failures give the finance team context for the invoice automation activity.

Explore invoice operations

Governed agreements and signing

Maintain versioned contract templates and reusable terms. The visual signing workflow preserves a timestamped signing event with the required name, declaration and signature steps.

Explore agreement presentation

Maintained operating knowledge

Documentation supports versions, review deadlines and a governed draft, review, approval, publication and archive process. Contextual help and reader feedback help keep instructions useful to the people relying on them.

Explore connected reporting

Your configured environment

Know the controls your business will use.

Your dedicated operating environment brings the business identity, commercial rules and authorized responsibilities together. Review the roles, location policies and enabled connections appropriate to your operation.

Explore your dedicated system
Provider configuration
Payment, mail, mapping, identity and weather connections use the supported services configured for the deployment. Privileged configuration belongs with authorized administrative access.
Visibility and record handling
Activity history and supporting detail are available within the applicable permissions, retention and redaction policies. Those policies define the records an authorized reviewer can access.
Available capabilities
Feature availability and account limits vary by plan, role, location and configuration. The enabled workflows determine the controls and records available to your business.

Explore how the platform connects operational responsibility, recorded activity and customer service.

Privacy and data handling Order Now