Who Is It For?

MIDDAG Account serves five distinct personas. Each interacts with the system differently, through different interfaces, with different goals. Understanding which persona you are helps you find the right documentation quickly.

WP Admin (Adopting Company)

You installed MIDDAG Account on your own WordPress site.

You run a business that sells products or services to other companies. You chose MIDDAG Account to centralize your B2B customer lifecycle instead of duct-taping multiple plugins together or paying for a SaaS billing platform.

What you do:

• Install, configure, and maintain the plugin on your WordPress site
• Set up your business entity, entitlement classes, and policies
• Connect your Stripe account, WooCommerce products, and other integrations
• Create your first organization and run through the purchase-to-entitlement flow

What you need from the docs: Getting Started guides, configuration walkthroughs, and recipes that show you how to set up common scenarios without writing code.

Start here: Requirements and Installation.

Internal Admin (Backoffice Operator)

You manage day-to-day customer operations through the WordPress admin panel.

You might work in operations, finance, sales support, or customer success. You spend time in the MIDDAG Account admin interface handling the daily work of managing B2B relationships: processing quotes, tracking entitlements, generating invoices, monitoring service delivery.

What you do:

• Look up any customer's complete picture in seconds: entitlements, invoices, licenses, services
• Process the pipeline from quote to payment to entitlement
• Manage organization lifecycles: onboarding, verification, suspension, recovery
• Generate financial documents: invoices, tax invoices (NFSe), payment reconciliation
• Monitor service delivery, review service requests, track SLA compliance

What you need from the docs: The Admin Guide and Operating Model sections, which explain what each screen does and how the daily workflows fit together.

Start here: Key Concepts and How It Works.

End Customer (Portal User)

You are the owner or admin of an organization that buys products or services.

You log into the customer portal to see what your company has purchased, accept quotes, manage licenses, download software, and handle billing. You want a self-service experience where you can find answers without calling anyone.

What you do:

• View all your entitlements in one place: licenses, environments, services, subscriptions
• Accept quotes and complete payments
• Download software and documents you are entitled to
• Create service requests linked to specific entitlements
• Manage your team: invite collaborators, assign permissions, remove former members

What you need from the docs: Portal-facing documentation is outside the scope of docs-site (which targets WP Admins). Your experience is shaped by the portal your admin has configured.

Collaborator (Team Member)

You were invited to an organization by its owner or admin.

You access the customer portal with permissions scoped to your role. A finance team member sees invoices and orders. An IT member sees licenses and downloads. A guest might only see shared documents. You see exactly what your scopes allow and nothing more.

What you do:

• Access the specific data your role requires: invoices, licenses, tickets, documents
• Perform actions within your assigned scopes: activate a license, create a service request, download a file
• Stay within clear boundaries: the system tells you what you can and cannot do

What you need from the docs: Like End Customers, your experience is portal-facing. WP Admins configure what scopes are available and how collaborators are invited.

Developer (API Integrator)

You build on top of MIDDAG Account using its REST API, hooks, or filters.

You might be building a custom customer portal, integrating MIDDAG Account with an external system, or extending its behavior with custom provisioning logic. You need clear API documentation, hook catalogs, and stable contracts.

What you do:

• Build customer-facing portals that consume the REST API v1
• Integrate external systems via webhooks and API calls
• Extend business logic through WordPress hooks and filters
• Build custom provisioning, notifications, or reporting

What you need from the docs: The Reference section, which covers architecture, REST API endpoints, hooks, webhooks, data model, and extension points.

Start here: Reference (developer documentation).

Quick reference

Persona	Interface	Docs section
WP Admin (Adopting Company)	WordPress admin, docs	Getting Started, Recipes
Internal Admin (Backoffice)	WordPress admin (MIDDAG Account UI)	Admin Guide, Operating Model
End Customer	Customer portal	Portal docs (out of scope)
Collaborator	Customer portal (scoped)	Portal docs (out of scope)
Developer	REST API, hooks, code	Reference

A note on audience

Most of docs-site is written for the WP Admin and Internal Admin personas. These are the people who install, configure, and operate MIDDAG Account day to day. Content outside of the Reference section assumes comfort with WordPress admin but does not assume knowledge of programming, APIs, or software architecture.

The Reference section is written for Developers and assumes technical proficiency with REST APIs, PHP, and JavaScript.