Your first five moves

1. Start with what needs you

   Open Start here. See your work, ask a question, or jump into a record. Try “Show me my highest priorities today.”

2. Find your Work Area

   Choose the team or operating space you work in. Its views keep the focus on that area and the folder you select.

3. Open a project or task

   Check the owner, priority, dates and next action. Open the record to see its context, updates and connected work.

4. Choose a useful view

   Use a board for flow, Data Grid for details, or Timeline for dates and dependencies. These are views of shared work.

5. Close the loop

   Record meaningful progress, request a review when required, and leave the next person a clear handover.

Start with your role

One record. A clearer path to delivery.

A task can appear in your personal work, a project, a board, a timeline and a report. Its identity and history stay connected, so you can change perspective without creating another copy.

Follow the example below to see how a request becomes reviewed work and a clear handover.

Choose your delivery rhythm

Learn the shape of Vision

A Frame is your organization’s boundary. Work Areas create focus inside it. Optional folders organize work, projects hold delivery context, and tasks carry the next action.

Spend less effort finding the right work

Start here accepts everyday questions and searches the Vision records you can access. Common questions about priorities, zombie tasks and projects behind schedule use recorded data directly. Results link back to the source.

Focused Work Areas reduce noise. The global God’s eye views let you look across the current Frame when you need the bigger picture. Search and global views still respect access.

Make the next step clear

Owners, due dates, dependencies, approvals and activity live alongside the work. Configured Work Pack review gates help work move through the agreed process. Engagement handovers keep the outgoing lead accountable until the recipient accepts.

The value is a connected path: request → delivery → review → handover. Your team still supplies the decisions and evidence that make the process meaningful.

Adapt the workspace to the team

Choose Work Area views, add task fields, organize projects and enable relevant Work Packs. One team can manage a delivery board while another works from a grid or sprint rhythm.

Configuration changes how people work with the shared engine. It does not require copying the same task into separate departmental systems.

Bring planned delivery and service work together

A team can plan a sprint, respond to an incident, create a linked follow-up task, review a change and record the time spent—all while keeping the delivery context connected. Service operations and project delivery do not have to become separate islands.

Vision fits teams that need both a delivery rhythm and operational accountability. Sprints preserve the commitment, approvals preserve the decision, SLAs expose time pressure, and Briefings make the result understandable to a customer.

From task tracking to delivery context

Useful by design, without inflated promises

Vision is designed to reduce navigation and repeated setup. We do not claim a measured speed advantage over another platform. Workflow behavior depends on configuration, permissions and the records your team maintains.

Core search answers, engagement checks, views and reporting do not need a model call. Optional AI assistance is available with the required access, provider connection and administrator budget.

From Frame to task

1. FrameYour organization’s boundary for people, access, integrations and settings.
2. Work AreaA focused operating space for a team, department or type of work.
3. FolderOptional organization inside a Work Area. Folders are one level deep.
4. ProjectA delivery outcome with owners, dates, health and connected work.
5. TaskAn actionable work record with its own status, context and history.

Focus locally. Look across when needed.

A Work Area’s horizontal views follow its scope. Select a folder to narrow the view. Top Level returns to the current Work Area’s overview.

God’s eye is the global view across accessible work in the current Frame. It does not span other customer Frames or reveal private records.

Connect without copying

Tasks can connect to projects, documents, milestones, dependencies and supported external tools. Accessible references can cross Work Areas without duplicating records or widening access.

Tasks and documents can also live directly in a Work Area or folder. A project is useful when you need shared delivery context; it is not mandatory for every piece of work.

Start here

Review what needs you, what is up next and what has been completed. Ask a question or use search to open the relevant record. Authorized users can switch between My work and My team.

Your default page is a personal setting. An explicit link to a task or project still takes you to that destination.

My Tasks

Use My Tasks to focus on your work. Confirm owner, priority and due date before deciding what to do next. Personal tasks and shared project tasks serve different purposes; choose the right scope when creating work.

If a legacy assignment cannot be confidently matched to an account, Vision may identify it as needing confirmation rather than guessing who owns it.

Heads Up

Review assigned work, approvals and followed-task updates. New @mentions can bring a permitted recipient back to the relevant work. Engagement obligations appear for named leads, handover recipients and reviewers.

Type @ in a supported task description or comment to choose a person from suggestions. Mentioning someone does not give them access to private work.

A practical daily rhythm

1. Choose

   Find the highest-impact work you can move today.

2. Check

   Read the current record, dependencies and outstanding decisions.

3. Act

   Do the work and update the shared record with the meaningful result.

4. Hand over

   Make the next action and its owner explicit.

Try a practical question

These questions use Vision’s recorded work and confirmed identity. A useful answer may explain that no matching records were found or that assignments need confirmation. It should not invent missing information.

What search can see

Search spans supported records you can access, including work, projects, documents and approved custom-field or engagement context. Ordinary search is broader than the My work summary. Explicit “my” or “my team” questions retain that personal or team scope.

Search does not automatically crawl the web, every connected MCP tool or the contents of arbitrary binary attachments. A hidden record remains hidden.

When AI helps

If a deeper question needs it, Start here can use a configured Claude or OpenAI provider within the administrator’s allowance and required XOS access. Answers use bounded relevant context and link to their sources.

Missing provider setup, unavailable evidence or a budget limit produces an explanation and useful next steps. Typing in the box and common built-in answers do not trigger a model call.

Move around a Work Area

1. Open the Work Area

   Choose it from the sidebar. Use the location chooser to move into a folder or back to Top Level.

2. Choose a view

   Overview, Projects, Work and Docs are the starting points. Add the optional views you use most.

3. Keep useful tabs

   Add views such as Data Grid, Calendar, Reports, Bandwidth, Sprints & Cycles, Engineering or Packs. Available options depend on access.

Keep or remove views

Optional tabs stay in your personal bar for the Work Area or folder on this device. Save view captures a named personal view with supported filters. Delete a saved view or remove a tab when it is no longer useful; the underlying work remains.

Shared Board/List views use their own sharing and ownership controls. A personal saved view should not be mistaken for a shared team configuration.

Make the space recognizable

Authorized owners can choose a built-in Work Area icon by clicking the icon beside its name. Search the icon chooser or restore the default globe.

Double-click the name or description to edit it when authorized. Keyboard and actions-menu alternatives keep these controls available without permanent edit buttons.

Know what stays connected

A scoped view narrows the work you are inspecting. Bandwidth still considers the person’s other visible commitments so a project filter does not create false availability.

Packs belong to a Work Area. Opening a pack from a folder returns to the Work Area’s scope.

Create a useful task

1. Name the outcome

   Use a title someone can understand without opening the description.

2. Add context

   Explain the result you need, attach or link useful evidence, and identify the next action.

3. Assign and schedule

   Choose the responsible person or team, priority, project when useful, and a realistic due date.

4. Connect the work

   Add subtasks, document references, milestones or dependencies where they clarify delivery.

Move work with evidence

Use the status that reflects the actual work. Configured workflows may require approval or completion evidence before a task can advance. A status change should not stand in for a missing decision.

Use comments and @mentions for collaboration. Keep changes and decisions in the record so the next person can understand what happened.

Add the details your team needs

Labels support lightweight categorization. Custom fields capture structured information such as a customer reference, acceptance date or check. Owners and Admins manage task definitions in Field Library; permitted task editors fill the values below Activity.

Track time from the task when needed. Time permissions and invoice locks still apply even if you can open the task.

Set up a project for clarity

1. Define the outcome

   Describe what this project should deliver and how the team will recognize completion.

2. Confirm ownership and access

   Choose the lead and relevant people or teams. Access follows the existing Frame and container rules.

3. Connect the plan

   Add dated work, milestones and dependencies. Keep reported progress and project health meaningful.

4. Post updates

   Record completed work, next steps and risks so others do not need to reconstruct progress from task changes.

Adjust dates in the timeline

Drag a scheduled task, project or milestone horizontally to propose a date move. Review the change before saving. Eligible dependent work can move forward as needed to avoid finish-to-start conflicts.

The review makes affected work visible, including accessible relationships outside the current view. Started, closed or controlled work is not automatically shifted. Dates use calendar days; this is not a working-day or critical-path scheduler.

Make dependencies explicit

Use Link tasks to add dependencies. A normal drag proposes a date change; link mode changes the relationship. Review conflicts rather than assuming every connected item can move.

Use the project’s Capacity view to inspect visible commitments across projects before adding more work to a person.

Choose the rhythm that fits

Use a Sprint when the team needs a goal, an explicit commitment and a planning, daily check-in, review and retrospective rhythm. Use a Cycle for a lighter repeating focus window. One- and two-week cadences are supported.

Open Sprints & Cycles from God’s eye for a broader perspective, or add it as a focused Work Area view. The sprint stays connected to its original tasks and projects.

Plan around the goal and the real capacity

Sprint estimates and capacity are planning units, not billable hours. The interruption reserve reduces the capacity available for planned delivery; it is not a time entry.

1. Define the outcome

   Give the sprint a meaningful name, owner, dates and a goal the team can assess.

2. Select ready work

   Choose the backlog items that serve the goal. Confirm owners, dependencies, estimates and useful documents.

3. Check the whole workload

   Use Bandwidth to inspect visible commitments across projects. Set sprint capacity and an interruption reserve for operational work.

4. Start the commitment

   Starting captures the committed scope. The baseline makes later changes visible instead of rewriting the original plan.

Run the sprint where the work lives

Dashboard, Operate, Calendar and Reports offer different perspectives on the same sprint. Delivery signals surface blocked work, incomplete estimates, capacity pressure and progress against the plan. They are prompts to inspect evidence, not promises of an outcome.

Make interruptions a conscious decision

An addition to an active sprint needs a written reason. Vision creates a leadership review request; the item stays outside the commitment until an authorized leader approves it with a note. The decision and scope change remain recorded.

This matters when the same engineers handle customer delivery and service follow-up. Urgent work can be considered without silently pretending the original commitment never changed.

Close with an outcome

Review completed work, remaining scope and the reason for spillover. Close the sprint with its outcome and make the next destination for unfinished work explicit. Completed sprint history preserves the result for later review.

Vision supports the team’s delivery practice. Clear goals, honest estimates, useful reviews and good decisions still come from the team. Core sprint metrics do not require AI tokens.

Establish the operating rhythm

1. Name the leads

   Assign customer and engineering leads plus an escalation reviewer from people with project access.

2. Set the cadence

   Choose independent customer-contact and progress deadlines. Defaults are seven calendar days.

3. Record the evidence

   Log a customer-facing call, meeting or message with an outcome and next action. Record engineering progress separately.

Make follow-up meaningful

An unanswered attempt is different from a completed customer interaction. Editing a task, importing a record or posting an ordinary comment does not reset either check-in clock.

Use the dashboard to find overdue contact, missing progress, blocked work and handovers awaiting action. Counts open their matching records. Heads Up shows obligations to the relevant people.

A handover ends with acceptance

Record scope, completed and remaining work, risks, dependencies, evidence and the first next action. Choose the receiving person and an acceptance deadline.

The outgoing engineering lead remains accountable until the recipient accepts. Requested changes require resubmission; a missed deadline raises attention rather than silently transferring ownership.

Keep the record honest

Contact and progress are recorded by your team. Vision does not infer a customer conversation from email activity or automatically read every message. Imported ownership may need mapping before check-ins can begin.

Start with the service modules you need

From an incident to a durable improvement

The incident and its delivery task have different purposes. Resolving the incident does not mean every improvement task is complete. The relationship lets the next person follow the context.

1. Capture the service context

   Record the impact, priority, owner and relevant service or configuration item.

2. Respond and coordinate

   Use the incident record, work notes, escalation and On-call where enabled.

3. Connect the follow-up

   Create a linked Vision task when the investigation needs engineering delivery. Keep its owner and due date explicit.

4. Review and resolve

   Use the appropriate approval and change workflow, record the outcome and retain supporting knowledge.

Bring service context into delivery decisions

Search configuration items by name or identifier instead of scrolling a long list. Linked service context helps a reviewer understand what a change could affect.

A follow-up task can participate in a project or sprint through the normal workflow. Active-sprint scope controls still apply; creating an incident does not automatically expand the team’s commitment.

Enable deliberately

An Owner or Admin configures Administration → Work packs → ITSM Pack and chooses the available modules. The display name can match the team’s language. Module access depends on the Frame’s paid grants; ITSM and CMDB are separately controlled.

Turning a module off retains its records while hiding its navigation and blocking its service actions. Re-enabling an authorized module restores the retained work. Access to private records is still enforced.

Follow the decision from request to outcome

1. Submit the request

   Describe the decision needed and link useful evidence. The request begins Pending with the submitter and submission time recorded.

2. Route to the right reviewer

   Configured routing and reviewer assignments determine who may decide. Being able to view the record is not permission to approve it.

3. Record the decision

   An authorized reviewer approves, requests changes or declines. Declines and requests for changes require an explanation.

4. Respond and resubmit

   The original submitter can return declined work or requested changes for review with a note explaining what changed. Earlier decisions remain in the history.

One decision history, several delivery contexts

Use approvals for supported service decisions, configured Work Pack review gates and sprint scope requests. Each workflow retains its own authorized reviewers and transition rules.

For example, a sprint addition stays out of committed work until leadership approves it. A configured pack stage can require a review before its workflow advances. A generic approval is not a blanket authorization for every linked action.

One assigned authorized reviewer can decide a shared-work request. Do not assume this means unanimous approval, sequential committee review or an electronic-signature contract.

Keep the evidence trustworthy

The decision records who acted, when and the required response. A completed decision cannot be rewritten through an ordinary record edit, and requests are retained as audit records.

Review the actual record and current evidence before deciding. For a changed request, explain the change and use the supported resubmission path.

Escalate when a decision needs attention

Raise an escalation with the delivery issue, context and outcome you need. The Escalations view brings unresolved work and recorded history together so leads can act on the source.

An engagement attention flag or Heads Up obligation does not automatically create an Escalations record. Use the explicit escalation action when that is the desired workflow.

Build a schedule people can read

Week, two-week, month and three-month zooms help you inspect different horizons. Shift details preserve exact times and the display timezone. Rotation intervals use elapsed hours, so daylight saving can change the local handoff time.

1. Create a rotation

   An Owner or Admin chooses the team or project scope, eligible responders, shift length and start.

2. Assign the roles

   Set primary and backup responders, with optional shadows. Confirm the acknowledgement window and routing policy.

3. Inspect the schedule

   Use the timeline, zoom, date navigation, timezone, search and My shifts filters to inspect the relevant coverage.

4. Resolve the gaps

   Review missing primary or backup cover and overlapping duty before relying on the schedule.

Adjust one shift without rewriting the rotation

Use temporary cover or an assignment edit for the selected person, role and time window. Include the reason. Arrange shifts lets an admin drag an eligible primary or backup assignment, review the proposed move and save it.

Moving an assignment does not move the repeating roster. Vacated time becomes an explicit gap to resolve. Canceling the editor leaves the saved schedule unchanged.

Move from coverage to response

Route an accessible incident to On-call manually, or use explicitly enabled automatic routing for eligible high-priority incidents. Responders can acknowledge, escalate to backup, snooze with a reason or hand off with a note.

Acknowledgement stops the response escalation clock; it is not incident resolution. Create a linked task with an owner and due date when follow-up needs its own delivery path. Review Handoffs & history for the recorded sequence.

Connect the channels you actually use

Project-linked Slack or Microsoft Teams destinations can receive configured notifications. Provider acceptance is not proof that a person has read or acknowledged the incident. The Vision response queue remains the place to confirm response state.

Calendar export is a downloadable schedule snapshot. On-call is a separately granted add-on; it does not include SMS, voice calls or native emergency push alerts.

Set a meaningful target

1. Open the relevant work

   Confirm the owner, priority and deadline. A due date alone is not proof that an SLA timer has been started.

2. Start the SLA

   Use the task’s SLA controls to set the supported duration and start the timer. The work’s due date and time provide the deadline.

3. Inspect the condition

   Look for Running, Paused, Met or Expired, alongside remaining time or time past target.

4. Act on the source

   Coordinate the response, update the record or escalate the need. A dashboard signal should lead back to the actual work.

Pause, resume and finish explicitly

Authorized task editors can pause and resume the timer. Pausing preserves the remaining time; resuming sets a new deadline from that remaining duration. These actions are recorded in activity.

Mark the target met when the work satisfies it. Stopping a breached SLA keeps the breach visible; it does not turn a missed target into a success. Starting a new SLA is a separate action.

Keep service timing separate from workflow progress

A task can be In progress or In review while its SLA is breached. Vision preserves the workflow status so the team can continue moving the work without concealing the missed target.

Service-module overviews and escalation reporting expose relevant SLA attention. On-call acknowledgement timing, project targets, engagement check-ins and task SLAs are distinct clocks; one action does not satisfy them all.

Agree the policy before relying on it

The task SLA is a deadline-based elapsed-time control. Do not assume it applies business calendars, holidays, contractual exclusions or a full entitlement engine. Define the team’s operational policy and use the supported controls consistently.

Check before assigning

1. Find the person

   Open Bandwidth or a project’s Capacity view.

2. Inspect their visible workload

   Compare the work in the current view with their other visible assignments.

3. Open the sources

   Inspect the actual tasks behind a count to understand urgency, effort and blockers.

4. Check scheduled hours

   Use bookings, working schedules and leave where available before treating a person as available.

Read the numbers correctly

A task count is not an estimate of hours. A booking is scheduled demand; it is different from logged time or remaining effort. Missing bookings and inaccessible work prevent a guaranteed availability claim.

Direct and team assignments are considered together so the same record is not counted twice for the same person. Opening a task keeps the source context available.

Use the context to make a decision

Discuss the tradeoff, adjust the schedule or reassign work with the responsible people. Bandwidth supports the decision; it does not silently redistribute commitments.

A customer-ready view of delivery

Share a coherent picture of selected projects: delivery totals, completion over time, current work status, reported project progress and overdue next actions. Where engagement check-ins are configured, customer contact and engineering progress remain separate signals.

The actual shared page is HTML with sharp text and SVG charts. Choose Aurora, Ocean or Sunrise for restrained gradient accents over the dark layout. The preview and published page use the same renderer.

Create a briefing

1. Open Reports → Briefings

   Choose accessible projects from the current view.

2. Set the context

   Add a title, choose a 7-, 30- or 90-day reporting period and select a palette.

3. Review the preview

   Inspect project progress, work status, overdue actions and recorded check-ins. Missing data stays explicit.

4. Choose how to share

   Use named signed-in recipients or, when authorized, an expiring link for anyone who has it.

Know what the link shares

A briefing is a reviewed snapshot, not a live synchronized dashboard. Refresh and publish a new link to share updated data. Links can expire after 1, 7 or 30 days and can be revoked.

Named recipients need an active account in the same Frame and current source access. Public-link publication is an Owner/Admin action and excludes private sources. A downloaded copy cannot be recalled.

Keep the numbers meaningful

Reported project percentage is different from the share of tasks completed. Cancelled work is not delivered work. Customer contact and engineering progress have separate dates.

Use source links inside Vision to investigate a result before making a delivery decision.

Readable on the customer’s screen

The layout adapts to narrower screens. Dense chart and table regions retain their labels and can scroll within their own area. Customers can read the shared snapshot without installing Vision.

For a weekly review, choose the relevant projects and period, inspect missing information, then publish the reviewed snapshot. Use a fresh preview and link for the next review.

Choose a useful starting point

Examples include Marketing, Engineering, Finance and accounting, Customer success and Professional services. A pack can supply typed intake, fields, stages, focused views and an assigned-reviewer workflow.

A pack is not a claim that Vision includes every specialized industry system. For example, a Finance workflow is not a general ledger, and a Professional services workflow is not a full customer-billing engine.

Configure before activating

1. Choose the Work Area

   Open Work packs in Administration or the authorized Work Area setup.

2. Review the configuration

   Set the display name, fields, reviewers and relevant controls. Installation creates configuration, not sample work.

3. Save and preview

   Validate the draft and inspect its effect before publication.

4. Activate

   Publish the reviewed setup. Authorized users can then use the focused pack entry.

Customize without losing the thread

Adjust supported fields, labels, stage names and task-section presentation. Keep stable identities and review history as the configuration evolves.

Deactivation retains existing work and history. Hidden sections are a presentation choice, not a security boundary. Paid capabilities still need their own server-granted access.

About custom job billing

A Job Billing Work Pack is in design for approved-job timesheets, customer/job/role/employee rates and accounting review. It is not currently available to activate. Existing time tracking and dated per-person rate cards remain separate features.

Create in the right place

Open a Work Area or folder and choose New doc. Its current location is used as the starting context. Give the document a clear title, structure the content and link relevant work.

Use the existing document editor for authored content. Tasks can reference documents so people can return to the source without duplicating the explanation.

Write for the next reader

Start with the purpose and the decision or action the reader needs. Link the evidence, keep ownership clear and record significant changes. Useful titles and structure make search more effective.

Access follows the document and its container. A link or mention does not open private knowledge to another person.

Connect to external material

Add supported file, folder or tool references when the source belongs elsewhere. A saved URL is a reference; it does not by itself authenticate an integration or synchronize its contents.

Record time against the work

Working schedules and leave describe availability for capacity planning. They do not replace actual time entries or automatically calculate payroll.

1. Choose the task

   Open accessible work and confirm that your logging policy permits it.

2. Track or enter the time

   Use the timer for live work, or add a manual duration or recorded interval. Include a useful note and the appropriate billable setting.

3. Review My Time

   Inspect the period, work references and recorded entries. Correct eligible entries before invoicing.

Control which jobs can be logged

Owners and Admins can configure Administration → Time tracking with a default policy and per-person exceptions. Approved jobs only requires an explicit task or project approval. Project approval covers current tasks without giving access to private work.

The policy applies to timers and manual entries. Revoking logging access retains recorded time; it does not erase the history.

Apply the right dated rate

An Owner or Admin defines per-person rate cards with an effective date, currency and optional task or project scope. Vision first looks for the person’s task-specific rate, then the recorded billing project, then the person default and the existing USD invoice fallback.

The entry’s work date determines the applicable rate. Supported currencies include USD, EUR, GBP, CAD, AUD, NZD, CHF and SGD. Each invoice uses one currency, with no automatic conversion. Admins set tax percentages; a region label does not calculate tax law or payroll.

Changing rates affects eligible uninvoiced work. Saved invoices keep their captured amounts.

From completed entries to an invoice

Invoice history lets you download the saved invoice again. A never-submitted invoice can be voided to release its entries for correction. Downloading does not send an invoice or collect payment.

1. Choose the period

   Open My Time → Create invoice for a period of up to 32 days.

2. Review eligible entries

   Select completed, billable, uninvoiced work. Running or paused timers are excluded; a project is not required.

3. Confirm the details

   Review sender, customer, dates, references, hours, rates and totals.

4. Create and download

   Create the invoice PDF. Vision reserves the source entries against duplicate billing and saves an immutable invoice snapshot.

Use the optional accounting handoff

Where a scoped Stark connection is configured for the person and Frame, explicitly submit the reviewed invoice for accounting review and refresh its status in Vision. The current Stark integration accepts USD. Other supported currencies remain available for PDF download.

Submission is not accounting approval or payment. Keep destination, amount and customer details under review before any external handoff.

Custom customer and job rates

The Job Billing Work Pack is in design for a broader customer/job/role/employee rate hierarchy and accounting review. That proposal is separate from the available dated per-person task/project rate cards described here.

Connect a Slack channel

An authorized owner can use Connect channel in a Work Area or the project’s connection settings to choose a verified Slack channel. Work Areas and projects can keep independent connections.

Saving the channel does not enable every notification. Choose the event types and explicitly enable updates. Existing Slack intake and interactive actions follow the connected identity and work permissions.

Link GitHub delivery evidence

Connect relevant repositories, work and pull requests. Vision can present linked review/check state and delivery context while GitHub remains the source for code, reviews and detailed CI/CD evidence.

Do not treat a linked pull request as approval to merge or deploy. Existing repository controls and Vision’s reviewed actions remain in force.

Be precise about a connection

A tool reference, saved storage link, authenticated connection and active workflow are different things. Verify the connection and supported actions before relying on an integration.

Teams support is not identical to every Slack interaction. MCP access depends on the configured server, tools, grants and review policy.

Start with the core engine

Common Start here answers, engagement deadlines, acceptance checks, views and reporting are based on recorded data and rules. They do not need AI to decide whether a check-in is overdue or a reviewer has accepted a handover.

Configure assistance deliberately

XOS requires the relevant paid add-on grant, a connected provider and administrator policy. Admins control permitted models, budgets and the kill switch. Fovelets are Vision’s specialist roles.

For deeper Start here questions, automatic fallback can use a configured provider within those allowances. Missing evidence or setup is explained; no answer should fabricate missing records.

Separate an answer from an action

Source access, action permissions, approvals and revision checks are enforced by the server. A model response cannot grant itself access or bypass a budget. Start here answers do not execute model-proposed changes.

MCP connections expose only their configured, authorized capabilities. They do not mean every external system is automatically indexed or searched.

Use Field Library

1. Open Administration → Field Library

   Owners and Admins manage task field definitions.

2. Choose the scope and type

   Define a field for the Frame, Work Area or project. Supported types include Text, Number, Date, Checkbox, Select and URL.

3. Add a clear name

   Use a label people can understand and fill consistently.

4. Use it on tasks

   Permitted task editors fill values in Fields below Activity.

Keep existing values safe

Definitions can be renamed, extended with select choices, archived or restored. Their type and location stay fixed after creation to preserve meaning. Archived fields retain recorded values.

Engagement fields have their own existing editor, linked from Field Library. They are not yet one combined catalog with task fields.

Understand the lock

Only an authenticated Owner or Admin manages definitions. A locked action leads through administrator sign-in; a shared password does not elevate a member’s account. Existing task edit permissions govern values.

Administrator starting checklist

1. Confirm the Frame

   Make sure you are configuring the intended organization.

2. Set up people and teams

   Use active accounts and appropriate roles. Confirm identities before assigning imported work.

3. Create the Work Area

   Choose ownership, access, optional folders and the views the team needs.

4. Try a complete workflow

   Create work, assign it, record progress, request a review and finish the handover as the relevant users.

5. Expand deliberately

   Add fields, packs and integrations once the basic workflow is clear.

Access follows the work

Frame membership does not mean every person can see every private record. Work Area, folder and record rules still apply. Search, reports, agents and connected workflows preserve those boundaries.

Adding a view, linking a record or mentioning a person does not grant additional access. Test important workflows using the actual member role.

Optional capabilities

XOS, On-call, CMDB Lite and ITSM Lite require the relevant server-owned paid grants. A pack, prompt or workspace setting cannot grant them. Availability also depends on your deployed release and configuration.

Use the in-product Help center for detailed operational guidance. Contact your Nano X representative for account or onboarding questions.

Import customer engagements

1. Prepare a supported export

   Use the engagement import workflow for a CSV or JSON export. Current batches support up to 500 projects and a 5 MB file.

2. Choose the destination

   Confirm the Frame and an accessible Work Area/folder before proceeding.

3. Map the records

   Review source IDs, statuses, fields, lead identities and initial check-in settings.

4. Inspect the preview

   Resolve invalid rows and duplicate source IDs. Preserve the original ownership when no active account matches.

5. Import, then activate the rhythm

   Map active leads and review check-in deadlines before expecting engagement obligations to run.

Keep imported history in perspective

A source modification date is not proof of customer contact. Unmatched accounts should remain Needs setup rather than being assigned to a convenient default person.

An import does not create external accounts, grant source-system access or establish continuous synchronization. Keep the original source available until the imported results are reviewed.

Make the imported work useful

Open an imported record, verify its fields and ownership, and run a real workflow with the team. Use the focused Work Area and Engagements dashboard to establish the ongoing operating rhythm.