Skip to content

Add Cloud OAuth consent changelog #3079

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
atharva-appwrite wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add Cloud OAuth consent changelog #3079

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions src/routes/changelog/(entries)/2026-07-03.markdoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
---
layout: changelog
title: Appwrite Cloud OAuth consent now supports resource-bound authorization
date: 2026-07-03
---
Comment on lines +1 to +5

@greptile-apps greptile-apps Bot Jul 3, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Missing cover image in frontmatter

Almost every changelog entry that describes a UI or product change includes a cover field (e.g. cover: /images/changelog/2025-07-03.avif) and a corresponding image file under src/images/changelog/. This entry has no cover field and no matching image exists in the repo. Because this particular change is a visual consent-screen redesign, a cover screenshot would be especially helpful for readers — without it the entry will render without a hero image while all surrounding entries have one.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!


Appwrite Cloud's OAuth consent flow now makes requested access easier to review before authorizing a connected app. The consent screen shows a read-only permission summary, grouping requested scopes into clear access rows so users can see what the app is asking for without accidentally changing the requested permission set.

For apps using Rich Authorization Requests, Appwrite Cloud now also lets users bind requested access to specific projects and organizations through `authorization_details`-based resource selection. Users can choose whether project and organization access applies broadly or only to selected resources, and Appwrite sends the resulting resource binding back when the request is approved.

This gives connected apps a clearer consent experience while keeping authorization precise: scopes describe the requested privileges, and `authorization_details` controls which Appwrite Cloud projects or organizations those privileges are bound to.

@greptile-apps greptile-apps Bot Jul 3, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 No follow-up link for readers

Most changelog entries close with an {% arrow_link %} component pointing to a blog post, docs page, or Discord discussion so readers can explore further. This entry ends without one. If there is a related docs page, blog post, or console deep-link for the new consent flow, adding an {% arrow_link %} would match the existing pattern and give readers a clear next step.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

Loading