Skip to content
NewSee how fast an edit goes live on this site
Halftone

Product

Introducing role-based access, part 3

What it does, who it is for, and how to try it today.

Hana Pike
Published 2 min read

Version history keeps every change, who made it, and why. Restoring an older version is a single action, and it never deletes the newer ones. This post covers what we changed, why, and what it means for you.

#What's next

Admins can scope access by project, so guest contributors see only what they are working on. Nothing about the experience changes for everyone else.

This is available today on every plan. We will keep shipping small improvements every week, and we read every piece of feedback that comes in.

#What we would do differently

Every change now shows its status in plain language. You see when it is saving, when it is publishing, and the moment it is live, with a link to check for yourself.

We designed for the person who has five minutes between meetings. The common path takes two clicks, and everything else stays out of the way until you ask for it.

“A cache key must include everything that can change the output, and nothing that cannot.”
Dee Marsh

#What changed

Teams told us the same thing in different words: the work was done, but getting it live took longer than doing it. This release is about closing that gap.

Preview links work for anyone you send them to, even people without an account. They expire on their own, so nobody has to remember to clean them up.

Version history keeps every change, who made it, and why. Restoring an older version is a single action, and it never deletes the newer ones.

Diagram of the request path before and after the change
Figure: the request path, before and after.

#The details

Admins can scope access by project, so guest contributors see only what they are working on. Nothing about the experience changes for everyone else.

This is available today on every plan. We will keep shipping small improvements every week, and we read every piece of feedback that comes in.

#What we measured

Every change now shows its status in plain language. You see when it is saving, when it is publishing, and the moment it is live, with a link to check for yourself.

We designed for the person who has five minutes between meetings. The common path takes two clicks, and everything else stays out of the way until you ask for it.

Teams told us the same thing in different words: the work was done, but getting it live took longer than doing it. This release is about closing that gap.

#Where we started

Preview links work for anyone you send them to, even people without an account. They expire on their own, so nobody has to remember to clean them up.

Version history keeps every change, who made it, and why. Restoring an older version is a single action, and it never deletes the newer ones.

Admins can scope access by project, so guest contributors see only what they are working on. Nothing about the experience changes for everyone else.

Diagram of the request path before and after the change
Figure: the request path, before and after.
Nowavailable:usagedashboardsHALFTONE / JOURNAL

Product6 min

Now available: usage dashboards

Built for the person with five minutes between meetings.

Lu Brandt
Introducingthe commandbarHALFTONE / JOURNAL

Product10 min

Introducing the command bar

The thinking behind the release and what comes next.

Ivo Santos
Introducingrole-basedaccessHALFTONE / JOURNAL

Product5 min

Introducing role-based access

Less waiting between done and live, for every team.

Eli Tanaka