
Overview
User Management controls who can access Fentu FSM and what they can do within the system. Each person who needs to log in requires a user account with appropriate permissions based on their role.User accounts are separate from technician records. A technician needs both a technician profile (workforce data) and a user account (system access) to use the mobile app.
When to Manage Users
Access this module to:- Create Accounts - Set up new users
- Manage Permissions - Control what users can access
- Reset Passwords - Help users who are locked out
- Deactivate Accounts - Remove access for departing employees
- Audit Access - Review who has access to what
User Information
Each user account includes:| Field | Description |
|---|---|
| Username | Login identifier |
| Contact email (often used as username) | |
| Full Name | Display name |
| Profile | Permission profile assigned |
| Branch | Associated branch |
| Status | Active, Inactive, Locked |
| Last Login | Most recent access |
| Created Date | When account was created |
User Types
| Type | Description | Typical Access |
|---|---|---|
| Administrator | System administrators | Full access to all features |
| Dispatcher | Service coordinators | Work orders, scheduling, customers |
| Technician | Field technicians | Mobile app, assigned work |
| Manager | Team managers | Team data, reports |
| Accountant | Finance users | Invoicing, financial reports |
| Read-Only | View-only access | Reports and dashboards |
Creating Users
Linking Users to Technicians
For field technicians:- Create the user account first
- Open the technician record
- Link to the user account
- Or select existing technician when creating user
Managing Permissions
Through Profiles
Permissions are assigned via profiles:- Each user gets one profile
- Profile determines accessible features
- Change profile to change permissions
- See Profiles & Roles for details
Data Access
Control what data users can see:| Level | Description |
|---|---|
| Global | All data across all branches |
| Branch | Only data for assigned branch |
| Team | Only data for assigned team |
| Personal | Only own records |
Combine permission profiles with data access levels for granular control. A dispatcher profile with branch-level access sees all work orders but only for their branch.
Account Administration
Password Management
| Action | How |
|---|---|
| Reset Password | Admin sets new temporary password |
| Force Change | Require password change at next login |
| Unlock Account | Clear lockout after too many failed attempts |
| Password Policy | Set minimum requirements (length, complexity) |
Account Status
| Status | Meaning | Action |
|---|---|---|
| Active | Normal, can log in | None needed |
| Inactive | Disabled, cannot log in | Reactivate to restore access |
| Locked | Temporarily blocked | Unlock to restore access |
| Pending | Awaiting first login | User needs to set password |
Security Features
- Session Timeout - Automatic logout after inactivity
- Login Attempts - Lock after too many failures
- Two-Factor Authentication - Additional login verification
- Password Expiration - Force regular password changes
Bulk Operations
Importing Users
For multiple new users:- Prepare user data in spreadsheet
- Use Import function
- Map columns to user fields
- Review and confirm import
- Send welcome emails with credentials
Exporting User List
Export user data for:- Audit purposes
- Integration with HR systems
- Backup before changes
- Compliance reporting
Best Practices
Unique Usernames
Unique Usernames
Use email addresses as usernames when possible. They’re unique and users remember them.
Minimum Permissions
Minimum Permissions
Give users only the permissions they need. More access means more risk.
Regular Audits
Regular Audits
Periodically review user accounts. Remove or deactivate unused accounts.
Prompt Deactivation
Prompt Deactivation
Deactivate accounts immediately when employees leave. Don’t wait for cleanup later.
Strong Passwords
Strong Passwords
Enforce password complexity. Weak passwords are the most common security vulnerability.
Document Assignments
Document Assignments
Keep records of why users have specific profiles. This helps with audits and reviews.
Common Questions
What's the difference between user and technician?
What's the difference between user and technician?
A user account provides system login access. A technician record contains workforce data. Field technicians need both.
Can one person have multiple user accounts?
Can one person have multiple user accounts?
Generally no. One person should have one account. Use profiles to grant access to multiple areas.
How do I handle shared logins?
How do I handle shared logins?
What happens when an account is locked?
What happens when an account is locked?
The user cannot log in. An administrator must unlock it. This typically happens after too many failed login attempts.
Can users change their own email/username?
Can users change their own email/username?
Depending on configuration, users may update their email. Username changes usually require admin action.
How do I transfer work when someone leaves?
How do I transfer work when someone leaves?
Reassign open work orders before deactivating the account. The system may prevent deactivation with active assignments.
Related Documentation
Profiles & Roles
Permission configuration
Technicians
Technician management
System Settings
Security settings
Import
Bulk user import
