> For the complete documentation index, see [llms.txt](https://guide.acumensystems.com.au/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.acumensystems.com.au/system-parts/master-files/system-options/security/access-objects.md). # Access Objects There are three types of access objects: * [**Menu**](/system-parts/master-files/system-options/security/access-objects.md#menu-objects) objects * [**Group**](/system-parts/master-files/system-options/security/access-objects.md#group-objects) objects * [**Special**](/system-parts/master-files/system-options/security/access-objects.md#special-objects) objects ### Menu Objects The most common object is the Menu Object. There is a Menu object for every item on the menu which requires security (which is to say nearly all the menu items have an object). The Menu object is the most direct way to provide access and always takes precedence over Group access. ### Group Objects These are simply access objects that can be used to specify an access level for a group of associated menu items. Group objects typically equate to parent menu items. For example items on the Debtors submenu have "Debtors" as a group object in addition to their menu object names. Group access only applies to items in that group for which there is no over-riding direct object access level. Individual objects may belong to more than one group. Group access levels are sought in reverse order (ie. from right to left as shown in the groups column) and only the first group entry found is used. For example the Product Pricing screen has a menu security object of "Pricing" and belongs to the groups "General" and "Prices". If no specific entry for "Pricing" can be found the system will search for a "Prices" entry. If this is not found it will continue and search for a "General" entry. If this is not found it will resort to the base access level for this user. ### Special Objects These are used to grant or deny access to special facilities within the software that do not equate to a menu item. Some of these grant specific abilities such as access to a price category and as such have their own pulldown with a selection relevant to the ability or function being specified. --- # 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://guide.acumensystems.com.au/system-parts/master-files/system-options/security/access-objects.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.