<commit_before>---
title: App Center - User Experience Guidelines for Enterprise Applications
layout: reference
---

Welcome to the SAP Concur App Center!

We are very excited to partner with your company. In this guide, we will help you streamline the process of connecting a user’s SAP Concur account to your system. You will find best practices for user- centered design, examples of dos-and-don’ts, and suggested steps to guide the administrator through the connection process.

It is not our intention to tell you what colors and fonts to use. Maintaining your brand integrity is important, and these guielines do not interfere with that. Rather, our goal is for SAP Concur administrator to have a pleasant and consistent experience across all of our partner applications. Observing these guidelines will help ensure that our shared users have positive experiences with both of our companies as a result of our partnership.

* [A word on accessibility](#word-on-accessibility)
* [Design guidelines](#design-guidelines)
  * [Account linking process](#design-guidelines-account-linking-process)
  * [Connect](#design-guidelines-connect)
  * [Accept Terms](#design-guidelines-accept-terms)
  * [Landing Page](#design-guidelines-landing-page)
    * [Verification](#landing-page-verification)
    * [Sign In or Sign Up](#landing-page-sign-in-or-up)
      * [Options](#sign-in-or-up-options)
      * [Account Creation](#sign-in-or-up-account-creation)
  * [Confirmation](#design-guidelines-confirmation)
* [Guideline Checklist](#guideline-checklist)
  * [Landing Page(s)](#guideline-checklist-landing-page)
  * [Account Creation](#guideline-checklist-account-creation)
  * [Confirmation Page](#guideline-checklist-confirmation)
  * [Disconnect](#guideline-checklist-disconnect)
* [Accessibility best practices](#accesibility-best-practices)
  * [Provide text alternatives](#accesibility-best-practices-text-alternatives)
  * [Distinguishable content](#accesibility-best-practices-distinguishable-content)
  * [Keyboard control](#accesibility-best-practices-keyboard-control)
  * [Predictable structure](#accesibility-best-practices-predictable-structure)
  * [Input assistance](#accesibility-best-practices-input-assistance)

## <a name="word-on-accessibility"></a>A word on accessibility

This guide also includes some suggestions on how to ensure your site is [Section 508 compliant](https://www.section508.gov/content/learn). At SAP Concur, we work hard to make sure our critical services are available and usable by every employee at the companies who use our products. From private companies to government agencies, we have a wide range of users with varying levels of abilities. Observing accessibility best practices in your product helps us meet our commitment to provide quality software to our entire user base.

## <a name="design-guidelines"></a>Design guidelines

This guide includes requirements and recommendations for your App Center partnership with SAP Concur. These guidelines will allow you to integrate SAP Concur’s user-centered design approach into the end user’s and administrator experience, creating a seamless integration. Required elements are essential, and recommended elements are optional but useful for creating a comprehensive integration with Concur.

### <a name="design-guidelines-account-linking-process"></a>Account linking process

This section provides guidelines for the process for an administrator to connect their company’s SAP Concur instance your application. A “user” (described generically within this document) for Enterprise applications is the company administrator (for more information on permissions required to activate an Enterprise application, please refer to the [activation guide](./guide-to-enabling-app-center-solutions-basic.pdf)). Note that not all steps below will apply to all applications. This guide, however, attempts to cover the common variations.

The connection flow begins from the SAP Concur App Center. Once the user has accepted the terms of the connection, the user will be redirected to your site.

Step 1 Connect

![Step 1 Connect](./app-center-ux-guidelines-enterprise-connect.png)

Step 2 Accept Terms

![Step 2 Accepts Terms](./app-center-ux-guidelines-enterprise-terms-and-conditions.png)

Step 3 Landing Page

![Step 3 Landing Page](./app-center-ux-guidelines-enterprise-landing-page.png)

Step 4 Account Creation

![Step 4 Account Creation](./app-center-ux-guidelines-enterprise-account-creation.png)

Step 5 Confirmation

![Step 5 Confirmation](./app-center-ux-guidelines-both-confirmation.png)

### <a name="design-guidelines-connect"></a>Connect

There are two possible configurations for enterprise listings that modify the primary action for the user.

1. **“Connect” as the primary action.** In this configuration, “Connect” is more prominent. This should be used in cases where the user can self-service and connect their Concur account to your application automatically.

![Connect - Activate](./app-center-ux-guidelines-enterprise-activate.png)

2. **“Request information” as the primary action.** In this configuration, “Request information” is more prominent. This should be used in cases where the customer must contact the partner before connecting. This may be the case for applications which have multiple options, versions and/or varying pricing.

![Request Information](./app-center-ux-guidelines-both-request-information.png)

### <a name="design-guidelines-accept-terms"></a>Accept Terms

The Terms & Conditions for your application will differ between Enterprise and Consumer applications. Enterprise applications require an additional, company-wide authorization.

For more information on the terms & conditions, please refer to the [documentation on the Developer Portal](./app-center-letter-of-authorization-faq-customer.pdf).
<commit_msg>Last set of changes before sending over to Brittany.<commit_after>---
title: App Center - User Experience Guidelines for Enterprise Applications
layout: reference
---

Welcome to the SAP Concur App Center!

We are very excited to partner with your company. In this guide, we will help you streamline the process of connecting a user’s SAP Concur account to your system. You will find best practices for user- centered design, examples of dos-and-don’ts, and suggested steps to guide the administrator through the connection process.

It is not our intention to tell you what colors and fonts to use. Maintaining your brand integrity is important, and these guielines do not interfere with that. Rather, our goal is for SAP Concur administrator to have a pleasant and consistent experience across all of our partner applications. Observing these guidelines will help ensure that our shared users have positive experiences with both of our companies as a result of our partnership.

* [A word on accessibility](#word-on-accessibility)
* [Design guidelines](#design-guidelines)
  * [Account linking process](#design-guidelines-account-linking-process)
  * [Connect](#design-guidelines-connect)
    * [Activate + Connect](#design-guidelines-connect-activate)
    * [Request Information](#design-guidelines-connect-request-information)
  * [Accept Terms](#design-guidelines-accept-terms)
  * [Landing Page](#design-guidelines-landing-page)
    * [Verification](#landing-page-verification)
    * [Sign In or Sign Up](#landing-page-sign-in-or-up)
      * [Options](#sign-in-or-up-options)
      * [Account Creation](#sign-in-or-up-account-creation)
  * [Confirmation](#design-guidelines-confirmation)
* [Guideline Checklist](#guideline-checklist)
  * [Landing Page(s)](#guideline-checklist-landing-page)
  * [Account Creation](#guideline-checklist-account-creation)
  * [Confirmation Page](#guideline-checklist-confirmation)
  * [Disconnect](#guideline-checklist-disconnect)
* [Accessibility best practices](#accesibility-best-practices)
  * [Provide text alternatives](#accesibility-best-practices-text-alternatives)
  * [Distinguishable content](#accesibility-best-practices-distinguishable-content)
  * [Keyboard control](#accesibility-best-practices-keyboard-control)
  * [Predictable structure](#accesibility-best-practices-predictable-structure)
  * [Input assistance](#accesibility-best-practices-input-assistance)

## <a name="word-on-accessibility"></a>A word on accessibility

This guide also includes some suggestions on how to ensure your site is [Section 508 compliant](https://www.section508.gov/content/learn). At SAP Concur, we work hard to make sure our critical services are available and usable by every employee at the companies who use our products. From private companies to government agencies, we have a wide range of users with varying levels of abilities. Observing accessibility best practices in your product helps us meet our commitment to provide quality software to our entire user base.

## <a name="design-guidelines"></a>Design guidelines

This guide includes requirements and recommendations for your App Center partnership with SAP Concur. These guidelines will allow you to integrate SAP Concur’s user-centered design approach into the end user’s and administrator experience, creating a seamless integration. Required elements are essential, and recommended elements are optional but useful for creating a comprehensive integration with Concur.

### <a name="design-guidelines-account-linking-process"></a>Account linking process

This section provides guidelines for the process for an administrator to connect their company’s SAP Concur instance your application. A “user” (described generically within this document) for Enterprise applications is the company administrator (for more information on permissions required to activate an Enterprise application, please refer to the [activation guide](./guide-to-enabling-app-center-solutions-basic.pdf)). Note that not all steps below will apply to all applications. This guide, however, attempts to cover the common variations.

The connection flow begins from the SAP Concur App Center. Once the user has accepted the terms of the connection, the user will be redirected to your site.

Step 1 Connect

![Step 1 Connect](./app-center-ux-guidelines-enterprise-connect.png)

Step 2 Accept Terms

![Step 2 Accepts Terms](./app-center-ux-guidelines-enterprise-terms-and-conditions.png)

Step 3 Landing Page

![Step 3 Landing Page](./app-center-ux-guidelines-enterprise-landing-page.png)

Step 4 Account Creation

![Step 4 Account Creation](./app-center-ux-guidelines-enterprise-account-creation.png)

Step 5 Confirmation

![Step 5 Confirmation](./app-center-ux-guidelines-both-confirmation.png)

### <a name="design-guidelines-connect"></a>Connect

There are two possible configurations for enterprise listings that modify the primary action for the user.

### <a name="design-guidelines-connect-activate"></a>Activate + Connect

In this configuration **Connect** is the prominent call to action. This should be used in cases where the user can self-service and connect their Concur account to your application automatically.

![Connect - Activate](./app-center-ux-guidelines-enterprise-activate.png)

### <a name="design-guidelines-connect-request-information"></a>Request Information

In this configuration “Request information” is more prominent. This should be used in cases where the customer must contact the partner before connecting. This may be the case for applications which have multiple options, versions and/or varying pricing.

![Request Information](./app-center-ux-guidelines-both-request-information.png)

### <a name="design-guidelines-accept-terms"></a>Accept Terms

The Terms & Conditions for your application will differ between Enterprise and Consumer applications. Enterprise applications require an additional, company-wide authorization.

For more information on the terms & conditions, please refer to the [documentation on the Developer Portal](./app-center-letter-of-authorization-faq-customer.pdf).

{'fraction_non_alphanumeric': 0.0864073609368465, 'fraction_numerical': 0.0028439983270598075, 'mean_word_length': 5.246603970741901, 'pattern_counts': {'":': 0, '<': 27, '<?xml version=': 0, '>': 27, 'https://': 2, 'lorem ipsum': 0, 'www.': 2, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7153036', 'n_tokens_mistral': 3101, 'n_tokens_neox': 2917, 'n_words': 1232}