Skip to main content

FORA Automated User Provisioning Setup Guide

FORA automatically syncs users from your organization's identity provider, ensuring your team always has the right access without manual user management.

Updated over 2 weeks ago

FORA automatically syncs users from your organization's identity provider, ensuring your team always has the right access without manual user management. This guide walks you through connecting either Google Workspace or Microsoft Entra ID (formerly Azure AD) to enable automatic user provisioning and deprovisioning.
​

Choose Your Identity Provider

Select the setup instructions that match your organization's primary identity system:


Google Workspace Setup

Prerequisites

  • Google Workspace administrator access

  • Ability to configure domain-wide delegation settings

Step 1: Enable Domain-Wide Delegation

  1. Sign in to your Google Admin Console

  2. Navigate to Security > API Controls > Domain-wide Delegation

  3. Click Add New to create a new delegation

  4. Enter the following details:

    • Client ID: 103157776030359327036

    • OAuth Scopes: Copy and paste this entire list:

https://www.googleapis.com/auth/admin.directory.user.readonly,https://www.googleapis.com/auth/drive.readonly,https://www.googleapis.com/auth/calendar,https://www.googleapis.com/auth/userinfo.email,https://www.googleapis.com/auth/userinfo.profile
  1. Click Authorize to save the delegation

Step 2: Collect Required Information

You'll need to provide the FORA team with two pieces of information:

Google Workspace Customer ID:

  1. In Google Admin Console, go to Account > Account Settings > Profile

  2. Copy the Customer ID (this is a long alphanumeric string)

Admin Email Address:

  • Provide any email address that has Google Workspace administrator privileges

Step 3: Share Information with FORA

Contact your FORA implementation team with:

  • Your Google Workspace Customer ID

  • Your admin email address


Microsoft Entra ID Setup

Prerequisites

  • Microsoft Entra ID (Azure AD) administrator access

  • Global Administrator or Application Administrator role

Step 1: Grant Admin Consent

Choose either option below:

Option A - Direct Consent Link:

  1. Click this link: Grant FORA Admin Consent

  2. Sign in with your administrator account

  3. Review the requested permissions

  4. Click Accept to grant consent

Option B - Through Entra Admin Center:

  1. Navigate to Identity > Applications > Enterprise Applications

  2. Search for "FORA" in the applications list

  3. Select the FORA application

  4. In the left sidebar, click Permissions

  5. Review the requested permissions

  6. Click Grant admin consent for [Your Organization]

Step 2: Collect Your Tenant ID

  1. In the Microsoft Entra Admin Center, go to Identity > Overview > Properties

  2. Scroll down to find the Tenant ID field

  3. Copy the Tenant ID (this is a GUID format like: 12345678-1234-1234-1234-123456789012)

Step 3: Share Information with FORA

Contact your FORA implementation team with your Tenant ID


What Happens Next

Once you've completed your setup and shared the required information:

  1. FORA will configure the integration using the credentials you provided

  2. Initial user sync will import all active users from your identity provider

  3. Automatic provisioning will begin - new users added to your workspace will automatically get FORA access

  4. Automatic deprovisioning will remove access when users are deactivated in your workspace

Required Permissions

Google Workspace Permissions

FORA requires these read-only permissions to sync your users:

  • Directory API: Read user profiles and organizational structure

  • Drive API: Access to meeting recordings and documents (read-only)

  • Calendar API: Access to meeting metadata for compliance scanning

  • Profile API: Basic user information for account linking

Microsoft Entra ID Permissions

FORA requires these permissions to sync your users:

  • User.Read.All: Read all user profiles

  • Group.Read.All: Read group memberships

  • Calendars.Read: Access meeting metadata

  • Files.Read.All: Access to Teams recordings and files (read-only)

Support

If you encounter any issues during setup or need assistance:

  • Contact your FORA implementation specialist

  • Email our support team with your setup questions

  • Reference this guide's URL when requesting help

Security Note: FORA only requires the minimum permissions necessary for user provisioning and compliance monitoring. We never store or have access to your organization's authentication credentials.

Did this answer your question?