Okta IdEA Transformation Design

Statement of Work

Confidentiality Notice

This Statement of Work constitutes Okta Confidential Information and is intended for the internal use of Okta Customers only to evaluate the Statement of Work and may not be duplicated, used or distributed externally or reproduced for external distribution in any form without express written permission of Okta, Inc.

Copyright (c) 2024 Okta, Inc. All Rights Reserved.


1. Project Summary

This Statement of Work (“SOW”) is issued under, and subject to, the terms and conditions of the Agreement (as that term is defined in the Order Form).

Okta Transformation DesignServices “Professional Services” are based on Okta’s practices by driving a discovery of the customer’s Okta’s identity landscape.  Okta’s Professional Services team will lead the Customer through the Okta Transformation Design engagement that discovers and analyzes the Customer’s identity infrastructure against their business objectives. Using this information, Okta will formulate a strategy for the Customer’s future state identity architecture requirements for immediate business needs and a longer term vision.


2. Project Scope

The following activities shall be within the scope of this SOW:

  • One (1) two-hour Project kick off and requirements gathering session.
  • Three (3) two-hour technical design sessions delivered up to a three (3) week time frame. 
  • One (1) two-hour future state readout session and one (1) high level Transformation Design readout report.
  • One (1) revision to final high level solution design document.


  • Okta project manager, technical architect, business architect, and technical consultant will meet with the Customer project team to discuss Customer prerequisites and requirements.
  • Okta project manager and Customer project team will schedule design sessions with Okta architect(s) and Okta technical consultant.

Customer Obligations

  • Actively participate in the Kick Off Meeting.
  • Collaborate with Okta project manager on creating a high level project schedule, project communication plan, and Kick Off Meeting Agenda.
  • Provide required resources for participation: executive sponsor, project sponsor, project manager, identity product owner, and technical resources.


  • The Kick Off Meeting will be delivered remotely.
  • The project communication plan is focused on the communication of the Okta and Customer Transformation Design efforts and is not the Customer's end user or business user communication plan. 


Okta Professional Services will conduct technical design sessions to analyze your identity infrastructure against your business objectives. These sessions will focus on security and operational efficiency. Okta Professional Services will leverage a prescribed methodology which will address the following scope:

  • Business Objectives
    • Current State
    • Current Challenges
    • Business Outcomes
    • Interim State
    • Future State
  • Security
    • Threat Detection + Prevention
    • Identify Proofing
    • User Management
    • User Lifecycle Management
    • Authorization Management
    • Authentication Management
  • Operational Efficiency
    • Architecture & Design
    • Federation Management
    • Directory Management
    • Application Integration / External Connections
    • Reporting & Monitoring
  • User Experience
    • UI/UX
    • Progressive Profiling
    • Consent Management
    • User Registration
    • Self Service 


Customer Obligations

To ensure that the Customer receives the greatest value from each technical design session, Okta requests the following:

  • Ensure that technical design sessions are scheduled and attended by the appropriate resources (Subject Matter Experts “SMEs”: employees, contractors, or third-party) that are relevant to the design session.
  • Ensure that the design sessions begin on time and that the resources are available for the duration of the technical design session.
  • Ensure that all information required for the technical design sessions (pre-work) is prepared in advance of the technical design session.
  • Provide access to any third-party services or service providers as required.
  • Provide complete and accurate data for integration with the Okta Service.


  • All technical design sessions are to be scheduled in two (2) hour blocks.
  • There will be a maximum of three (3), two (2) hour design sessions.


Okta will provide a Readout Document, and perform one (1) review with the Customer team for any additional feedback. The high level solution design document will include:

  • Identity Enabled Business Goals + Outcome Summary
  • High Level Requirements with Solution Design Recommendations
  • User Personas and Journeys Maps
  • Current State Architecture Diagram
  • Future State Solution Architecture Diagram
  • Capability Maturity Assessment 
  • Roadmap + Recommendations
  • Executive Summary

Customer Obligations

To ensure that the Customer receives the greatest value from each design session, Okta requests the following:

  • Timely review and approval of high level solution design document components.


  • Future State readout session is to be scheduled in one (1) two-hour block.
  • Up to 6 personas and 2 journeys will be included.
  • Up to 6 business processes (i.e. User Registration, Password Reset, etc) will be mapped.
  • Documentation will be provided in English.
  • Documentation developed will be based on Okta template formats.


3. Out of Scope

Not all Okta functionality, or features, are appropriate for this type of Professional Services or potentially require additional Okta technical resources. The following features, functionality and activities are out of scope for this Statement of Work:

  • Implementation activities
  • Okta configuration updates
  • Code, extension, application, and / or integration reviews
  • Support sessions
  • Troubleshooting sessions
  • Detailed technical design documentation
  • HRMS/HCM “as a source of truth” technical design sessions
  • Any services or activity not specifically included in the Project Scope section of this SOW.
  • Features not supported within the Okta Integration Network (OIN).
  • Any functionality that is part of Roadmap, Beta or Early Adopter programs.
  • Customer staging, end user communication, and change management. 


4. Fees & Expenses

Customer shall pay Okta the Fees and expenses set forth on the applicable Order Form in accordance with the terms of the Agreement. Actual reasonable and out-of-pocket expenses and taxes are not included herein and will be invoiced separately per the terms of the Agreement.

The Professional Services described in this SOW will be provided on a fixed fee basis.The term of this SOW (“SOW Term”) shall commence on the date the Order Form is fully executed (“Order Form Effective Date”) and shall expire on the earlier of:  (a) six (6) months after the Order Form Effective Date, or (b) upon completion of the Project Scope set forth in Section 2.  The Professional Services included in this SOW will be available to Customer during a eight (8) week period within the SOW Term commencing on the initial Project Kick Off Meeting (as defined above) which may be scheduled after execution of the applicable Order Form.  All Professional Services available under this SOW may only be redeemed during the SOW Term.   Project delays resulting from Customer’s failure to Cooperate (as defined below) will not extend the SOW Term Okta is not responsible for and shall be relieved of responsibility for performing any Professional Services which have not been completed during the term due to Customer’s failure to Cooperate or failure to schedule such Professional Services in a timely manner. No refunds or credits will be provided for any Professional Services Fees. Fees will be invoiced upon the execution of the Order Form and will be due in accordance with the terms of the Agreement.


5. Scheduling

Each project begins with a Project Kick Off Meeting to review requirements and to ensure that all stakeholders understand project objectives; identify resources, roles, and responsibilities; identify and mitigate risk; develop a project schedule, and maintain velocity during project execution. As such, Okta and Customer project managers will be responsible for planning, management and execution of a project schedule for Okta resources.

Okta will provide Professional Services during regular business hours (8:00 a.m. to 5:00 p.m.), Monday through Friday, except holidays (''Business Hours'') of the Okta office which is providing the Services. Okta will work remotely based on a mutually agreed plan throughout the execution of this engagement. For technical architects and consultants, remote work shall be scheduled at a minimum of two (2) hours per technical design session. Customer must cancel any Professional Services scheduled to be provided at least two (2) business days in advance or it will lose the scheduled design session(s) and that particular session will be marked as complete.


6. OKTA Resourcing

The Okta Project team will be assigned and onboarded following execution of Order Form and based on current resource availability. If Okta resources are released from the project due to lack of Customer engagement, we do not guarantee their availability when project activity resumes. As a result, new resources may need to be onboarded at the expense of Customer. 

Project Manager

  • Main point of contact for Customer
  • Schedules and organizes project kick-off.
  • Coordinates design sessions in collaboration with Customer Project Manager. 
  • Tracks / Monitors project progress.
  • Manages any issues that arise.

Technical Consultant

  • Mentors and provides Okta knowledge to Customer.
  • Leads interaction and collaboration with other Okta teams such as Engineering, Product Management and Support, as needed.
  • Performs hands on technical configuration, integration assistance, and troubleshooting of the Okta service and platform during the design sessions.

Technical Architect

  • Technical subject matter expert with cloud and on-premise based IT system experience.
  • Documents, reviews, and manages technical requirements for specific cloud-based solutions powered by the Okta platform.
  • Develops architectural and strategic plans for cloud services.
  • Designs and implements identity lifecycle integration with Okta.
  • Provides technical leadership to the project team.

Business Architect

  • Assists in workshop planning, persona work and research.
  • Supports design workshops, determines user impacts and documentation work.
  • Aligns Customer processes to Okta solutions. 


7. Customer Obligations

General Customer Obligations

The Customer will:

  • Remain engaged throughout the duration of the Professional Services by actively participating, providing requested integration information, and otherwise completing its obligations as set forth in this SOW in a timely manner (“Cooperate”).
  • Complete the functional and technical analysis and discovery.
  • Establish a communication and escalation plan including assigning appropriate resources who are knowledgeable about the technical and business aspects involved in the project including a dedicated project manager.
  • Provide access to any third-party services or software, as required.
  • Procure services or software and license rights necessary for the Okta Service to integrate to such services or software.
  • Pay any service provider costs required to enable SSO on applications that are in scope of this engagement.
  • Provide and test all of the necessary remote access by Okta to Customer systems prior to the commencement of the Professional Service.
  • Be responsible for all hardware/virtual machines operating system(s), browser(s), commercial application(s), code for custom developed applications, application/web server(s), directory(s), database, network, proxy, and firewall maintenance and security as well as an active backup and recovery strategy as applicable for the aforementioned.
  • Provide complete and accurate data for integration with the Okta Service.
  • Prepare and manage all corporate communications and training activities to promote greater adoption and higher satisfaction from Users. Sample communication templates may be provided for Customer use.


8. Assumptions

General Project Assumptions

  • Any service or activity not specifically included in this SOW is not included in the scope of this engagement.
  • Support for out of scope requirements will require the execution of a new SOW with an associated cost.  Upon execution of a new SOW, Okta cannot guarantee that the project resources will be re-assigned to the new Professional Services engagement.
  • Okta preparation, research, and follow-up activities toward the completion of the Project Scope are billable and may not involve Customer Resources.
  • Okta and Customer will work together in good faith to resolve any issues quickly.
  • Scheduling for the Professional Services to be performed are based upon a first come first serve basis and will be mutually agreed upon by the parties prior to the commencement of the Professional Services hereunder.
  • Okta will follow independent software vendor guidelines for supported and deprecated versions of a product.
  • The Professional Services will be conducted remotely unless otherwise mutually agreed to by the parties.
  • Should any work be required at Customer’s site, travel expenses shall be invoiced in accordance with the Agreement.
  • Customer will be responsible for any fees related to Customer site travel expenses that cannot be refunded due to cancellations, such as airfare. 
  • All Professional Services are provided in the English language, unless otherwise agreed to by the parties.