Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents

...

Each user has a role with a group of privileges that allow access to different cloud features. To change user access to features, modify the user role and add or remove privileges. 

See Create a user roleManage roles

Define which cloud locations users can deploy in

You can allow each tenant to access a set of cloud locations (including providers, public cloud regions, and datacenters).  All the users of a tenant can deploy in the allowed locations.

...

Administrators with the appropriate privileges can manage the cloud locations listed in their scope, assuming that their tenant also has access to these locations.

See Create a scopeManage scopes

Restrict a user to a set of virtual datacenters

...

Administrators can create restricted virtual appliances, which means that users cannot access the VMs without the appropriate privileges. However, the VMs are still running in the user's tenant, which enables you to bill the tenant for the virtual resources.

See https://abiquo.atlassian.net/wiki/spaces/doc/pages/367394986/Move+virtual+machines#Move-a-VM-to-a-restricted-virtual-appliance

Require users to get approval for all VM launch, deploy, and reconfigure actions

You can create a workflow connector to use the Workflow feature to hold deploy actions (deploy, undeploy, reconfigure) until an external system approves the changes. 

See Abiquo workflow feature/wiki/spaces/doctest/pages/311374701