> For the complete documentation index, see [llms.txt](https://docs.veedna.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.veedna.com/sca360-flexible-deployment-for-data-center-cloud-integrated-environments/registering-lineaje-sca360.md).
# Registering Lineaje SCA360
You must register Lineaje SCA360 to activate your deployment and enable access to its features.
To register the Lineaje SCA360 you deployed:
1. Log in to the [Lineaje Portal](https://app.veedna.com/).
2. In the left-hand navigation, select **Integrations**.
3. Under **SCA360**, click **Deploy on Private Cloud** > **Download CLI.**
4. Click **Download SBOMDetect** CLI.
5. Click **Verify Device** > **Verify Link**.
6. In the browser window that opens, enter your credentials and click **Sign In**. Click **Yes** to grant access.
7. Go back to the Lineaje Portal browser window.
8. Copy the command shown under **Run the CLI** section.
9. Go back to the **Session Manager** browser window and paste the command. Alternatively, on the Lineaje SCA360, go to the folder /opt/veecli and run the command. It should display **Successfully registered veeCLI**. If it fails, contact Lineaje Support.
---
# 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.veedna.com/sca360-flexible-deployment-for-data-center-cloud-integrated-environments/registering-lineaje-sca360.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.
