Roles and the audit trail
- Viewer sees everything and changes nothing. For managers and auditors
- Operator can also run a backup, restore files to the machine they came from, and handle alerts
- Administrator can do everything, including adding repositories, devices, policies and users, and restoring one machine's data onto another
- Two-factor authentication with an authenticator app, plus single-use recovery codes. Setup verifies before it is switched on, so a half-finished setup can never lock you out
- Sign in with Microsoft 365 is available. If your administrator has connected your organisation's Microsoft 365 account, users can sign in with their existing Microsoft identity instead of a separate password. The section below has the setup steps
- Changing a password signs that account out everywhere it was already signed in, so a departing employee or a stolen login does not keep working because a browser tab stayed open
- Signing in and adding a device are both rate limited, so a stolen password cannot be paired with unlimited guesses at the second factor
- The audit log under Monitoring records sign-ins, policy changes, restores, users added, and tokens made and revoked, with who did it and when. It is kept for 365 days, and you can search it by person, machine, action or date. If an auditor needs a copy, ask us and we export it for you
- The audit trail survives deletion of the client it belongs to
Microsoft 365 single sign-on
If your organisation uses Microsoft 365, your team can sign in to the Satkosh console with their existing Microsoft account instead of managing a separate password. An administrator connects the account once, and after that any user created in the console can use the Sign in with Microsoft button on the login page.
An administrator signs in to the Satkosh console and opens Settings, Microsoft 365 Sign-In.
The administrator connects the organisation's Microsoft 365 account. This is a one-time setup that authorises Satkosh to accept sign-ins from your Microsoft 365 directory.
The administrator creates users in the Satkosh console. Each user is mapped to their Microsoft 365 identity.
Once created, users go to console.satkosh.com and click Sign in with Microsoft. They authenticate with their existing Microsoft 365 credentials and land in the console without a separate password.
- Only an administrator can connect the Microsoft 365 account. This is deliberate: linking an identity provider is a security decision, not a convenience one
- Users must be created in the Satkosh console first. A Microsoft 365 account alone does not grant console access until an administrator has explicitly added that user
- Removing a user from your Microsoft 365 directory, or disabling their account, immediately prevents them from signing in to the Satkosh console
- Microsoft 365 SSO works alongside multi-factor authentication. If your Microsoft 365 tenant enforces MFA, that carries through to the Satkosh sign-in
- Email-and-password sign-in continues to work for accounts that are not connected to Microsoft 365, so mixed environments are supported
- Google Workspace SSO is on the roadmap for organisations that do not use Microsoft
Microsoft sign-in errors: what each error code means and how to fix it