> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/publishing/url-link-to-a-published-project.md).

# URL Link to a Published Project

## Description

When you publish a logicnets project you can provide two pieces of information:

1. The published package name, which the system defaults to your project's name in the Designer with spaces and other special characters removed.
2. The startcode, which the system defaults to blank.

If a previously published project exists with either of these, you will be prompted to skip or overwrite the published project. Select ***overwrite*** to continue with publishing, and the system will update the package and URL.

## Accessing the URL

After publishing your application, you can get a copy of the URL to the published application by going to the package overview page and doing the following:

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-0757af2212e8672f7b622e085b7e7189bc2e1b07%2Fff78d2bf-06c0-4bde-8dd2-616879e01fda.png?alt=media)

1. Right-click your mouse on the "arrow" icon next to "Run the application in a new window".
2. Select "copy link address" from the context menu to load the URL into your computer's clipboard.
3. Paste that link in a document, email, or other location.

## Understanding the URL

Typically the link looks something like this: [*https://yourinstance.logicnets.net/yourcompany/logicnets.lns?verb=start\&code=1234567890ABCDEF*](https://yourinstance.logicnets.net/yourcompany/logicnets.lns?verb=start\&code=1234567890ABCDEF)*.* However, if you enter a startcode as part of publishing your application, the system replaces the unique identifier, as follows: [*https://yourinstance.logicnets.net/yourcompany/logicnets.lns?verb=start\&code=YOURSTARTCODE*](https://yourinstance.logicnets.net/yourcompany/logicnets.lns?verb=start\&code=YOURSTARTCODE)*.*

You can enter the same (or different) startcodes each time you publish. If you use the same name and startcode for your published package the system overwrites any prior version of the package with the newer one. Additionally, you can permanently associate a startcode with a project in the Project Settings.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-5ffa0a4990fbbeceb9b10b75e7ae4bb105182cc7%2Ff05d1bf1-fb3f-498e-9bc3-2209c75608c2.jpg?alt=media)

### Friendly URLs

LogicNets-hosted installations benefit from some URL rewrite configuration, so you can use and bookmark a short URL like these examples:

* [*https://yourinstance.logicnets.net/yourcompany/1234567890ABCDEF*](https://yourinstance.logicnets.net/yourcompany/1234567890ABCDEF)
* [*https://yourinstance.logicnets.net/yourcompany/YOURSTARTCODE*](https://yourinstance.logicnets.net/yourcompany/YOURSTARTCODE)

### Runtime URLs

In Release 8.4+ runtime URLs will also reference the startcode in the URL format, for example:

* https\://\[root\_URL]/\[instance/company]/\[**startcode**]?\_session=12345678


---

# 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://community-test.logicnets.com/release-9/platform-documentation/publishing/url-link-to-a-published-project.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.