> For the complete documentation index, see [llms.txt](https://docs.vcheckglobal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vcheckglobal.com/platform/permissions.md). # Permissions ## Overview: Your Access on the Vcheck Platform * The purpose of User Roles is to tailor your experience, ensuring you only have access to the features and tools necessary for your responsibilities. * A user can have one or several roles based on their job function. When you are onboarded to the Vcheck Platform, you are assigned a User Role. This role determines what features and actions you have access to in the system. ### Understanding User Roles User Roles help us tailor your experience in the Portal by giving you access to the tools and features you need. Most of our clients are granted Full Access, which allows them to utilize the platform’s complete toolset. Depending on your role, you might be able to: * Submit new projects * View and download reports * Manage users or billing * Communicate with the Vcheck team directly in the platform A user can have one or several roles based on their responsibilities. Your account manager will help you determine the set up that works best for your team. *** #### Need to Update Your Access? If you require a change to a User Role—either for yourself or a member of your team—contact Support directly at . --- # 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://docs.vcheckglobal.com/platform/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.