User Setup Clause Samples

User Setup. Provider will provide Preventia with a list of Unique Providers and a description of the type of access required for each User. Preventia will create an initial User ID and password for the Unique Providers appointed by Provider. After the initial setup and User IDs and passwords have been provided by Preventia, Provider will manage the user accounts.
View SourceView Similar (3)
User Setup. Click on to enter the setting interface. select , you may increase users, edit users and delete users. Only the user with administrator permission can carry out the revision. As the following figure: Click on “Add User” will pop-up the following dialogue box. In the white dialog box, you can increase new“Username” , “Password ” and “Description”. The right side will come out the permission option of browsing, playback, management and remote access for new user. Click on “Edit User” will pop-up the following dialogue box. In the white dialogue box, you can increase new“Username” , “Password ” and “Description”. The right side will come out the permission option of browsing, playback, management and remote access for new user. Click on to save. After setting, click on to exit.
View SourceView Similar (2)
User Setup. Customer will provide ▇▇▇▇▇▇▇▇-▇▇▇▇▇▇ with a Customer Administrator. ▇▇▇▇▇▇▇▇-▇▇▇▇▇▇ will create an initial User ID for the Customer Administrator appointed by Customer. After the initial setup, Customer will setup and manage the additional User accounts.
View SourceView Similar (2)
User Setup. Customer will provide the Company with a list of Support Users and a description of the type of access required for each User. Serviceaide will create an initial User ID and password for each User identified by Customer. After the initial setup and User IDs and passwords have been provided by Serviceaide, Customer will be solely responsible for managing the User accounts, including requests to remove User access upon change in employment status or role.
View Source
User Setup. Within the user section of the portal, you can add and remove internal users as you see fit for your own brokerage. When setting up a User you can also select which report types you wish to be available to each User within your brokerage. Information on the process for users can be found in the user section of the DASH Portal User Manual.
View Source

Related to User Setup

  • Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

  • Workstation/Laptop encryption All workstations and laptops that process and/or store County PHI or PI must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as Advanced Encryption Standard (AES). The encryption solution must be full disk unless approved by the County Information Security Office.

  • The Web Services E-Verify Employer Agent agrees to, consistent with applicable laws, regulations, and policies, commit sufficient personnel and resources to meet the requirements of this MOU.

  • Local Circuit Switching Capability, including Tandem Switching Capability 4.2.1 Local circuit switching capability is defined as all line-side and trunk-side facilities, plus the features, functions, and capabilities of the switch. The features, functions, and capabilities of the switch shall include the basic switching function of connecting lines to lines, lines to trunks, trunks to lines, and trunks to trunks. Local circuit switching includes all vertical features that the switch is capable of providing, including custom calling, custom local area signalling service features, and Centrex, as well as any technically feasible customized routing functions. 4.2.2 Notwithstanding BellSouth’s general duty to unbundle local circuit switching, BellSouth shall not be required to unbundle local circuit switching for ▇▇▇▇ when ▇▇▇▇: (1) serves an End User with four (4) or more voice-grade (DS0) equivalents or lines served by BellSouth in Zone 1 of one of the following MSAs: Atlanta, GA;

  • One-Way Interconnection Trunks 2.3.1 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Onvoy to Frontier, Onvoy, at Onvoy’s own expense, shall: 2.3.1.1 provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.3.1.2 obtain transport for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.3.2 For each Tandem or End Office One-Way Interconnection Trunk group for delivery of traffic from Onvoy to Frontier with a utilization level of less than sixty percent (60%) for final trunk groups and eighty-five percent (85%) for high usage trunk groups, unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for all final trunk groups and eighty-five percent (85%) for all high usage trunk groups. In the event Onvoy fails to submit an ASR to disconnect One-Way Interconnection Trunks as required by this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the rates set forth in the Pricing Attachment. 2.3.3 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Frontier to Onvoy, Frontier, at Frontier’s own expense, shall provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA.