> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/design-considerations-and-frameworks/user-management/managing-users/accessmanagement-audit-functionality.md). # AccessManagement Audit Functionality ## Description LogicNets allows you to publish projects as packages and make them available using a published start code. Based on the configured authentication and roles settings and the configured user groups, users can access these packages with or without authentication and with specific roles. You can also place published packages on the logon portal dashboard. Deploying packages with start codes but without authentication or defined user roles risks allowing security leaks in your system; therefore, LogicNets recommends you periodically check which packages are deployed and who can access them. To support this audit/security check, LogicNets added two dashboards to the Access Management function: *Package/Groups* and *Users/Groups*. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-0ec4d67ac8b2455d8b1148123484651cb659fb6a%2F781ed43c-4cbf-438e-ba16-c5dee5e6e871.png?alt=media) ## Starting an Audit To start an audit, click the *Access Management* icon on your dashboard. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-6aeb93d9f0990b5409c8bba6071e9874498cb7f5%2F5d0d2c0a-8b8c-47c0-a766-479c75978065.png?alt=media) From the left-side navigation bar, select the *Audit* icon. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-6eaa5829a4632fb06b3cbcdc6ce6d4ebe1079121%2Ff5ca8b79-4b26-437e-8aac-3b1f81a18784.png?alt=media) The system gathers the current information from your LogicNets system and displays your Audit dashboard. ## Package/Groups The *Package/Groups* dashboard lists all packages available on a company's installation, and this dashboard displays the following information for each package: * Start code * The groups that can start a package through the Logon Dashboard/Portal * The roles assigned to each user group One of the groups in this view is Guests, which identifies those packages that users can access without authentication. An authenticated user is authorized to use a package if there are no defined roles or if the authenticated user has at least one package role assigned. Packages without roles will appear with role (default). The Package/Groups view also checks for common security weaknesses and displays warnings when a package with start code and one of the following is true: * The authentication is disabled. This means authentication is not enables and any user or guest can access the package. * The package does not have defined roles. This means any authenticated user is authorized to use the package. * One of the parent frameworks is not available. This means the parent package () is not installed. ## Users/Groups The *Users/Groups* dashboard lists all users defined in the system and each group to which that user is assigned. The dashboard lists the following user types: * Local users * Users configured in user groups as non-local users * Rule-based/dynamic users defined in IdP configurations; for example, *strfind(user\_email, "@logicnets%.com")* contains all users ending with @logicnets.com. ## Download Filtered data shown on screen can be downloaded to JSON format only currently. To review and use the data in other formats such as Microsoft XL, the JSON file can be imported and split into columns using Power Query (example instructional video [here](https://youtu.be/0H1YRUu-jLI?si=af3IMdn30i_Aly1k)), or there are free and paid third-party tools like [gigasheet.com](http://gigasheet.com) that offer an upload JSON and download CSV service. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://community-test.logicnets.com/release-9/design-considerations-and-frameworks/user-management/managing-users/accessmanagement-audit-functionality.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.