Genesys’ User Access Sample Clauses
The 'Genesys’ User Access' clause defines the terms under which users are granted access to Genesys’ systems, platforms, or services. Typically, this clause outlines who is authorized to use the system, the process for assigning user credentials, and any restrictions or responsibilities associated with such access. For example, it may specify that only designated employees of the client company can log in, and that sharing login information is prohibited. The core function of this clause is to ensure secure and controlled access to Genesys’ resources, thereby protecting sensitive information and maintaining system integrity.
Genesys’ User Access. Genesys will create individual user accounts for each of its employees or contractors that have a business need to access Customer Data or Customer systems within the Genesys PureConnect Cloud Service environment. The following guidelines will be followed regarding Genesys user account management:
(A) User accounts are requested and authorized by Genesys management.
(B) Strong password controls are systematically enforced.
(C) Connections are required to be made via secure VPN using strong passwords that expire every ninety (90) days.
(D) Dormant or unused accounts are disabled after ninety (90) days of non-use.
(E) Session time-outs are systematically enforced.
(F) User accounts are promptly disabled upon employee termination or role transfer, eliminating a valid business need for access.
Genesys’ User Access. Genesys employees approved to access R2S or A3S are required to use multi- factor authentication, but VPN is not required. Genesys employee accounts to R2S are reviewed at least every 90 days.
Genesys’ User Access. Genesys will create individual user accounts for each of Genesys’ employees that have a business need to access Customer Data or Customer’s systems within the Cloud Services environment. The following guidelines will be followed regarding Genesys’ user account management:
3.3.1. User accounts are requested and authorized by Genesys management.
3.3.2. Strong password controls are systematically enforced.
3.3.3. Connections are required to be made via secure VPN using strong passwords that expire every ninety (90) days and multi- factor authentication.
3.3.4. Session time-outs are systematically enforced.
3.3.5. User accounts are promptly disabled upon employee termination or role transfer that eliminates a valid business need for access.
Genesys’ User Access. Genesys will follow strict protocol and authorisation flows to create individual user accounts for each of Genesys’ employees that have a business need to access Customer Data or Customer’s systems within the Cloud Services Environment. The following protocol will be followed regarding Genesys’ user account management:
Genesys’ User Access. 1. Genesys employees who are approved to access the A3S Environment require multi-factor authentication, but the VPN, VDI, and direct access to product prohibitions and controls in Genesys Cloud do not extend to the A3S environment.
2. Genesys employee account access to the A3S environment is reviewed at least every 90 days.