---
title: "Share skills, not access: how Acme scopes every run"
description: "Skills can travel across the whole company, yet each run only sees what the person running it is already allowed to open."
canonical: "https://acme-jaret.duckdns.org/blog/permission-aware-skills"
site: "Acme"
type: "BlogPosting"
published: "2026-10-08"
updated: "2026-10-08"
authors:
  - "Tom Lindqvist"
  - "Maya Okafor"
  - "Daniel Reyes"
topic: "Governance"
---

# Share skills, not access: how Acme scopes every run

Sharing a skill should never mean sharing access. When a teammate runs a skill you wrote, Acme evaluates every document and tool call against *their* permissions, not yours.

## Three layers of control

- **Data permissions** are inherited from each source system at query time.
- **Tool permissions** decide which actions a skill may take and who can approve them.
- **Publishing controls** let admins review skills before they’re shared company-wide.

## Auditing every run

Each run produces an audit record with the sources retrieved, the tools called and the final output. Security teams can export these records to their SIEM or review them in the admin console.

> Permission-aware by default was the requirement that got us through our security review in a single meeting.
>
> — CISO, Globex