---
metaLinks:
  alternates:
    - https://app.gitbook.com/s/j6QEqM3Sd94bdPsX4HaN/admin/environments
---

# 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.md" %}
[environments.md](environments.md)
{% endcontent-ref %}

{% content-ref url="add/" %}
[add](add/)
{% endcontent-ref %}

Environments can be organized in groups and given tags.

{% content-ref url="groups.md" %}
[groups.md](groups.md)
{% endcontent-ref %}

{% content-ref url="tags.md" %}
[tags.md](tags.md)
{% 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.md" %}
[environments.md](environments.md)
{% endcontent-ref %}

{% content-ref url="groups.md" %}
[groups.md](groups.md)
{% endcontent-ref %}

{% content-ref url="policies/" %}
[policies](policies/)
{% endcontent-ref %}

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

{% content-ref url="aeec.md" %}
[aeec.md](aeec.md)
{% endcontent-ref %}

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

{% content-ref url="update.md" %}
[update.md](update.md)
{% endcontent-ref %}