Sandbox
  • 01 Apr 2022
  • 3 Minutes To Read
  • Dark
    Light
  • PDF

Sandbox

  • Dark
    Light
  • PDF

Your Mambu instance includes a production tenant and a sandbox tenant, or sandbox environment.

Your live application is hosted on your production tenant, while the sandbox is an fully-functional, isolated testing environment that runs on a separate tenant. You can use your sandbox to test configurations, updates, and new products or features before making them available to your clients in production. This allows you to "play in the sandbox" to try out new features and workflows, train your staff, or develop applications without changing your live data.

The complete Mambu UI and Mambu API are both fully available in the sandbox and production environments. You may log into the Mambu UI at the following URLs:

  • Sandbox: https://TENANT_NAME.sandbox.mambu.com
  • Production: https://TENANT_NAME.mambu.com

For more information on the sandbox API, see Sandbox in our API Reference.

Please Note

If you have federated authentication enabled, you must set up separate applications for both tenants in your IdP. For more information, see Using sandboxes with federated authentication enabled.

The two tenants are part of the same instance, but are otherwise mostly independent. What you do in your sandbox does affect production data, and vice versa, with one important exception:

Please be Aware

Sandbox tenants do not have redundant servers or database backups. We strongly recommend that you do not use a sandbox for live client data.

The sandbox is generally one version ahead of the production environment. As such, it may include changes that are currently in, or may soon be in, the production environment. For more information, see Mambu Release Cycle.

Sandbox management

To manage your sandbox, go to the Customer Service Portal. For more information and instructions, see Customer Service Portal - Sandbox Management.

Distinguishing the sandbox from production

You may distinguish sandbox from production by referring to the base URL. In addition, the sandbox UI has a blue bar with the label Sandbox Environment at the bottom of the page.

Mambu dashboard with blue sandbox environment bar

Populating your sandbox with data

To populate your sandbox with data, you may:

  • Clone production data to your sandbox
  • Use Configuration as Code (CasC)

Cloning production data to your sandbox

There are two options available for cloning production data to your sandbox: Clone with Production Anonymized Client Data and Clone with Production Data. For more information on how to clone, see Customer Service Portal - Cloning production to sandbox.

For security and compliance reasons, when you clone your production data to sandbox, API keys are not copied over. You must create new API keys for your newly cloned sandbox environment. For more information, see API Consumers - API keys.

Client data anonymization

If you clone production with anonymized client data, your data will be modified as described below.

Notifications:

  • Unsubscribed

    • all clients are unsubscribed from notifications
  • Deleted:

    • notification requests associated with the client
    • notification messages associated with the client
    • notification messages associated with client loan accounts
    • notification messages associated with client savings accounts
    • client tasks

Client fields:

  • Obfuscated:

    • first name
    • last name
  • Deleted:

    • middle name, gender, notes, email address, birth date, home phone, mobile phones, address, assigned branch key, assigned centre key, assigned credit officer key.
    • client Identification documents (also corresponding attachments from remote file storage)
    • client profile picture and signature picture (from images table)
    • client attachments (from remote file storage and documents table)
    • client custom field values
    • portal preferences
    • client comments
    • client activities (activities, sub-activities and field change items)

Client loan accounts:

  • Obfuscated:

    • loan name
  • Deleted:

    • notes
    • custom fields for client loan accounts
    • attachments for client loan accounts (from remote file storage and documents table)
    • client loan accounts transactions
  • Deleted:

    • transaction comments
    • transactions custom fields

Client loan accounts gurantees:

  • Obfuscated:

    • asset name
  • Deleted:

    • guarantees custom field values

Client loan repayments:

  • Deleted:
    • repayments notes
    • comments for client loan accounts
    • client loan accounts activities (activities, sub-activities and field change items)

Client deposit accounts:

  • Obfuscated:

    • account name
  • Deleted:

    • notes
    • custom fields for client savings accounts
    • attachments for client savings accounts (from remote file storage and documents table)

Client savings accounts transactions:

  • Deleted:
    • transaction comments
    • transactions custom fields
    • comments for client savings accounts
    • client savings accounts activities (activities, sub-activities and field change items)

Client lines of credit:

  • Deleted:
    • notes
    • custom fields for client lines of credit
    • attachments for client lines of credit (from remote file storage and documents table)
    • lines of credit activities (activities, sub-activities and field change items)

Client guarantees (guarantees in which the client is guarantor):

  • Obfuscated:

    • asset name
  • Deleted:

    • guarantees custom field values

Using Configuration as Code (CasC) to populate your sandbox

CasC is an Early Access feature that allows you to batch configure Mambu elements using YAML-formatted requests. For more information, see Configuration as Code Overview.


Was This Article Helpful?

What's Next