Released integrates tightly with your project permission in Jira, removing the burden of setting up additional roles or access controls to draft and publish release notes.
## Global permissions
### Access global permissions
In the Jira top navigation:
* Select ⚙ > **System**.
* Click **Global Permissions**.
### Released administrator
Released administrators are able to configure and adjust global settings in Released, such as [Product Hub details](/guide/product/administration/general.md), [internal domains](/guide/product/administration/trusted-domains.md), or [user verification](/guide/product/administration/user-verification.md).
{% hint style="warning" %}
By default, all Jira users are granted the **Released: Administrator** permission. To restrict access, you can modify permission in the Global Permissions settings.
Read more about Global Permissions in the [Jira documentation](https://support.atlassian.com/jira-cloud-administration/docs/manage-global-permissions/).
{% endhint %}
## Workspace permissions
A workspace currently has two access types.
### Open
Everyone with access to the Jira site can view the workspace and edit the changelog.
### **Restricted**
To access a portal, users will require **Edit issue** permission in one of the linked projects. See the [Jira documentation](https://confluence.atlassian.com/adminjiraserver/managing-project-permissions-938847145.html) to learn more about Jira project permissions.
{% hint style="warning" %}
If multiple projects are linked to a portal and the user only has access to one of them, they will only be able to view issues from projects they have access within the portal.
{% endhint %}
---
# Agent Instructions: 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:
```
GET https://docs.released.so/guide/product/administration/permissions.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.