Skip to content

An artifact may be a team's, which its members read and its admins may take down, or private, its owner's alone and the default, which only a platform admin may still take down; every row of artifact.list says the gallery tab it is under, and the administrators' table is admin.artifacts.list in the console's Operate area

Decision 953 · accepted · 2026-10-26 · issue #62

Superseded in part

In part by 964.

Issue #62's third slice, as the maintainer decided it on #765 on 2026-10-26: "Team visibility for artifacts: visibility: team:<name>", and, from the gallery's design the same day, a private visibility, "Only you: nobody else can find or open it, not even your team admin. Share it when you are ready", which #62 asked for as the default. It builds on Decisions 948 and 950 and changes one rule of 948, said below.

A team's

team:<name> is for the members of that team, read from the identity provider's groups at every request as a profile's people are, so leaving the team takes it away at the next click.

  • Who publishes one. A member of the team. A platform administrator publishes to any team there is (not_found for one that is not). Anybody else is forbidden, with a sentence that names the teams they are in (you are not in team research, so you cannot publish to its people; you are in team:engineering), which is how the tool, /publish and the desktop dialog list a person's teams at the moment one is refused. A team that does not exist is refused to a non-administrator as one they are not in: whether it exists is not theirs to learn, as for Admin's teams.
  • Its quota is that team's, whatever team the publisher is in first and whatever team a pod session runs under: the bytes are the team's because the artifact is. An owner who moves an artifact to a team moves every stored byte of it to that team's quota, checked as a publish is, and its team becomes that team.
  • Who takes it down. Its owner deletes it; a team administrator of that team, member or not, and a platform administrator take it down (artifact.delete with by: takedown). A team administrator sees their teams' artifacts as a platform administrator sees every one, and takes down no other kind: an organisation's or a profile's artifact stays the platform administrators' to take down, as Decision 948 has it.

Private, the default

private is its owner's and nobody else's: no team member, no team administrator, no profile's people. A link (artifact.share) works on it as on any other, and is how it is shared; whoever a link reached sees it as shared. A publish that names no visibility makes a new one private (artifact.publish, the daemon's artifact.publish, publish_artifact, /publish with a path alone, the desktop's Publish…), and a new version that names none keeps what it was for.

The one exception, and the rule of 948 it changes. Decision 948 let a platform administrator see every artifact. They no longer see another person's private one: not in artifact.list, artifact.get, artifact.open or on the artifacts host. A platform administrator may still take one down, by artifact.delete or admin.artifact.takedown naming its id, audited as any takedown, and admin.artifacts.list names it (its title, owner and size, never its content) so that a takedown has something to name. That is the only thing anybody but its owner and its links' holders may do to one. Not chosen: no takedown at all, which would leave an operator no way to remove a page that breaks the organisation's rules or fills its storage; and a platform administrator who reads it, which is what "not even your team admin" rules out for anybody who is not its owner.

The administrators' table

The console is the administrators' panel (the maintainer, on #765), so a person's own gallery is not where an administrator works through what people published. admin.artifacts.list is every artifact for a platform administrator, private ones included, and for a team administrator their teams' own; admin.artifact.takedown is the takedown from it, destructive and confirmed by its id over MCP. Both are placed on a new Operate area, Published artifacts, a plain table with Take down typed by the id. Reading the table is not audited; the takedown is. Nothing there opens an artifact.

Governs: apps/troupe_plane/lib/troupe/plane/artifacts.ex, apps/troupe_plane/lib/troupe/plane/admin.ex, apps/troupe_gateway/lib/troupe/gateway/artifacts.ex