Skip to main content

Settings

Configure SSO, ticketing integrations, and notification channels for your Kscope workspace.

Google SSO​

warning

Prerequisite: The user must first be added to the Team page using their Google email address.

Step 1: Enable Google SSO in Kscope​

  1. Navigate to Agent Hub > Settings

  2. Go to SSO and click Enabled

  3. Copy the Kscope callback URL (click the copy icon)

Step 2: Create an OAuth Client ID in Google Cloud​

  1. In Google Cloud Console, go to APIs & Services > Credentials

  2. Click CREATE CREDENTIALS > OAuth client ID

  3. Select Web application as the Application type

  4. Name it (e.g., kscope-sso)

  5. Under Authorized redirect URIs, paste the Kscope callback URL

  6. Under Authorized JavaScript origins, add https://<your_tenant_id>.kscope.ai

  7. After creating, copy the Client ID and Client secret

Step 3: Add Credentials in Kscope​

Go back to Kscope Settings and enter the Client ID and Client secret from Google Cloud.

Users can now log in with their Google credentials.

Microsoft SSO​

warning

Prerequisite: The user must first be added to the Team page using their Microsoft email address.

Step 1: Enable Microsoft SSO in Kscope​

  1. Navigate to Agent Hub > Settings > SSO and click Enabled
  2. Copy the Kscope callback URL

Step 2: Register Application in Azure Portal​

  1. Go to App registrations

  2. Click New registration, name it (e.g., kscope-sso)

  3. Keep default Supported Account types

  4. For Redirect URI, select Web and paste the Kscope callback URL, then click Register

  5. Copy the Directory (tenant) ID and Application (client) ID

  6. Click Add a certificate or secret > New client secret

  7. Set description to "Used for Kscope SSO" and copy the secret Value

  8. Go to Token configuration > Add optional claim

  9. For all 3 types (ID, Access, SAML), select all claims

Step 3: Add Credentials in Kscope​

Go back to Kscope Settings and enter the Tenant ID, Client ID, and Secret Key from Azure Portal.

Users can now log in with their Azure credentials.