Provision blueprint
By choosing the right provision blueprint, you ensure your product is set up to trigger the correct automated workflows.
Provision provider
You can let Upmind pick the best provision provider automatically, select a specific one, or set up advanced dynamic rules for more control. This flexibility means you can easily scale, switch, or customise how and where your products are provisioned.
Configuration mode
The configuration mode lets you decide how Upmind matches your product to a provider setup, either by using your brand’s default settings or by matching specific attributes like location or features.
Provider configuration
The provider configuration is where you choose the exact settings or credentials for your selected provider, such as the brand’s default setup or a custom configuration. This step makes sure that Upmind connects to your provider with the right details.
Setup functions
Setup functions define what action Upmind takes when a product is activated, usually creating a new account or service. You can choose from standard actions like create or customise what happens during setup, so your customers get instant access to their new service without delays.
Order setup fields
Order setup fields control when and how customers provide the information needed for provisioning. You can decide if details are collected before payment, after payment, or optionally at either stage, giving you flexibility to match your sales process and customer experience.
- Inherit from category (None): Uses the default timing set by the product category.
- None (Before payment): Customers must enter all required info during checkout, before they pay.
- Optional: Customers can provide some info at checkout and confirm or complete details after payment.
- Hidden (After payment): Customers pay first, then provide the info needed for provisioning.
Provision fields
Provision fields are the specific data points, like package name, domain, or server location, that Upmind maps to the provider during setup. These fields make sure the right information is sent for each order, making automated provisioning accurate and customised to each product or service. These features collectively provide control, flexibility, and limitations for resellers within Upmind.
| Field Name | Description |
|---|---|
| Package Identifier | This is a unique identifier for a hosting package (the package name). It helps Upmind distinguish between different hosting plans. |
| Reseller Privileges | Defines the permissions and limits granted to a reseller account, such as the ability to create, manage, and allocate resources to user accounts, set quotas, and access certain management features within the hosting platform. |
| Account Owns Itself | When enabled, this means that an account can manage itself. Without this, only the root admin can manage the account. |
| Reseller ACL Name | ACL stands for Access Control List. This setting specifies the name of the ACL list associated with a reseller. ACLs control what actions a user or reseller can perform. |
| Reseller Account Limit | This sets a limit on the number of accounts a reseller can create. It helps in controlling the reseller’s business scale. |
| Reseller Disk Space Limit (MB) | Specifies the maximum disk space that a reseller can allocate across all their accounts. It prevents a reseller from overcommitting resources. |
| Reseller Diskspace Overselling | If enabled, this allows resellers to allocate more disk space than physically available, relying on the assumption that not all users will use their full allocation. |
| Reseller Bandwidth Limit (MB) | Similar to disk space, this sets the maximum bandwidth that a reseller can allocate among their accounts. |
| Reseller Bandwidth Overselling | When enabled, this allows resellers to oversell bandwidth, assuming that not all users will use their full allocated bandwidth. |