Administrative Users Sample Clauses

Administrative Users. During the configuration and set-up process for each Platform, Customer will identify an administrative user name and password for Customer's Periscope account. Periscope reserves the right to refuse registration of or cancel user names and passwords it deems inappropriate.
AutoNDA by SimpleDocs
Administrative Users. Administrative Users shall be issued a password for Customer’s account. Administrative User accounts cannot be shared or used by more than one Administrative User. In addition to any other terms and conditions contained herein, as a condition to access and use of the SaaS, each Administrative User shall agree to abide by the terms of Better Impact’s click-through end-user terms of use which Better Impact may adopt from time to time, and, in each case, Customer shall ensure such compliance. Customer shall immediately notify Better Impact of any violation of the terms of any of the foregoing by any Administrative User upon becoming aware of such violation, and shall be liable for any breach of the foregoing agreements by any Administrative User. Customer will be responsible for (i) all uses of any account that Customer has access to, whether or not Customer has authorised the particular use or user, and regardless of Customer’s knowledge of such use, and (ii) securing its Better Impact account, passwords (including but not limited to all Administrative User and passwords) and files. Better Impact is not responsible for any losses, damages, costs, expenses or claims that result from stolen or lost passwords, any failure of Customer to implement or adhere to reasonable security standards, or any malicious behavior of an Administrative User.
Administrative Users. Client shall designate one person as their Primary Administrative User on Exhibit A, which is hereby incorporated into this Agreement. Client may designate additional Administrative Users authorized to contact MMI for Support Requests pursuant to Sections 2.9 (Support Services) and 2.10 (Support Request Requirements). As described within this Agreement, the person(s) listed in the Exhibit A are the only representatives of Client authorized to contact and submit support requests to MMI, and they are responsible for troubleshooting all Authorized User and Applicant issues prior to submitting support requests to MMI. Client is responsible for maintaining a current list of the Administrative User(s) with MMI, and must notify MMI within 48 hours of any change in an Administrative User by providing MMI an updated Exhibit A listing all of Client’s Administrative Users. Client shall be responsible for training replacements for any of Client’s Administrative Users. If Client requests MMI provide replacement training, such training shall be provided at MMI’s then-standard rates for training. Client shall pay MMI’s then standard hourly rate for support and assistance provided to Administrative Users necessitated from Client’s failure to designate a properly trained person as an Administrative User.
Administrative Users. Administrative Users are users who access the SAS® Financial Management for SAS® 9 Software to perform installation of and set and maintain parameters around the use of, applications running the SAS® Financial Management for SAS® 9 Software.
Administrative Users. During the configuration and set-up process for each Platform, Customer will identify an administrative user name and password for Customer’s Pinnacle account. Pinnacle reserves the right to refuse registration of, or cancel user names and passwords it deems inappropriate.
Administrative Users. A license for a RemoteWare Server also permits up to 10 Users to access the administrative console to modify operating properties of the Program or review information within the administrative consoles.
Administrative Users. An “Administrative User” is an individual who will have access to all functionality of the Service and authority to designate other Administrative Users. Administrative Users determine who will be authorized to use the Service “Delegated User” for the entire Customer. For example, in the event the Customer has specific separate subsidiaries, by authorizing an Administrative User for the customer, the Administrative Users will have rights to any and all legal entities associated with the customer. Customer assumes sole responsibility for designating one or more Administrative User(s), for authorizing their access and for any Delegated User access. Administrative User is responsible for, but not limited to; (a) the receipt, proper distribution and maintenance of all user access; (b) maintaining the ability of the Delegated Users to access the Services; (c) if desired, establishing limits on each Delegated User’s authority to access information and conduct transactions; (d) designating another Delegated User to be a successor Administrator who will, when authorized, possess the Administrator’s capabilities; (e) adding, modifying or removing any Administrative or Delegated User access, and making other changes to transaction access of Delegated Users. Customer is responsible for any Payments, Transfers and other Services executed by Administrative or Delegated Users and the resulting charges for those services which may be incurred by Customer Xxxxxxx assumes no responsibility for designation, validation or usage related to customer access to the service. Customer shall notify Bank of any changes in access to or use of the services by the Administrator(s). Notwithstanding the foregoing, whenever an Administrator leaves Customer’s employ or Customer otherwise revokes an Administrator’s authority to access or use the Services, Customer must notify Bank in writing immediately.
AutoNDA by SimpleDocs
Administrative Users. Client authorizes its Admins to (i) act on Client’s behalf; (ii) provide information on Client’s behalf; and
Administrative Users. During the configuration and set-up process for each Platform Instance, Customer will identify an Administrative User name and password for Customer’s AIT account. AIT reserves the right to refuse registration of, or cancel User names and passwords it deems inappropriate.
Administrative Users. During the configuration and set-up process for each Platform, Customer will identify an administrative user name and password for Customer’s FullPath account. FullPath reserves the right to refuse registration of, or cancel usernames and passwords it deems inappropriate.
Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!