Prepare Your Document Libraries for Appspace Federated Search: Best Practices for SharePoint, Google Drive, Box, and OneDrive

Organizations connect external document systems to Appspace so employees can search SharePoint, Google Drive, and Box from Spotlight global search and browse linked Document Libraries inside Communities—without leaving the intranet. That experience works best when the source library is organized for discovery, not just for storage.

For: IT administrators, SharePoint/Google/Box owners, and Appspace administrators who configure federated search connections and Document Library integrations.

It covers SharePoint, Google Drive, and Box as document-management sources. Federated Search also includes ServiceNow; that provider is out of scope here. OneDrive is not a Document Library or Federated Search provider—only Microsoft Drive passport / OAuth plumbing exists today.

Search behavior is not the same for every provider. Google Drive federated search matches file names only. SharePoint uses Microsoft Graph Search (KQL) and can return summary snippets from indexed content. Box Search is called without a content-type restriction, so enterprise Box can match file content. How you name files, scope connections, and assign permissions still determines whether Appspace search feels fast, relevant, and trustworthy—but do not tell SharePoint or Box admins that Appspace never searches body content.

Federated search (Spotlight / Universal Search) and Document Library connections (Community library tab) are configured separately. You can enable one without the other, but both benefit from the same source-library hygiene.

How Appspace Uses Your Source Library

Understanding these platform behaviors helps explain the recommendations below.

SharePoint Document Libraries, Google Drive, and Box are configured in Admin Console with library passports and Search Integrations. For setup, see Configure Employee Experience Settings (part 2) and Create and Edit Posts, Stories, and Pages in a Community. OneDrive / Microsoft 365 federated search is not generally available; OneDrive is not in the live Document Library or Federated Search provider set.

Search semantics by provider

Core Principles

1. Optimize for how each provider searches — Google Drive lives or dies on file names. SharePoint and Box can also match indexed body content; still use clear names and titles.
2. Scope as narrowly as the product allows — Prefer selected SharePoint libraries or sites over the whole tenant. For Google Drive and Box, drive/folder scope exists only on the admin passport path; user-passport connections cannot pick a Shared Drive or ancestor folder.
3. Align permissions before go-live — Fix access in the source system. With a user passport, Appspace cannot expose content a user cannot already reach. With an admin passport, everyone sees up to that passport's ceiling.
4. One logical home per document — Duplicates, drafts, and archived copies create confusing search results.
5. Match Community intent to folder intent — The Appspace Community audience should mirror the SharePoint library or folder audience.

Do

Naming and metadata

• Use descriptive, searchable file names that include topic, document type, and audience where helpful (for example, 2026-Employee-Benefits-Guide-HR.pdf instead of Final_v3.pdf). This is essential for Google Drive and still valuable for SharePoint and Box.
• Populate native title and description fields in SharePoint columns, Box descriptions, or Google Drive file details. These values appear in result metadata and can improve findability where the provider indexes them for search—not all fields are query targets in Appspace.
• Apply a consistent naming convention across teams (date prefix, department code, document type) so employees can predict search terms.
• Keep file names unique within a connected library when versioning matters. SharePoint native versioning handles same-name uploads in SharePoint. Appspace upload/version alignment with SharePoint native versioning is limited today—prefer uploading new versions in SharePoint.
• Use standard, supported file types for content you expect employees to open from Appspace (Office documents, PDF, common image formats).

Information architecture

• Create purpose-built libraries or root folders for intranet discovery—for example, HR Policies, Brand Assets, or Sales Enablement—rather than connecting a general-purpose team site dump.
• Keep folder depth manageable (aim for three to four levels or fewer). Deep paths are harder to browse in Document Library views and add little search value when folder names are not descriptive.
• Separate active content from archives using distinct libraries or top-level Archive folders, and exclude archives from federated search scope when possible.
• Map one Appspace Community to one well-defined source root so browsing and search context stay aligned.
• Document the canonical location for each document type so authors do not scatter copies across sites.
• SharePoint: Prefer site or selected library federated search scope. Tenant-wide search (no site/library selected) is available but noisy and heavier on Microsoft Graph.
• Google Drive / Box: If you need a curated Shared Drive or folder (and to keep personal My Drive out of results), use an admin passport so source-group / folder controls are enabled. User-passport Google Drive search uses allDrives and can include My Drive files the user can access.

Permissions and identity

• Grant access through groups (Microsoft 365 groups, SharePoint groups, Google Groups, Box groups) rather than ad hoc individual sharing.
• Ensure employee email addresses match between Appspace and the document system so ownership and access mapping work correctly.
• Prefer user passports for federated search when you want each employee to see only what they personally can access.
• Use admin passports deliberately—only when a shared, consistent result set is intended (for example, a curated public knowledge base folder). Remember this is also the only path that lets you pick Google Drive / Box folder or Shared Drive scope in the console.
• Validate access with representative test accounts before announcing federated search to the organization.

Operations and governance

• Review connected scope quarterly and remove libraries or folders that no longer belong in intranet search.
• Assign a library owner responsible for naming standards, permission hygiene, and retiring outdated content.
• Test search with real employee queries during pilot (policy names, form numbers, acronyms) and adjust naming or scope based on misses.
• Plan for rate limits on large tenants by avoiding unnecessarily broad connections that query huge libraries on every search.

Don't

Naming and metadata

• Don't rely on folder path alone to convey meaning. Cryptic file names stay hard to find—especially in Google Drive, where federated search is filename-only.
• Don't use generic names such as Document.docx, Untitled, Copy of…, or Final_FINAL across hundreds of files.
• Don't assume Appspace never searches document bodies. That is true for Google Drive (filename only). SharePoint Graph Search and Box enterprise search can match indexed content. Native DMS search may still differ from Appspace results.
• Don't treat custom metadata columns, Box metadata templates, or Google Drive labels as primary Appspace filters yet. Advanced provider-specific metadata filters are planned for future releases.

Information architecture

• Don't connect an entire SharePoint tenant or all Shared Drives unless you accept noisy results, slower queries, and higher API load. Tenant-wide SharePoint search is possible; it is rarely a good default.
• Don't assume private My Drive is excluded. User-passport Google Drive federated search can return My Drive files the user can access. Don't mix personal drafts with official content if employees will search with a user passport.
• Don't maintain multiple uncoordinated copies of the same policy in different sites if employees are expected to find "the" official version through Appspace.
• Don't reorganize folder structures aggressively during initial rollout. Moves within a connected library are supported, but large restructures can temporarily disrupt browse views, webhook sync, and user bookmarks—validate moves during pilot, especially for non-admin authors.
• Don't expect cross-library move/copy in Appspace to preserve a single item identity. Document Library integrations treat each connected library independently.

Permissions and identity

• Don't assume Appspace elevates access when using a user passport. If a user lacks SharePoint (or Drive/Box) read permission, the file will not appear in their federated search results.
• Don't use an admin passport with broader access than intended. Search results reflect what that passport can access; user passports are required when each employee should see only their own permitted content.
• Don't leave broken inheritance and one-off sharing links unmanaged; they produce inconsistent "sometimes I find it, sometimes I don't" behavior.

Operations

• Don't publish federated search before validating passport authentication and connection scope in Admin Console.
• Don't store sensitive or legal-hold content in broadly connected libraries unless access controls are explicitly verified.
• Don't ignore duplicate-file/version behavior. Prefer uploading new versions in SharePoint. Appspace upload/version alignment with SharePoint native versioning is limited today.

Provider-Specific Guidance

Microsoft SharePoint

SharePoint supports both federated search and Document Library browsing with webhook-based metadata sync. Google Drive and Box follow similar patterns for library vs search connections, but search semantics and scoping UI differ (see the matrix above).

SharePoint federated search scope is one of:

1. Tenant — no site (SourceGroup) selected → search across SharePoint
2. Site — site selected, no libraries (Sources) → that site
3. Libraries — site plus selected lists/libraries (listId filters)

OneDrive: Passport app microsoft-drive exists. OneDrive is not in Document Library, Federated Search, or external storage provider types. Do not treat it as a peer of SharePoint for this guide.

Google Drive

Box

Recommended Rollout Checklist

Use this sequence when connecting a new source library:

1. Define the audience — Which employees should find this content from Appspace?
2. Pick the smallest viable scope the product allows — SharePoint: one site or selected libraries, not the whole tenant. Google Drive / Box: admin passport plus Shared Drive or folder if you need a curated, non-personal result set; otherwise user-passport search is broad (allDrives / enterprise).
3. Audit top 20 documents — Rename and add descriptions where file names are unclear (required for Google Drive findability).
4. Fix permissions — Group-based access; remove orphaned shares.
5. Configure passport — User passport for personalized results; admin passport only if you intend a shared ceiling or need Drive/Box folder scope.
6. Create federated search connection — Admin Console → search integration settings. For SharePoint, set provider filter types to Document Library if pages should not appear.
7. Optionally link a Document Library to a Community — When browse + context matter, not search alone. One Community → one library; optional single root folder.

   

    

   

    

8. Pilot with 5–10 real queries — Confirm SharePoint summaries vs Drive filename hits vs Box content matches behave as you expect.

   

    

9. Assign an ongoing library owner — Quarterly scope and content hygiene review.

Troubleshoot

Use Case

Scenario: A global HR team publishes policies in SharePoint while employees are expected to find everything through Appspace.

The SharePoint site historically mixed project folders, personal drafts, and official policies in one default document library. Federated search returned hundreds of Policy.docx and Draft.docx matches—including Site Pages from the team site, because the connection used default content classes.

What worked:

1. Created a dedicated HR Policies library with versioning enabled in SharePoint.
2. Renamed files using {Year}-{Topic}-{DocType}.pdf.
3. Connected that library (site + selected library)—not the entire tenant or the whole HR team site—to Appspace federated search, and set provider filter types to Document Library so Site Pages stayed out.
4. Linked a subfolder root within that library to the HR Community Document Library tab—the archive lived in a separate library that was not connected.
5. Used a user passport so employees only saw policies their role could access.

Employees now find the correct policy in the first few Spotlight results, and the Community library browse view matches search expectations.

Related Articles

• Configure Employee Experience Settings (part 2)
• Create and Edit Posts, Stories, and Pages in a Community
• Add and Manage Topics
• Create Library Passport for Third-Party Integration
• Create Google Drive Passport in Appspace
• Centralized File Management