Obtain Client Consent or Direction Sample Clauses

Obtain Client Consent or Direction. If the CCO approves the proposal to overrule the recommendation of Xxxxx Xxxxx, WCM shall fully disclose to each client holding the security at issue the nature of the conflict, and obtain the client’s consent to how WCM will vote on the proposal (or otherwise obtain instructions from the client as to how the proxy on the proposal should be voted).
AutoNDA by SimpleDocs

Related to Obtain Client Consent or Direction

  • Without Consent Notwithstanding anything to the contrary set forth in Section 9.04(a):

  • Privacy Consent; Consent to Publication of Agreement Contributor consents to the OpenID Privacy Policy and also agrees that OIDF may publish a copy of this Agreement as signed by Contributor via posting on the OIDF publicly-accessible website, and Contributor consents to such publication. If Contributor is a Legal Entity Contributor, it also represents that it has obtained appropriate consent under applicable law from all individuals listed in this Agreement to the publication of this Agreement and their personal information listed herein. The parties have formed this Agreement as of the Effective Date. OPENID FOUNDATION (“CONTRIBUTOR”) By: (Sign) Xxxx Xxxxxx By: (Sign) Xxxxxx Xxxxxxxxx Name: (Print) Title: Program Manager 7/21/2022 Name: (Print) Title: Xxxxxx Xxxxxxxxx 7/18/2022

  • Zone File Access Agreement Registry Operator will enter into an agreement with any Internet user, which will allow such user to access an Internet host server or servers designated by Registry Operator and download zone file data. The agreement will be standardized, facilitated and administered by a Centralized Zone Data Access Provider, which may be ICANN or an ICANN designee (the “CZDA Provider”). Registry Operator (optionally through the CZDA Provider) will provide access to zone file data per Section 2.1.3 of this Specification and do so using the file format described in Section 2.1.4 of this Specification. Notwithstanding the foregoing, (a) the CZDA Provider may reject the request for access of any user that does not satisfy the credentialing requirements in Section 2.1.2 below; (b) Registry Operator may reject the request for access of any user that does not provide correct or legitimate credentials under Section 2.1.2 below or where Registry Operator reasonably believes will violate the terms of Section 2.1.5. below; and, (c) Registry Operator may revoke access of any user if Registry Operator has evidence to support that the user has violated the terms of Section 2.1.5 below.

  • Your Consent By using any of the Services, you agree to this Privacy Policy and consent to the collection and use of information and/or data contemplated hereby. If you do not consent to the terms herein, do not use the Services. This is our entire and exclusive Privacy Policy and it supersedes any earlier version. To withdraw consent (which can happen at any time) and have data deleted, or data corrected, please contact call at +0 000 000-0000. We may change this Privacy Policy by posting a new version of this Privacy Policy on our Website or through the Mobile App, and it is your responsibility to review this policy periodically. When we do change the policy, we will also revise the “Revised” date at the end of the Privacy Policy and may notify you or post a message on the Website and/or through the Mobile App. Your continued use of the Website or the Mobile App constitutes your agreement to this Privacy Policy, as amended from time to time. By accessing, browsing, and using the Website or Mobile App, you agree that you have read, understood, and accept this Agreement, as may be amended from time to time. Please read it very carefully and let us know if you have any questions. If you do not agree or consent to any of the terms herein, do not use the Services.

  • Certain Notifications Until Closing From the Signing Date until the Closing, the Company shall promptly notify the Investor of (i) any fact, event or circumstance of which it is aware and which would reasonably be expected to cause any representation or warranty of the Company contained in this Agreement to be untrue or inaccurate in any material respect or to cause any covenant or agreement of the Company contained in this Agreement not to be complied with or satisfied in any material respect and (ii) except as Previously Disclosed, any fact, circumstance, event, change, occurrence, condition or development of which the Company is aware and which, individually or in the aggregate, has had or would reasonably be expected to have a Company Material Adverse Effect; provided, however, that delivery of any notice pursuant to this Section 3.4 shall not limit or affect any rights of or remedies available to the Investor; provided, further, that a failure to comply with this Section 3.4 shall not constitute a breach of this Agreement or the failure of any condition set forth in Section 1.2 to be satisfied unless the underlying Company Material Adverse Effect or material breach would independently result in the failure of a condition set forth in Section 1.2 to be satisfied.

  • Customer Instructions The documentation shipped with the returned defective Boeing Product may include specific technical instructions for additional work to be performed on the Boeing Product. The absence of such instructions will evidence Customer's authorization for Boeing to perform all necessary Corrections and work required to return the Boeing Product to a serviceable condition.

  • Consent Except as otherwise provided herein, when the consent of a party is required herein, such consent shall not be unreasonably withheld or delayed.

  • Public Notification BellSouth will maintain on its Interconnection Services website a notification document that will indicate all Central Offices that are without available space. BellSouth shall update such document within ten (10) calendar days (in Mississippi, 10 business days) of the Denial of Application due to Space Exhaust. BellSouth will also post a document on its Interconnection Services website that contains a general notice where space has become available in a Central Office previously on the space exhaust list. BellSouth shall allocate said available space pursuant to the waiting list referenced in Section 2.5.

  • Requirements Prior to Approval 3.2.1 Prior to the issuance of a Development Permit, the Developer shall provide the following to the Development Officer, unless otherwise permitted by the Development Officer:

  • Written Notification Failing settlement at this level, the Union shall in writing notify the Employer of the alleged discrepancy and the names of the employees involved, and the period of time that such discrepancy is claimed to cover. Upon receipt of such written notice, the Employer agrees to promptly furnish the representative of the Union wage data pertaining to the alleged wage discrepancy.

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