Application Setup

Step 1: Accessing the Dashboard

Start by accessing the Basiq Dashboard at dashboard.basiq.io. If you are a new user, you'll need to register first by providing your details. For existing users, simply log in with your credentials. This is your control center for interacting with all of Basiq's services.

Step 2: Creating a New Application

Once logged in, your next action is to create a new application. This can be done by locating and clicking on the “Create New Application” button in the Dashboard. When naming your application, choose a name that reflects its purpose or the environment it's aligned with. For example, an application intended for a production environment could be named “Home Loans - Production”. You will then choose between two types: the Default Application, suitable for Sandbox or Production environments, and the Business Application, which supports collecting data from businesses under the CDR Business Consumer Consent.

Step 3: Configuring Application Settings

After creating your application, you need to configure its settings. This involves specifying whether the application aligns with a specific development environment, like Development, Staging, or Production. If the application is intended for a specific business function or department, name it accordingly, such as “Credit Cards - UAT”. This naming convention aids in better organisation and management of your applications.

Best Practices and Strategies

When setting up applications in the Basiq Dashboard, it's vital to adopt strategies that align with your organisational structure and operational needs. Here are some best practices and additional points to consider:

• Reflect Development Environments: Create separate applications for different stages of your development lifecycle - Development, Staging, and Production. This approach helps in isolating data and functionalities based on the application's current stage and usage.

• Align with Business Functions: For organisations with multiple departments or varied use cases, consider creating applications specific to each function. This segregation ensures that the data and functionalities of each department do not overlap, maintaining data integrity and focus.