> For the complete documentation index, see [llms.txt](https://docs.aisera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aisera.com/aisera-platform/adding-metadata-to-knowledge-articles.md). # Adding Metadata to Knowledge Articles This topic describes how you can use content tag metadata to filter Knowledge Articles after they have been ingested to the Aisera Gen AI Platform. ### Before Ingestion into the Aisera Gen AI Platform When you are planning to ingest Ticket and Knowledge Base Article data from your Enterprise software to the Aisera Gen AI platform, you may want to add metadata tags to your articles before connecting your Enterprise data store to the Aisera platform. The instructions for adding tags to your articles should be in the Product Documentation for the system you are using. For example: If you are using **Zendesk**, information about how to add content tags is here:\ For **Salesforce**, the information is here: For **ServiceNow**, the information is here:
For **Confluence**, see:\ [Ingesting Dynamically Generated Content from Confluence](https://docs.aisera.com/aisera-platform/adding-data-to-your-tenant/integrations-and-data-sources/connectors/confluence-connector/ingesting-dynamically-generated-content-from-confluence) (adds new field) \ For **NexThink**, the information is here:\ \ You may need your company’s administrator for your Enterprise system to add these content tags. ### How Content Tag Metadata Can Be Used in the Aisera Gen AI Platform You can limit which users see which content as fulfillment in an application/bot by adding content tags. ### Contant Access Control Content Tags are associated with user permissions, since you are filtering by the user and the topic tags. The Aisera Gen AI platform offers two types of content access control: [Content-level Permissions](https://docs.aisera.com/aisera-platform/adding-data-to-your-tenant/content-access-control#content-level-restrictions-acls-for-kb-articles) (ACLs per Knowledge Article) [Content Access Controls via APIs](https://docs.aisera.com/aisera-platform/adding-data-to-your-tenant/content-access-control/content-access-control-via-apis) (if supported) ### Channel Metadata Filters You can limit which content is returned to a specific channel by setting up filters when you add a channel to your tenant configuration. Specify metadata tags as key-value pairs during channel configuration for use in RAG searches. When a RAG search is invoked, the metadata tags are appended to the end of the user’s query, allowing different channels to return tailored results while still utilizing the same bot. ### Tenant Configuration for Channels You can also use custom fields and session variables with channels. See [Channel Configuration](https://docs.aisera.com/aisera-platform/tenant-setup/aisera-platform-configuration/tenant-configuration-settings/channels#channel-configurations) for more details. ### Using the Aisera Ingestion APIs The Aisera Ingestion API for Knowledge includes the following: The content tags should already be included in each document by the time you start ingesting the knowledge articles. If you haven’t added content tags before you ingest the articles, you can add content tags and then ingest the articles again. ### Anonymizing PII See [Masking PII and PHI](https://docs.aisera.com/aisera-platform/tenant-setup/security-and-privacy-traps/masking-pii#pdf-page-cexr5nkox79faqeifwl3-applying-pii-phi-at-the-datasource-level) for information. ### Application/Bot-Level Permissions See [Access Attributes](https://docs.aisera.com/aiseragpt/how-to-set-up-an-aiseragpt-bot/add-application-access-attributes). ### General Steps to Optimize a Document for RAG Indexing [How to Optimize Documents](https://docs.aisera.com/aisera-platform/adding-data-to-your-tenant/data-ingestion/optimizing-documents-for-rag-indexing/how-to-optimize-documents) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.aisera.com/aisera-platform/adding-metadata-to-knowledge-articles.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.