Resource, Person, Access
Dynacop is built on three nouns. Learn these and the panel makes sense.
Resource
Section titled “Resource”A Resource is a protected machine — a Windows server or desktop running the agent. It has a name (the hostname), a health state (online / offline / stale), an agent version, and inventory (OS, IP addresses, listening ports, firewall state).
Person
Section titled “Person”A Person is a human, identified by email — not by a Windows login name. This is the key idea: one person uses a single authenticator to sign in to many Windows accounts on many machines. The same identity is used for the panel and for Windows sign-ins.
Access
Section titled “Access”Access is the bond that says this person may sign in to this resource (optionally to a specific Windows account, and optionally only over a certain protocol or until a certain date). Without access, a person cannot pass MFA on that machine.
Person ──has Access to──▶ Resource (+ which Windows account, which protocol)Account (a Windows login) is separate
Section titled “Account (a Windows login) is separate”A Account here means a Windows login account on the machine (like Administrator or test01) — never a human. One or many People can be given Access to the same Windows Account. When several people share one account, the code they enter at sign-in identifies which person it was.
Two planes
Section titled “Two planes”- Access plane — People and their Access to Resources (who can sign in where). Managed under Resource Users.
- Management plane — your admin team and their roles in the panel. Managed under Team.
They’re separate on purpose: being able to sign in to a server is different from being able to administer the workspace.
Next: Person ≠ Account.