User Management. The Solution shall have a robust user management system that allows administrators to control access to the platform, set permissions, and manage user accounts.
User Management. Participant may allow Access to its employees, agents, medical staff, other health care providers, and other support staff employed or otherwise retained by Participant who have a need for Access in providing services for or at Participant (“Users”) and who have accepted the EpicCare Link User Terms and Conditions, as may be amended from time to time by HSHS. Participant shall provide such access in accordance with any agreed upon procedures for granting Access to Users. HSHS shall retain final authority with respect to the granting of Access to Users. Participant shall require that all User Access is in accordance with written reference manuals, training materials, and procedures relating to Users’ Access (“User Documentation”) provided by HSHS (if any).
User Management. According to the subscription licensed, QUADIENT will provide You with the adequate access log-ins to the Quadient Cloud Services. If You create a user account via the web-portal at xxxxxxxxxxxxx.xx, or synchronize your users with other user management tools, You are responsible for the authorized users Yourself. Once You have created a company account, You may invite the authorized users for Your entity. Please make sure You explain to Your authorized users that all users invited to the portal have the same rights and may change or delete the information. If an accidental deletion happens on Your side, QUADIENT cannot guarantee a back-up. Please make sure You back-up and archive Your Customer Data and content in your own systems regularly. Upon the establishment of a subscription or License, one or more User names and passwords may be generated in connection with such subscription or License (“Credentials”). The Credentials are used to authenticate the User and thereby allow access to the Services, including any of your data stored as part of the Services. You are solely responsible for maintaining the confidentiality of the Credentials and may not transfer or share the Credentials with any third parties. You acknowledge and agree that QUADIENT and its licensors and suppliers may rely on the Credentials as the sole test to control whether Users accessing and using the Services on your behalf are authorized to do so. You are fully liable for any act or omission of any Users that access or use the Services with the Credentials or otherwise through your account. You will: (a) notify QUADIENT immediately of any unauthorized use of any Credentials or account or any other known or suspected breach of security; (b) not impersonate another user or provide false identity information to gain access to or use the Service; and (c) be solely responsible for the accuracy, quality, integrity, legality, reliability, appropriateness, and intellectual property ownership and right to use all data submitted by you in the course of receiving the Services.
User Management. 1. The objective of User Management is to have all State-identified user accounts established and maintained during the development and implementation.
2. The Contractor shall be responsible for establishing a process by which access is granted at various levels according to the user’s role and permissions. The state and contractor will mutually establish which levels each party will be responsible for and then held accountable for adding, deleting, and suspending users of the CCRS solution.
3. The Contractor shall perform other user management functions such as the assignment of roles, initial passwords, password resets, etc. The solution must enable data Stewards to define data access policies and provision access in a self-service manner. The solution must provide a web interface to manage a Role-Based Access Control (RBAC)
User Management. Ability to control access rights to the system by means of a ‘role-based’ system. This includes the ability to define access levels down to the page and virtual page level whereby specific page features can be hidden from certain users
User Management. The user management feature allows an Administrator to manage the Internet Users or groups of Internet Users to ensure that each User only has one account for WCP Service. This feature only works if the directory connectivity shared feature described in Clause 1.1.4.1.3 (Directory Connectivity) is set up to support the User Management feature. Customer acknowledges and agrees that: (i) the WCP Service is priced on per-User basis, (ii) it is responsible for ensuring that each User only has one WCP Service account per User, (iii) Orange or its third party service provider may check the User activity to verify that each User only has one (1) account, and (iv) Orange may increase the Charges for WCP Service without notice if any User is found to have more than one (1) account.
User Management. 3.3.2.1 The Supplier shall ensure the RM/DRS enables the following capabilities as a minimum for registered Contracting Authorities Users and Supplier Users, unless otherwise specified by Contracting Authorities. primary User ID or User reference; full name; e-mail address; User status (new, suspended, terminated, re-certification required, on- leave, etc.); necessary dates (e.g. User account start, termination, last-changed, re- activation); group, job or other role/responsibility; and access the scanned Record(s) through a intuitive electronic search database for instant Electronic Retrieval.
3.3.2.2 The Supplier shall ensure the RM/DRS shall be able to set up Users and User groups with different authorisation and access levels in addition to or in line with Contracting Authorities requirements. This shall include but not be limited to: administrative access to set up user access (creation, updating, suspending, de-suspending and deletion of User profiles); Requestor access to request Records; information editor access; manual Destruction Date amendment access; system privileges.
3.3.2.3 The Supplier shall ensure that the following information is indexed on the RM/DRS for each Record to be scanned, unless otherwise specified by Contracting Authorities: Supplier reference number Date and time Record Scanned Destruction Date Description field
3.3.2.4 The Supplier shall scan each Record individually and save the scan on the RM/DRS in the following format; File type: PDF (or otherwise specified) Scan Resolution: 300dpi (or otherwise specified) Scan Format: black and white (or otherwise specified) File name: RM/DRS barcode number (or otherwise specified)
3.3.2.5 The Supplier shall ensure that each Scanned Record is a clear Image of the original and complies in full with the formats as set out in 3.3.2.4, unless otherwise specified by Contracting Authorities.
3.3.2.6 The Supplier shall ensure that the Record(s) is scanned to ensure that it is demonstrably trustworthy in line with BS10008: Evidential weight and legal admissibility of electronic information, where specified by Contracting Authorities at the Call Off stage.
User Management. 6.1 The User shall be responsible for management and operation of own account information for External Services. Xxxxx shall not be liable for any disadvantage or damages caused by the leak or loss of account information.
6.2 The User shall be responsible for the management of data, software, etc. stored on the device using the SHALO
User Management. 8.5.1 Login with Facebook & Google+ To simplify the sign-up procedure for users, we have implemented a social login service that allows users to sign into Graasp using their existing accounts on popular social networking services. Currently, Graasp supports signing up with Facebook and Google+ accounts in addition to the regular email-based sign- up. Other than speeding up the sign-up procedure, the profile and social graph information obtained from the identity providers (Facebook or Google+) could be used later to provide personalised content for users. Figure 30 shows how the signup process with a social network login works. After choosing to log in with Facebook or Google+, we ask the user’s permission to access her profile information. Once the user grants the permission, she is redirected to the Facebook or the Google+ login page (if she is not already logged in to Facebook or Google+). Using her login information of Facebook or Google+, the user can directly sign into Graasp. To implement the social network login service, we make use of the OAuth xxxx- dard for secure authorization. After the user grants Graasp the permission to access her profile information, a session token is returned from Facebook or Google+. Using the session token, Graasp makes API calls to Facebook or Google+ on behalf of the user, and retrieves the profile information of the user including email, name, picture, and so on. If the email already exists in Graasp, the user automatically signs into Graasp with the existing account. Otherwise, a new Graasp account is created for the user.
User Management. About… Main Toolbar Icons Open Data Run Project Show/Hide Toggles Print Report Show Color Zoom In Zoom Out Set Axis Browse by All Colors Allele Call Icons Size Calibration Show Chart/Table
