Getting started
You reach the Provider Console with a NetApps SSO account, and only after someone invites you. This page covers your invitation, signing in, what to do when you have no access, finding your way around, and the setup checklist that unlocks discovery and activation.
Accept your invitationlink
A NetApps InsureTech administrator invites your company's first owner. After that, owners and admins invite the rest of the team from the Team screen.
- Open the invitation email. NetApps SSO sends it on behalf of NetApps InsureTech.
- Follow the link and sign in to NetApps SSO, or create your account, with the same email address the invitation was sent to.
- Complete the steps NetApps SSO asks for. You then land in the console, signed in.
Sign inlink
- Open the Provider Console. If you are not signed in, you see Sign in to the provider console.
- Select Continue with NetApps SSO.
- Sign in with the NetApps SSO account your organisation uses.
- You return to the console on the Overview screen, or on the page you were trying to open.
If the page shows Sign-in is temporarily unavailable. Please try again shortly. instead of the button, the console could not start a sign-in session. Wait a moment and reload the page.
To leave, select Sign out in the console menu.
If you see "No provider access"link
You signed in, but your account has no active membership of any insurer on NetApps InsureTech. This happens when nobody has invited you yet, or when an owner or admin has suspended or removed your access.
Ask an owner or admin of your company to invite you or reinstate you, then sign in again. Use Sign out on that screen to switch to another NetApps SSO account.
Find your way aroundlink
- The navigation groups screens into Catalogue, Operations, Integration and Organisation. The Provider Console overview lists every screen.
- Until your setup is complete, Setup sits at the top of the navigation and the Overview screen shows: "Your setup is incomplete, so discovery and activation cannot run yet."
- Under Appearance, choose a light theme, a dark theme or Match system theme.
Complete the setup checklistlink
The Setup screen lists everything NetApps InsureTech needs from you before discovery can run. A progress bar shows how many items are done, and reads Complete when you finish.
| Checklist item | Done when | Where you fix it |
|---|---|---|
| Sandbox API address | You save a sandbox API address. | Setup screen |
| Insurance categories | You choose at least one category. | Setup screen |
| Supported languages | You choose at least one language. | Setup screen |
| Settlement account | Your settlement bank account is on file. | Profile screen (link: Add it on the Profile page) |
| Sandbox credentials | You issue sandbox credentials. | Credentials screen (link: Issue them on the Credentials page) |
Fill in the Integration cardlink
The Integration card on the Setup screen holds four fields. Both API addresses must point at an API that follows the insurer API specification, which the card links to.
| Field | What to enter |
|---|---|
| Production API address | Your production API. Only needed to go live, so you can add it later. No other insurer can use the same address. |
| Sandbox API address | Your sandbox API. NetApps InsureTech uses it for discovery, Check connection and certification. |
| Insurance categories | The platform categories you sell in. The list shows the platform's active categories. |
| Supported languages | The languages your products support: English, French, Hausa, Igbo, Yoruba, Nigerian Pidgin, Arabic, Portuguese, Swahili, Spanish and German. |
To save the card:
- Open Setup from the navigation.
- Enter or change the fields.
- Select Save setup. The card shows Setup saved. and the checklist updates.
Owners and admins can save the setup. Every change is recorded in the NetApps InsureTech audit log.
Next stepslink
- Add your business names, company details and RC number on Profile.
- Add your settlement account on Profile.
- Invite your team on Team.
- Issue sandbox credentials on Credentials, or start with Adapter AI if your API does not follow the insurer API specification yet.