> For the complete documentation index, see [llms.txt](https://gromet.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gromet.gitbook.io/docs/additional-features/team-features.md).

# Team Features

### 🚀 Advanced (Team) Features 

Gromet is designed to scale with your team.

For growing organisations and power users, we’re building a set of **Team-tier** features to supercharge collaboration, reliability, and control:

* ☁️ **Cloud Script Storage**\
  All your scripts can be saved automatically in the cloud, with no local files to manage.
* 👥 **Team Sharing & Roles**\
  Share scripts across your organisation, in just a single click, with permission controls for editors, viewers, and admins.
* 🕓 **Auto-Save & Version History**\
  Keep track of every change with automatic saving and rollback support.
* 📊 **Usage & Access Logs**\
  Track script runs, inputs used, and user access for transparency and compliance.

These features are available in our **Team plan**.

👉 Want early access? [Join the Waitlist](https://workspace-8790.formaloo.co/f1gkf9)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://gromet.gitbook.io/docs/additional-features/team-features.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.