User Permissions. The access and entitlements given to a User in connection with RBC Edge, which may or may not, in certain cases, be enforced by Royal Bank in other Electronic Channels or in-person or otherwise assisted service channels, such as in-branch.
User Permissions. Company will:
(a) provide notice to End Users of the size of the Application package and the potential for data usage and messaging charges (if applicable) prior to the initial installation of each Application and item of Content delivered to an Interactive Device over the AT&T Service. Company will control the form, content and display of such notices and messages; however, i) Company will incorporate any reasonable feedback or suggestions provided by AT&T, and ii) any references to the carrier require prior AT&T review and approval; End User acceptance of user granted permissions may be required either before initial download of the AADS download or at other points during use as determined by AT&T.
(b) provide notice and obtain end user consent for all applicable User Granted Permissions also including System Level Permissions, such notice and consent to be consistent with the Android platform conventions for permissions for downloaded applications and updates;
(c) ensure mutual client/server authentication is performed between the Application performing the installation and the server that is delivering the Application and/or Content prior to installing the Application and/or Content;
(d) implement protection mechanisms to ensure the Applications downloaded and installed on AT&T Devices are authentic versions of the software;
(e) not install or update any other software or applications except for the AADS or those apps distributed through AADS as requested by End User;
(f) obtain prior written approval from AT&T, which shall not be unreasonably withheld or delayed, prior to enabling automatic software updates over the AT&T Service.
User Permissions. Current State—When creating a new user, permissions cannot be copied from an existing user in the current system. In ANB Go Business—When creating a new user, permissions can be copied from an existing user in ANB Go Business. Current State—Administrators can see and grant dual control rights to all Cash users. In ANB Go Business—There is no visibility into dual control settings for Administrators in ANB Go Business. Administrators no longer can grant or remove dual control from any user. Dual control is set at the company level by American National Bank. To change this setting, it is necessary to contact the bank and update the agreement on file. What’s changing? | Administration
User Permissions. Each party reserves the right to establish the permissions granted to each individual user employed by the party. Authorized Individual permissions include accessibility to specific modules and applications, ability to view, modify, delete, and print any aspect of the Xxxxxxxx System as defined by the parties’ approved permissions for data related to their respective agency. Each party also maintains the right to partition specific records and information within any record that is deemed private and inaccessible by the other party. Designation of personnel with Super User Access must be requested in writing and approved the Live Oak Chief of Police.
User Permissions. Permission is granted to temporarily download copies of the materials (information) on QR Codes for personal/commercial use for tracking and tracing ASPIRE Resources only. This is the grant of a permission, not a transfer of title, and under this permission you may not:
i. modify the materials; ii. attempt to decompile or reverse engineer any software contained using the ASPIRE QR Codes; iii. remove any copyright or other proprietary notations from the materials; or iv. transfer the materials to another person or “mirror” the materials on any other server.
User Permissions. The Contractor shall support the unique functionality needed for PSAPs, County Coordinators, and Cal OES.
User Permissions. The Contractor shall demonstrate the ability to generate user types, associate appropriate actions and data sharing / conveyance using different user types, and comply with requirements in EXHIBIT A: TECHNICAL REQUIREMENTS for user types. When Cal OES agrees that the Contractor has passed all three (3) areas of acceptance testing, system acceptance shall be considered complete, and the Contractor shall begin the process of implementing the Data Sharing System statewide. The Contractor shall work with the Cal OES to finalize the Implementation Plan for statewide deployment.
