Onboarding and Offboarding

  • Updated

In this section of the user guide, we will walk you through all aspects of onboarding, off-boarding and user management. As a principal member there are three key activities to take consideration;

  1. First, Onboarding underlying clients;
  2. Offboarding underlying clients;
  3. User management - add, edit or remove users

2.1 Onboarding an Underlying Client

2.1a Onboarding an underlying client process

onboarding_process_underlying_client.png

 

2.1b Onboarding an underlying client procedure

Process Ref.  Process Step Owner Duration Aligned SLA
Onboarding process
1.1 Underlying client indicates it wants to use the ION product Underlying Client    
1.2

Principal member collates contract / onboarding material

  • ION PM T&Cs + IO Vault End-User License Agreement & Onboarding link
Principal Member    
1.3 Principal member provides documents via email Principal Member    
1.4 Underlying client review / complete / returns to principal member Underlying Client   SLA 1 Start
1.5 Principal member reviews documents from underlying client and io review EULA Principal Member & IO    
1.6

Further info required?

  • If yes, follow step 1.21
  • If no, follow step 1.7
Principal Member    
1.7 Contracts and onboarding documents are signed and saved centrally Principal Member & IO    
1.8 Onboard underlying client to principal member company contact / process and procedures Principal Member   SLA 1 Finish
1.9 IO customer office receives documents and reviews io.finnet    
1.10 IO Internal processes are complete io.finnet    
1.11

IO shares user credentials with underlying client via email

  • This will be for both admin and general users
  • Emails will be to all individual users

Please note - Principal member to approve underlying client io.vault users before their credentials can be created

io.finnet    
1.12

Underlying client logs into io.vault product and creates new password.

Please note - Password should include - >8 characters, capital letter, number, special character

Underlying Client    
1.13

Any login issues?

  • If yes, follow step 1.22
  • If no, follow step 1.15
Underlying Client    
1.14 Create required vaults for the business requirements Underlying Client    
1.15 Share vault address/s with principal member via email Underlying Client   SLA 2 Start
1.16 Principal member to add underlying clients vault address/s to internal database Principal Member    

1.17

Submit and sign an "Allow address" transaction for each provided address Principal Member    

1.18

Notify underlying client of address activation Principal Member   SLA 2 Finish

1.19

Underlying client can now create transactions within the network Underlying Client    

Further info required?

1.20

Request further info from the client Principal Member    

1.21

Provide required information to principal member Underlying Client    

Underlying Client Login Issue

1.22

Raise ticket to principal member via their support structure Underlying Client    

1.23

Raise ticket to IO Customer Office via support portal Principal Member    

1.24

Customer office receives request and reviews io.finnet    

1.25

Internal IO resolution io.finnet    

1.26

IO shares updated user credentials with underlying client via email

  • Share via new email
io.finnet    

 

2.1c Onboarding an underlying client SLA's

SLA Ref. SLA Description Process Step Start & End Duration Owner
1 Time taken from underlying client sharing contract material to principal member reviewing and countersigning 1.4 - 1.8 48 hours Underlying Client & Principal Member
2 Time taken from principal member sharing contract and onboarding material to IO reviewing and start onboarding 1.15 - 1.18 24 hours Principal Member & io.finnet

 

2.2 Offboarding an Underlying Client

You will be able to offboard your underlying clients when required. Below is the documented end to end process;

2.2a Offboarding an underlying client process

offboarding_process_underlying_client.png

 

2.2b Offboarding an underlying client procedure

Process Ref.  Process Step Owner Duration Aligned SLA
Offboarding Process
1.1 Underlying client wants to cancel its ION membership Underlying Client    
1.2 Completes principal members cancellation document & shares with principal member Underlying Client   SLA 1 Start
1.3 Principal member receives and reviews documents Principal Member    
1.4

Further info required?

  • If yes, follow step 1.11
  • If no, follow step 1.5
Principal Member    
1.5 Save offboarding details centrally Principal Member    
1.6 Informs IO customer office of offboarding & final data via email Principal Member    
1.7 Customer office documents offboarding data and startes IO internal processes io.finnet    
1.8 IO informs the principal member of offboarding completion io.finnet    
1.9 Principal member confirms offboarding to the underlying client via email Principal Member   SLA 1 Finish
1.10 Underlying client receives confirmation Underlying Client    
Further info required?
1.11 Request further info from the client Principal Member    
1.12 Provide required information to principal member Underlying Client    
Principal Member Internal Process
1.13 Confirm closure date Principal Member    
1.14 Inform underlying client that all tokens / currency will need to be removed before offboarding Principal Member    
1.15 Prepares for off boarding via Vault Solution Underlying Client    

 

2.2c Offboarding an underlying client SLA's

SLA Ref.  SLA Description Process Step Start & End Duration Owner
1 Time taken from the underlying client sharing the cancellation documents until the principal member confirms via email 1.2 - 1.9 48 hours Underlying Client & Principal Member

 

2.3 User management - add, edit or remove users

Once you and your underlying clients are onboarded to IO and therefore, the io.network product, you both may need to add, edit or remove users to the product. Below is the documented processes;

There are two reasons for you to raise adding or removing a user with io;

  1. You, as the principal member need to add, edit or remove a user for the io.network dashboard or your direct vaults
  2. Your underlying client requires to add, edit or remove a user from their io.vault setup

2.3a Add, edit or remove users process - Principal Member

Process Ref.  Process Step
1

To raise this request with IO;

  1. Visit our website, click contact us in the top right corner and choose "user management" from the options;
2

Complete the company details of the form and choose what you need support against;

  • Add
  • Edit,
  • Or remove a user
3

Once chosen, confirm the volume of amendments required

  • Up to 10 per request
4 Complete individual users information
5 Once added, complete the authorized signatory section and click submit
6 Once submitted, you will receive an acknowledgement confirmation

Please note - Only company admin users from the underlying client can request to add, edit or remove users

Please note - Separate requests are required if you need to add, edit or remove users at the same time

 

2.3b Add, edit or remove users process - Underlying Client

Process Ref.  Process Step
1 Underlying client requests amendments to principal member via standard support process
2

Principal member reviews request;

  1. If valid, follow step 3
  2. If not valid, inform the underlying client
3

To raise this request with IO;

  • Visit our website, click contact us in the top right corner and choose "user management" from the options
4

Complete the company details of the form and choose what you need support against;

  • Add
  • Edit
  • Or remove a user.
5 Once chosen, confirm the volume of amendments required
6 Complete individual users information
7 Once added, complete the authorized signatory section and click submit
8 Once submitted, you will receive an acknowledgment confirmation
Please note - Separate requests are required if the underlying client needs to add, edit and remove users at the same time

 

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.