Security, Governance & Administration - Environment Management

Environment Management is a key part of Security, Governance, and Administration in Microsoft Power Platform. It helps administrators organize, secure, monitor, and control the spaces where apps, flows, chatbots, connections, and business data are created and managed.

Microsoft Learn defines a Power Platform environment as a space to store, manage, and share an organization’s business data, apps, chatbots, and flows. It also explains that an environment works as a container to separate apps that may have different roles, security requirements, or target audiences. [1](https://learn.microsoft.com/en-us/power-platform/admin/environments-overview)

Environment Management is important because Power Platform solutions are often used by many departments, teams, and users. Without proper environment planning, apps and flows may be created in the wrong place, users may receive more access than required, test solutions may mix with production solutions, and administrators may lose visibility over business-critical resources.

Environment Management means planning, creating, securing, monitoring, and governing Power Platform environments so that apps, flows, chatbots, data, and resources are managed safely and efficiently.

What is a Power Platform Environment?

A Power Platform environment is a container where Power Platform resources are stored and managed. These resources can include business data, Power Apps apps, Power Automate flows, Copilot Studio chatbots, Power Pages sites, connections, gateways, and Dataverse databases.

Microsoft Learn explains that organizations can use environments in different ways. For example, an organization may use a single environment, create separate environments for test and production versions, create environments for different teams or departments, or create environments for different global branches. [1](https://learn.microsoft.com/en-us/power-platform/admin/environments-overview)

Environment Concept	Simple Meaning	Example
Environment	A container for business data, apps, chatbots, and flows	Development Environment
Resources	Items created or managed inside an environment	Power Apps app, Power Automate flow, Dataverse database
Separation	Keeping solutions apart based on purpose, role, security, or audience	Separate Test and Production environments
Administration	Managing users, roles, settings, policies, monitoring, and governance	Environment Admin managing access

The table summarizes Microsoft Learn’s explanation that environments store and manage data, apps, chatbots, and flows, and also separate apps based on roles, security requirements, or target audiences. [1](https://learn.microsoft.com/en-us/power-platform/admin/environments-overview)

Why Environment Management is Important

Environment Management is important because Power Platform is used to build business solutions that may contain sensitive data, automated processes, user permissions, and connections to other systems. If environments are not managed properly, it becomes difficult to control access, maintain governance, and separate development from production.

Microsoft Learn states that environments can be used to separate apps that have different roles, security requirements, or target audiences. It also gives examples of environments for test and production versions, teams, departments, and global branches. [1](https://learn.microsoft.com/en-us/power-platform/admin/environments-overview)

Environment Management helps organizations:

Separate development, testing, and production solutions.
Control who can create apps, flows, chatbots, and resources.
Protect business data and reduce unnecessary access.
Apply governance rules for different teams or departments.
Monitor apps and flows more effectively.
Manage deployment and lifecycle of solutions.
Support security, compliance, and administration requirements.

Environment Scope

Environment scope means the boundary within which an environment exists and operates. Microsoft Learn explains that each environment is created under a Microsoft Entra tenant, and resources in that environment can only be accessed by users within that tenant. [1](https://learn.microsoft.com/en-us/power-platform/admin/environments-overview)

Microsoft Learn also explains that an environment is bound to a geographic location. When an app is created in an environment, that app is routed only to datacenters in that macro region geography. Items such as chatbots, connections, gateways, and Power Automate flows are also bound to the environment’s location. [1](https://learn.microsoft.com/en-us/power-platform/admin/environments-overview)

Scope Area	Explanation
Tenant Scope	Each environment is created under a Microsoft Entra tenant.
User Access Scope	Environment resources can only be accessed by users within that tenant.
Geographic Scope	An environment is bound to a geographic location.
Resource Scope	Apps, chatbots, connections, gateways, and flows are bound to the environment’s location.

The table summarizes Microsoft Learn’s description of environment tenant scope, user access scope, geographic location, and resource binding. [1](https://learn.microsoft.com/en-us/power-platform/admin/environments-overview)

Environment as a Security Boundary

An environment acts as a logical security and management boundary. Different environments can be used to separate resources by business purpose, target users, or security needs.

Microsoft Learn explains that environments serve as containers to separate apps that might have different roles, security requirements, or target audiences. [1](https://learn.microsoft.com/en-us/power-platform/admin/environments-overview)

For example, an organization may use:

A development environment for makers and developers.
A test environment for validation and user testing.
A production environment for live business users.
A department-specific environment for HR, Finance, or Operations solutions.

The examples above are educational examples based on Microsoft Learn’s statement that environments can separate apps by role, security requirement, target audience, teams, departments, or global branches. [1](https://learn.microsoft.com/en-us/power-platform/admin/environments-overview)

Environment and Dataverse

Microsoft Learn explains that every environment can have zero or one Microsoft Dataverse database. Dataverse provides storage for apps and chatbots. Whether a database can be created depends on licensing and permissions within that environment. [1](https://learn.microsoft.com/en-us/power-platform/admin/environments-overview)

This is important because an environment with Dataverse may require additional planning for tables, data access, security roles, app permissions, and governance.

Microsoft Learn explains that Microsoft Dataverse uses a role-based security model to control access to a database and its resources in an environment. Security roles are used to configure access to all resources in an environment or to specific apps and data in the environment. [2](https://learn.microsoft.com/en-us/power-platform/admin/database-security)

Dataverse Point	Meaning
Zero or one Dataverse database	Each environment can have no Dataverse database or one Dataverse database.
Storage	Dataverse provides storage for apps and chatbots.
License and permissions	Database creation depends on license and permissions.
Role-based security	Security roles control access to Dataverse database resources.

These points are based on Microsoft Learn’s environment overview and Dataverse role-based security documentation. [1](https://learn.microsoft.com/en-us/power-platform/admin/environments-overview)[2](https://learn.microsoft.com/en-us/power-platform/admin/database-security)

Environment Resource Boundary

Resources inside an environment are connected to that environment. Microsoft Learn explains that when an app is created in an environment, the app is only permitted to connect to data sources that are also deployed in that same environment, including connections, gateways, flows, and Dataverse databases. [1](https://learn.microsoft.com/en-us/power-platform/admin/environments-overview)

Microsoft Learn gives an example where two environments named Test and Dev each have a Dataverse database. If an app is created in the Test environment, it can connect to the Test database but not the Dev database. [1](https://learn.microsoft.com/en-us/power-platform/admin/environments-overview)

Environment: Development
   |
   +-- Development App
   +-- Development Flow
   +-- Development Dataverse Database

Environment: Test
   |
   +-- Test App
   +-- Test Flow
   +-- Test Dataverse Database

Environment: Production
   |
   +-- Production App
   +-- Production Flow
   +-- Production Dataverse Database

The diagram is an educational representation based on Microsoft Learn’s explanation that apps connect to data sources deployed in the same environment. [1](https://learn.microsoft.com/en-us/power-platform/admin/environments-overview)

Power Platform Admin Center

The Power Platform admin center is the main administration portal for managing Power Platform environments and settings. Microsoft Learn states that the Power Platform admin center provides a unified portal for administrators to manage environments and settings for Power Apps, Power Automate, Power Pages, Microsoft Copilot Studio, and some Dynamics 365 apps. [3](https://learn.microsoft.com/en-us/power-platform/admin/admin-documentation)

Microsoft Learn explains that the Power Platform admin center includes feature areas such as Actions, Manage, Security, Copilot, Monitor, Deployment, Licensing, and Support. [3](https://learn.microsoft.com/en-us/power-platform/admin/admin-documentation)

Admin Center Area	Purpose
Actions	View recommendations about Power Platform implementation to enhance security, reliability, and health.
Manage	Manage environments, environment groups, and tenant settings.
Security	Use security features to run organizational workloads safely.
Copilot	Access resources, usage tracking, and governance controls for Copilot features.
Monitor	Measure and improve operational health metrics of resources built or deployed in Power Platform.
Deployment	Manage application lifecycle management workloads and deployment visibility.
Licensing	View licensing attention and license consumption for environments.
Support	Access self-help solutions or create support tickets.

The feature areas and descriptions are based on Microsoft Learn’s Power Platform admin center overview. [3](https://learn.microsoft.com/en-us/power-platform/admin/admin-documentation)

Environment Roles

Environment roles control what users can do inside an environment. Microsoft Learn explains that environments have two built-in roles that provide access to permissions within an environment: Environment Admin and Environment Maker. [1](https://learn.microsoft.com/en-us/power-platform/admin/environments-overview)

Microsoft Learn’s Dataverse security documentation explains that Power Platform uses different role types at different scopes, including tenant-level admin roles, environment-level roles, Dataverse security roles, and app-specific roles. [2](https://learn.microsoft.com/en-us/power-platform/admin/database-security)

Role Type	Examples	Scope	Typical Use
Tenant-level admin roles	Power Platform administrator, Dynamics 365 administrator, Global Administrator	Entire tenant	Manage environments, policies, and platform settings across the organization.
Environment-level roles	Environment Admin, Environment Maker	Single environment without Dataverse	Create and manage resources such as apps, flows, and connections.
Dataverse security roles	System Administrator, System Customizer, Basic User	Single environment with Dataverse	Control access to Dataverse tables, apps, and data.
App-specific roles	Dynamics 365 Sales roles, Customer Service roles	Single environment with Dataverse	Provide access to features in specific Dynamics 365 or Power Platform apps.

The role type descriptions are based on Microsoft Learn’s Dataverse role-based security documentation. [2](https://learn.microsoft.com/en-us/power-platform/admin/database-security)

Environment Admin Role

The Environment Admin role is used for administrative control within an environment. Microsoft Learn states that the Environment Admin role can perform all administrative actions on an environment, including adding or removing a user or group from the Environment Admin or Environment Maker role and provisioning a Dataverse database for the environment. [1](https://learn.microsoft.com/en-us/power-platform/admin/environments-overview)

Environment Admin Capability	Explanation
Add or remove users/groups from roles	Can manage Environment Admin and Environment Maker role membership.
Provision Dataverse database	Can provision a Dataverse database for the environment.
Administrative actions	Can perform administrative actions on the environment.

These capabilities are directly based on Microsoft Learn’s description of the Environment Admin role. [1](https://learn.microsoft.com/en-us/power-platform/admin/environments-overview)

Environment Maker Role

The Environment Maker role is used for users who create resources in an environment. Microsoft Learn identifies Environment Maker as an environment-level role. Microsoft Learn’s role type table explains that environment-level roles apply to a single environment without Dataverse and are used to create and manage resources such as apps, flows, and connections. [2](https://learn.microsoft.com/en-us/power-platform/admin/database-security)

In simple terms, Environment Makers are usually the people who build apps and flows, while Environment Admins are responsible for managing the environment itself.

Role	Simple Explanation	Common Responsibility
Environment Admin	Manages the environment	Controls roles, settings, and administration
Environment Maker	Creates resources inside the environment	Creates apps, flows, and connections

The comparison is a learning-friendly explanation based on Microsoft Learn’s environment role and role type descriptions. [1](https://learn.microsoft.com/en-us/power-platform/admin/environments-overview)[2](https://learn.microsoft.com/en-us/power-platform/admin/database-security)

Tenant-Level Admin Roles vs Environment-Level Roles

Tenant-level admin roles and environment-level roles are different. Microsoft Learn explains that tenant-level admin roles such as Power Platform administrator, Dynamics 365 administrator, and Global Administrator apply to the entire tenant, while environment-level roles such as Environment Admin and Environment Maker apply to a single environment without Dataverse. [2](https://learn.microsoft.com/en-us/power-platform/admin/database-security)

Microsoft Learn also notes that tenant-level admin roles do not automatically grant Dataverse data access. To work with data in a Dataverse environment, a tenant admin must also be assigned the System Administrator Dataverse security role in that specific environment. [2](https://learn.microsoft.com/en-us/power-platform/admin/database-security)

Role Scope	Examples	Important Point
Tenant-level	Power Platform administrator, Dynamics 365 administrator, Global Administrator	Applies across the tenant but does not automatically grant Dataverse data access.
Environment-level	Environment Admin, Environment Maker	Applies to a single environment without Dataverse.
Dataverse-level	System Administrator, System Customizer, Basic User	Controls access to Dataverse tables, apps, and data in an environment.

These points are based on Microsoft Learn’s role-based security documentation. [2](https://learn.microsoft.com/en-us/power-platform/admin/database-security)

Environment Types

Different environment types are used for different purposes. Microsoft Learn explains that environment usage depends on the organization and the apps being built. It gives examples of using separate environments for test and production versions, teams, departments, and global branches. [1](https://learn.microsoft.com/en-us/power-platform/admin/environments-overview)

The following table gives a beginner-friendly explanation of common Power Platform environment types. The Microsoft Learn environment overview is the official source for the environment concept. Additional environment type explanations below are presented as educational descriptions for learning clarity. [1](https://learn.microsoft.com/en-us/power-platform/admin/environments-overview)

Environment Type	Learning-Friendly Explanation	Common Purpose
Default Environment	An environment that is commonly available in a tenant for general creation scenarios.	Basic creation, personal productivity, and learning scenarios.
Production Environment	An environment used for stable and live business solutions.	Running business-critical apps and flows.
Sandbox Environment	A non-production environment used for testing, development, and training.	Testing changes before production.
Developer Environment	An environment used by individual makers or developers for experimentation.	Learning, prototyping, and individual development.
Trial Environment	A temporary environment used to evaluate Power Platform capabilities.	Short-term exploration and evaluation.
Microsoft Teams Environment	An environment related to building Power Platform solutions within Microsoft Teams.	Team-based apps and flows.
Managed Environment	An environment with additional management, security, governance, and operational capabilities.	Enterprise governance and controlled administration.

The official Microsoft Learn source supports the core environment concept, environment separation, and environment management capabilities. The individual environment type descriptions are provided as learning-friendly explanations. [1](https://learn.microsoft.com/en-us/power-platform/admin/environments-overview)[4](https://learn.microsoft.com/en-us/power-platform/admin/environment-management-overview)

Managed Environment and Environment Management Capabilities

Microsoft Learn explains that environment management is an offering of premium capabilities that allows admins to manage Power Platform at scale with more control, less effort, and more insights. [4](https://learn.microsoft.com/en-us/power-platform/admin/environment-management-overview)

Microsoft Learn also states that environment management provides enhanced security, governance, and operations features for environments that have opted in to these capabilities. It describes environment management as delivering advanced protection, greater visibility, and operational excellence. [4](https://learn.microsoft.com/en-us/power-platform/admin/environment-management-overview)

Capability Area	Meaning
Managed Security	Helps protect data, control access, prevent data exfiltration, and improve visibility into security posture.
Managed Governance	Provides a structured framework to help ensure environments are used in compliance with policies and requirements.
Managed Operations	Supports organizations in building, deploying, and operating critical workloads.
Managed Availability	Listed as one of the environment management capability areas in Microsoft Learn.

The capability areas are based on Microsoft Learn’s environment management capabilities article. [4](https://learn.microsoft.com/en-us/power-platform/admin/environment-management-overview)

Security in Environment Management

Security in environment management focuses on protecting data, controlling access, managing identities, and ensuring that only the right users have the right permissions.

Microsoft Learn describes managed security as including security posture management, data protection and privacy, identity and access management, threat protection, and compliance. [4](https://learn.microsoft.com/en-us/power-platform/admin/environment-management-overview)

Microsoft Learn also explains that Dataverse uses a role-based security model to control access to a database and its resources in an environment. [2](https://learn.microsoft.com/en-us/power-platform/admin/database-security)

Security Area	Meaning in Environment Management
Identity and Access Management	Controls who can access environment resources.
Role-Based Security	Uses roles to define what users can do in an environment or Dataverse database.
Data Protection and Privacy	Helps protect business data and privacy-sensitive information.
Threat Protection	Helps protect workloads from threats.
Compliance	Helps align environment usage with organizational or regulatory requirements.

These security areas are based on Microsoft Learn’s managed security description and Dataverse role-based security documentation. [4](https://learn.microsoft.com/en-us/power-platform/admin/environment-management-overview)[2](https://learn.microsoft.com/en-us/power-platform/admin/database-security)

Governance in Environment Management

Governance means setting rules, controls, and processes for how environments are used. Governance helps ensure that users create and manage Power Platform resources in a controlled and accountable way.

Microsoft Learn explains that managed governance provides a structured framework to help ensure environments are used in compliance with organizational policies and regulatory requirements. It also states that managed governance helps organizations maintain control over their data, optimize resource usage, and ensure that activities in the platform are transparent and accountable. [4](https://learn.microsoft.com/en-us/power-platform/admin/environment-management-overview)

Governance Topic	Purpose
Environment Strategy	Defines how environments should be organized and used.
Policy Compliance	Helps align environment usage with organizational and regulatory requirements.
Transparency	Helps make platform activities visible and accountable.
Resource Optimization	Helps optimize resource usage.
Capacity and Cost Management	Helps manage capacity and cost efficiently.

The governance topics are based on Microsoft Learn’s managed governance description, including policy compliance, transparency, resource usage, capacity, and cost management. [4](https://learn.microsoft.com/en-us/power-platform/admin/environment-management-overview)

Administration in Environment Management

Administration includes the tasks that administrators perform to manage environments, settings, users, permissions, policies, monitoring, deployment, licensing, and support.

Microsoft Learn states that the Power Platform admin center is a unified portal for administrators to manage environments and settings. It also identifies the Manage area as the place to manage environments, environment groups, and tenant settings. [3](https://learn.microsoft.com/en-us/power-platform/admin/admin-documentation)

Administrative Area	Purpose
Environment Management	Manage environments and environment groups.
Tenant Settings	Manage settings that apply across the tenant.
Monitoring	Measure and improve operational health metrics of resources.
Deployment	Support application lifecycle management and deployment visibility.
Licensing	View license attention and consumption for environments.
Support	Access support and self-help options.

These administrative areas are based on Microsoft Learn’s Power Platform admin center overview. [3](https://learn.microsoft.com/en-us/power-platform/admin/admin-documentation)

Environment Strategy

An environment strategy is a plan for how environments should be created, named, secured, and used across an organization. It helps prevent confusion and supports better security, governance, and lifecycle management.

Microsoft Learn explains that organizations may create separate environments to group test and production versions of apps or chatbots, create environments for teams or departments, or create environments for different global branches. [1](https://learn.microsoft.com/en-us/power-platform/admin/environments-overview)

A simple learning-friendly environment strategy is:

Environment	Purpose	Typical Users
Development	Build and experiment with apps, flows, and solutions.	Makers and developers
Test	Validate changes before release.	Testers, makers, selected business users
Production	Run live business solutions.	Business users and support teams

The Development-Test-Production model is an educational strategy based on Microsoft Learn’s support for separating test and production versions. Organizations should adapt environment strategy based on their own security and governance requirements. [1](https://learn.microsoft.com/en-us/power-platform/admin/environments-overview)

Environment Groups

Microsoft Learn’s Power Platform admin center overview states that the Manage area is used to manage environments, environment groups, and tenant settings. [3](https://learn.microsoft.com/en-us/power-platform/admin/admin-documentation)

For beginner understanding, environment groups can be understood as a management concept that helps administrators organize environments together. The source confirms that environment groups are managed from the Power Platform admin center, but the cited source does not provide deeper procedural details in the search result. [3](https://learn.microsoft.com/en-us/power-platform/admin/admin-documentation)

Environment Management Lifecycle

Environment Management can be understood as a lifecycle. Administrators plan the environment strategy, create or manage environments, assign roles, build or deploy resources, monitor usage, and improve governance over time.

Plan Environment Strategy
        |
        v
Create or Manage Environment
        |
        v
Assign Roles and Access
        |
        v
Build or Deploy Apps and Flows
        |
        v
Monitor Usage and Health
        |
        v
Review Security and Governance
        |
        v
Improve and Maintain Environment

This lifecycle is an educational representation. Microsoft Learn supports the underlying concepts of environment strategy, environment roles, admin center management, monitoring, deployment, security, and governance. [1](https://learn.microsoft.com/en-us/power-platform/admin/environments-overview)[3](https://learn.microsoft.com/en-us/power-platform/admin/admin-documentation)[4](https://learn.microsoft.com/en-us/power-platform/admin/environment-management-overview)

Environment Management Checklist

The following checklist helps learners understand what administrators should consider while managing environments.

Checklist Area	Question to Ask
Purpose	What is this environment used for?
Audience	Which users, teams, departments, or business groups need access?
Security	Who should be Environment Admin, Environment Maker, or Dataverse user?
Dataverse	Does this environment require a Dataverse database?
Location	Which geographic location should the environment be bound to?
Governance	What policies and controls should apply?
Monitoring	How will operational health and usage be reviewed?
Lifecycle	Is this environment for development, test, production, or another purpose?
Deployment	How will apps and flows move between environments?
Ownership	Who is responsible for maintaining the environment?

This checklist is an educational planning tool based on Microsoft Learn’s environment overview, admin center feature areas, environment roles, Dataverse security, and environment management capabilities. [1](https://learn.microsoft.com/en-us/power-platform/admin/environments-overview)[3](https://learn.microsoft.com/en-us/power-platform/admin/admin-documentation)[2](https://learn.microsoft.com/en-us/power-platform/admin/database-security)[4](https://learn.microsoft.com/en-us/power-platform/admin/environment-management-overview)

Example: Development, Test, and Production Environment Setup

A common environment management idea is to separate development, testing, and production. Microsoft Learn explicitly supports the idea of creating separate environments that group test and production versions of apps or chatbots. [1](https://learn.microsoft.com/en-us/power-platform/admin/environments-overview)

Development Environment
   |
   | Build and modify app/flow
   v
Test Environment
   |
   | Validate and test app/flow
   v
Production Environment
   |
   | Business users use stable solution

The diagram is an educational representation based on Microsoft Learn’s example of separate test and production environments. The development stage is added as a learning-friendly extension for explaining lifecycle management. [1](https://learn.microsoft.com/en-us/power-platform/admin/environments-overview)

Environment Management and ALM

ALM means Application Lifecycle Management. In Power Platform, environment management supports ALM because apps and flows may need to move from development to testing and then to production.

Microsoft Learn’s Power Platform admin center overview states that the Deployment area helps administrators manage Power Platform application lifecycle management workloads, including managing pipeline deployments at enterprise scale and maintaining visibility of deployments in the tenant. [3](https://learn.microsoft.com/en-us/power-platform/admin/admin-documentation)

ALM Stage	Environment Role
Development	Build and change apps, flows, and solutions.
Testing	Validate changes before release.
Production	Run stable business solutions for users.
Deployment Management	Use deployment visibility and ALM controls from administration features.

The ALM explanation is educational. Microsoft Learn directly supports the Deployment area for ALM workloads and pipeline deployment visibility. [3](https://learn.microsoft.com/en-us/power-platform/admin/admin-documentation)

Monitoring and Operational Health

Monitoring helps administrators understand the operational health of Power Platform resources. Microsoft Learn explains that the Monitor area in the Power Platform admin center is used to measure and improve operational health metrics of resources built or deployed in Power Platform, such as apps. [3](https://learn.microsoft.com/en-us/power-platform/admin/admin-documentation)

Monitoring is part of administration because environments may contain many apps, flows, and resources. Without monitoring, administrators may not know whether resources are healthy or need attention.

Licensing and Capacity Awareness

Licensing is also part of environment management. Microsoft Learn states that the Licensing area of the Power Platform admin center allows administrators to view a summary of environments in the tenant requiring licensing attention and license consumption for environments. [3](https://learn.microsoft.com/en-us/power-platform/admin/admin-documentation)

Microsoft Learn also explains that managed governance includes capacity and cost management. [4](https://learn.microsoft.com/en-us/power-platform/admin/environment-management-overview)

Topic	Why It Matters
License Attention	Administrators need visibility into environments requiring licensing attention.
License Consumption	Administrators need to understand license usage for environments.
Capacity Management	Governance includes managing capacity and cost efficiently.
Cost Management	Governance helps manage cost-related decisions for platform usage.

These points are based on Microsoft Learn’s admin center licensing description and managed governance capability description. [3](https://learn.microsoft.com/en-us/power-platform/admin/admin-documentation)[4](https://learn.microsoft.com/en-us/power-platform/admin/environment-management-overview)

Best Practices for Environment Management

The following best practices are suggested for beginner-level learning. They are based on Microsoft Learn’s concepts of environment separation, environment roles, Dataverse, admin center management, managed security, managed governance, and managed operations.

Use separate environments when apps or flows have different roles, security requirements, or audiences.
Separate test and production solutions where appropriate.
Assign Environment Admin access carefully.
Give Environment Maker access only to users who need to create resources in that environment.
Plan whether Dataverse is required before designing apps and flows.
Use the Power Platform admin center to manage environments and settings.
Use monitoring to review operational health.
Use governance controls where environments require stronger oversight.
Plan environment location carefully because environments are bound to a geographic location.
Consider lifecycle needs such as development, test, deployment, and production use.

These recommendations are educational interpretations based on Microsoft Learn’s environment overview, role documentation, admin center overview, and environment management capabilities.