Namespaces

> Supported for Services Namespaces for Feature Flag Management Platforms

> Supported for Sentinel RMS Supported for Sentinel Fit Supported for Services Supported for third-party license enforcements Prerequisites for Creating a Namespace

> Supported for Sentinel RMS Supported for Sentinel Fit Supported for Services Supported for third-party license enforcements Creating a Namespace

> Supported for Sentinel RMS Supported for Sentinel Fit Supported for Services Supported for third-party license enforcements Actions for Namespaces

New to Sentinel EMS?
See How to Use Sentinel EMS?

What Is a Namespace?

The creation and use of namespaces differs according to the enforcement.

Sentinel RMS, Sentinel Fit, Services, Third-party

A namespace acts as a logical partition for your Sentinel EMS workspace, enabling you to maintain separate “storage locations” for each of your product lines. This enables you to group products and features together. For example, you may want to use namespaces to group catalog entities and manage permissions. Namespaces are for your internal use and are not exposed to end users.

Sentinel LDK

A namespace represents the Batch Code created at the backend when the batch code is introduced.

In Sentinel EMS, a namespace also acts as a workspace, differentiating between separate storage locations, similar to those that are designated for use with Sentinel RMS. If you have multiple namespaces, the features, memory files, and products in each namespace are available only to those users who have permissions for that namespace. Users with roles that have entitlement-related permissions (such as order takers) can access these items from all namespaces.

Supported for Sentinel LDK IMPORTANT Although namespaces may be available for all enforcements, vendor users working with Sentinel LDK enforcement must use the pre-seeded namespaces that are created at the back end when a batch code is introduced.

A product can include only the features and memory files* defined in that product’s namespace. If you want to add a feature or memory file* from another namespace, you must create that feature or memory file* in the relevant namespace. Similarly, a product suite* can include only products from the same namespace.

Entitlements transcend namespaces and can contain products and product suites* from one or more namespaces. This means that all of the products and product suites* across namespaces are available to an order taker (that has permission to view, add, edit, and delete entitlements) while creating entitlements.

Namespaces for Feature Flag Management Platforms

The features driven by feature flag management platforms are created using the pre-seeded Feature-Flag namespace. You must not delete or rename this namespace. Otherwise, you will not be able to restore existing feature flag data in Sentinel EMS.

Prerequisites for Creating a Namespace

The vendor user must have administrative rights in Sentinel EMS.

Creating a Namespace

You create a namespace from the Namespaces page.

To create a namespace:

1.From the navigation pane, select Catalog > Namespaces to view the Namespaces page.

2.Click the Add Namespace button.

3.Fill in the namespace attributes.

4.After the namespace is saved, specify permissions for the namespace users as needed. For more information, see Vendor Users and Roles.

Namespace Attributes

The following table explains the namespace attributes:

Attributes	Description	Required/Optional	Valid Values
Name	Name of the namespace. The validity of the namespace name depends on the enforcement in use.	Required	>Must be unique >Alphanumeric >1 to 200 characters
Ref ID 1	Reference identifier that identifies the namespace in an external system.	Optional	>Alphanumeric >0 to 100 characters
Ref ID 2	Reference identifier that identifies the namespace in an external system.	Optional	>Alphanumeric >0 to 100 characters
Description	Additional information about the namespace.	Optional	>Alphanumeric >0 to 500 characters

Actions for Namespaces

The following table lists the actions available for namespaces:

Action	Description
	Edit	Updates existing namespace information. For details on editing namespaces, see Editing an Entity. Note: You can modify all attributes irrespective of the deployment status of a namespace. A namespace is considered "deployed" when it is used in an entitlement.
	Delete	Deletes the namespace. See Deleting an Entity to understand how to delete a namespace. Note: >You cannot delete deployed namespaces. >Deleting a namespace also deletes all of its associated features and products upon confirmation.

Action

Description

Edit

Updates existing namespace information. For details on editing namespaces, see Editing an Entity.

Note: You can modify all attributes irrespective of the deployment status of a namespace. A namespace is considered "deployed" when it is used in an entitlement.

Delete

Deletes the namespace. See Deleting an Entity to understand how to delete a namespace.

Note:

>You cannot delete deployed namespaces.

>Deleting a namespace also deletes all of its associated features and products upon confirmation.