Feature request: org-level default sharing for published artifacts

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

When Claude Code agents publish artifacts via the Artifact tool, every artifact is private by default. There is no way to change this default — not at the org level, not via the tool's parameters, not in settings.json.

For teams using scheduled Claude Code agents (cron), this means every report published automatically requires a manual share click before teammates can see it. The agent can't share on its own. The org admin can't set a default. The tool itself has no sharing parameter.

Current workflow: agent publishes artifact at 9am Friday → artifact is private → I open claude.ai → click share → select org → repeat for each of 4 reports → teammates can finally view them. This defeats the purpose of automation

Proposed Solution

Two complementary options (either would help; both together would be ideal):

1. Org-level admin setting: In the Claude.ai org admin panel, add a toggle: "Default artifact visibility: Private / Org / Public." All artifacts published under the org would inherit this default.

1. Artifact tool sharing parameter: Add an optional parameter to the Artifact tool call:

sharing: "org" | "public" | "private"

This lets agents and skills explicitly set visibility at publish time, without requiring admin intervention per artifact.

Ideal UX: Admin sets org default to "org." Every artifact published by any agent or user in the org is immediately visible to teammates — no manual share step required.

Alternative Solutions

No viable workaround for automated/cron agents. The share action requires a human clicking in the claude.ai UI — there is no API or CLI flag to share an artifact programmatically.

Manual workaround for interactive sessions: share each artifact immediately after publishing. Doesn't scale to scheduled agents or team workflows.

Other tools (e.g., Notion, Confluence, GitHub Pages) all support org/workspace-level default visibility. This is standard for any collaboration-oriented publishing feature.

Priority

High - Significant impact on productivity

Feature Category

Documentation

Use Case Example

1. We run 4 scheduled Claude Code agents every Friday morning (cron) that publish weekly reports as artifacts: Loop Engineering Radar, Skill Health, What's New in Claude, and a launch page index.

1. Each agent calls the Artifact tool and gets back a claude.ai URL.

1. The launch page artifact links to all 4 reports so teammates can open one bookmark and see everything.

1. Problem: all 4 artifacts are private. Teammates hit an access error when they click the links.

1. With org-level default sharing, step 4 never happens — artifacts publish as visible to the org automatically, and the bookmarked launch page just works for the whole team.

This would save ~5 minutes of manual clicking every Friday and, more importantly, make fully unattended agent-published reports actually usable by a team.

Additional Context

The Artifact tool currently accepts: file_path, title, description, favicon, url (for updates), and capabilities. There is no sharing or visibility parameter.

The claude.ai artifact viewer has a Share button that works fine for interactive use. The gap is programmatic/agent publishing — there's no hook for automation to set visibility.

Relevant: teams using Claude Code for scheduled reporting (via claude -p with bypassPermissions in cron) are the most affected. These agents can't interact with the