So currently there are two ways of using a remote knowledgebase with Folio:
Manage content in the external KB, interact with KB through eHoldings (only implemented for EBSCO KB so far). In this scenario the data continues to be held in the external KB and is not brought into Folio.
Import content from the external KB into the Folio internal KB (only implemented for GOKb so far). In this scenario the data is held in the internal KB - which is what you see when you search the Agreements eResources tab.
As Khalilah said, we are working on adding the ability to import package data directly into the internal KB. The internal KB can hold data from multiple sources, so once we’ve completed the data import work, you will be able to use GOKb and also import additional package data from files into the internal KB.
In theory you can use both approach (1) and (2) at the same time, although this might be confusing - hence the introduction of the “Hide internal agreements knowledgebase” setting in Settings->Agreements->General - you use this if you only want to manage knowledgebase content through eHoldings.
Whichever approach you use, you are able to add the eresources to Agreements and through the agreement also connect to licenses
Hope that all makes sense?