SSO

Provides Single Sign-On for employee access to QFD.

Benefits of using this Addon

SSO delegates user access to the system to client system administrators and company procedures. It is a recommended best practice for a properly secured system.

What does it replace?

Utilizing a username and password to log into the system directly. Without SSO, user access is managed entirely from within QFD.

What phase is this recommended in?

It is recommended that all clients utilize this addon if appropriate company resources are available to create the integration.

How long from phase kickoff can this be implemented?

Upon receiving the necessary connection details, this can be implemented within one month.

Who is responsible for what to implement this addon? What information is required to implement this addon?

Quavo Responsibilities	Work with client to understand options for SSO and available technologies Upon receiving necessary connection details, create an access profile to the system utilizing SSO within one month
Client Responsibilities	Work with Quavo to agree upon a SSO technology and identity provider Provide SSO details to Quavo within one month of phase kickoff
Third Party Responsibilities

What does a timeline look like for implementing this addon?

Weeks to completion/Responsibility mapping

Party

Kickoff

1

2

3

4

5

6

7

8

9

10

11

12

Quavo

1

2

Client

1

2

1

2

How is pricing determined?

Metric	Description
Monthly Charge	A flat fee is assessed per month, regardless of the number of users, logins, authentication attempts, etc.

What success criteria should be met prior to going live?

Users should be able to utilize their company procedures to access QFD in a test environment.

Any best practices for implementation or things to know after going live?

Quavo recommends SAML as a standard, but can support other options for identity providers. We recommend all clients implement SSO as a requirement for this application.