> For the complete documentation index, see [llms.txt](https://guides.noloco.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.noloco.io/users-and-permissions.md). # Users & Permissions - [User Table](https://guides.noloco.io/users-and-permissions/user-table.md): Understanding the User Table: a central repository of all user-related information - [User Management](https://guides.noloco.io/users-and-permissions/user-management.md): Manage your existing users and invite new users to your app from the User Management tab - [Sharing Your App](https://guides.noloco.io/users-and-permissions/sharing-your-app.md): Copy your app's link, invite people by email and create invite links, all from the Share button in the builder - [Invite Links](https://guides.noloco.io/users-and-permissions/sharing-your-app/invite-links.md): Create reusable links that let people request access to your app with a set role, optionally limited to your email domain - [Permissions Quick Start](https://guides.noloco.io/users-and-permissions/permissions-quick-start.md): Quick start guide for setting up permissions in Noloco apps - [User Roles & Permissions](https://guides.noloco.io/users-and-permissions/user-roles-and-permissions.md): Keep tight control over user access levels using User Roles & Permissions - [Record-level permissions](https://guides.noloco.io/users-and-permissions/user-roles-and-permissions/record-level-permissions.md): Control user access with record-level permission rules - [Field-level permissions](https://guides.noloco.io/users-and-permissions/user-roles-and-permissions/field-level-permissions.md): Learn how to use field-level permissions to control which users can read, update & create data in Noloco apps. - [Permissions vs Visibility vs Filters](https://guides.noloco.io/users-and-permissions/permissions-vs-visibility-vs-filters.md): Understand when to use permissions, visibility rules, or filters for access control - [Permissions Troubleshooting](https://guides.noloco.io/users-and-permissions/permissions-troubleshooting.md): Troubleshooting guide for common permission issues and solutions - [Open Sign Up](https://guides.noloco.io/users-and-permissions/open-sign-up.md): If you need to let new customers sign up to your app, you can enable open sign up - [Offboarding Users](https://guides.noloco.io/users-and-permissions/offboarding-users.md): Deactivate user accounts without losing their data - [Testing as other users](https://guides.noloco.io/users-and-permissions/testing-as-other-users.md): Testing your app from the perspective of different users to test permissions, roles, filters and more. --- # 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://guides.noloco.io/users-and-permissions.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.