Drive connector: indexed object count identical after full reconnect, is the allowlist applied??

[Fran _Administración_]

Hi all,

I'm trying to scope the Rovo Google Drive connector to a single shared drive, and after several days I can't tell whether the allowlist is being applied at all. I'd appreciate a sanity check from anyone who has this working.

**Goal**

A Rovo agent that answers only from the documents in one Google shared drive ("Integración - Documentación"). Nothing else from Drive should be indexed.

**Setup**

- Google Drive connector added by a Workspace admin account, with domain-wide delegation.
- Allowlist: one entry, the shared drive root URL (ID starting with 0A...). Verified it's the drive root, not a subfolder — an earlier subfolder URL was correctly rejected with "folder does not exist in any shared drive you have access to".
- Blocklist, date filter, group inclusion/exclusion: all unconfigured.
- "Allow personal drives" toggle: OFF. The "Review included content" summary confirms "Shared drives: 1 location included in the allowlist" and "My Drive: not included".
- The org has only 2 shared drives in total.

**Verified contents of the allowlisted drive**

Using the Drive API with the same admin account that the connector delegates to:

- 147 total items: 124 files + 23 folders
- Of those files, 22 are of types the connector documents as indexable (3 PDFs + 19 CSVs)
- Expected indexed object count: roughly 45

**What actually happens**

- Day 1, right after fixing the allowlist: 26,082 indexed objects
- Day 2: 26,217 — it went UP, not down
- Days 3-4: still 26,217, unchanged
- I then deleted the connector entirely and created a new one from scratch. After the initial indexing spinner finished, the count is again exactly 26,217 — byte-identical to the previous connector's figure.

That last point is what I can't explain. A brand-new connector landing on the exact same number as the deleted one suggests either the count is cached org-level telemetry rather than the connector's real state, or the previous index was never purged on disconnect.

**Questions**

1. Is the allowlist actually enforced for Google Drive today? I found AI-1226 ("Create Allowlists for Rovo Google Drive ingestion"), which is still in Gathering Interest and states there is no known workaround — yet the admin UI does show a working allowlist tab that accepts drive, folder and file URLs. Has this shipped, or is the UI ahead of the engine?

2. How often does the "indexed objects" counter refresh, and does it survive a connector being deleted and recreated? If it's cached, it's very hard to verify any scoping change.

3. What does the green "Sync in progress" label mean exactly? It appears permanently with grey and green color depends of the moment. Is it a status badge (sync enabled) rather than a progress indicator?

4. If the allowlist isn't enforced yet, is the blocklist the recommended approach — i.e. explicitly blocking every other shared drive?

Thanks in advance for any pointers.