# Permissions

<figure><img src="https://1499735372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCU5VgN3YVTfigwSnbdbk%2Fuploads%2F0o06IlIhWy9U1K9D6vbo%2FWorkspace%20-%20Access.png?alt=media&#x26;token=c3a45092-d1c8-4d0b-9eaf-60127f0ca91e" alt=""><figcaption><p>Limit access to your workspace</p></figcaption></figure>

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&#x20;

### Access global permissions

In the Jira top navigation:&#x20;

* Select ⚙ > **System**.
* Click **Global Permissions**.

### Released administrator&#x20;

Released administrators are able to configure and adjust global settings in Released, such as [Product Hub details](general), [internal domains](internal-domains), or [user verification](user-verification).&#x20;

{% 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.&#x20;

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.&#x20;

### Open

Everyone with access to the Jira site can view the workspace and edit the changelog.&#x20;

### **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.&#x20;

{% 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 %}
