The onboarding process guides you through the initial steps to get your organization started with Woodcore. Our support team will guide you through the onboarding sessions from the first introduction till your organization is fully migrated to Woodcore and ready to go live!
The onboarding process largely depends on your use case and the Woodcore system you intend to utilize.
We have created a template to enable you to understand what happens in each step and in what order they take place. The onboarding process is divided into the following steps:
The first step in contacting or getting across to us is by filling out a form available on our website. This form contains your organization profile, use case, contact information, and other important details. The purpose of this form is to let us know your interest and provide you with more information about Woodcore's products offering.
Once we have received this form, a representative from our team will contact you to set up a meeting to introduce our product, understand your use case, and how Woodcore can be configured to provide the service(s) you require. This is known as the first introduction.
In addition, during the first introduction, we will walk you through a demo of the Woodcore system in general i.e the API, and the console.
If you choose to proceed with Woodcore, an invoice will be sent by email to the billing contact of your organization for the necessary payments. You will also be required to sign a Service-Level Agreement (SLA) and other required Non-Disclosure documents provided by Woodcore. Once this is completed, we can properly begin your integration and configuration.
Next, a test environment or console is provided for your organization. The test environment will help the user explore the features and functionalities of the system and gain a better understanding of how the system works. Test tenant will also enable the users to come up with questions on how best we can configure the system to suit their product demands.
The test environment is duplicated into two:
- The first test environment will serve as a platform for testing and getting acquainted with the system.
- The second test environment will be used for data migration purposes. This is for clients who wish to migrate their existing data to the Woodcore system. These data will be added to the test environment first before the organization goes live.
Once a test environment has been provisioned for your organization, login credentials will be sent to the respective users as requested by the organization.
For compliance reasons, all of our clients go through some compliance checks before an account is provisioned for them. Approval takes at most 24 hours
The API integration process is an important step in enabling API users seamlessly integrate with the Woodcore APIs. To ensure the security of the APIs, authentication is required using unique API keys that are provided to users on the test console.
As part of this process, we will guide you through the available APIs that are best suited to your specific use case. This involves identifying the relevant APIs and providing detailed documentation on how to set up and configure the APIs to ensure optimal performance. A representative from our team will work closely with you to ensure that you have all the information and support needed to successfully integrate the Woodcore APIs into your existing systems and workflows.
The next step in the onboarding process is the system configurations. This covers all the setups and configurations required for your organization. Here, we provide an information request template for your organization to fill out. In this template, you are to provide all the necessary information that will enable us to configure the tenants properly to meet your organization's demands. These templates include system configurations such as:
- Offices setup
- Chart of accounts
- Product configuration
- Roles within an organization and their permissions
- Employee details
- The names and roles of specific users of the system. These are the employees within your organization who will be granted access to the console.
In addition, there may be fields unique to your organization that are not available by default in the system, this unique fields can be created using what is referred to as Data tables. This feature will enable you to customize the console to fit the specific details of your business. See data tables for more information.
The data migration process refers to the transferring of existing data from a previous system to the Woodcore core banking system. This is essential for users with existing customer data.
As earlier mentioned, a tenant is created with two test environments. The first environment is created for the purpose of the user testing the system and getting familiar with the system. The second test environment is created for the purpose of migrating data to Woodcore’s core banking application. The duration for data migration largely depends on the quantity of data being migrated.
See Data migration for more information
Prior to this, the system configuration would have taken place and users within your organization will be granted access to the system. In order to ensure the user has adequate information on the working of the console. The support team will walk you through a series of training sessions to explain the features and functions available on the system and how you can achieve optimal results and performance within the system. This is also an opportunity to go through your configured console to verify the configurations made.
We prioritize the security of our users as we understand the importance of their data. We have incorporated a high-level security system using multi-factor authentication via third-party authenticators. This provides an additional level of security by requiring users to log in using One-Time Password in order to gain access to the console.
During this session, we will walk you through the security process which includes the authenticators, how it works, and best security practices.
The tenant is officially launched. Data migrated to the test environment are replicated in production.
It's not over between us🤭, Our support team is always available to provide assistance if you run into any issues or experience difficulties.
If you are logging into the system for the first time, as mentioned earlier, your URL and credentials will be sent to you automatically via email. Woodcore requires multi-factor authentication (MFA) also known as 2FA before you can login successfully.
Two-factor authentication is implemented to protect both a user's credentials and the resources the user can access. It provides a higher level of security than authentication methods that depend on single-factor authentication (SFA), in which the user provides only one factor- typically, a password or passcode.
Our console is fully secured with a VPN — Which means that ONLY some designated person(s) within your organization will be allowed to access the console.
On Woodcore, after inputting your username and password (this is the first stage of Authentication), if your credentials are correct, a QR code would be displayed on your screen which you would scan with your Authentication application mentioned above.
After scanning the QR code with your authenticator app, a 6-digit code would be displayed to you. This 6-digit code is the necessary code to validate your access to the system. Input the 6-digit code and click on the Verify button to connect the Authenticator app to the WoodCore console.
On subsequent login attempts, an OTP would be generated on your Authenticator app. Enter the OTP in the screen shown below and if inputted correctly, a successful login is recorded and you will be taken to your dashboard.
You should see some scanty graphs with no metrics, don't worry — You need to feed data into it. We have ensured that all provisioning for new clusters on the system comes with a template based on your use case.
Woodcore works best with modern web browsers such as Firefox or Chrome (including other Chromium-based browsers) and Opera.
Updated 6 months ago