# Environment-related

In Portainer terms, an *environment* is an instance that you want to manage through Portainer. Environments can be Docker, Docker Swarm, Kubernetes, ACI or a combination. One Portainer Server instance can manage multiple environments.

{% hint style="info" %}
Endpoints were renamed to Environments in version 2.10.
{% endhint %}

{% content-ref url="environments/environments" %}
[environments](https://docs.portainer.io/admin/environments/environments)
{% endcontent-ref %}

{% content-ref url="environments/add" %}
[add](https://docs.portainer.io/admin/environments/add)
{% endcontent-ref %}

Environments can be organized in groups and given tags.

{% content-ref url="environments/groups" %}
[groups](https://docs.portainer.io/admin/environments/groups)
{% endcontent-ref %}

{% content-ref url="environments/tags" %}
[tags](https://docs.portainer.io/admin/environments/tags)
{% endcontent-ref %}

User access can be managed within environments, within environment groups, or using polices to define access for multiple environments at once.

{% content-ref url="environments/environments" %}
[environments](https://docs.portainer.io/admin/environments/environments)
{% endcontent-ref %}

{% content-ref url="environments/groups" %}
[groups](https://docs.portainer.io/admin/environments/groups)
{% endcontent-ref %}

{% content-ref url="environments/policies" %}
[policies](https://docs.portainer.io/admin/environments/policies)
{% endcontent-ref %}

Automatic onboarding scripts can be generated for larger Edge Agent deployments.

{% content-ref url="environments/aeec" %}
[aeec](https://docs.portainer.io/admin/environments/aeec)
{% endcontent-ref %}

Edge Agent environments can be updated (and updates rolled back) directly from within Portainer.

{% content-ref url="environments/update" %}
[update](https://docs.portainer.io/admin/environments/update)
{% endcontent-ref %}