---
title: "Jira / Atlassian Cloud Confluence V1 content restrictions API now requires view access for edit access: 2026-10-15 | Harbyn"
description: "Jira / Atlassian Cloud Confluence V1 content restrictions API now requires view access for edit access, announced Oct 15, 2026."
canonical: "https://harbyn.com/changes/atlassian-jira/2026-10-15-confluence-content-restrictions-v1-api-behavior-changes"
last-updated: 2026-10-16
---

# Jira / Atlassian Cloud Confluence V1 content restrictions API now requires view access for edit access

Markdown version of <https://harbyn.com/changes/atlassian-jira/2026-10-15-confluence-content-restrictions-v1-api-behavior-changes>.

Behavior change - Jira / Atlassian Cloud. medium severity. In effect.

The Confluence Cloud REST API V1 content restrictions endpoints will require principals with update (Can edit) restrictions to also have read (Can view) restrictions. Requests to remove only a read restriction when both restrictions are held will be rejected. The rollout is progressive by tenant and in progress.

## Facts

| Fact | Value |
| --- | --- |
| Vendor | [Jira / Atlassian Cloud](https://harbyn.com/vendors/atlassian-jira.md) |
| Kind | Behavior change |
| Severity | medium |
| Status | In effect |
| Announced | Oct 15, 2026 |
| Added to Harbyn | Oct 16, 2026 |
| Lead time | No dated deadline |
| Review | Reviewed by a person, extracted by a model |

## Find it in your code

```sh
npx harbyn scan
```

This change names no identifier the scanner can match line by line, so the scan tells you whether your repository uses Jira / Atlassian Cloud, from its packages and API hosts. Nothing leaves your machine.

## Sources

Where this event comes from: the page we read, when we read it, and the hash of that snapshot.

- <https://developer.atlassian.com/changelog/> (changelog, fetched 2026-10-16 04:38 UTC, sha256 `47b4328bff25ef49356e19f76ca271bb0aed12147ef0885b007a1b01d7c318b1`)

## Related changes

### More from Jira / Atlassian Cloud

- [New IP address ranges in use from January 1, 2027](https://harbyn.com/changes/atlassian-jira/2026-10-16-atlassian-cloud-adds-new-ip-address-ranges.md) (Behavior change, effective Jan 1, 2027)
- [Existing Operations tools move from MCP V1 to MCP V2](https://harbyn.com/changes/atlassian-jira/2026-10-20-existing-operations-tools-move-from-mcp-v1-to-mcp-v2.md) (Behavior change, announced Oct 20, 2026)
- [Removed jira:fullPage and confluence:fullPage modules](https://harbyn.com/changes/atlassian-jira/2026-10-21-removed-jira-fullpage-and-confluence-fullpage-modules.md) (Retirement, effective Sep 30, 2026)
- [Search REST API returns 400 for invalid custom JQL function queries](https://harbyn.com/changes/atlassian-jira/2026-10-08-direct-validation-of-custom-jql-functions-in-search-rest-api.md) (Behavior change, announced Oct 8, 2026)

### Changes at other vendors

- [Amazon Selling Partner API: ORDER\_CHANGE notifications add PreFulfillmentStatusChange for Amazon Autos](https://harbyn.com/changes/amazon-sp-api/2026-10-14-sp-api-updates-new-listings-items-api-ivp-values-in-eu5-jp-and-ca-stores-oct-3.md) (effective Oct 28, 2026)
- [BigCommerce: 301 redirects will apply only to storefront channels](https://harbyn.com/changes/bigcommerce/2026-10-07-301-redirects-now-apply-to-storefront-channels-only.md) (effective Nov 10, 2026)
- [GitHub: Secret scanning audit log business field changes to enterprise slug](https://harbyn.com/changes/github/2026-10-20-updates-to-github-secret-scanning-7.md) (effective Nov 12, 2026)
- [Let's Encrypt: Default certificate lifetime changes to 64 days](https://harbyn.com/changes/letsencrypt/2026-10-07-64-day-certificate-lifetimes-coming-feb-2027.md) (effective Feb 10, 2027)

[All upcoming deadlines](https://harbyn.com/deadlines.md)