Handling Admin Approval Requirements When Enabling SSO on INVOLVE

What you are seeing

When setting up Single Sign-On (SSO) for INVOLVE, you may encounter a screen requesting admin approval that looks like this:

Why you're seeing it

This approval prompt appears because your organisation's IT department has configured admin consent policies in Microsoft Entra ID (formerly Azure AD). These security policies require administrator approval for new applications before users can access them.

This is a normal security measure and indicates your IT team has implemented proper governance controls.

What to Do

Step 1: Request Approval

1. Fill out the justification field with a clear business reason, such as:

   • "Required for INVOLVE platform access for our volunteer management"

   • "Business-approved SSO integration for Volunteer management"

   • "Pre-approved application for Volunteer management"

2. Click "Request approval" - don't cancel

3. You'll see a confirmation that your admin has been notified

Step 2: Follow Up Internally

Contact your IT administrator or help desk and provide them with:

• Application Name: INVOLVE by Eduka

• Business Justification: Needed for volunteer management

• Urgency Level: ASAP

• Screenshot: Of the approval request (if helpful)

Step 3: What Your IT Admin Needs to Know

For IT Administrators: The INVOLVE application requests these standard permissions:

• User.Read: Basic profile information (name, email)

• offline_access: Maintain sign-in session

These are standard, low-risk permissions required for SSO functionality.

While waiting for approval, you can:

• Use standard login: Access INVOLVE with your regular username/password

For IT:

"Does this app look suspicious?"

• No - This is the legitimate INVOLVE application

• The developer name may appear as "EDUKA SOLUTIONS PTY LTD" which is the parent company