SENET uses a unified approach to registration fields. All settings are synchronized across all system modules: on the login screen, in Shell, CAP, and SENET ID.
Field Types and Their Management
You can manage data display in the Settings → CAP (Portal settings) section.
| Field Type | Examples | Management |
|---|---|---|
| System | Email, login, first name, password | Always required. Cannot be disabled. |
| Profile | Phone, surname, gender, etc. | Can be enabled/disabled in the settings. |
If you select registration by phone number, the system will automatically make this field required instead of email.
Required Fields and Modal Window
You can set each field to "Required" status. This activates strict data entry control:
During registration: The user will not be able to create an account until all required fields are completed.
Appearance of new fields: If you make a field required after users have already registered, a modal window will appear the next time they log in.
Action blocking: The modal window will not allow the user to continue until the missing data is entered. This ensures your customer database is always complete.
Customisable Field States
In addition to being required, fields can have the following states:
Enabled — the field is displayed in forms.
Restricted — the field is visible only to staff with the appropriate permissions; it is hidden from regular users and other staff.
Access Rights
Two permissions define field logic management:
1. Permission: Configure registration fields
Allows enabling/disabling fields and changing their states (required/restricted). Without this permission, staff can only view the settings.
2. Permission: Access sensitive user data
Determines which staff members can view and edit data in “Restricted” fields.
If an employee does not have this permission, they will not see restricted fields in the player's profile.
This does not prevent the employee from saving the form, even if the restricted fields are not completed.
This allows you to centrally manage user data collection and protect sensitive information, while maintaining flexibility for different registration scenarios.
Comments
0 comments
Please sign in to leave a comment.