SyteLine User Administration: Complete Management Guide
User administration in Infor SyteLine controls who can access the system, what they can see and do, and how their sessions are managed. Proper user setup goes beyond creating login credentials—it involves license type assignment, security group membership, default site configuration, and form-level access permissions. Misconfigured user profiles are the most common source of support tickets in SyteLine environments, and a disciplined administration process prevents both security gaps and frustrated users.
User Profile Creation and License Assignment
New user setup in SyteLine begins in the Users form (System Administration > Users) where you create the user profile, assign authentication credentials, and select the license type. SyteLine license types—Named User, Concurrent, Self-Service, and Shop Floor—determine which forms and features the user can access and how the license pool is consumed. The user profile also defines the default site, language, configuration, and initial form that loads at login. For environments using Windows Authentication or LDAP integration, the username must match the domain account, and the authentication mode is set in the SyteLine Configuration Utility (SLConfigUtil.exe) on the utility server.
- Create user profiles in System Administration > Users form with username, full name, email, and license type assignment
- Select the appropriate license type: Named User (dedicated), Concurrent (shared pool), Self-Service, or Shop Floor Terminal
- Set the default site, configuration, and initial form in the user profile to streamline the login experience
- Configure authentication mode in SLConfigUtil.exe: Forms Authentication (SyteLine-managed) or Windows Authentication (domain SSO)
- Enable or disable user accounts using the Active flag rather than deleting users to preserve audit trail integrity
Role-Based Access and Default Configuration
After creating the user profile, assign security groups that control form access, field visibility, and data-level permissions. SyteLine's security model is additive—users receive the union of permissions from all assigned groups. The User Groups form (System Administration > User Groups) maps users to one or more security groups. Each user also needs a default configuration that determines the SyteLine client behavior: web client URL, form rendering options, and session timeout parameters. For multi-site deployments, the user's site assignment controls which site's data they access by default and whether they can switch between sites during a session.
- Assign security groups to users through the User Groups form, granting cumulative permissions from all assigned groups
- Set the user's default configuration to control client type (Web, Smart Client) and session behavior parameters
- Configure multi-site access by assigning primary site and enabling site-switching permissions for cross-site users
- Define user-level overrides for email notification preferences, report output format, and homepage layout
- Document the standard security group assignments per job role using a User Access Matrix for audit compliance
Session Management and Troubleshooting
Active user sessions are monitored through the Active Sessions form (System Administration > Active Sessions) which shows connected users, session duration, client type, and last activity timestamp. Session management is critical for concurrent licensing environments where orphaned sessions consume license slots. The SyteLine Application Server (Mongoose) manages session state, and the session timeout parameter in the configuration determines how long an idle session persists before automatic termination. Common user administration issues include locked accounts from failed login attempts, session persistence after browser closure, and license pool exhaustion during peak usage.
- Monitor active sessions in System Administration > Active Sessions to track license consumption and identify idle connections
- Configure session timeout in the Configuration form (typically 20-30 minutes) to automatically release idle license slots
- Use the Kill Session function in Active Sessions to forcibly terminate orphaned or stuck user sessions
- Set account lockout policy in SyteLine Parameters: maximum failed attempts (typically 5) and lockout duration (15-30 minutes)
- Run the User License Utilization report weekly to identify over-provisioned Named licenses that could be converted to Concurrent
Need streamlined user administration in SyteLine? Netray's AI agents automate user provisioning, license optimization, and access auditing—book a demo.
Related Resources
SyteLine Security Group Configuration Guide
Configure security groups in Infor SyteLine to control form access, field visibility, and data permissions. Step-by-step guide for role-based security administration.
Infor SyteLineSyteLine Environment Management Guide: Dev, Test, Prod
Manage SyteLine development, test, and production environments with database refresh, configuration sync, and promotion workflows. Complete environment admin guide.
Infor SyteLineSyteLine Security Roles Best Practices
Design SyteLine security roles for least-privilege access. Role architecture, form permissions, IDO security, and audit compliance for CloudSuite Industrial.