> For the complete documentation index, see [llms.txt](https://docs.arcware.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arcware.cloud/arcware-cloud-platform/getting-started-with-arcware-cloud/sharing-your-project/share-links-password-protected-access.md).

# Share Links (Password-Protected Access)

To provide an added layer of security and cleaner URL management by allowing users to access streams without exposing the unique Share ID directly in the web address.

#### The Difference Between Standard and Tokenless Links

By default, Arcware Cloud generates a direct share link that includes the access token within the URL itself, allowing for instant, one-click access.

* Standard Share Link: [https://share.arcware.cloud/share-d2477d89-0548-4785-9b9f-149071fb4fe3](https://share.ragnarok.arcware.cloud/share-d2477d89-0548-4785-9b9f-149071fb4fe3)

While convenient, this exposes the Share ID in the browser's address bar. For a more secure, authenticated approach, you can share only the base URL and provide the Share ID to your user separately.

* Share Link without the Share ID: [https://share.arcware.cloud](https://share.ragnarok.arcware.cloud/share-d2477d89-0548-4785-9b9f-149071fb4fe3)

#### How to Use the Share Link without the Share ID

When a user navigates directly to the base URL [https://share.arcware.cloud](https://share.ragnarok.arcware.cloud/share-d2477d89-0548-4785-9b9f-149071fb4fe3), the stream will not load automatically. Instead, they will be prompted to authenticate their access.

Step-by-Step Guide:

1. Share the Base URL: Provide your end-user with the clean link: `https://share.arcware.cloud`.
2. Provide the Share ID: Send the user the unique Share ID (e.g., `share-d2477d89-0548-4785-9b9f-149071fb4fe3` through a separate, secure channel. The Share ID can be found and copied from the Share links created on the platform.
3. Authenticate: Upon visiting the link, the user will see a prompt titled "Enter password to access your stream" (see reference image).
4. Unlock: The user must paste the Share ID into the Password field and click the Unlock Stream button to launch the application.

<figure><img src="https://451842398-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxeRHVvCMHTEw8OnxbYIg%2Fuploads%2Fic9QG5x2ntZmvHCuMR23%2Fimage.png?alt=media&amp;token=3df461f3-6b4e-4bc8-a871-8a9d432813ca" alt=""><figcaption></figcaption></figure>

#### Why Use This Method?

* Enhanced Privacy: Because the Share ID is never exposed in the browser's URL bar, it will not be accidentally saved in the user's browser history, bookmarks, or captured in external server referral logs.
* Two-Step Authentication Feel: By distributing the base link and the Share ID via different communication channels (e.g., sending the link via email and the token via an internal messaging app), you ensure that only the intended recipient can access your 3D stream.
* Cleaner Presentation: The base URL looks much more professional, compact, and trustworthy when shared in presentations, client emails, or marketing materials.


---

# 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.arcware.cloud/arcware-cloud-platform/getting-started-with-arcware-cloud/sharing-your-project/share-links-password-protected-access.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.