IT platform administration and integrations

IT Platform Administration & Integrations

Connect devices, manage access and configure the service. Administration tools, search, exports and integrations support an organised platform as the environment grows.

Explore administration in detail.

Administration

Agent enrolment & deployment

Connect one device or prepare site installers for a rollout. Manage enrolment keys, held devices, agent updates and removal.

Close explanation of Agent enrolment & deployment

What it does

Connect computers to the managed platform through a deliberate enrolment process. Vycko supports individual setup and site-oriented rollout preparation, with controls over enrolment keys, device admission and the agent lifecycle.

How you can use it

  • Start small or prepare a rollout. Enrol an individual computer or prepare the supported site installer route for several devices.
  • Manage admission. Review keys and held devices so computers are associated with the appropriate customer and site before becoming part of ongoing care.
  • Maintain the agent. Follow supported agent-update, health and removal workflows, keeping the installed capability relevant to the tools being used.

In practice

A support provider starts with one business workstation, confirms the customer setup and then prepares the remaining site’s supported rollout.

Controls & availability

Feature availability depends on the operating system, agent version and granted permissions. Windows has the broadest feature set; Mac and Linux capabilities should be confirmed for the intended workflow.

Ask us about Agent enrolment & deployment
Administration

Roles, customer scope & sign-in

Separate administrator, technician and read-only access. Use authenticator sign-in and supported passkeys with scoped customer visibility.

Close explanation of Roles, customer scope & sign-in

What it does

Match platform access to the work a person is responsible for. Roles and customer scope help separate administration, technical support and read-only visibility, while supported stronger sign-in controls protect access to the workspace.

How you can use it

  • Role-based access. Distinguish administrator, technician and read-only responsibilities rather than giving every account the same tools.
  • Customer boundaries. Limit the customers and environments an account can see, keeping a multi-client support team’s access aligned with its responsibilities.
  • Stronger verification. Use supported authenticator sign-in and passkeys, with fresh verification for the sensitive operations that require it.

In practice

A support business gives a technician access to the clients they look after, while an authorised read-only colleague can review the permitted information without changing computers.

Controls & availability

Sign-in is only one layer. Remote tools, approvals, secret reveal and integrations also have their own applicable permission checks; portal users use a separately scoped customer experience.

Ask us about Roles, customer scope & sign-in
Administration

Audit log & CSV exports

Review who changed what and when. Export supported device, inventory, warranty, alert and audit views within the reader’s permissions.

Close explanation of Audit log & CSV exports

What it does

Keep the platform’s decisions and actions reviewable. The audit log records supported activity, while CSV exports make selected estate and support information available for an authorised review outside the dashboard.

How you can use it

  • Who, what and when. Review available action, approval, policy, access and support events with their relevant customer or device context.
  • Investigate and explain. Filter the audit view to understand a change, answer a customer question or review how a support task was handled.
  • Supported exports. Export permitted device, software-inventory, warranty, alert and audit views, following the selected scope and available filters.

In practice

A business asks why a setting changed. The support team reviews the related action and approval record, then shares an appropriate authorised export for the discussion.

Controls & availability

Audit and export access follow the reader’s permissions. An export is a snapshot of the chosen information and does not grant access to hidden customers, secrets or internal data.

Ask us about Audit log & CSV exports
Administration

API, MCP & webhooks

Connect authorised tools through scoped platform access. Manage keys, connected assistants and supported event delivery.

Close explanation of API, MCP & webhooks

What it does

Connect authorised tools to the platform through supported integration routes. API access supports external workflows, MCP connects compatible assistants to permitted capabilities, and webhooks deliver selected platform events to a configured receiver.

How you can use it

  • Scoped credentials. Manage supported access keys and permissions so an integration receives the relevant scope instead of an unrestricted operator identity.
  • Connected assistants. Use the available MCP tools within their configured authority, keeping device work subject to the platform’s applicable controls.
  • Event delivery. Configure supported signed webhook events, review delivery attempts and failures, and manage signing-secret rotation where needed.

In practice

A support business sends selected alert events to an authorised external workflow, while a connected assistant uses permitted platform tools to help investigate a device.

Controls & availability

Available actions depend on the integration’s permission and current catalogue. Webhook receivers must verify signatures and handle retries; an integration does not bypass customer policy or approval requirements.

Ask us about API, MCP & webhooks
Administration

Platform settings & usage

Manage policies, AI controls, update settings, catalogue entries, remote access, portal settings and platform usage.

Close explanation of Platform settings & usage

What it does

Configure the platform around the service you want to provide. Settings bring the supported customer policies, technical controls and delivery choices into a manageable workspace, while usage information helps administrators understand platform activity.

How you can use it

  • Care and automation choices. Manage relevant AI controls, alerts, update policies, remediation settings and reviewed catalogue entries.
  • Access and customer experience. Configure supported remote-access, portal, reporting and integration settings for the intended environment.
  • Administration and review. Manage available agent, vulnerability-data and warranty-provider settings, and inspect the supported usage or cost information.

In practice

An administrator prepares a new customer by reviewing its action rules, update choices, notification routing and portal access before the managed devices are rolled out.

Controls & availability

Sensitive settings require the applicable administrator permissions and verification. Enabling a setting does not add a capability that the device, agent or configured provider does not support.

Ask us about Platform settings & usage

Features depend on the device, operating system, installed agent and configured permissions. Readiness checks provide evidence and guidance, not certification. The website tour uses illustrative data and does not connect to live devices.

IT. On Autopilot.

See Vycko in your environment.

Tell us about the computers or clients you support.

Newark Solutions Ltd trading as Vycko