How can we help?

Use the Home workspace for priorities, workload, approvals, risks and upcoming work.

Follow the commercial lifecycle: Opportunity → Proposal → Estimate → AI Scope of Work → Purchase Request → Vendor Purchase Order → Project.

Use Work for projects, tasks, milestones, calendar and team execution.

Use Finance and People & HR for governed financial and workforce operations.

Use Nour across the platform to ask questions, understand context and prepare controlled actions.

Open your company workspace, for example app.mmtone.com or your tenant subdomain.

Enter your work email and password on the MMT ONE sign-in page.

If Google Authenticator is enabled, enter the current six-digit code once when prompted.

After sign-in, confirm the company/workspace name in the interface before making changes.

Open your profile and review language, appearance, notification and security settings.

Use the primary navigation to open Commercial, Projects, Finance, People & HR and other entitled workspaces.

Use the workspace header and contextual actions for the most common activity on the current page.

Use pinned or recent items where available to return to frequently used work.

Open Nour when you are unsure where information lives; ask for the business outcome rather than a table or module name.

Use browser deep links only after confirming you are on the correct tenant hostname.

Review the top indicators for approvals, open tasks, overdue work, meetings and business alerts.

Open Needs Your Attention and start with overdue, blocked, high-risk or approval-dependent items.

Review Nour Insight for a concise explanation of what changed or requires a decision.

Open the related project, commercial record, task or approval directly from the card.

Refresh after completing actions so the dashboard reflects the latest state.

Open your profile from the account menu.

Verify your name, email and contact information.

Choose your preferred appearance/theme where available.

Review notification preferences so critical approvals and assigned work remain visible.

Use the security area for password and two-factor settings; never share authentication codes with another user.

Open Nour from the dedicated Nour workspace or an embedded Ask Nour action.

Ask the question in business language, for example “What decisions are waiting for me?” or “Which projects have margin risk?”.

Add scope when helpful: customer, project, date range, owner, department or status.

Review the answer, cited evidence/context and any assumptions before acting.

Continue the conversation to investigate causes, compare options or prepare an action.

Look for the source context, records, dates and calculations behind the answer.

Distinguish exact tenant facts from published reference evidence or recommendations.

Check the time period and company/tenant context for financial, HR and operational facts.

If evidence is incomplete, ask Nour what is missing or request the source records.

For high-impact decisions, verify the underlying record before approval or commitment.

Ask Nour for the outcome, such as creating a meeting, preparing a task, drafting an email or progressing an approved workflow.

Review the proposed action card, target record, fields and expected effect.

Confirm the action only if the target, data and permission scope are correct.

Wait for the success/evidence response before assuming the change was completed.

Open the source record to verify the resulting state when the action is financially, commercially or operationally important.

Open Inbox/Mailbox to review connected personal or shared mailboxes.

Use search, categories and thread context to find the conversation.

Open the related customer, opportunity, project or task when the message affects delivery or a commitment.

Use AI assistance to summarize or draft where enabled, then review the text before sending.

Record or create follow-up work when an email creates an obligation, meeting or deadline.

Create or open the opportunity/lead and capture the customer, contact, source, owner and need.

Record the expected value, timing and next step when known.

Use activities, notes and tasks to preserve follow-up context.

Move qualified work toward a Proposal rather than keeping it as disconnected notes.

Review Commercial Intelligence for pipeline value, weighted revenue, risk and stalled opportunities.

Open Commercial → Proposals and select New Proposal.

Choose the customer/prospect and confirm proposal dates, currency and owner.

Add items, quantities, selling prices, taxes/discounts where applicable and internal expected margin.

Add scope, terms and supporting notes, then review the customer-facing preview/PDF.

Send or share through the approved channel and track status, follow-up and outcome.

When the opportunity is ready for formal pricing, convert or progress it to an Estimate using the approved flow.

Open Commercial → Estimates and create or open the relevant estimate.

Confirm customer, dates, currency, opportunity/proposal linkage and responsible owner.

Build the line-item BOQ with quantity, unit selling price, tax/discount and descriptions.

Review totals and expected margin before submitting for approval or customer use.

Use AI Scope of Work when the estimate/BOQ is ready for a narrative delivery scope.

After commercial approval, convert the approved estimate context into a Purchase Request when procurement is required.

Open the AI Scope of Work workspace from the estimate or AI SOW menu.

Confirm the correct Estimate/BOQ and attach relevant source documents when the scope depends on them.

Generate the draft and allow the quality/risk review to complete.

Review deliverables, assumptions, exclusions, dependencies, acceptance criteria and responsibilities.

Edit any statement that is not supported by the commercial record or source documents.

Generate the customer-facing output only after human review and approval.

Open Approvals or the approval state on the relevant Proposal/Estimate/PR.

Review value, margin, scope, customer, owner and any exception that triggered approval.

Open supporting evidence before approving unusual discount, margin or commitment.

Approve, reject or return for changes with a concise reason.

Confirm the source record moved to the expected status after the decision.

Open Commercial Intelligence.

Review pipeline value, weighted revenue, average margin, approvals pending and deals at risk.

Filter by period, owner, customer, status or other available dimensions.

Open risky or stalled records directly from the insight.

Use Nour to explain major changes, concentration, margin deviation or next actions.

Open Purchasing → Purchase Requests or convert from the approved Estimate.

Confirm the Estimate/Project mapping and inherited items/quantities.

Verify selling unit price inherited from the Estimate; enter or review the internal unit cost separately.

Review selling total, cost total, profit and margin before submitting.

Select the appropriate approver and submit the PR through the approval flow.

Do not create Vendor POs beyond the approved/remaining PR quantity.

Open the approved PR and create a Vendor Purchase Order.

Choose the supplier/vendor and confirm commercial terms, dates and currency.

Select PR items and enter the quantity being ordered.

Verify the system-calculated remaining PR quantity before saving.

Enter vendor cost only; customer selling price remains in the originating commercial record.

Track approval, delivery and payment state until closure.

Open the relevant PO/project logistics view.

Record expected delivery date, actual delivery progress and responsible party.

Update partial, delayed, delivered or exception states as evidence arrives.

Link delays or delivery risks to the project/task that is impacted.

Use logistics intelligence to surface overdue or blocked deliveries and escalate critical dependencies.

Create or open the Project after the commercial handoff.

Confirm customer, project owner, dates, team members and the originating commercial/PO context.

Create milestones that represent meaningful delivery checkpoints.

Break milestones into assigned tasks with due dates and priorities.

Track project cost, expenses, vendor commitments and revenue context.

Review project profitability and unresolved risks before closing the project.

Open Work → Tasks or the project task list.

Create the task with a clear outcome, owner, due date and priority.

Link it to the correct project/milestone and add dependencies or files when needed.

Use status such as open, in progress, pending or complete according to the actual state.

Update progress and comments when ownership, risk or due date changes.

Close only when the agreed outcome and required evidence are complete.

Define a milestone around a measurable delivery outcome rather than a vague phase name.

Set the planned date and link the tasks required to achieve it.

Assign accountable owners through the underlying work.

Review overdue or at-risk tasks before the milestone date.

Mark the milestone complete only after its dependent deliverables are accepted.

Open the team/capacity or workload view available to your role.

Compare busy, available and overloaded team members.

Open the work behind a high-load indicator before reassigning anything.

Move or reschedule work only after checking skill, dependency and deadline impact.

Use Nour to summarize capacity risks and identify tasks that can be redistributed.

Open Calendar from Work or the workspace navigation.

Create the meeting/event with date, time, participants and purpose.

Link the meeting to a customer/project/task when it represents delivery or a decision.

Review participant availability when the calendar integration supports it.

After the meeting, record decisions and create follow-up tasks rather than leaving actions only in notes.

Open the relevant customer, commercial, project, task, SOW or procurement record.

Upload the file in that record’s attachment/evidence area.

Use a meaningful filename/version and remove obsolete duplicates when policy allows.

Check customer visibility before sharing externally.

For AI-assisted scope or investigation, verify the attachment is actually selected as source evidence.

Open Finance/CFO Intelligence.

Review period performance, revenue, cost, profit, cash and relevant exceptions.

Use the period/date filters to make sure comparisons use the intended fiscal window.

Open the source transaction, project or customer behind an exception.

Use Nour to explain material variance, margin deviation, collection risk or unusual movement.

Create or open the invoice from the appropriate customer/project context.

Verify line items, tax, due date, currency and customer details.

Send the approved invoice and monitor its payment status.

Record or reconcile received payments using the configured payment/banking process.

Review overdue balances and payment progress in Finance/Customer PO views.

Open Finance → Expenses and create the expense.

Choose the correct category, date, amount, currency and responsible employee/vendor.

Link the expense to a project/customer when it affects project profitability.

Attach receipt or supporting evidence where required.

Submit through approval/review and confirm the cost appears in the relevant financial/project view.

Open Accounting/Finance and confirm the active fiscal period.

Use the chart of accounts, banking, bills, journals and transfers according to your finance process.

Reconcile banking/transaction items before period close.

Review exceptions and close-readiness indicators rather than relying on dashboard color alone.

Use reversal/correction flows for mistakes instead of deleting governed accounting history.

Open the Budget workspace.

Choose the fiscal period, business area/project and budget basis.

Enter or review planned values using the configured mapping.

Compare actual versus budget and investigate material variance.

Update forecasts/scenarios through the approved process rather than altering historical actuals.

Open People & HR → Employees.

Create or open the employee profile and verify name, contact, job/department and employment details.

Add the profile image and required HR information according to access policy.

Assign the correct manager, role/permissions and project/team context where applicable.

Keep status and employment changes current so workload and reporting remain accurate.

Open the attendance/timesheet area available to your role.

Record or review work date, shift/attendance state and time entries.

For project work, link time to the correct project/task where required.

Submit corrections or leave through the configured approval flow.

Managers review exceptions, missing entries and workload impact before payroll/close processes.

Open the payroll area if your role has access.

Confirm employee, pay period and source attendance/HR data.

Review earnings, deductions and adjustments before approval.

Generate or approve payslip/payroll output through the configured workflow.

Correct errors using the supported adjustment/reversal process and preserve audit history.

Open Automation and start from a template when a suitable one exists.

Define the trigger: business event, schedule or approved condition.

Drag the required action blocks into the flow and connect them in the intended order.

Set conditions, recipients, record mappings and safeguards for each step.

Save the draft and run Simulation before enabling real execution.

Open the saved workflow and select Simulate.

Choose or create the simulation scenario/input.

Review which trigger, conditions and branches are taken.

Inspect the expected actions, skipped steps and failure handling.

Fix mapping or logic errors and simulate again until the expected path is stable.

Open the ALPHA Automation Assurance result for the workflow.

Review mandatory safety, regression, audit and SLO checks.

Confirm the workflow is canary-ready before attempting a real limited execution.

Run the approved canary against a safe real use case.

Treat production certification as complete only after successful real canary evidence.

Open resilience.mmtone.com and sign in.

Start at Dashboard to understand current readiness, risks and latest evidence.

Use Discovery to identify infrastructure, applications, dependencies and providers.

Use Testing/Validation to select a scenario and target.

Review Results, topology/blast radius, evidence and generated reports.

Track remediation and retest until the intended control/recovery outcome is proven.

Open Connectors/Discovery and choose the technology/provider.

Enter configuration using the secure connector setup flow; do not place secrets in notes.

Use Test Connection.

If it passes, confirm the connector can see the expected objects/scope.

If it fails, use the displayed reason to check firewall, credentials/configuration, permissions or visibility before retrying.

Open Testing/Validation and select a scenario such as site, database, cloud region, storage, network, cyber isolation or compound failure.

Choose the target, or allow MMT ONE to select the relevant critical scope when supported.

Review the simulated failure source and the unavailable component(s).

Run the analysis to calculate blast radius, dependencies and recovery sequence.

Review achieved/expected RTO/RPO, validation evidence and any failed control.

Assign remediation and retest to prove improvement.

Open the test result.

Review the topology from failure source through dependent systems and business services.

Read the impact summary and recovery order alongside the diagram.

Open evidence items to understand the observation that supports each conclusion.

Generate/share the governed report for executive, technical or audit use as appropriate.

Open Security and review current alerts, connector health and priority incidents.

Open an alert to see the affected asset, source system, time and technical evidence.

Correlate related events before treating repeated symptoms as separate incidents.

Create or review the service/ticket record when remediation is required.

When recovery evidence arrives, update/close the ticket while preserving the technical justification and audit trail.

Open the connector inventory.

Choose the vendor/system and run Test Connection.

Confirm PASS includes the intended visibility/scope, not only network reachability.

For FAIL, review the reason such as firewall, configuration, authentication/authorization or data visibility.

Correct the cause and retest before relying on the connector for incident automation or reporting.

Open the incident/RCA workspace or related ticket.

Confirm the affected service, start/end time and observed business impact.

Collect relevant evidence from connected monitoring/security/infrastructure systems.

Build the timeline and distinguish symptoms, contributing conditions and root cause.

Document corrective/preventive actions, owner and due date.

Link closure evidence and retain the RCA for future comparison and assurance.

Open administration/staff permissions.

Start from the user’s job responsibility and required outcomes.

Grant access to the relevant workspaces/actions; avoid broad administrator rights for convenience.

Test the user experience with the intended tenant and role.

Review permissions after job/department changes and remove access that is no longer required.

Open the SaaS/company administration area from the master platform if your role permits.

Review tenant identity, status, plan/entitlements and assigned modules.

Confirm the tenant hostname and branding.

Verify staff/admin access and core company settings inside the tenant.

Run tenant health/module stability checks after major configuration or deployment changes.

Open the relevant integration/connector setup.

Use a named service account or approved OAuth connection with least privilege.

Configure the minimum scope required for the business use case.

Run Test Connection and verify the expected data/object visibility.

Document the owner and renewal/credential dependency.

Retest after firewall, identity, vendor API or domain changes.

Open your profile or appearance control.

Choose light, dark or the available theme preference.

Choose the supported language where the workspace provides language switching.

Reload the current page if a legacy component does not immediately inherit the preference.

Report unreadable text/icon contrast as a UX defect rather than working around it with browser zoom alone.

For “419 Page Expired”, refresh the sign-in/form page to obtain a new CSRF token, then submit again.

For Google Authenticator, start from the normal sign-in page and enter the current code once; do not open the temporary 2FA URL directly.

For a 404 after sign-in, return to the normal tenant root and confirm the hostname is the new mmtone.com tenant.

For a 503, treat it as a service incident and contact support; repeated refreshes do not repair a backend outage.

For missing menus, confirm role/permissions and product entitlement before assuming the module is unavailable.

Mobile centers on Home, Work, Nour, Inbox and More rather than cloning every desktop administration screen.

Use Home for priorities and attention items.

Use Work for high-frequency tasks, approvals, projects and calendar.

Use Nour as the intelligence/action entry point with governed confirmations.

Use desktop MMT ONE for deep configuration, advanced administration and complex designers.

Capture the exact page/URL, tenant, time and action you were performing.

Record the visible error message and whether other users/services are affected.

For data issues, include the record identifier but never passwords, OTP codes, tokens or private keys.

Email support@mmtone.com with the impact and evidence, or use the configured support channel.

For a service outage or security incident, mark the business impact and urgency clearly so restoration takes priority.