Skip to content
Docs/Settings & administration/Configure and disconnect an integration

Configure and disconnect an integration

Single sign-on, Stripe, Twilio, DocuSeal, NZQA, NSI, TEC DXP and form requests — each configured per provider, tested from the card, disconnected from the same place.

Staff portalWho: AdministratorsLast updated 3 September 2026
Flow

Every integration, the same four moves

ConfigureSave — card turnsActiveTest (where safe)Disconnect when nolonger needed

Diagram: Every integration, the same four moves. Steps:

  • Configure
  • Save — card turns Active
  • Test (where safe)
  • Disconnect when no longer needed

Connections:

  • Configure → Save — card turns Active
  • Save — card turns Active → Test (where safe)
  • Test (where safe) → Disconnect when no longer needed
Staff actionPallara does this
  1. Open Administration → Integrations and select Configure on the provider's card.
  2. Enter the configuration and Save. The card changes from Not Configured to Active. Secrets are encrypted at rest and belong to your provider; a platform-level setting is only a fallback for providers that have not configured their own.
  3. Select Test where it is appropriate. NZQA validates that a provider code exists without a network call; DocuSeal reports Connected — templates endpoint reachable; Twilio reports Connected — account verified.
  4. Configure → Disconnect removes the configuration and returns the card to Not Configured.
Integrations: one card per provider, with its state and Configure and Test actions.
FIG. 1Integrations: one card per provider, with its state and Configure and Test actions.
IntegrationWhat it enables
NZQA Results ReportingYour provider code for the F23 and QE1 results returns.
TEC Data Exchange Platform (DXP)SDR/ITR submissions and Ngā Kete services via OAuth2 client credentials — the ESL machine account.
National Student Index (NSI)NSN search, verification and assignment via OAuth2 client credentials — the Ministry machine account.
StripeInvoice and enrolment payments on your own Stripe account. Money is paid into your Stripe balance, not Pallara's; the keys come from Developers → API keys in your Stripe dashboard.
DocuSeal (e-signatures)Enrolment agreements and consent forms for signature on your own DocuSeal; documents are stored on the instance you name.
Twilio SMS & WhatsAppSend and receive SMS and WhatsApp through your own Twilio account.
Microsoft Entra ID / Google WorkspaceSingle sign-on for provisioned staff and learners against your own directory.
Student Form RequestsSend enrolment forms and consent requests to learners through a secure tenant webhook.

Address lookup (Google Places) is configured at the platform level rather than per provider, and the key is restricted by IP or API — never by HTTP referrer, because Pallara calls Google from the server.

Take careThe TEC and NSI Test controls call real OAuth endpoints. Do not use them with placeholder credentials.
Was this guide helpful?