Skip to main content

Enable Self-Service Content Sources

Self-service content sources let your users connect their own SharePoint sites from the Zeta Alpha app. Each user signs in with their Microsoft account once, picks the sites to sync, and the platform crawls as that user: the crawl sees exactly what the user can see, and document visibility follows their own SharePoint permissions.

As the tenant admin you control the whole offering: which provider users sign in through, what they can request, how often their sources sync, and whether requests need your approval. This guide walks the full loop:

  1. Activate the feature for your tenant
  2. Register the OAuth provider
  3. Create a request template
  4. What your users do
  5. Review and approve requests

Prerequisites​

  • Admin access to the Zeta Alpha Platform UI.
  • An Entra ID app registration with delegated permissions and the redirect URI for your environment. Follow Delegated (per-user) access to set it up, and keep the Application (client) ID, Directory (tenant) ID, and the credential (client secret or certificate) at hand. Microsoft's app registration quickstart covers the portal basics.

Step 1: Activate the feature​

Go to your tenant, open Features, and find Self-service Content Sources. Set Status to Active and configure the tenant defaults:

SettingWhat it does
Auto-approve requestsWhen on, requests to add or remove a source skip your review queue and take effect immediately. Requests to change a source skip it too, unless Updates require approval is on.
Max pending requests per userHow many requests a user may have awaiting review at once.
Updates require approvalWhen on, changes a user makes to an already-approved source (different sites, OneDrive toggle) go through review even while Auto-approve requests is on.
Notification emailWhere "a new request awaits review" notifications go. Leave blank to send none.

Each of these is a tenant-wide default; a request template can override any of them per template (step 3).

While the status is not Active, users do not see the offering in the app and requests are rejected. Templates and providers can still be configured in advance.

Step 2: Register the OAuth provider​

Go to OAuth Providers and create a provider of kind Microsoft (Entra ID). This stores your app registration once, centrally: the credential is encrypted, never returned by the API, and rotated in one place.

Fill in:

  • Name: a stable lookup key, unique per tenant (for example microsoft-delegated).
  • Display Name: what users see on the sign-in button (for example Microsoft 365).
  • Client ID and Directory (tenant) ID: from the app registration. The directory ID is your Entra ID directory, not the Zeta Alpha tenant.
  • The credential: a Client secret or a Certificate (PEM private key + SHA-1 thumbprint), matching what you created in the app registration.
  • Scopes: requested at sign-in. Click Use SharePoint defaults to prefill the four scopes SharePoint delegated crawling needs: offline_access, User.Read, Sites.Read.All, Files.Read.All. They must also be granted as delegated permissions on the app registration (with admin consent); see the permission table and Microsoft's permissions reference.

You can rotate the credential at any time. While connected accounts or content sources use the provider, its Client ID and Directory (tenant) ID cannot change: create a new provider instead.

The redirect URI on the app registration must be the callback URL Zeta Alpha provides for your environment, the same URL described in the app-access guide. Sign-ins fail with a redirect mismatch error otherwise.

Step 3: Create a request template​

A template is the offering: users can request exactly what you templated, nothing else. Go to Request Templates and click Create Request Template.

  • Name: stable lookup key, immutable after creation.
  • Display Name, Description, Logo URL: how the option renders in the user's "Add knowledge base" flow.
  • Connector: what the template offers.
  • OAuth Provider: the provider from step 2; users sign in through it when connecting their account.
  • Scheduled Tasks: the sync cadence of every source created from this template, per task type (cron format). At least one task is required: the template defines how often its sources sync.
  • Policy Overrides: per-template overrides of the tenant defaults from step 1. Every field offers Inherit tenant default (currently: …), so overrides are explicit and the effective value is always visible.
  • Notification email: overrides the tenant address for requests created from this template.
  • Workflow Overrides: ingestion workflow names applied to sources created from this template.
  • Field Mappings: field mappings applied to sources created from this template.

Enabled controls visibility: disable a template to withdraw the offering without deleting it.

Step 4: What your users do​

In the app, users open My knowledge bases and click Add knowledge base:

  1. Choose source: pick a template (skipped when only one is offered).
  2. Name: name the source so they can identify it later, with an optional message for the reviewing admin.
  3. Sign in: the Microsoft sign-in for the template's provider, in a popup. One interactive sign-in produces the refresh token that makes unattended crawling possible; users are not asked again unless access is revoked.
  4. Select sites: the SharePoint sites the signed-in account can reach, plus an Include my OneDrive toggle. Expanding a selected site narrows it to specific document libraries; leaving them all selected syncs the whole site.
  5. Done: the wizard states the outcome (created immediately under auto-approval, or awaiting your review) and how often the data will sync, from the template's schedule.

On the same tab users follow their sources afterwards: how many documents are searchable (with failed and still-processing documents counted apart), last sync, expired authorizations with a one-click reconnect, and editing or removing the source (both subject to the approval settings).

Step 5: Review requests​

When a request lands in review, the notification email (template address first, tenant address as fallback) links straight to it with a Review request button. The requester's message, when they left one, appears in the email and on the request's detail page next to the review controls.

On the request detail page you see the requester, the sites they picked, and the template behind the request:

  • Approve creates the content source with the requested configuration and the template's platform defaults (schedule, workflows, field mappings) and starts a full crawl right away. Later crawls follow the template's cadence, authenticated as the requesting user.
  • Deny requires a review comment, which is shown to the requester on their My knowledge bases page.

Requests to update or remove an approved source arrive in the same queue; approving a removal drains the source's documents from the index. With Auto-approve requests on, new sources are created the moment a user completes the wizard and removals apply at once; update requests still come to you while Updates require approval is on.

What's next?​