Diagnosly
Register
Product How it works Personality Pricing Docs Sign in Register
Browse documentation
Personal
Getting started
What is Diagnosly Personal?Signing inInstalling the appYour first diagnosisA tour of the app
Using Diagnosly
Running a diagnosisDiagnosis historyFollow-upsWhat it can change, and how you approve itBackups and restore pointsApp updates
Credits and billing
How credits workSpending limits and checkpointsTopping up
Privacy and security
Privacy basics (PII scrubber)Your data and deleting your account
Help
TroubleshootingFrequently asked questions
Enterprise

For IT teams managing many PCs. Not needed for Diagnosly Personal.Learn more

Set up your fleet
Fleet agent installSetting up your first fleet
Fleet management
Fleet overviewFavouriting devicesBulk actionsRunning checksCommand audit trailFleet troubleshooting & alerts
Security and access
Role-based access control
Integrations
SSO with OktaSSO with Azure AD / Entra IDSMTP / email

Role-based access control

Three roles, admin, tech, viewer, gate access to user management, command execution, and read-only views.

Diagnosly has three built-in roles, set per user and scoped per tenant.

Role What they can do
admin Everything: user management, billing, install tokens, settings, delete devices
tech Run scripts, diagnose, view command history, manage script library, manage schedules
viewer Read-only across the dashboard. Cannot run commands, cannot edit any config

Assigning roles

In Admin → Users, change a user's role via the inline dropdown. You can't change your own role (prevents lockout).

Self-protect

The system prevents:

  • Deleting yourself.
  • Deactivating yourself.
  • Demoting yourself away from admin if you're the last admin.

Sessions & MFA

JWTs are 1-day TTL by default. MFA enforcement is per-tenant:

  • disabled: no MFA challenge ever
  • optional: users can opt in; not required
  • required: every user must enrol before first login
  • admin_only: only admin users must enrol

Configure at Settings → Security.

SSO

If you've configured an OIDC or SAML identity provider (Okta, Azure AD, Google Workspace), users sign in via that flow. JIT user provisioning creates the user on first login. See SSO with Okta.