> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/introduction-to-avo-assure/exploring-home-page/managing-home-page/projects-in-avo-assure-1.md).

# Copying Project Link

The copy project link allows you to share direct links to the home page with the project details. Opening a project link automatically restores the selected project, even after a page refresh or when opened in a new browser tab. Access to the linked page is determined by your project assignment and permissions. This article explains how to copy and use project links for quick access and collaboration.

{% hint style="info" %}
**Note**:

* When you share a project link with a user, the user must be added to the project.
* You must log in to the Avo Assure instance to access a project's direct link.
  {% endhint %}

To copy project link, perform the following actions:

1. On the **Home** page, from **Projects** list, select required project.
2. On the browser address bar, select the project link.
3. Press **Ctrl + C** Key combination on the keyboard. The link gets copied.


---

# 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.avoautomation.com/avo-assure/introduction-to-avo-assure/exploring-home-page/managing-home-page/projects-in-avo-assure-1.md?ask=<question>&goal=<user_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.