At Habitat, we've been thinking about what apps might need to build rich permission-ed interactions and interoperate. Here's our take ⤵️
Habitat's road to release: 03 ReBAC on spaces
habitat.leaflet.pubAug 21, 2026 at 9:56 PM
Habitat's road to release: 02 sap for syncing permissioned spaces - building [at] habitat
A package to help apps keep permissioned data up-to-date.
Habitat & permission spaces for organizations - building [at] habitat
Our plans for organizational permissions on spaces
calendar pt. 2: spaces, meet cliques! - building [at] habitat
permission-ed data without AppViews
but should apps see our data? - building [at] habitat
thinking small on the protocol
greensky: what does permissioned data feel like? - building [at] habitat
How to handle granular permissions | Authorization Resources | Google for Developers
Granular permissions give users more control over the specific data they share with apps, improving transparency, security, and trust.
Habitat's road to release: 03 ReBAC on spaces - building [at] habitat
Fine-grained permissioning on top of spaces.
Habitat's road to release: 01 simplespace - building [at] habitat
First up: a pre-implementation of permissioned spaces
Permissioned Data: Space Access - Nick's Blog
Stepping outside the shapes series for a deep dive: how space configuration decides which people and which apps get credentials. Here be dragons.
research.latha.org
A permissioned appview for research documents on AT Protocol. True data ownership with optional monetization.
We know picking the right OAuth scopes can be confusing, so we built a tool to help with that. Grab the proper scopes and permission sets from apps across the ecosystem with our new Scope Builder.
Scope Builder - AT Protocol Docs - AT Protocol
atproto.comThe key questions: how much power will apps be given to determine and enforce what data is permissioned? What incentives will apps have to make any data public? So far the protocol has been a forcing function for (adversarial) interop. We need to be intentional about not recreating app silos.
daniel holmgren 🫠
hey we're really working on permissioned data! read the first in a series of posts i'll be doing about our design decisions along the way. this one is about our decision to not do an e2ee system
We know picking the right OAuth scopes can be confusing, so we built a tool to help with that. Grab the proper scopes and permission sets from apps across the ecosystem with our new Scope Builder.
Scope Builder - AT Protocol Docs - AT Protocol
atproto.com
