×

Please give details of the problem

Docs

Find

Configuring Your Customer Account

As an administrator, you are responsible for managing your customer account and configuring it according to your requirements.

For this purpose, you use the Account Configuration module of DigitalSuite Studio. Access to the module is restricted to users with an Administrator profile.

For detailed information on the settings you can configure, refer to the Customer Accounts concepts and the inline documentation of the Account Management module.

The following sections describe details of the main configuration tasks:

Managing User Authentication

One of your most important tasks is to determine how the users of your account are authenticated when they access DigitalSuite and the applications running on it. DigitalSuite supports the following authentication methods:

  • Login/Password: Users log in with their email address and password stored in DigitalSuite. Login/Password authentication is always available, even if a different method is selected for an execution mode.

  • Google OAuth2: Users connect to DigitalSuite using their Google account. You have to ensure, that a user with the same email address as the Google account exists in your customer account. Alternatively, you can enable auto-provisioning: If a user logging in with Google credentials does not yet exist in DigitalSuite, a corresponding DigitalSuite user account is created. The new user will be granted access to the applications accessible to all users of the account.

  • SSO with SAML 2.0: Users connect to DigitalSuite using the credentials of a SAML 2.0 compliant identity provider. Single sign-on is supported. This means that users who try to connect to DigitalSuite and are not yet logged in to the SAML identity provider's federated environment need to specify their credentials to this provider. Otherwise, they can continue working with their existing login.

You can configure a different authentication method for each execution mode of DigitalSuite. This means, for example, that there is no need to have real users in Google or the SAML identity provider system to test applications, as long as the Login/Password method is used for Test mode. For details on the methods and their configuration, refer to User Authentication.

Managing user authentication also includes defining a password policy to limit the number of login attempts for your users. Users who fail to log in within the maximum number of attempts are locked out of their accounts. You need to unlock their account before they can log in again.

Configuring Domains

If you want your users to authenticate with Google Open ID, or if you want to use DigitalSuite EnterpriseConnect for secure access to on-premise resources, you need to specify the domains to be used in the account configuration. You can define as many domains for your account as needed, using valid domain names such as my.enterprise.connect.com.

Domains for DigitalSuite EnterpriseConnect also require a user name and password for authentication, which later is specified together with the domain name in the configuration of the on-premise EnterpriseConnect Agents.

Configuring a Personalized Environment for End Users

By default, the portal page of DigitalSuite, https://portal.runmyprocess.com, redirects the users of your account to the development environment for creating and testing applications. This environment may be of little use to your end users. For this reason, you may want to restrict its access to designers, and configure a redirection to a personalized environment and a custom homepage for your end users. This personalized environment could, for example, display a list of all the applications the current user has access to.

DigitalSuite provides the following options for configuring a personalized environment. You can:

  • Set separate custom homepages for each of the access environments, desktop, mobile, or tablet. The custom homepage may be an external web page or a web interface developed in DigitalSuite. In the latter case, you should use a dedicated project accessible to all users.

  • Combine the homepage and authentication method configured for your account by using the https://portal.runmyprocess.com/{account_id} redirection. This is useful if users log in to DigitalSuite with SAML 2.0 or Google OAuth2 authentication or from a custom login page and then should be redirected to a custom homepage.

  • Use the standard portal application, RunMyProcess - Homepage, provided by DigitalSuite as the basis for your own homepage, and adapt the web interface and stylesheet as required.

For conceptual details, refer to Custom Homepages. For information on creating the homepage, refer to the Developer Guide.

Preparing User Metadata and User Preferences

You can add custom information as attributes to each user of your account, for example, postal addresses, phone numbers, identifiers, accounts, passwords, or data required for applications. For this purpose, you can define user metadata or user preferences.

Each user can enter values for user preferences, only users with an Administrator profile can enter values for user metadata. Different values can be specified for each execution mode of DigitalSuite. The values can be evaluated in applications.