Update 1.40: Roles, approvals and signing in, Mesa
Updated
Rights can be tailored per role and previewed first, editing is requested instead of refused, and signing in is better protected.
New:
Rights per role, tried out first:
Under Settings › Team › Roles you set per role and collection what may be read, created, edited, deleted or published, and a withdrawn right stays withdrawn. “View as role” shows navigation, lists and editor with exactly those rights, read-only and even before you save.
Asking instead of a dead end:
Anyone who may only read an entry asks for permission with “Request Edit”. Whoever approves picks 1, 7 or 30 days, after which the right ends by itself, and the decision is made right in the entry.
The inbox shows what is new:
A dot marks open requests and any decision on your own request that you have not seen yet. Each request sits on one line with what is asked, by whom and for which collection, can be assigned to someone and carries a due date.
Give rights back in one click:
An activity log line that took rights from an account carries “Give back”. Every account has its own history, and an edit there names only what actually changed.
Invitations that arrive:
If the invitation email does not arrive, you copy a fresh link and pass it on yourself. Whoever has set their password is signed in straight away, and the account no longer shows up wrongly as an expired invitation.
Better protected sign-in:
A space can require the second factor for everyone, eight backup codes help when the code does not arrive, and confirmed devices skip it. A new password ends “Remember me” on all other devices, and repeated failed attempts slow down the account itself, wherever they come from.