> ## Documentation Index
> Fetch the complete documentation index at: https://docs.parable.work/llms.txt
> Use this file to discover all available pages before exploring further.

# Parable Pros

> Understand the Parable Pros attribution shown on a Parable and who can change it.

# Parable Pros attribution

## Sources

Docs: [Ponder Primer](/ponder/primer), [Primary responsibility](/ponder/parables/permissions/primary)

Web App: Open a Parable in **Ponder**. The Parable header says whether Parable
Pros built it. Parable administrators can change that fact; Workspace members
see the settled value.

## Story

**Parable Pros** identifies who built a Parable. It replaces the earlier
Purpose menu, which sorted Parables into categories that no longer exist. It
is an attribution only: it does not decide which people may open or edit the
Parable.

Use the value when ownership or support depends on who supplied the Parable.
A Workspace can still use a Parable built by Parable Pros when that Parable is
deployed to the Workspace and the person has the required access.

## Security

Changing Parable Pros attribution does not grant access. Workspace deployment,
current responsibility, route permissions, feature availability, and ordinary
Workspace Protection continue to govern what a person can see and do.

The control has separate view and modify permissions on Admin and Workspace
surfaces. Editing also requires Parable manage access and responsibility for
the Parable. A Workspace can change attribution on a Parable it originated;
a delivered copy retains its upstream owner's attribution. These permissions
do not grant access to Workspace data.

## Stability

Attribution is independent from publication. Publishing a Version does not
change who built the Parable, and changing the attribution does not publish,
withdraw, deploy, or revoke a Version.

For those behaviors, use [Personal vs. Published Versions](/ponder/parables/purposes/personal-vs-published)
and the publishing guides.