> For the complete documentation index, see [llms.txt](https://xoops.gitbook.io/smartfaq-tutorial/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://xoops.gitbook.io/smartfaq-tutorial/operating-instructions/categories.md). # Categories Moving on to the next area of the administration setup, we need to create at least one category in order to input and display content in the module. The categories page is accessed either by the link in the module icon or from the tab menu that heads the administration pages. The Category page displays two main regions; The first is a list of Created categories showing all Categories and sub-categories. This can be hidden by clicking the ![image001.png](/files/-LD6N1KHkQijoB0ip83Z) (close icon) The second region is a **Create category** form allowing administrators to create categories and sub-categories. This can also be hidden by clicking the ![image001.png](/files/-LD6N1KMDV3pNFHZjxFg) (close icon). Clicking the ensuing ![image001.png](/files/-LD6N1KOXLOv6IYAN1ge) (open icon) Returns the data. **Create category.** Initially SmartFAQ will not have any categories and you will need to plan and create these before using the module. Lets begin by inputting details of a new category in the form. **Editing categories.** Once you have created a category it will appear in the Created Categories list. It will include a truncated description, weight position and edit / delete icons. The category names will be shown as clickable links that open the category on the module web page. This allows administrators a full view of the category details before taking any actions to edit or delete. The Web Pages in turn will display an Click for more details about Category button ![image001.png](/files/-LD6N1KSiaUzN2p8yNU5) (Category icon) before its description Clicking this will bring you straight back to the original administration page to continue any actions. This same procedure applies to sub-categories, except you will see the ![image001.png](/files/-LD6N1KUDCdt4Ga8hJJW) (sub-category icon) > **NOTE:** SmartFAQ features a very flexible permission system. This allows administrators to grant viewing access of any category to any group in the system. This also applies to sub-categories, BUT users in a group can only view a sub-category if it also has access to its parent category. Viewing permissions can also be decided on a specific question basis, both for Q\&As and Open questions. To allow a specific question to be visible to any group means it must also be in a category that also has permission to be viewed by that group. Users may be in more than one system group, so care should be taken before setting up complex SmartFAQ configurations. **Page: /modules/smartfaq/admin/category.php** ![image001.png](/files/-LD6N1KYDun7f4Gmxa19) ## Categories: Viewing categories in web page as administrator: **Page: /modules/smartfaq/category.php?categoryid=1** This image shows tool tips to show Administrators links to edit/ delete categories while logged in and viewing the module webpage. ![image001.png](/files/-LD6N1KaYVOnMzD-EqOv) Fig. 10 Categories page showing administration options --- # 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, and the optional `goal` query parameter: ``` GET https://xoops.gitbook.io/smartfaq-tutorial/operating-instructions/categories.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.