[dev-dist]

This pull request significantly restructures and clarifies the documentation for API key permissions on the Chainlink Platform. The changes focus on making the permissions tables more readable, grouping permissions by product and function, and providing clearer descriptions for each permission. Additionally, the update ensures that the documentation accurately reflects how API key permissions relate to user roles.

Key improvements and changes:

Documentation structure and clarity:

• Permissions tables for all products (Platform, CRE, ACE, CRE Connect) are now grouped by functional area (e.g., Policy manager, Core, Operations) with clearer headings and more descriptive column names.
• Each permission entry now includes a concise description of what it allows, making it easier to understand the scope and impact of each permission.
• Role columns in tables now clearly indicate which roles have each permission, improving transparency around access control.

Content accuracy and policy clarification:

• Updated the explanation of how API key permissions relate to user roles: users can only grant permissions that their own roles include, but can retain existing permissions on a key even if their role changes.
• Clarified that API keys operate strictly within the permissions assigned to them, regardless of the creator's role.

General updates:

• Updated the lastModified metadata to reflect the latest changes.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
documentation	Ready	Preview	Oct 27, 2026 7:17pm UTC

[github-actions]

👋 dev-dist, thanks for creating this pull request!

To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team.

Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks!