1. Avaya Access Changes 5-April-2010

2. Avaya – Proprietary. Use pursuant to your signed agreement or Avaya policy.2 Who is Impacted and When? Who is impacted? Global  Customers Company Administrators Sold To Administrators Basic Users  Partners Company Administrators Sold To Administrators Basic Users  Avaya Access Administrators When?  Effective March 28, 2010

3. Avaya – Proprietary. Use pursuant to your signed agreement or Avaya policy.3 What is Changing?  Main Changes for All Users – Customers and Partners  New process to request access to PLDS and EZ Quote applications  E-Notification improvements to getting Product Notifications  New Administrator Functionality – Customer, Partner, and Avaya Access Administrators  New features for administrators to manage user requests  Other Form and Process Changes – Customer, Partner, and Avaya Access Administrators Awareness  Changes to registration/pre-registration forms  Changes to some request and approval processes

4. Avaya – Proprietary. Use pursuant to your signed agreement or Avaya policy.4 Content TopicSlide # Audience CustomersPartners Customer & Partner Administrators Avaya Access Administrators  Main Changes for All Users Main Changes for All Users5-10XXXX  New Administrator Functionality New Administrator Functionality 11-18XX  Other Form and Process Changes Other Form and Process Changes 19-23XX

5. Avaya – Proprietary. Use pursuant to your signed agreement or Avaya policy.5 Main Changes for All Users TopicSlide # Audience CustomersPartners Customer & Partner Administrators Avaya Access Administrators  User Profile “Roles” User Profile “Roles”6-8XXXX  User Access Type User Access Type9XXXX  E-Notification Changes E-Notification Changes10XXXX

6. Avaya – Proprietary. Use pursuant to your signed agreement or Avaya policy.6 User Profile “Roles”  Users can request access to the following applications during the registration/pre- registration process, or from their Avaya Access Profile  Product Licensing and Delivery System (PLDS)  EZ Quote (Partners only)  It’s as easy as selecting the “Role” that is associated with the type of access that is needed in the application  Refer to the “Notes Page” of this slide to see a list of roles and their permissions  Only roles that are valid for the user type (Customer or Partner) are displayed  Customers will only be able to select “PLDS User”  Partners will be able to select “PLDS User” and from 1 of the 5 “EZQ” roles  Only one (1) role can be selected for each application Welcome to the Avaya Product Licensing and Delivery System

7. Avaya – Proprietary. Use pursuant to your signed agreement or Avaya policy.7 User Profile “Roles” Registration / Pre-Registration  New users can request access to PLDS and/or EZ Quote roles at the same time they are registering (or pre-registering) for their Avaya Access login  Roles for specific applications are only displayed after the following entries are made:  Relationship: Customer or Partner  User Access Type: User, Company Administrator, or Sold To Administrator  Valid account information: Sold To(s) for Customers and Link ID for Partners Customer Partner

8. Avaya – Proprietary. Use pursuant to your signed agreement or Avaya policy.8 User Profile “Roles” Profile Management  A role can be selected (or changed) as part of the user’s Profile management  Approval process:  Basic “PLDS User” and “EZQ Partner Sales Basic” roles are automatically added to the user profile -- no additional approval is required  Partner requests for an EZ Quote a role other than “EZQ Partner Sales Basic” will go to an administrator for approval -- users will receive an email once their role request has been approved (or denied) Partner View Customer View

9. Avaya – Proprietary. Use pursuant to your signed agreement or Avaya policy.9 User Access Type Profile Management  Approval process:  Requests for a downgrade in access to what a user can currently do are automatically be approved  Requests for a higher level of security then what a user can currently do will to go to the Company and/or Avaya Administrator for approval  Registered users can change their User Access Type (basic User, Company Administrator or Sold To Administrator) from their profile  Users no longer need to submit an email to request this change User Profile

10. Avaya – Proprietary. Use pursuant to your signed agreement or Avaya policy.10 E-Notification Changes  Users can setup their Product Notifications to receive information on future release versions the minute they are available  Consolidation of notifications -- multiple notifications for a single day are consolidated into one (1) daily digest for all the day’s notifications -- reduces the number of emails sent to subscribers  Eliminates the need for a user to update their subscription every time a new release version for a product is introduced  To setup (or change) Product Notification subscriptions to include future release information, go to your E-Notification subscriptions -- change the Release Version for the product to “All and Future”  Refer to the “Notes Page” of this slide for detailed instructions

11. Avaya – Proprietary. Use pursuant to your signed agreement or Avaya policy.11 New Administrator Functionality TopicSlide # Audience Customers & PartnersInternal Avaya Company Administrators Sold To Administrators Avaya Access Administrators  “Unclaim” a Request “Unclaim” a Request12-14XXX  New Request Types New Request Types15-16XX  Change Email Address Change Email Address17-18XX

12. Avaya – Proprietary. Use pursuant to your signed agreement or Avaya policy.12 “Unclaim” a Request  What has changed?  Approval Requests have a “Unclaim” Action button  An administrator can “unclaim” a request that is owned by another administrator  Who has access to this new functionality?  Sold To Administrators  Company Administrators  Avaya Access Administrators  Where in the Avaya Access application does the administrator perform this function?  Unclaiming a request is available from the “All Requests” tab -- User Management > Approval Request > All Requests

13. Avaya – Proprietary. Use pursuant to your signed agreement or Avaya policy.13 “Unclaim” a Request Business Rules If your “User Access Type” is: Then you can “Unclaim”: Exception*: If the request’s Action is “Claimed,” because:  Sold To Administrator  Requests for another Sold To Administrator in your company with access to the same Sold To accounts  Requests in your own “My Requests” cue  The request is currently claimed/owned by a Company Administrator or Avaya Access Administrator  Company Administrator  Requests for any Sold To Administrator in your company  Requests for another Company Administrator in your company  Requests in your own “My Requests” cue  The request is currently claimed/owned by an Avaya Access Administrator  Avaya Access Administrator  Any requests, including requests in your own “My Requests” cue  No exceptions apply *Note: The exceptions are identified in your listing of All Requests with an Action of “Claimed.” In this case the request cannot be unclaimed and the Action is not an active button.

14. Avaya – Proprietary. Use pursuant to your signed agreement or Avaya policy.14 “Unclaim” a Request Action Type for All Requests  “Unclaim” is displayed when the request is in your My Requests cue or in another user’s cue  Click on “Unclaim” to move the request back to a “Claim” action which will allow another user to claim and work the request  “Claim” is displayed when the request must still be acted upon  Click on “Claim” to work the request and move it to your “My Requests” cue  “Claimed” is displayed when the request is claimed/owned by another user with a higher security level  You cannot change the Action Note: You can now display up to 50 requests on “All and My Requests” listing pages

15. Avaya – Proprietary. Use pursuant to your signed agreement or Avaya policy.15 New Request Types “Add Role”  “Add Role” is a new Request Type for administrators of Partner profiles  Since EZ Quote is currently only for Partners, this Request Type will only appear for administrators of Partners  Refer to “Main Changes for All Users – User Profile Roles” for information on where the user can request this change from their Profile  Approval process:  Basic “PLDS User” and “EZQ Partner Sales Basic” roles are automatically approved; administrators will not see a request for approval  Partner profile changes for EZ Quote access other than the “EZQ Partner Sales Basic” role will go the administrator’s cue for approval

16. Avaya – Proprietary. Use pursuant to your signed agreement or Avaya policy.16 New Request Types “Change User Access Type”  Users can change their User Access Type as part of their Profile management  Refer to “Main Changes for All Users – User Request Type” for information on where the user can request this change from their Profile  Approval process:  Requests for a downgrade in access to what a user can currently do are automatically be approved  Requests for a higher level of security then what a user can currently do will to go to an administrator for approval as a “Change User Access Type” request  Basic User or Sold To Administrator access can be approved by a Company or Avaya Access Administrator  Company Administrator access must by approved by an Avaya Access Administrator

17. Avaya – Proprietary. Use pursuant to your signed agreement or Avaya policy.17 Change Email Address  What has and has not changed?  An administrator can change a user’s email directly in the Avaya Access application -- allows the administrator to change an email address for a user who cannot access to their own Profile  Approval Requests are still created when a user changes their email as part of managing their own Profile  Who has access to this new functionality?  Avaya Access Administrators  Where in the Avaya Access application does the administrator perform this function?  It is available to the administrator from the User Profile Toolbox -- Search > Users > View Profile

18. Avaya – Proprietary. Use pursuant to your signed agreement or Avaya policy.18 Change Email Address Administrator Steps Outcome once the change has been successfully saved…  A message is displayed: “Email Address successfully changed for the user”  An email will go to the old and new email address confirming the change Refer to the “Notes Page” of this slide for detailed instructions 1)Search & select desired User Profile to display 2)Validate user, select, complete & save “Change Email Address” information

19. Avaya – Proprietary. Use pursuant to your signed agreement or Avaya policy.19 Other Form and Process Changes TopicSlide # Audience Customers & PartnersInternal Avaya Company Administrators Sold To Administrators Avaya Access Administrators  Form Changes Form Changes20-22XXX  Process Changes Process Changes23XXX

20. Avaya – Proprietary. Use pursuant to your signed agreement or Avaya policy.20 Form Changes Company ID Field for Registration “Company ID” is no longer a requirement for a user to register  Customers are required to enter at least one (1) Sold To Number  Partners are still required to enter their Link ID Partner Customer

21. Avaya – Proprietary. Use pursuant to your signed agreement or Avaya policy.21 Form Changes Company ID/Link ID Field for Pre-Registration “Company ID” still appears on the Pre- Registration form…but functions differently based who is submitting the form  Customers will have their Company ID pre-populated  Partners will have their Link ID pre- populated  Avaya Associates, if pre-registering a:  Customer – the Company ID/Link ID field will be a display only field  Once a valid Sold To Number is entered, the Company ID/Link ID field is automatically populated with the Company ID for that Sold To  Partner – the Partner’s Link ID must be entered in the Company ID/Link ID field

22. Avaya – Proprietary. Use pursuant to your signed agreement or Avaya policy.22 Other Form Changes  The “Role” selection is only displayed after the following entries are made:  Relationship/User Access Type  Valid account information (Sold To(s) for Customers or Link ID for Partners)  Role options are based on the previous entries  Refer to the section “Main Changes for All Users” for more information on Roles  “Reason for pre registration” limits the entry to 30 characters  Prevents a users from entering more than 30 characters  Eliminates the error that occurred when more than 30 characters were entered

23. Avaya – Proprietary. Use pursuant to your signed agreement or Avaya policy.23 Process Changes Pre-Registration Pre-registration by a “Sold To” Administrator must be approved upfront  Online pre-registration forms submitted by Sold To Administrator is no longer automatically approved  A Company or Avaya Administrator must approve the pre-registration before the new user receives the invitation to complete the registration process  Pre-registrations submitted by a Sold To Administrator will appear as a “New Registrant Approvals” request -- the same as other pre-registration requests that must be approved Company (or Avaya) Admin Approves Request for “New Registrant Approval” Sold To Admin Submits Online Pre-Registration for a New User In Their Company Pre-Registered User Receives Email to Complete Registration Process Pre-Registered User Completes Their Registration by Setting Up Their Password & Security Question/Answer