Glossary
One concept, one word. These are the terms used across the panel, emails, and these docs.
| Term | Meaning |
|---|---|
| Workspace | Your organization’s space in Dynacop — resources, people, team, and settings live here. |
| Customer | A workspace you manage on behalf of a client (MSP model). Your company is the provider. |
| Resource | A protected machine (Windows server or desktop) running the agent. |
| Person | A human, identified by email. Never derived from a Windows login name. |
| Account | A Windows login account on a resource (e.g. Administrator). Never a human. |
| Access | The bond allowing a Person to sign in to a Resource (optionally: which Account, which protocol, until when). |
| Registration code | A DC-… code that authorizes a machine to join your workspace at install time. Single-use or a reusable key. |
| Invitation | An emailed one-time link a person uses to enroll their authenticator. |
| Authenticator | The person’s TOTP app (Google Authenticator, Microsoft Authenticator, Authy — any standard app). |
| Shield | Dynacop’s attack-blocking layer: correlates failed sign-ins by source IP and blocks attackers in Windows Firewall. |
| Attack | A detected brute-force source — failed Windows sign-in events aggregated per source IP. |
| Block | A single firewall block against one IP: automatic (threshold), persistent (low-and-slow), or manual. |
| Monitor-only | A resource that watches sign-ins but doesn’t prompt for MFA (Require MFA on: none). |
| Enforced | A resource that requires the second factor on console and/or RDP sign-ins. |
| Fail-mode | What happens when MFA can’t complete: open = allow (default), closed = deny. |
| Trusted device | A browser that skips the email step of panel sign-in for 30 days. |
| Team | Your panel administrators and their roles (separate from people who merely sign in to machines). |