User Authorization Clause Samples
The User Authorization clause defines the permissions and rights granted to users to access and use certain systems, services, or data. Typically, it outlines the process by which users are granted access, such as through account creation, password assignment, or role-based permissions, and may specify any limitations or conditions on that access. This clause ensures that only authorized individuals can use specific resources, thereby protecting sensitive information and maintaining system security.
User Authorization. 6.2.8.1 On the destination system, users are granted access to specific resources (e.g. databases, files, transactions, etc.). These permissions will usually be defined for an individual user (or user group) when a userid is approved for access to the system.
User Authorization. 7.1 After the User's registration, the User's access to the Mapflow Platform is carried out by going through the authorization procedure, that is, by specifying a unique username and password for the Account.
7.2 After the User logs into the Account, the Account data entered by the User on his device can be automatically saved by the User in the device browser settings until the User completes the work under his Account and does not require further re-entry of data to access the Account with each use of the Platform. Mapflow.
7.3 The User is obliged to immediately notify the Company at the email address specified in clause 1.1. of the User Agreement, about any case of unauthorized (not authorized by the User) access to the Platform using his Account and (or) about any violation (suspicion of violation) of the confidentiality of his data for access to the Account.
7.4 For security reasons, the User is obliged to independently carry out a safe shutdown of work under his Account, using the appropriate function button at the end of each session of work with the Platform. The Company is not responsible for possible loss or damage to data, as well as other consequences of any nature that may occur due to violation by the User of the provisions of this clause of the User Agreement.
7.5 Any actions performed using the User's Account are considered to have been committed by the User, except when the User is in the manner provided for in clause 7.3. Of the User Agreement, notified the Company of unauthorized access to the Platform using the User's Account and (or) of any violation (suspicion of violation) of the confidentiality of his data, which the User uses to access the Account. Otherwise, the User is solely responsible for all actions (as well as their consequences) in connection with the use of the Mapflow Platform under the User's Account, including cases of voluntary transfer by the User of data for access to his Account to third parties on any terms (including under agreements or agreements), as well as cases of violation of the rights and legitimate interests of third parties.
7.6 The User's account can be deleted at the initiative of the User.
User Authorization. If Customers need MEGVII to process the personal information of their users during their use of the Service of FaceID platform, they shall ensure that, before delivering the user information to MEGVII through API, they have obtained the legal and valid authorization from the users required for their demanded service. The authorization content includes that: (1) Users know and agree that the Customers collect their identity information including name, valid ID information and face picture that are required by Customers for using the Service and the Customers will provide such information to MEGVII; (2) Users know and agree that MEGVII has the right to obtain their identity information from the Customers for the Service and then return the identification results to the Customers; (3) Users know and agree that MEGVII has the right to provide their identity information to cooperative third parties of MEGVII for the Service and the cooperative third parties of MEGVII will return the identification results to MEGVII (this authorization is only necessary when it involves with a cooperative third party of MEGVII).
User Authorization. Customer is hereby notified that BND will not confirm the authority, identity, or existence of the person or persons obtaining reports, exporting data, performing transactions, or engaging in financial activities on behalf of Customer via BND Direct. It is the responsibility of the Customer to maintain the user listings and authorizations granted to users of the Customer.
User Authorization. All Usernames and passwords issued in connection with the Accounts are issued only to duly authorized representatives and/or signers on the applicable Account. All authorization levels have been reviewed by an authorized representative and are valid and appropriate.
User Authorization. UA provides a mechanism to exchange user credentials but does not specify how the applications use these credentials. Client and server applications may determine in their own way what data is accessible and what operations are authorized.
User Authorization. We may consider each individual to whom you provide a new or existing Username and User Password to be an authorized User of your Digital Banking service. Unless otherwise restricted as permitted under this Agreement, Users are authorized to: (1) enter into this Agreement, including any amendments we may make from time to time; (2) access your account(s) in any manner and for any purpose available (whether available now or in the future) through Digital Banking; and (3) use any Digital Banking service in any manner and for any purpose available (whether available now or in the future) through Digital Banking.
User Authorization a set of actions specified in Annex 1 (registration and authorization procedure) to this Agreement, completed in the BelkaCar App or on the Website, in order to identify the registered User for subsequent use of the BelkaCar Service through the BelkaCar App and/or Website.
User Authorization. All User Names and Passwords issued in connection with the accounts and or loans are issued only to duly authorized representatives and/or signers on the applicable account or loan Safeguarding Security Codes and Security Procedures Subject to the next sections, You are responsible for all transfers, payments and other transactions using your User Name and Password on the ▇▇▇▇▇▇▇ Online Services. We will not be liable for and will not reimburse you for any losses that may occur as a result of use of your User Name and Password by a third party. You are responsible for keeping your Password and Account data confidential. Lost, Stolen or Unauthorized Use of User Name and Password SEE YOUR LOAN AGREEMENT FOR BILLING ERROR NOTICE FOR YOUR RIGHTS AND RESPONSIBILITIES FOR LOANS. SEE YOUR WIS BROKERAGE ACCOUNT RULES FOR YOUR RIGHTS AND RESPONSIBILITIES FOR BROKERAGE ACCOUNTS. You must tell us at once if you believe that your Password has been lost or stolen, otherwise you could lose all of the money in your accounts accessed by the Password plus your maximum overdraft line of credit, if applicable. If you believe your Password has been lost or stolen or that someone has transferred or may transfer money from your account without your permission. Call us at ▇▇▇-▇▇▇-▇▇▇▇ Send us an electronic message using Contact Us within ▇▇▇▇▇▇▇ OnlineServices Write to us at: ▇▇▇▇▇▇▇ Online Services P.O. Box 10305, WFD ▇▇▇ ▇▇▇▇▇▇▇▇▇, ▇▇ ▇▇▇▇▇ Limitation on Losses Suffered on Consumer Accounts Only If you tell us within two (2) Business Days after you discover that your Password or User Name has been taken or used without your permission, your liability will not exceed $50.00. If you do not tell us within two (2) Business Days of the unauthorized use of your User Name or Password, and we can prove we could have stopped someone from using your Password without your permission if you had told us, your liability can be as much as $500.00.
User Authorization. A User seeking the use of the services of TO Company can only do so after authorization of an account. Validity and authorization of a User for using the services of TO Company in a Trip or leg is provided by a confirmed Booking ID via TOMP-API or similar API functionality. TO Company holds the right to reject booking requests for concern of protecting its fleet based on the User information provided in Annex 3: Use of APIs and alternatives.