Jaroslav BenešandClaude Opus 5
9d7fb72bdb
sharing.forget_principal has existed since shares did, documented as the thing that stops a recycled id inheriting somebody's grant, and was called by nobody. Deleting a group left every grant naming it; deleting an account left both the grants to it and the grants of its own work -- that second half is the one nothing else could catch, since their rows cascade and the shares of those rows have nothing to cascade from. Both now run before the delete, while the rows are still findable, and a deleted resource forgets its own. library.share defaulted to False, which meant sharing shipped documented as done and unreachable: the panel only renders for somebody holding it, so out of the box nobody could share anything and nothing said why. It is on. The panel itself was checkboxes inside the resource's *save form*, listing every group and every account on the instance, unpaginated, on every detail page -- and a tick only took effect if you also saved the resource. It is its own routes now: search, one grant per POST, the panel re-rendered from what is stored. Anything already shared stays listed whatever the search says, or removing a grant would mean searching for the name it was given to. Reports join the shareable set and memories still do not: a finished piece of work is the thing somebody most wants to hand over, and a record about a person is not content to pass round. reports.visible became sharing.visible_to, which is the one line its own docstring predicted. Two things fell out: `owned` beside `get`, because sharing grants reading and deleting is the owner's alone; and reading somebody else's report no longer clears their unread dot. Permissions gained the answer to "what can this person actually do?" -- explain() is resolve()'s working shown rather than thrown away, naming admin, the baseline, or the groups that granted each one. That is the simulation the union rule exists to make unnecessary, and until now the only way to get it was to open every group and read the grids by eye. Users and groups are list-plus-detail, and membership is edited from one side: it was on both, and a full-form POST from either overwrote what the other had shown. Read and write are split for notes, memory and skills -- checked on the tool's declared risk, after the gate so it can only narrow, and defaulting on. Quotas are the union rule applied to numbers, with the corner that makes it interesting: zero means "no limit" and wins outright, or a group saying unlimited would count for less than one saying a million. Absent means "no opinion". _narrower folds a group's ceiling with the instance's and is deliberately not min, for the same reason. Five axes, enforced where each is knowable -- before a reply is built, before a second one starts, on an agent reply's clock, before a minute of GPU, and beside the helper cap -- and usage is recorded even for a reply that was stopped or errored, because an endpoint charges either way. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
94 lines
3.4 KiB
HTML
94 lines
3.4 KiB
HTML
{% extends "admin/_layout.html" %}
|
|
{% from "_macros.html" import icon %}
|
|
{% set section = "groups" %}
|
|
|
|
{% block title %}Groups & permissions - {{ brand.name }}{% endblock %}
|
|
{% block heading %}Groups & permissions{% endblock %}
|
|
|
|
{% block admin_content %}
|
|
<p class="admin-lede">
|
|
Permissions are a <strong>union</strong>: everyone starts with the baseline
|
|
below, and each group they belong to can add more. A group never takes
|
|
something away, so being in a second group can only widen what someone can do —
|
|
which is what keeps “why can this person not do X?” answerable without
|
|
simulating every group they are in. Administrators bypass all of it.
|
|
</p>
|
|
|
|
{% if saved %}
|
|
<div class="alert alert--success">{{ icon("check", "icon--sm") }} <span>{{ saved }}</span></div>
|
|
{% endif %}
|
|
|
|
<section class="card">
|
|
<h2 class="card__title">Baseline permissions</h2>
|
|
<p class="card__lede">
|
|
What every signed-in user can do before any group is considered. Turn
|
|
something off here and grant it through a group to make it opt-in.
|
|
</p>
|
|
|
|
<form method="post" action="/admin/permissions/defaults">
|
|
{% for section_name, defs in permission_groups.items() %}
|
|
<div class="field">
|
|
<span class="field__label">{{ section_name }}</span>
|
|
{% for definition in defs %}
|
|
<label class="checkbox perm-row">
|
|
<input type="checkbox" name="permission" value="{{ definition.key }}"
|
|
{{ 'checked' if baseline[definition.key] }}>
|
|
<span>
|
|
<strong>{{ definition.label }}</strong>
|
|
<span class="perm-row__desc">{{ definition.description }}</span>
|
|
</span>
|
|
</label>
|
|
{% endfor %}
|
|
</div>
|
|
{% endfor %}
|
|
<div class="btn-row"><button class="btn btn--primary" type="submit">Save baseline</button></div>
|
|
</form>
|
|
</section>
|
|
|
|
<h2 class="admin-section-title">
|
|
Groups <span class="badge">{{ groups|length }}</span>
|
|
</h2>
|
|
|
|
{#
|
|
Rows, not a form each. The old page rendered every group's full permission
|
|
grid, every member and every model on one screen -- fine for two groups and
|
|
unreadable at ten, which is the list-plus-detail rule the model admin already
|
|
follows.
|
|
#}
|
|
<div class="model-rows">
|
|
{% for group in groups %}
|
|
<a class="model-row" href="/admin/groups/{{ group.id }}">
|
|
<div class="model-row__main">
|
|
<span class="model-row__name">{{ group.name }}</span>
|
|
{% if group.description %}
|
|
<span class="model-row__id">{{ group.description }}</span>
|
|
{% endif %}
|
|
</div>
|
|
<div class="model-row__meta">
|
|
<span class="badge">{{ group.users | length }} member{{ '' if group.users|length == 1 else 's' }}</span>
|
|
{% if granted[group.id] %}
|
|
<span class="badge badge--leaf">+{{ granted[group.id] }} permission{{ '' if granted[group.id] == 1 else 's' }}</span>
|
|
{% endif %}
|
|
{% if group.limits_json %}<span class="badge">quotas</span>{% endif %}
|
|
</div>
|
|
</a>
|
|
{% else %}
|
|
<div class="empty" style="padding: var(--sp-8) 0">
|
|
<p class="empty__text">
|
|
No groups yet. Everybody gets the baseline above and nothing more.
|
|
</p>
|
|
</div>
|
|
{% endfor %}
|
|
</div>
|
|
|
|
<section class="card" style="margin-top: var(--sp-6)">
|
|
<form method="post" action="/admin/groups" class="btn-row">
|
|
<input class="input" name="name" placeholder="New group name" required
|
|
aria-label="New group name">
|
|
<button class="btn btn--primary" type="submit">
|
|
{{ icon("plus", "icon--sm") }} Create group
|
|
</button>
|
|
</form>
|
|
</section>
|
|
{% endblock %}
|