Abiquo Documentation Cookies Policy

Our Documentation website uses cookies to improve your experience. Please visit our Cookie Policy page for more information about cookies and how we use them.


Abiquo 4.5

Skip to end of metadata
Go to start of metadata




Introduction to resellers

Resellers are platform customers (enterprise tenants) that can have their own customers on the platform. This document describes how to create a reseller administrator, and the different levels of access that you can grant this user. This document is a basic guide only, and customers should always consult the Abiquo Customer Service team for specific guidance and to resolve any doubts.

The platform has two main ways of controlling access: through roles with privileges and through scopes (for administration and resources). This document assumes you have a basic understanding of Abiquo roles and scopes. See Manage Roles and Manage Scopes.

Generally, we recommend that you create a tenant admin role for your specific environment based on the default ENTERPRISE_ADMIN role, and then add scope and additional privileges for reseller administrators.




Reseller administrator scope and flag

A reseller admin will have an administration scope that includes the Abiquo enterprises (tenants) that they will manage, which are their customers.

The reseller admin can manage these tenants and the resources of each individual tenant.

So, for example, you could have a reseller called "Onseller", which is an Abiquo tenant.

The reseller can then manage its customers (also Abiquo tenants) called "Customer", "Customer2" and "Customer3".

  1. Create a scope for your reseller, and select the list of tenants that the reseller will administer and the datacenters that they can work with.
  2. Edit the reseller enterprise and do the following:
    1. Assign the scope as the default
    2. Select the Reseller flag

The platform will mark the Reseller with (R) in the Enterprise list.




Reseller administrator role and privileges

A reseller admin role can have a range of privileges depending on how you will manage resellers and cloud users on the platform. So how the reseller will "manage its customers" will vary, depending on the privileges.

Before you create a reseller admin, we recommend that you first extend the standard ENTERPRISE_ADMIN role to create a basic tenant admin role for your platform. For example, if your tenant admins should be able to manage hard disks, add this privilege, and so on.

Base reseller privileges

The base privileges for reseller admins are these Home view privileges:

  • List enterprises within scope
  • Allow user to switch enterprise

When you assign these privileges to a reseller admin role, the user can view a list of their enterprises (in scope) in the home view and switch from one enterprise to another to manage virtual resources.

When the reseller admin switches to an enterprise, they will be able do all the typical enterprise administration tasks. For example, obtain public IP addresses and create private networks, upload templates, etc.

The reseller admin stays in the enterprise they have switched to until they switch to another. The enterprise does not change when the user logs out and logs in again. 

Users view privileges

The users view privileges determine how the administrator can manage their customers and cloud users.

It is not necessary for your reseller administrators to have these privileges. 

For example, if you manage all cloud user accounts with a centralized system, you may wish to remove the Manage users privilege from the reseller administrator.

User management

If your reseller will be managing users, in addition to the Manage users privilege that is part of the standard tenant admin role, you can assign additional privileges.

To allow the reseller to manage enterprises and users in a single pane of glass, rather than by switching enterprises, assign the privileges to Manage enterprises and Manage users of all enterprises. 

Note that although the privilege is called "Manage users of all enterprises", the administrator can only manage the enterprises listed in their scope.

Shared resource management

If your reseller needs to be able to share resources (VM templates and VApp spec blueprints) to give access to their customers, then your reseller will be able to share templates and specs by assigning (or unassigning) their own scope and the scopes beneath their scope in the hierarchy to templates and specs.

Note that it is possible for enterprises to belong to more than one scope and this means that you can create a scope just to group tenants who will all use the same resources.

Resellers creating tenants and the scope hierarchy

If your reseller is able to create their own tenants, Abiquo will automatically add these to the reseller's scope. 

If the reseller's tenants are part of a scope hierarchy and your reseller does not need to manage their users or enterprises, then you can remove them from your reseller's scope. If you wish to allow your reseller to manage their own scope hierarchy, assign the Manage scopes privilege. This means that the reseller can add their tenants to a scope hierarchy beneath their own scope

Note that each enterprise must have a default scope and you should check that this scope is appropriate (for the enterprise and users) and use the lowest possible scope for the enterprise, because administrators can assign the enterprise scope to users, even if it is higher than or completely different to their own scope!

Reseller Pricing

With the platform's pricing system, you can assign prices to your reseller customers using a pricing model, which has a list of resource prices. Generally, you would enable resellers to view their own pricing model and to create new pricing models for their own customers, based on the prices that you will charge them.

For a full guide to Pricing for the Reseller, see Reseller Pricing in the pricing documentation.




Create an organization hierarchy

Some large customers may require a hierarchy of tenants on the platform (i.e. a tree of multiple enterprises). These tenants can have their own scope hierarchy with multiple levels.

For more information, see Create an organization hierarchy in hybrid cloud.

  • No labels