Configure your environments in the following application steps:
- Locale Settings application step
Use the Locale Settings application step to manage and support different languages in your environments, and set your default language.
- Service Administrators application step
Configure the administrators for your environments in the Service Administrators application.
- Environment application step
Use the Environment application step to configure user interface settings, default theme, and default time zones, for different environments.
- Solutions application step
In the Tenant Environment Setup application, use the Solutions step to activate, deactivate, or purge solutions for your environments.
- Single Sign On application step
Use the Single Sign On application step to configure inbound and outbound single sign on (SSO) authentication. Security Assertion Markup Language (SAML), OpenID Connect (OIDC), and Basic/Native SSO types are supported.
- Client Credentials application step
In the Tenant Environment Setup application, use the Client Credentials application step to configure authentication for inbound integrations coming into the platform. This allows external systems to authenticate with Nextworld and get access tokens for making API calls without requiring a user to manually sign in.
- Global Settings application step
Use the Global Settings application step to define the tenant's default lifecycle for owned and customized metadata. This is necessary for customer defined attributes (CDAs) and user templates to automatically locate tenant owned data. Optionally, configure the tenant to hide or show actions based on user permissions, or override the default emails sent when a user account is activated or for password resets.
Locale Settings application step
Use the Locale Settings application step to manage and support different languages in your environments, and set your default language.
By default, the Primary Language is set to English, and the Country is set to United States.
When you support a language, it allows the users in your environment to change their locale setting in the User Settings menu to the language of that locale. Learn more in Support additional languages on the platform.
Open the record for your tenant in the detail form to access the languages you can support. These are determined by your contract with Nextworld.
Each record with a Base ownership represents a language you can support. To support a language, use the Support Language row action, and then select Prepare Plan. After you're notified that the job is complete, there is a new record for that language that has an ownership of Owned. This indicates that the language is now enabled in your environments, and you and your users can select the new locale in your user settings.
If you create your own metadata that your users need to access in a different language, you are responsible for translating the text-based elements of those objects. Learn more in Metadata translations.
Use the Repair Language row action on your Owned record if you encounter issues with the translations in your environments. To remove the option for your users to access the platform in a language you've supported, use the Discontinue Language row action.
Service Administrators application step
Configure the administrators for your environments in the Service Administrators application.
Add the users that will be administrators for your environments. You can add individual users as well as user groups. Additionally, you can indicate backup approvers for these individuals or groups.
For more information, see Approval backup configuration.
Environment application step
Use the Environment application step to configure user interface settings, default theme, and default time zones, for different environments.
Open an environment record to select the default:
- Theme configured in the Theme Builder application. Learn more in Theme Builder application.
- User interface settings configured in the User Interface Settings applications. Learn more in Configure UI settings across the platform.
- Interface design. This can be overridden by individual users in their User Profile Menu on the Appearance page.
- Product family and module. This defaults these field values in newly created metadata.
- Time zone.
The system determines what time zone is used for an environment based on the Display Preferred Time Zone checkbox. Options include:
- Display Preferred Time Zone selected—The system looks for a Custom Time Zone in the User Profile. If no Custom Time Zone exists, it uses the Default Time Zone for that environment. If no time zone is selected, the system uses the default time zone configured by the platform.
- Display Preferred Time Zone cleared—The system looks for a Custom Time Zone in the User Profile. If no Custom Time Zone exists, it uses the user's browser's time zone.
Solutions application step
In the Tenant Environment Setup application, use the Solutions step to activate, deactivate, or purge solutions for your environments.
A solution is a group of applications, features, and processes that together enable you to complete a business process. Learn more in Solutions.
The following actions can be performed in the Solutions application step:
Activate | Create a record for the applicable tenant and environment and add a detail row to specify which solution you would like to activate. Save the record, then select Activate from the row action menu to activate the solution in your tenant and environment. | |
Deactivate | Select Deactivate from the row action menu of the applicable detail record to remove the solution from the environment. Solutions can be reactivated or purged from the deactivated state. | |
Purge | Select Purge from the row action menu for the detail record that corresponds to the applicable solution . |
Some solutions require additional configuration steps, such as obtaining and registering API keys. For more information, see Enable AI models in your environment.
Solutions
Nextworld and partners offer solutions for your environments. A solution is a group of applications, features, and processes that together enable you to complete a business process.
For example, Nextworld offers solutions for Nextworld Intelligence, as well as Financials.
Solutions are purchased and authorized by the platform. Once a solution has been authorized, system administrator can activate it in the Tenant Environment Setup application, in the Solutions / Localizations application step. Each environment must be individually configured to use a solution. Learn more in Solutions application step.
Single Sign On application step
Use the Single Sign On application step to configure inbound and outbound single sign on (SSO) authentication. Security Assertion Markup Language (SAML), OpenID Connect (OIDC), and Basic/Native SSO types are supported.
The SSO Type you select determines the requirements for configuration. Options include:
OIDC—Use the OpenID Connect page to configure inbound OIDC authentication. Optionally, use the Third Party SSO Configuration page to configure outbound OIDC authentication which can be used in endpoints and connectors.SAML—Use the SAML 2.0 page to configure inbound SAML authentication.Native/Basic—Use the Native/Basic SSO type to add a list of Allowed Redirect Links. This enables users to connect external MCP clients to the platform.
Learn more in Single Sign On configuration.
When SSO is configured you'll have an alternative login address for SSO. Obtain the URL details when you set up SSO through support.
Sign Out
Optionally, configure your IDP solution to add a logout URL that logs out all open sessions of the platform. This is useful for scenarios when Nextworld is part of a multiplatform solution. When the logout URL is called, all sessions in the brower are logged out of the domain.
The logout URL is #/logout. For example, https://cloud.nextworld.net/#/logout would log the user out of all instances of the platform within their browser.
Global Settings application step
Use the Global Settings application step to define the tenant's default lifecycle for owned and customized metadata. This is necessary for customer defined attributes (CDAs) and user templates to automatically locate tenant owned data. Optionally, configure the tenant to hide or show actions based on user permissions, or override the default emails sent when a user account is activated or for password resets.
Prerequisites
To configure the Tenant Default Lifecycle, you must:
- Have the
TenantConfigurationrole assigned to you. - Create the lifecycle you want to set as the Tenant Default Lifecycle in every environment the tenant owns.
Set the Tenant Default Lifecycle
To set the Tenant Default Lifecycle, create a new record and enter the lifecycle you created. Optionally, select the Secure App Actions checkbox to hide application links, field, row, and form actions if users don't have permission to execute them. Once applied, the permissions required for different types of buttons are:
- Application Links—Requires Read row security access to the destination application's table.
- Logic Blocks—Requires access to execute the logic block. This is determined by the type of security applied to the logic block:
- —All users are authorized to execute.
- —Users must have access to the table, logic block, or security group that allows them to execute.
- —Called from other logic blocks, so users can't execute directly.
AI Model Fallback
Disable AI Model Fallback if your tenant has a legal or regulatory obligation that prohibits fallback to an alternate model or region. This setting is typically configured during implementation but can be updated if your requirements change.
Email overrides
You can optionally change the default email sent to users when they activate their account, request a password reset, or complete a password reset using the UserActivationEmailHTML , Password Reset Email, and Reset Confirmation Email fields.
Each field has a template which you can load using the buttons below the fields. To view the template’s HTML or paste your own HTML into the field, select the Fullscreen button in the editor bar, then select the Code View </> button.
If you create your own HTML, ensure the proper substitution fields are used so the system populates them correctly. The required substitution fields are:
- [Tenant Name]: Identifies the associated group of users and data within the given Environments.
- [Username]: The user being activated.
- [Password]: The temporary password being sent.
- [Login URL]: The URL link for initial sign in to the platform.
Single Sign On configuration
Configure single sign on (SSO) to allow an external identity provider (IDP), such as Entra, JD Edwards, or Jumpcloud, to authenticate users signing into the platform. Both Security Assertion Markup Language (SAML) and OpenID Connect (OIDC) SSO types are supported.
Prerequisites
Contact support and let the support team know which type of SSO, and which IDP, you are setting up. Support will:
- Set up a DNS record.
- Add a URL to your tenant record.
- Provide you with the configuration details that you need for the next step.
Single Sign On application
Platform requirements for SSO are configured in the Tenant Environment Setup composite application, in the Single Sign On application step. SAML and OIDC have different requirements which can be reviewed in the following topics:
Sign Out
Optionally, configure your IDP solution to add a logout URL that logs out all open sessions of the platform. This is useful for scenarios when Nextworld is part of a multiplatform solution. When the logout URL is called, all sessions in the brower are logged out of the domain.
The logout URL is #/logout. For example, https://cloud.nextworld.net/#/logout would log the user out of all instances of the platform within their browser.
SAML configuration
Configure SAML single sign on in the Single Sign On application step within the Tenant Environment Setup application.
External Identity Provider (IDP)
In your IDP, you must:
- Set up a new SSO profile. For example, in Entra search for Enterprise Applications, select New Application, then Non-Gallery Application, then Configure Single Sign-On.
- Enter the Entity ID that identifies Nextworld as your service provider:
- The naming convention is
<tenant>.cloud.nextworld.net...nw<tenant>. For example,acme.cloud.nextworld.net...nwacme - For European companies, use
<tenant>.eu.nextw.com...nw<tenant>.
- The naming convention is
- Use the SAML URL provided by platform support to identify Nextworld as a your service provider in the IDP.
- Note the URL and X509 provided by your IDP. These will be used in the Single Sign On Identity Provider application step and are different than the SAML URL and X509 given to you by support to use in the IDP application.
Single Sign On application
In the Single Sign On Identity Provider application step, create a new record of type SAML. On the SAML 2.0 page, copy and paste the information from your IDP configuration page into the following fields:
| Entity ID | The identifier for your IDP. In Microsoft Entra, this value is contained in the Entra AD Identifier field. |
| SAML URL | The login service endpoint for the IDP. In Microsoft Entra, this value is contained in the Login URL field. |
| x509 Certificate | The X.509 certificate associated with your IDP signing certificate. In Microsoft Entra, visit the App Federation Metadata URL and search for the X509 Certificate or X509 Data. |
Then, determine how you want the SSO to identify the user. Options include:
| Default (no SSO User Mapping Field or Login Name Encoding) | Use when the user identifier in the external system is the same as the user's username in the platform. The NameID subject of the SAML assertion finds the platform user whose username is equal to the NameID value. | For example, if the SAML Response has this for NameID: <saml:NameID Format="urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress">John.Smith@ACME.com</saml:NameID> The system would look for a username of John.Smith@ACME.com |
|---|---|---|
| Login Name Encoding | Use when NameID does not match a platform username, but the platform username is elsewhere in the SAML response. Define the SAML segment that contains the user platform username by replacing it with the format X_LOGIN_NAME_X. | For example, if the SAML response is: <saml:Attribute Name="http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress" NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:uri"><saml:AttributeValue xsi:type="xs:string">John.Smith@ACME.com</saml:AttributeValue></saml:Attribute> You would replace it with: <saml:Attribute Name="http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress" NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:uri"><saml:AttributeValue xsi:type="xs:string">X_LOGIN_NAME_X</saml:AttributeValue></saml:Attribute> |
| SSO User Mapping Field | Use when the platform username differs from anything returned by the external IDP in the SAML response. Define an Attribute from the SAML response that uniquely identifies a user. The value of the attribute matches the External IDP User ID field on user records. | For example, If the SAML Response contains <saml:Attribute Name="http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress" NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:uri"><saml:AttributeValue xsi:type="xs:string">John.Smith@acme.com</saml:AttributeValue></saml:Attribute> You could enter http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress to find this attribute. In the user record, you would enter John.Smith@ACME.com in the External User ID field. |
Mark the new profile as Active. You can have only one Active Single Sign On Identity Provider profile at a time.
On the General SSO Configuration page, add a redirect URL for each external application you want to allow to authenticate with the platform.
OIDC configuration
Configure OIDC single sign on in the Single Sign On application step within the Tenant Environment Setup application.
SSO Authentication for Nextworld
To configure SSO authentication into Nextworld, in your IDP, you must set up a new SSO profile.
Then, in the Single Sign On application step, create a new record of type OIDC and copy and paste the information from your IDP configuration page into the following fields on the OpenID Connect page:
| Client ID | The identifier for your IDP. In Okta, this is contained in the Client ID field. |
|---|---|
| Client Secret | The secret code for your IDP. In Okta, this is contained in the Secret field. |
| OIDC Token Issuer URL | The URL of the entity that issues the tokens. Once this value is entered, the OIDC Auth URL and OIDC Token URL fields are automatically populated. For example, in Okta, this could be something like: https://trial-4284753.okta.com/ This is the base URL used when going to the /.well-known/openid-configuration endpoint to find other URLs. If you entered the example URL in Okta, the system would use https://trial-4284753.okta.com/.well-known/openid-configuration to find the Auth Server, Token, and JWKS URLs. |
You must map the unique identifiers from the ID tokens into the External Identity Provider User ID field in SSO user records in the Users application. By default, the sub claim is used to match the records because it is guaranteed to be in any token that comes from the IDP.
Optionally, you can use the SSO User Mapping Field field in your SSO configuration record instead. If used, the field must map a claim in the OIDC ID token which contains a value that uniquely identifies a user in the IDP.
On the General SSO Configuration page, add a redirect URL for each external application you want to allow to authenticate with the platform.
SSO Authentication for Third Party Endpoints and Connectors
To configure outbound authentication for third parties, add a record for each third party IDP on the Third Party SSO Configuration page of the Single Sign On application step.
By default, a single System User token is retrieved from third party systems and used for all endpoint and connector authentication. If you add a record for the third party system in your SSO configuration, each user is assigned a unique token from the third party upon authentication. This authentication can then be used in endpoints and connectors.
Proof Key for Code Exchange (PKCE) is automatically included within OAuth requests from the Nextworld platform. The external authorization provider which the request is sent to dictates whether it is used. Review the documentation for your provider to determine their requirements.