Understanding PMA Keeper, Pro, beta, and complimentary access
Understand how PMA separates a person’s account, organization membership, organization plan, access mode, subscription status, capability entitlements, and measured allowances.
Before you begin
- An active PMA account.
- Access to at least one organization.
- For organization-specific usage, owner, administrator, or billing-manager context.
Interface walkthrough
These annotated interface maps describe the current PMA controls. They do not replace a real record review in your workspace.
Shows the current plan, beta or trial state, measured usage, scheduled changes, and downgrade impact.
Compares Keeper and Pro without offering a live checkout during beta.
Stores the person’s real name separately from organization names so support can locate the correct account.
Step-by-step workflow
Identify the person and organization
Your sign-in account represents you. Each organization represents a collection or operating workspace and owns its own plan state.
Read the access mode
Invited beta, complimentary, trial, commercial, and internal describe why access exists. Keeper, Pro, Pro Beta, and Internal Unlimited describe the effective capability catalogue.
Review measured allowances
Open Plan & Usage to compare current active resources with plan allowances. Database checks—not browser labels—control protected creation paths.
Understand billing status
Beta 85 prepares billing-provider fields but does not collect cards, activate checkout, process payment webhooks, issue invoices, or charge customers.
Expected result
You can distinguish the person, organization, plan, access mode, subscription status, and usage allowances without treating an organization name as the customer’s identity.
Safety boundaries
- Organization ownership is not PMA platform administration.
- Billing-manager status does not grant access to husbandry or health records.
- A hidden Control Vault route is only an extra layer; authorization and MFA remain mandatory.
- Paid billing is not active in Beta 85.
Troubleshooting
The plan name and access mode look different
This is expected. An invited beta organization may use the Pro Beta catalogue while its access mode remains invited beta.
The organization has a silly or generic name
Support searches the account holder’s first name, last name, email, user ID, organization ID, and future provider IDs. The organization name is only one search field.