License Rights and Multi User Scenarios Clause Samples

The "License Rights and Multi User Scenarios" clause defines how licensed rights to use a product or service are allocated and managed when multiple users are involved. Typically, this clause outlines whether the license is granted per user, per device, or for a group, and may specify restrictions on sharing access or transferring rights among users. Its core function is to clarify the scope of permitted use in multi-user environments, preventing unauthorized sharing and ensuring compliance with licensing terms.
License Rights and Multi User Scenarios. 1. Computer. In this agreement, "computer" means a hardware system (whether physical or virtual) with a storage device capable of running the software. A hardware partition or blade is considered to be a computer. 2. Multiple or Pooled Connections. You may not use hardware or software to multiplex or pool connections, or otherwise allow multiple users or multiple computers or devices to access or use the software indirectly through the licensed computer.
View Source
License Rights and Multi User Scenarios. 1. Computer. In this agreement, "computer" means a hardware system (whether physical or virtual) with a storage device capable of running the software. A hardware partition or blade is considered to be a computer. 2. Multiple or pooled connections. You may not use hardware or software to multiplex or pool connections, or otherwise allow multiple users or multiple computers or devices to access or use the software indirectly through the licensed computer. 3. Use in a virtualized environment. If you use virtualization software, including client hyper-v, to create one or more virtual computers on a single computer hardware system, each virtual computer, and the physical computer, is considered a separate computer for purposes of this agreement. This license allows you to install only one copy of the software for use on one computer, whether that computer is physical or virtual. If you want to use the software on more than one computer, you must obtain separate copies of the software and a separate license for each copy. Content protected by digital rights management technology or other full-volume disk drive encryption technology may be less secure in a virtualized environment. 4. Remote access. The user that primarily uses the licensed computer is the "primary user." The primary user may access and use the software installed on the licensed device remotely from any other device, as long as the software installed on the licensed device is not being used non-remotely by another user simultaneously. As an exception, you may allow others to access the software simultaneously only to provide you with technical support.
View Source
License Rights and Multi User Scenarios 
View SourceView Similar (17)

Related to License Rights and Multi User Scenarios

  • License Rights Subject to the terms and conditions of this ▇▇▇▇ and payment of applicable fees, Honeywell hereby grants a limited, revocable, non-exclusive, non-assignable, non-transferable, non-sublicensable right and license to use the Software in object code form, and any related Documentation for such Software solely: (i) in the form made available by Honeywell and in accordance with the Documentation; (ii) for User’s internal business purposes, including, for example, use by User’s authorized employees, related entities, contractors, or representatives who have been informed of and agree to comply with the terms of this ▇▇▇▇ (“Authorized End Users”); and (iii) in accordance with any express limitations on the number of Authorized End Users, accounts, assets, sites or other usage metrics set forth in the Documentation or any written agreement with Honeywell or an authorized licensor (collectively, “Software Use Rights”). Upon termination or expiration of the applicable order, subscription license term, and/or this ▇▇▇▇, User’s license to the Software and Documentation terminate immediately and User will stop using the Software and Documentation and return, destroy or delete, as directed by ▇▇▇▇▇▇▇▇▇, all copies of the Software and associated keys. User is responsible for its Authorized End Users’ compliance with this EULA.

  • Sublicense Rights Licensee shall not have the right to grant sublicenses under the licenses granted to it under Section 2.1(a) (Development and Commercialization License to Licensee) and Section 6.3(d) (Use of Coherus Trademark), without the prior written consent of Coherus, which consent may be withheld [***], except with respect to [***], in which case [***]. For the avoidance of doubt, it shall be [***] with respect to [***]. If Coherus consents in writing to allow Licensee to grant a sublicense, then Licensee may grant such sublicense, through [***], subject to the following: (a) each Sublicensee shall agree to be bound by all of the applicable terms and conditions of this Agreement; (b) the terms of each sublicense granted by Licensee shall provide that the Sublicensee shall be subject to the terms and conditions of this Agreement; (c) Licensee’s grant of any sublicense shall not relieve Licensee from any of its obligations under this Agreement; (d) Licensee shall be liable for any breach of a sublicense by a Sublicensee to the extent that such breach would constitute a breach of this Agreement, and any breach of the sublicense by such Sublicensee shall be deemed a breach of this Agreement by Licensee to the extent that such breach would constitute a breach of this Agreement as if Licensee had committed such breach; provided, however, that in each instance of any breach, Licensee and/or Sublicensee shall have the right to cure any such breach pursuant to the terms of this Agreement; and (e) Licensee will notify Coherus of the identity of any Sublicensee, and the territory in which it has granted such sublicense, promptly after entering into any sublicense. Notwithstanding anything to the contrary in this Agreement, for clarity, Licensee shall not have the right to grant sublicenses under Section 2.1 (License Grants) to any Third Party to Manufacture Products or to conduct Process Development.

  • License; Use Upon delivery to an Authorized Person or a person reasonably believed by Custodian to be an Authorized Person of the Fund of software enabling the Fund to obtain access to the System (the “Software”), Custodian grants to the Fund a personal, nontransferable and nonexclusive license to use the Software solely for the purpose of transmitting Written Instructions, receiving reports, making inquiries or otherwise communicating with Custodian in connection with the Account(s). The Fund shall use the Software solely for its own internal and proper business purposes and not in the operation of a service bureau. Except as set forth herein, no license or right of any kind is granted to the Fund with respect to the Software. The Fund acknowledges that Custodian and its suppliers retain and have title and exclusive proprietary rights to the Software, including any trade secrets or other ideas, concepts, know-how, methodologies, or information incorporated therein and the exclusive rights to any copyrights, trademarks and patents (including registrations and applications for registration of either), or other statutory or legal protections available in respect thereof. The Fund further acknowledges that all or a part of the Software may be copyrighted or trademarked (or a registration or claim made therefor) by Custodian or its suppliers. The Fund shall not take any action with respect tot the Software inconsistent with the foregoing acknowledgement, nor shall the Fund attempt to decompile, reverse engineer or modify the Software. The Fund may not ▇▇▇, sell, lease or provide, directly or indirectly, any of the Software of any portion thereof to any other person or entity without Custodian’s prior written consent. The Fund may not remove any statutory copyright notice or other notice included in the Software or on any media containing the Software. The Fund shall reproduce any such notice on any reproduction of the Software and shall add any statutory copyright notice or other notice to the Software or media upon Custodian’s request.

  • Research Use The Requester agrees that if access is approved, (1) the PI named in the DAR and (2) those named in the “Senior/Key Person Profile” section of the DAR, including the Information Technology Director and any trainee, employee, or contractor1 working on the proposed research project under the direct oversight of these individuals, shall become Approved Users of the requested dataset(s). Research use will occur solely in connection with the approved research project described in the DAR, which includes a 1-2 paragraph description of the proposed research (i.e., a Research Use Statement). Investigators interested in using Cloud Computing for data storage and analysis must request permission to use Cloud Computing in the DAR and identify the Cloud Service Provider (CSP) or providers and/or Private Cloud System (PCS) that they propose to use. They must also submit a Cloud Computing Use Statement as part of the DAR that describes the type of service and how it will be used to carry out the proposed research as described in the Research Use Statement. If the Approved Users plan to collaborate with investigators outside the Requester, the investigators at each external site must submit an independent DAR using the same project title and Research Use Statement, and if using the cloud, Cloud Computing Use Statement. New uses of these data outside those described in the DAR will require submission of a new DAR; modifications to the research project will require submission of an amendment to this application (e.g., adding or deleting Requester Collaborators from the Requester, adding datasets to an approved project). Access to the requested dataset(s) is granted for a period of one (1) year, with the option to renew access or close-out a project at the end of that year. Submitting Investigator(s), or their collaborators, who provided the data or samples used to generate controlled-access datasets subject to the NIH GDS Policy and who have Institutional Review Board (IRB) approval and who meet any other study specific terms of access, are exempt from the limitation on the scope of the research use as defined in the DAR.

  • Synchronization Rights The Licensor hereby grants limited synchronization rights for One (1) music video streamed online (Youtube, Vimeo, etc..) for up to 500000 non-monetized video streams on all total sites. A separate synchronization license will need to be purchased for distribution of video to Television, Film or Video game.