Gemini Enterprise Vertex AI Search App: Confluence Data Granularity Vagueness

During the datastore creation process, it is unclear how to make granular selections of what data is ingested beyond just the content type. We do not want to ingest the entire confluence space, nor all the pages within a space, we are interested in ingesting specific pages within a Confluence Space.

During the datastore creation process, we can only select the content type (Page/Whiteboard/Blog/etc..) but we need to be able to choose which pages/etc.. to include. There’s a vague “Google Identity will be used for the access control. Learn more.” description, which points to generic non-helpful permissions. We experience the same limitation when attempting to trim an already created data store.

When I navigate to the Confluence datastore, then the “Pages” content type, I get a generic “Viewing documents is not available This data store contains access controlled documents which cannot be viewed.”, and there’s no indication of where to go to adjust permissions so I could drill down within the pages and make selections of what to include/exclude