1

Follow guided activation

New organisations open on a persistent activation path. It tracks the required journey from workspace and service foundation to agent credential, first reporting endpoint and first ticket.

  • Use the setup strip to return to the next required action from anywhere in Ordantra.
  • Required milestones define operational readiness; inviting teammates and resolving the first outcome remain visible without blocking solo operators.
  • Platform administrators can see the current milestone without accessing tenant work.
2

Understand the organisation boundary

Your organisation owns membership and can contain one or more workspaces. A workspace isolates tickets, assets, agents, queues, teams, policies and reports for a team or operation.

  • New registrations receive an editable Main workspace.
  • Keep one workspace when the whole team shares an operating model.
  • Create another workspace only when data or policies genuinely need separation.
3

Review the starter service desk

The initial workspace includes a default Service desk queue, Service desk resolver team and Standard support SLA policy. They are starting points, not a prescribed operating model.

  • Rename or extend the starter records to match real ownership.
  • Existing empty workspaces can create the same foundation with one guided action.
  • Confirm inbound email, portal and notification delivery before broad rollout.
4

Run an endpoint pilot

Enrol a small Windows or Linux pilot before a fleet rollout. Confirm identity, inventory category status, last-seen time, risk findings and the platform-specific agent baseline.

  • Use the workspace enrolment key only for registration.
  • Start with representative endpoints, not every device.
  • Review collected and unavailable inventory categories.
5

Prove the connected workflow

Take one real ticket from triage through asset context and resolution, then run one controlled change with approval, validation and rollback information.

  • Assign clear ownership in the queue.
  • Link the affected asset or problem.
  • Confirm the activity trail tells the story afterward.