Enterprise Deployment: Common Questions

This page is for the “roll it out across the organisation” case. The authoritative feature-by-feature breakdown is on the pricing page; this page explains what those rows actually mean.

How do I deploy WorksLink across hundreds of machines?

Use mass deployment, which is included on every plan, free included. Once machines are enrolled, they are organised through device management and groups.

Can devices be organised into groups?

Yes, but two separate things are worth distinguishing:

• Group management — categorising devices. Available on every plan.
• Group sharing — sharing a group with other accounts. Team and Enterprise only.

For a multi-person operations team, group sharing is the one that matters: without it each account only sees its own groups, and “access by role” has nowhere to live.

How many policies can I configure?

Unlimited, on every plan.

Can it be branded as our own product?

Yes — custom branding is a Team and Enterprise capability; Free and Personal do not include it. For software vendors and equipment manufacturers who deliver remote support under their own brand, this is usually a hard requirement.

Can WorksLink integrate with our own systems?

Team and Enterprise plans provide two kinds of integration:

• Remote control integration — embedding the ability to start a session in your own system
• Recording and connection log integration — feeding audit data into your own ticketing or compliance systems

Free and Personal plans do not include integration.

What actually separates the Team and Enterprise plans?

This is the most-asked question and the least obvious from the comparison table:

Across every row of the feature comparison, Team and Enterprise are identical. The difference is the number of licensed accounts — Team includes one, Enterprise includes three — with pricing to match.

Channel and device allowances start the same on both and can be increased on either. In other words: if you only need one sign-in seat, Team is not missing any feature.

Is self-hosted deployment available?

A standalone deployment option exists. Because it depends on your network environment, compliance requirements and operating model, arrangements go through customer support rather than a standard published plan.

What should be settled before rolling out widely?

Three things, in this order:

1. Decide which machines are unattended and write the list down — that is your access boundary. See unattended access.
2. Confirm the audit trail is on — logs and recording are Team and above. See security and auditing.
3. Standardise device naming and grouping — a list of five hundred ad-hoc names is unusable when you actually need to find a machine.

The fuller rollout sequence is in remote desktop for internal IT operations.