Customers and delegation
Dynacop’s MSP model gives a provider one console over many customers, with real isolation between them.
Creating a customer
Section titled “Creating a customer”Under Customers → Add customer, name the customer workspace and choose:
- your team’s role in it (e.g. Operator),
- optionally which group of your team gets the access,
- optionally a duration (30 / 90 / 365 days or unlimited) — expired delegation simply stops working.
The customer’s resources, people, access, and policies then live in their own isolated workspace, while your dashboard, audit, and attack views span your company plus every customer you manage.
Switching context
Section titled “Switching context”Use the workspace switcher to work inside a customer. What you can do there is exactly your delegated role — nothing more.
Technician access: all customers or selected
Section titled “Technician access: all customers or selected”Each of your team members either inherits access to all customers or is set to custom — only the customers (and roles) you pick. This is how you keep a junior tech on two accounts while seniors see everything.
What the customer sees
Section titled “What the customer sees”Transparency is part of the trust model. In the customer’s own workspace, their settings show:
- who manages them (your company, the role, any expiry) — and they can revoke that delegation,
- which external people hold access into their resources, with last-use — revocable individually.
Delegation is single-level: a customer workspace cannot create customers of its own.
Licensing: technicians are free
Section titled “Licensing: technicians are free”Billable people are those with sign-in access to machines. Your technicians manage customers through delegation — they hold no access in the customer’s workspace, so they consume no customer licenses. See billing scope.