> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/arm-1/arm-features/environment-provisioning/sharing-a-template.md).

# Sharing a Template

### Environment Provisioning: Template Sharing for Subusers (Custom Admin Configuration)

#### Overview

The Environment Provisioning module now supports enhanced template sharing capabilities, enabling better collaboration and reducing dependency on Admin users.

This update allows Subusers to share templates they create, while maintaining control and governance over shared resources.

***

#### What’s New

**🔹 Subuser Template Sharing**

Subusers can now share **only the templates they own**, enabling faster collaboration without requiring Admin intervention.

**🔹 Admin Capabilities (Unchanged)**

Admins continue to have full control and can share **any template**, regardless of ownership.

***

#### How It Works

**👤 For Subusers**

* You can **share templates that you have created**.
* The **Share option will be enabled** only for your own templates.
* For templates created by other users:
  * The Share option will be **disabled or hidden**.

**👑 For Admin Users**

* You can **share any template** in the system.
* No changes have been made to existing Admin functionality.

***

#### UI Behavior

| Scenario                          | Share Option Visibility |
| --------------------------------- | ----------------------- |
| Subuser viewing own template      | Enabled                 |
| Subuser viewing others' templates | Disabled/Hidden         |
| Admin viewing any template        | Enabled                 |


---

# 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://knowledgebase.autorabit.com/product-guides/arm-1/arm-features/environment-provisioning/sharing-a-template.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.