User, Role and Access Management Sample Clauses

User, Role and Access Management. This part of the data model is used to control that the access of data on a regional hub. It allows managing users, roles and operations. Only the responsible administrator of a hub is able to create new users with an initial password. After the creation, the user gets roles assigned in the context of an arbitrary number of databases. Since it is possible that one participant is running several databases, we also have to ensure that a user may play different roles on those databases. E.g., Graz is hosting two databases where on one hand user-A is administrator of database-A, but on the other a normal user in database-B. To ensure the fulfilment of that needs each user gets roles assigned which always belong to a specific participant database. Connected to a role there are operations that the user is allowed to perform when owning a role. E.g., having the role LocalAdmin the user is allowed to add content to the participant database in which context he holds the role.
AutoNDA by SimpleDocs

Related to User, Role and Access Management

  • Outpatient emergency and urgicenter services within the service area The emergency room copay applies to all outpatient emergency visits that do not result in hospital admission within twenty-four (24) hours. The urgicenter copay is the same as the primary care clinic office visit copay.

  • Restricted Use By Outsourcers / Facilities Management, Service Bureaus or Other Third Parties Outsourcers, facilities management or service bureaus retained by Licensee shall have the right to use the Product to maintain Licensee’s business operations, including data processing, for the time period that they are engaged in such activities, provided that: 1) Licensee gives notice to Contractor of such party, site of intended use of the Product, and means of access; and 2) such party has executed, or agrees to execute, the Product manufacturer’s standard nondisclosure or restricted use agreement which executed agreement shall be accepted by the Contractor (“Non-Disclosure Agreement”); and 3) if such party is engaged in the business of facility management, outsourcing, service bureau or other services, such third party will maintain a logical or physical partition within its computer system so as to restrict use and access to the program to that portion solely dedicated to beneficial use for Licensee. In no event shall Licensee assume any liability for third party’s compliance with the terms of the Non-Disclosure Agreement, nor shall the Non-Disclosure Agreement create or impose any liabilities on the State or Licensee. Any third party with whom a Licensee has a relationship for a state function or business operation, shall have the temporary right to use Product (e.g., JAVA Applets), provided that such use shall be limited to the time period during which the third party is using the Product for the function or business activity.

  • Access Management The Engineer shall coordinate and evaluate access management within the project limits in accordance with the latest State Access Management Manual or as directed by the State.

  • Approved Services; Additional Services Registry Operator shall be entitled to provide the Registry Services described in clauses (a) and (b) of the first paragraph of Section 2.1 in the Specification 6 attached hereto (“Specification 6”) and such other Registry Services set forth on Exhibit A (collectively, the “Approved Services”). If Registry Operator desires to provide any Registry Service that is not an Approved Service or is a material modification to an Approved Service (each, an “Additional Service”), Registry Operator shall submit a request for approval of such Additional Service pursuant to the Registry Services Evaluation Policy at xxxx://xxx.xxxxx.xxx/en/registries/rsep/rsep.html, as such policy may be amended from time to time in accordance with the bylaws of ICANN (as amended from time to time, the “ICANN Bylaws”) applicable to Consensus Policies (the “RSEP”). Registry Operator may offer Additional Services only with the written approval of ICANN, and, upon any such approval, such Additional Services shall be deemed Registry Services under this Agreement. In its reasonable discretion, ICANN may require an amendment to this Agreement reflecting the provision of any Additional Service which is approved pursuant to the RSEP, which amendment shall be in a form reasonably acceptable to the parties.

  • Information regarding Interconnection Facilities 4.2.1 The SPD shall be required to obtain all information from the STU/CTU/concerned authority with regard to the Interconnection Facilities as is reasonably necessary to enable it to design, install and operate all interconnection plant and apparatus on the SPD’s side of the Delivery Point to enable delivery of electricity at the Delivery Point. The transmission of power up to the point of interconnection where the metering is done for energy accounting shall be the responsibility of the SPD at his own cost.

  • Interconnection Customer Provided Services The services provided by Interconnection Customer under this LGIA are set forth in Article 9.6 and Article 13.5.1. Interconnection Customer shall be paid for such services in accordance with Article 11.6.

  • Interconnection Customer Compensation If the CAISO requests or directs the Interconnection Customer to provide a service pursuant to Articles 9.6.3 (Payment for Reactive Power) or 13.5.1 of this LGIA, the CAISO shall compensate the Interconnection Customer in accordance with the CAISO Tariff.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • User Access Transfer Agent shall have a process to promptly disable access to Fund Data by any Transfer Agent personnel who no longer requires such access. Transfer Agent will also promptly remove access of Fund personnel upon receipt of notification from Fund.

  • Project Management Services Contractor shall provide business analysis and project management services necessary to ensure technical projects successfully meet the objectives for which they were undertaken. Following are characteristics of this Service:

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