BryanNetPlans: time, usage, limits and validity
Prerequisites and authority
Use an individual staff account with the action permission and required organization module/license. Viewing a menu does not establish permission to mutate records.
Define an access plan
Open Plans and choose the supported create/edit action. A plan describes the commercial access offer; a subscription records a customer's entitlement to that offer.
Set name, price, time or usage type, validity, speed and concurrency. For a usage plan, include its data allowance as well as validity. The quota does not remove the time limit. Explain both clearly to customers.
| Field | Operator interpretation |
|---|---|
| Price | Amount charged for the offer |
| Validity | Access duration or defined validity period |
| Speed | Configured access rate, subject to upstream capacity |
| Concurrent devices | Maximum simultaneous connections |
| Data quota | Allowance for a usage subscription |
Device history is not a lifetime replacement allowance. Admission enforces the plan's simultaneous-device limit across managed routers, including unexpired pending reservations. Replacing a registered device does not grant extra concurrent sessions.
The API represents a fixed duration using a positive duration_days value; fractional days represent shorter periods. For example, one hour is 1/24 of a day, not a zero-day plan. data_quota_bytes is a positive integer byte count and speed_limit_mbps is a positive integer. Confirm the units shown by the administrator form before entering converted values. Create a test subscription and inspect its dates/profile before selling the plan; an API field representation is not a substitute for checking the resulting offer.
When editing a plan, verify how existing subscriptions are affected rather than promising either immutable snapshots or immediate updates without evidence. Keep a record of material commercial changes and use Time-based versus usage-based plans for customer-facing explanations.
Related guides
Related guides: Staff accounts, roles and permissions, Administrative session and audit investigation, System operations and task controls, Roles and permission matrix.