Share this page

# Editions

Your edition defines which activities you can perform.

In this topic:

## Editions overview

OpenText Software Delivery Management editions provide you with the following capabilities.

Edition | Description
--- | ---
Enterprise edition | Enables you to scale to large groups with the benefits of cross-workspace and cross-program capabilities. These include: Shared customization such as rules, user-defined fields, workflow, forms, and lists Shared entities such as users and releases Cross-workspace reporting on data from multiple workspaces using the same widget Cross-program functionality for the Backlog module Data access control For an overview of workspaces and their programs, isolated spaces, and shared spaces, see Space configuration. Model-Based Testing (MBT): You can obtain a special license that enables model-based testing functionality, enhancing your testing based on business flows. For details, see Functional Testing Help Center.
Pro edition | Provides you the same set of features as Enterprise Edition within isolated workspaces. Shared space and program capabilities are not provided.
Developer (add on) | The Developer license is a named license that is added on top of a core Pro or Enterprise license. The Developer license enables backlog management, defect management, DevOps pipeline management, and manual testing execution. Developer license capabilities depend on your core license edition. For details, see Trial license.

Back to top

## Functionality by edition

Details of the functionality provided with each of the editions are listed in the table below.

Functionality | Enterprise | Pro | Developer
--- | --- | --- | ---
Dashboard and Delivery Insights |  |  |
Public dashboard sharing |  |  |
Automation ROI metrics |  |  |
Cycle Time Insights |  |  |
Risky Code Commits Analytics |  |  |
Risk Based Testing |  |  |
Requirements * |  |  |
Backlog * |  |  |
Team Backlog |  |  |
IDE plugins |  |  |
Development Center (Commits, Pull Requests, Branches) |  |  |
DevOps efficiency |  |  |
Team collaboration |  |  |
Defects module |  |  |
Security integration - Fortify Suite |  |  |
Pipelines with build and Test Automation analytics |  |  |
Manual test execution (manual tests and BDD scenarios) |  |  | Single test
My Work |  |  |
Synchronization using Connect |  |  |
Flag rules |  |  |
Quality module |  |  |
On-Demand Automated test execution (with OpenText Functional Testing integration) and test suites |  |  |
Gherkin tests |  |  |
Release planning, shared releases and calendars |  |  |
Cross-release planning |  |  |
Release processes management |  |  |
Shared workspaces customization |  |  |
Cross-workspace reporting |  |  |
Shared application modules |  |  |
Entity migration between workspaces |  |  |
Data access control |  |  |
Workspace SAFe program |  |  |
Entity label customization |  |  |
Available License Types | Named or Concurrent | Named or Concurrent | Named only

* See the section below for more details.

Back to top

## Developer license

Developer license is a named license that is added on top of a core Pro or Enterprise license.

The following guidelines apply to Developer licenses:

- Users with a Developer license can view backlog items, such as epics and features, but not create or modify them. Users that cannot modify epics or features will also be unable to edit any related entities. A Developer license user, however, can add comments to an existing feature.

- If a Requirement type entity is linked to other entities to which the user has permissions, it will be visible. However, the linked Requirement entity cannot be edited.

- Each named user has one license type assignment (Core or Developer) at the site level for on-premises, and at the space level for SaaS.

- The Developer license is not a role, but a license type. In addition to assigning a Developer license to a user, you also need to assign a role to the user.

- Developers who are part of an Enterprise edition can access shared public dashboards.

- Developer license users cannot plan features for any release (Release planning). They can however, plan backlog items such as User stories, Defects/Issues, and Quality stories (Cross-release planning).

Assigning licenses to users

For details on managing Developer licenses, see Assign Developer licenses.

If the user is new, assign the Developer license at user creation.

In Settings > Spaces > Users, the License type column shows whether existing users are assigned a Core or Developer license.

- To assign a Developer license to a user, or to restore their Core license, click Core/Dev in the user's License Type column and modify as needed.

- You can switch a user from Dev to Core and vice versa at any time.

- Deactivating a user releases their license even if the license is still assigned.

Note: The right pane shows usage data.

Developer licenses are always named, so they do not impact allocation or usage of concurrent licenses. If a Dev user opens a session, they do not impact the concurrent usage.

Back to top

## Trial license

When you first start, you automatically receive a Trial license which gives you a 90-day trial for 100 users.

By default, your trial is Enterprise Edition, which allows one shared space. If you create a shared space in an Enterprise Edition trial and then install a license for Pro Edition, the trial shared space should not be used in a production environment since the sharing capabilities may not be supported in future releases.

Back to top

## License management

For details on how to manage on-premises licenses and how to allocate licenses from OpenText Application Quality Management to OpenText Software Delivery Management, see Manage licenses.

Back to top

See also:

- Manage licenses
- Space configuration
- Admin

https://admhelp.microfocus.com Software Delivery Management 8942
Tips to improve your search results... OpenText™ Software Delivery Management Help Center OpenText™ Software Delivery Management Help 26.1 All View Local Help Center View Online Help Center Version: