> For the complete documentation index, see [llms.txt](https://docs.storylane.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.storylane.io/changelog/updates-for-march-2023/march-29-2023.md).

# March 29, 2023

### New Features

The following set of releases are geared towards making Storylane completely self-serve and are focused on the demo URLs customization,

* **Company Logos:** You can now upload your company logo by yourself in the settings section. This will automatically superimpose the logo on all your demos and help you maintain your own branding on your demos.<br>
* **Favicon:** Remember the small icon accompanying the page you're on in your browser tabs? You can now update these icons, called as favicons, as well with your company logo, again to be automatically applied to all your demos.<br>
* **Subdomain:** You can now also update the subdomain of your demo URLs to your organization name (or anything else) by simply adding the new name in the Storylane subdomain field, inside settings. \
  \
  Please remember this is not available in free plans and if you're on a growth plan, you can update your entire demo URL (not just the subdomain) to carry just your company's name.

And below is how, you can go about making the above changes,

{% embed url="<https://app.storylane.io/share/mus9pbxng4dj>" %}


---

# 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.storylane.io/changelog/updates-for-march-2023/march-29-2023.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.