> 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/signing-in-and-workspaces.md).
# Signing In & Workspaces
Sign in to the Vcheck Platform and switch between workspaces.
To access the Vcheck Platform, go to [https://portal.vcheckglobal.net](https://portal.vcheckglobal.net/).\
You’ll be prompted to log in using your email address and password. If you prefer not to use a password, click **Send access link** to receive a secure one-time login link valid for 15 minutes.
**Multiple Workspaces**
If you’re associated with multiple client accounts, you will have access to multiple workspaces within a single login. You can select the workspace you would like to use after logging in.
To switch accounts later:
1. Click on the Workspace
2. Select **Switch Workspace**.
3. Click on the Workspace you want to enter from the list.
---
# 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/signing-in-and-workspaces.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.
