Authorized User Designation Sample Clauses

Authorized User Designation. Client shall designate all current Administrative Users of the eSOPH System in accordance with Section 2.6 (Administrative Users). A current Administrative User may grant System access to additional Authorized Users. Client shall ensure its Authorized Users’ compliance with the terms of this Agreement, and Client assumes and accepts all responsibility and all liability for each of Client’s Authorized Users, and any user whom the Client, or Client’s Authorized Users, grants eSOPH System access, including all their acts or omissions while accessing and using the eSOPH System and/or any information obtained through such access and use. 2.2.1 [Deleted] 2.2.2 [Deleted]
Sample 1Sample 2
AutoNDA by SimpleDocs
Authorized User Designation. PARTICIPANT INFORMATION AUTHORIZED USER INFORMATION
Sample 1

Related to Authorized User Designation

  • Authorized Use The Student Data shared pursuant to the Service Agreement, including persistent unique identifiers, shall be used for no purpose other than the Services outlined in Exhibit A or stated in the Service Agreement and/or otherwise authorized under the statutes referred to herein this DPA.

  • Authorized Users Authorized Users" are:

  • Authorized Uses The Participating Institutions and the Authorized Users may make all use of the Licensed Materials as is consistent with the applicable law and with this Agreement, including but not limited to the following licensing conditions ("Authorized Uses"). In addition, the Licensed Materials may be used for purposes of research, education or other non-commercial use as particularly follows:

  • Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-­‐based Directory Service at <whois.nic.TLD> providing free public query-­‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-­‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry. 1.1. The format of responses shall follow a semi-­‐free text format outline below, followed by a blank line and a legal disclaimer specifying the rights of Registry Operator, and of the user querying the database. 1.2. Each data object shall be represented as a set of key/value pairs, with lines beginning with keys, followed by a colon and a space as delimiters, followed by the value. 1.3. For fields where more than one value exists, multiple key/value pairs with the same key shall be allowed (for example to list multiple name servers). The first key/value pair after a blank line should be considered the start of a new record, and should be considered as identifying that record, and is used to group data, such as hostnames and IP addresses, or a domain name and registrant information, together. 1.4. The fields specified below set forth the minimum output requirements. Registry Operator may output data fields in addition to those specified below, subject to approval by ICANN, which approval shall not be unreasonably withheld.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!