For WordPress developers

Build your product. Make access intentional.

AAM grew with developers who needed deeper integrations than a settings screen could offer. The AAM PHP Framework gives your code a consistent way to store access controls and resolve decisions.

PHP FrameworkAAM::api()Deep integration
ACCESS / DEVELOPERS
01
Your application logic

A feature needs a precise decision about a user, role or visitor.

02
AAM PHP Framework

Services, access levels and resources resolve the relevant controls.

03
Your implementation

Use the decision in a workflow you can explain and maintain.

A clearer decision at every step

Built for your work

Go deeper than a role check.

The framework is the programmable layer for managing and resolving access. Start with the quick start, then explore the service references for the resources your project uses.

01 / CONSISTENCY

One access model

Work with roles, users, visitors and default access through a framework built around WordPress resource relationships.

02 / INTEGRATION

Services in code

Manage controls for URLs, content, API routes and other resources through the documented AAM service API.

03 / CLARITY

Decisions you can trace

Ask what access actually resolves to, then make the right choice in your own business logic.

For the builders

Start with a real API.

The AAM PHP Framework exposes services for managing and resolving access controls. The AAM plugin handles WordPress restrictions; the framework gives your code a consistent way to work with access decisions.

Explore the PHP Framework →
// The URL service, ready for the current access level
$urls = AAM::api()->urls();

// Ask for a decision in your own workflow
if ($urls->is_denied($_SERVER['REQUEST_URI'])) 

The next step

Start building with AAM.

The PHP Framework reference is the shortest path from an access requirement to a working integration.

Explore developer API →