Reseller groups let your company apply a consistent commercial and API policy to a set of reseller accounts. Define the group around a real offer, then review which settings are inherited and which account-specific exceptions are permitted.
IN THIS ARTICLE
01 Plan the group
Identify the TLD catalogue, pricing rules, funding arrangement, API access, DNS allowances and support responsibilities that belong together. A group label alone does not activate every service or grant access to another reseller's customers.
- Open Domain Reseller > Reseller groups and create or edit the intended group.
- Configure its published offer and permitted functions through the relevant pricing, permissions and reseller settings pages.
- Review the settings scope before saving. The interface distinguishes Global, Reseller group and One reseller.
- Apply only the overrides needed for that group, leaving appropriate values inherited.
- Assign a test reseller and inspect the effective profile, permissions, prices and limits.
Why can two resellers in different groups see different controls?
API scopes, account state, group policy and service switches work together. A broad API key cannot operate a service that the platform has disabled, and a group permission does not transfer ownership of resources.
Use the reseller portal or permitted profile API to review the resulting account experience. Verify a read request and one controlled workflow, then test an action the group should not allow.
02 Manage exceptions explicitly
Use a reseller-specific override when one account needs a justified difference. Record the reason and review it when the account changes group. Avoid creating many nearly identical groups solely to hold undocumented one-off exceptions.
For automatic group assignment based on qualifying activity, inspect the actual conditions and resulting group before advertising a benefit. Do not freeze a domain-count threshold in your documentation unless it is part of the current offer.
03 Change groups without surprising resellers
Preview affected prices, TLD availability, funding and API permissions before moving established accounts. Existing orders and invoices need their own review; a catalogue change is not necessarily retroactive repricing.
Communicate changes to the current offer and give resellers enough information to update their downstream systems. After saving, verify the effective account state again rather than relying only on the group editor's values.