2FA
Two-factor authentication
In addition to a password, the user enters a one-time code sent to their email address.
Security
Keep your data where you want it.
fsDesk Pro runs on your organization's infrastructure. Access to information is controlled through roles, permissions, and separate views for the service team, customers, and subcontractors.
Discuss security requirementsDEPLOYMENT
On‑premise
The application and its data run on a server controlled by your company.
ACCESS
Roles and scopes
Users only see the functions and information they need for their work.
AUTH
2FA
An additional login code strengthens account security.
VISIBILITY
Full separation
Customers and subcontractors do not get access to the entire ticket database.
Access architecture
Not every user needs the same view of the system.
That is why fsDesk Pro separates the views of the service team, customers, and external companies.
01 / TEAM
Administrator, coordinator, technician
Roles can separate administrative tasks, work coordination, and the handling of specific tickets.
02 / CUSTOMER
Separate customer portal
Customers can view their own tickets, communication, statuses, and attachments without access to other customers' data or internal service information.
03 / SUBCONTRACTOR
Access only to assigned tickets
An external company can work on an assigned task in fsDesk Pro without gaining access to the entire organization or other customers.
Protection layers
Security is part of everyday work, not a separate module.
ALERTS
Login notifications
The system can send email notifications about successful and failed login attempts.
PERMISSIONS
Field and status permissions
You can control not only access to a module, but also who can edit specific data and make workflow changes.
CONTINUITY
Temporary substitutions
During an absence, responsibilities and notifications can be temporarily transferred to a designated person.
On‑premise
Your infrastructure. Your procedures.
The deployment model lets your organization retain control over backups, server administration, and its own environment maintenance policies.
Define during deployment
Server environment
Where the application and database will be installed.
Backups
In line with your organization's security policy.
User roles
Who administers, coordinates, and works on tickets.
Customer access
The scope of visibility and actions available in the customer portal.
Organizational requirements