Keep clients separate
Review requests in the client’s organization. Technicians can see which client, device and user each request belongs to.
For managed service providers
Manage client access in one console.
Handle Windows elevation requests by client organization. Give technicians the app, device and reason they need to make a decision.
Up to 50 Windows devices free forever
Built around client work
A clear view for each client.
Make approvals easier to handle across client environments, while keeping requests and policies in the organization they belong to.
Set rules by client
Use rules for known applications and keep exceptions available for technician review. Each client can have different needs.
Review decisions across your work
Find which requests were approved, denied or handled by a rule. Use the audit trail to discuss recurring exceptions with clients.
A repeatable MSP rollout
Start with one client.
Pick a client with common Windows elevation needs and use the pilot to refine your approval process.
- 1Choose an initial clientAgree which devices and routine Windows tasks are in scope.
- 2Define who reviews requestsMatch approvals and rules to your client’s needs and your technicians’ responsibilities.
- 3Review before expandingCompare handling time and review the record of decisions together.
Common questions
MSP rollout questions.
Can I review requests by client?
Yes. The dashboard is designed around separate client organizations. You can review requests with client, user and device context.
Can clients have different rules?
The policy model is designed around organization scope. Set rules that match each client’s approved applications and review process.
What if I manage more than 50 devices?
Contact the team with your device and client counts to discuss a larger rollout.