> For the complete documentation index, see [llms.txt](https://docs.violetlabs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.violetlabs.com/features/scripts/faq-and-examples.md).

# FAQ and Examples

## FAQ

<details>

<summary>Can anyone access a script I've created?</summary>

Currently, all Scripts are accessible to all users, as long as they have permission to all the data within them.

If a script contains a Violet Variable linked to data that a user does not have access to, they will also **not have access to that script.**&#x20;

We are working to implement a more tailored and comprehensive permissions model for Scripts - stay tuned!

</details>

<details>

<summary>Why are my runs slow?</summary>

Running a script after a period of inactivity may take more time than usual. If your Scripts feature is starting to be heavily used by your team and seems to be running slower than expected, please reach out to us.

</details>

## Examples

Check out more example scripts:

* [Calculate a satellite’s orbital period based on input altitude, and write the output to a Violet parameter](https://www.loom.com/share/048ef85184d246188120b7163a6270aa)
* [Vary aircraft parameters and observe the effect on calculated mission duration](https://www.loom.com/share/39c10e9ec9124747bdacd8e0597f88f5?sid=57f6f2eb-bfce-4330-8123-54d2272e59d1)
* [Calculate satellite link budget, vary component technical specifications and observe the effect on SNR](https://www.loom.com/share/ad9c107ffc8e4ee2a3b76081fdd31bdc?sid=33e0078a-c031-4841-acb5-eefa8f132c31)


---

# 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.violetlabs.com/features/scripts/faq-and-examples.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.