Login IDs Sample Clauses

Login IDs. Service Provider may assign a login code (a “Login ID”) to each Customer or Recipient User that will have access to the Service Provider Systems. It shall be the Customer’s responsibility (i) to protect these Login IDs against unauthorized disclosure and unauthorized use and (ii) to ensure that the information accessed is used solely for the purpose of receiving Services authorized under the Agreement and for no other purpose. Each Login ID will be used only by the User assigned such Login ID by Service Provider. Customer will not permit Login IDs to be used or shared by multiple employees without Service Provider’s prior written consent. Customer will be responsible for any access to the Service Provider Systems by any User or any person accessing the Service Provider Systems through any Login ID issued to Customer or any User, regardless of whether such access was authorized. Customer will not, and will not permit any person to, use the Service Provider Systems in any manner, or attempt to access areas of the Service Provider Systems, other than as expressly specified in the Agreement.
Sample 1Sample 2
AutoNDA by SimpleDocs
Login IDs. By receipt of this notification, I have been issued a unique Login ID. I will not allow others to login using my Login ID; I acknowledge that it is used for accountability of action performed on Service Provider’s computing environment.
Sample 1Sample 2

Related to Login IDs

  • Hyperlinks 12.1 You must not link to any material using or by means of the Services that would, if it were made available through the Services, breach the provisions of this Policy.

  • Links If The Services are made available through the Internet, the Financial Institution’s website may provide links to other websites, including those of Third Parties who may also provide services to You. You acknowledge that all those other websites and Third Party services are independent from the Financial Institution’s and may be subject to separate agreements that govern their use. The Financial Institution and Central 1 have no liability for those other websites or their contents or the use of Third Party services. Links are provided for convenience only, and You assume all risk resulting from accessing or using such other websites or Third Party services.

  • Metadata Bibliographical, structural & descriptive data of the Licensed Material as defined in Schedule 5.

  • End User An “End User” is you, an individual or entity, which receives the Models from Licensee or Authorized Licensee User pursuant to this End User Agreement to use in the regular course of your affairs, but not for resale, modification, distribution or exploitation by third parties without AnyLogic’s prior written consent.

  • End Users Customer will control access to and use of the Products by End Users and is responsible for any use of the Products that does not comply with this Agreement.

  • Vaccine Passports Pursuant to Texas Health and Safety Code, Section 161.0085(c), Contractor certifies that it does not require its customers to provide any documentation certifying the customer’s COVID-19 vaccination or post-transmission recovery on entry to, to gain access to, or to receive service from the Contractor’s business. Contractor acknowledges that such a vaccine or recovery requirement would make Contractor ineligible for a state-funded contract.

  • Bus Drivers For overtime worked on normal working days or on days of rest, bus drivers shall be paid as follows:

  • Query a search query initiated from the Search Box or a Hyperlink, or a request for Matched Ads initiated by the Ad Code on an Ad Page. Results: Paid Search Results, Hyperlink Results, Domain Match Results, Web Search Results and/or Matched Ads, to the extent included in this Agreement and as appropriate to the context. Search Box: a graphical area in which a user can enter a Query. SO: the Service Order.

  • Functionality Customer is entitled to additional functionality previously purchased or bundled with the software if available in the version or update released on or after the start date of the Agreement. Customer acknowledges that certain functionality in current and previous software versions may not be available in future upgrades. Added functionality may require additional paid services (clinical and technical) to configure and support.

  • DNS Registry Operator shall comply with relevant existing RFCs and those published in the future by the Internet Engineering Task Force (IETF), including all successor standards, modifications or additions thereto relating to the DNS and name server operations including without limitation RFCs 1034, 1035, 1123, 1982, 2181, 2182, 2671, 3226, 3596, 3597, 4343, and 5966. DNS labels may only include hyphens in the third and fourth position if they represent valid IDNs (as specified above) in their ASCII encoding (e.g., “xn-­‐-­‐ndk061n”).

Time is Money Join Law Insider Premium to draft better contracts faster.