> For the complete documentation index, see [llms.txt](https://help.sdocs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sdocs.com/sdocs/administration/additional-troubleshooting/creating-a-sharing-rule-for-license-key-template.md).
# Creating a Sharing Rule for License Key Template
The License Key template record is leveraged when a user generates or saves a template. If an object is set to private, users are only allowed to view records they own (or records their colleagues own via Roles). However, every user that needs to generate a document needs to confirm if the org licensing is valid.
For them to accomplish that goal, they will need to have read access to the License Key template. Because the object is set to private, a sharing rule can be created to allow all users (or specific roles/profiles) to access the License Key template.
\
Instructions
To create a sharing rule:
* Navigate to Setup > search for Share Settings
* In the “Manage sharing settings for:” drop down select the **Sdoc Template** object
* Click New under SDoc Template Sharing Rules
* From here you can set up the Sharing Rule, example:
{% hint style="info" %}
Note: Sharing settings for the S-Docs Template object can be set up to allow certain roles, profiles, or for all users.
{% endhint %}
\
Related articles
(There are no related articles listed.)
---
# 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://help.sdocs.com/sdocs/administration/additional-troubleshooting/creating-a-sharing-rule-for-license-key-template.md?ask=&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.