Vycko
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.

Two IT administrators planning computer settings at their workspace.

Explore administration in detail.

Open a feature to read the full explanation, practical examples and controls.

Administration

Agent enrolment & deployment

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

Read the full 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.

Read the full 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.

Read the full 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.

Read the full explanation of API, MCP & webhooks

What it does

Connect your own AI assistant to Vycko’s evidence and remote tools through MCP. Engineers can investigate device health, inspect services, processes, logs and files, and make permitted repairs from a compatible assistant. Direct MCP tools use the platform API without invoking Vycko’s built-in AI, so the reasoning uses your assistant account instead of Vycko AI tokens.

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.
  • ChatGPT and Claude. Use a private OAuth connection for supported ChatGPT custom apps, or a scoped bearer API key with Claude Code and compatible MCP clients. Claude Desktop needs a compatible bridge; the current private OAuth route does not support direct claude.ai sign-in.
  • Diagnosis and repair. Read device evidence, request reviewed runbooks, use permitted remote actions and verify the result. Tool responses and reasoning are handled by your chosen assistant under its own account terms and usage limits.
  • 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 connection’s scope, permissions, client and current tool catalogue. Direct changes can run immediately, and change-capable connections can make approval decisions in the key owner’s name. Your AI provider’s subscription, usage limits and charges still apply. Webhook receivers must verify signatures and handle retries.

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.

Read the full 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
Administration

Microsoft 365 management

Manage Microsoft 365 users, licences, mailboxes and groups beside your devices. Review security signals and controlled starter and leaver workflows.

Read the full explanation of Microsoft 365 management

What it does

A new starter, a full mailbox or a leaver request often involves more than one system. Vycko brings Microsoft 365 work into the customer's workspace, so the people, licences and computers can be handled with the same support context.

How you can use it

  • Prepare for Monday. Close access when someone leaves.. A starter request arrives through the portal. The technician creates the Microsoft 365 account with the appropriate licence and groups, prepares the usual software and checks the laptop. The request and conversation stay with the customer.
  • Spot a full mailbox before it stops the work. The accounts mailbox is nearly full. The warning appears before the team starts receiving delivery failures, giving the technician a chance to review the mailbox and choose the permitted next step.
  • Put unusual account activity in front of the right person. An alert identifies a new rule forwarding mail outside the company. The technician can investigate the rule, review sign-in evidence and make an authorised response, with the steps recorded.

In practice

The accounts mailbox is nearly full. The warning appears before the team starts receiving delivery failures, giving the technician a chance to review the mailbox and choose the permitted next step.

Controls & availability

Availability depends on the enabled services, customer policy, device support and granted permissions. October additions are being rolled out; confirm the available workflows during setup. Changes use the applicable approvals, fresh-code controls and audit history.

Ask us about Microsoft 365 management
Administration

Reseller companies & branding

Give partner IT companies their own branding, verified domains and customer workspace, with company access boundaries and separate AI allowances.

Read the full explanation of Reseller companies & branding

What it does

Vycko supports IT companies serving other IT companies. Each reseller company can run its customer operation with its own name, branding and web addresses, while the platform keeps its company records and access scoped separately.

How you can use it

  • Make the staff app and customer portal feel familiar. Use your company name, light and dark logos, colours, support email and telephone number. Verified domains give staff and customers the appropriate branded address.
  • Separate company records and access. Each reseller company has its own customers, devices, engineers, keys, settings, audit log and AI allowance. Company filtering and database row security form part of the documented boundary.
  • One partner's support operation. A partner IT company supports its own customer estate. Its engineers sign in at the partner's address with its logo and colours. Customers use the partner's portal for requests and reports, while the company keeps its own access keys, limits and AI allowance.

In practice

A partner IT company supports its own customer estate. Its engineers sign in at the partner's address with its logo and colours. Customers use the partner's portal for requests and reports, while the company keeps its own access keys, limits and AI allowance.

Controls & availability

Availability depends on the enabled services, customer policy, device support and granted permissions. October additions are being rolled out; confirm the available workflows during setup. Changes use the applicable approvals, fresh-code controls and audit history.

Ask us about Reseller companies & branding

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.

See Vycko working.

Bring the jobs you want to make easier. We’ll show you the relevant workflows.

Newark Solutions Ltd trading as Vycko