Namespace properties are configurations that affect a whole namespace. They may affect different areas, like authorization, managing caching mechanisms in the processing pipelines, etc. They can only be configured by administrators. Each property is a key and a value. The examples below show the value only: depending on the property that value is either a plain string or number, or a JSON object.

How To Update Namespace Properties

To update namespace properties, follow these steps:

1. Use the GET /ewx/v1/billingaccount/billingaccount/namespace/{id} endpoint to fetch the current configuration.
2. Locate the "properties": [...] array in the JSON response and copy them.
3. Go to the PUT /ewx/v1/billingaccount/billingaccount/namespace/properties endpoint to update the properties. Copy over the example value by clicking it.
4. Fill in the namespace id and paste the properties you just copied in the properties array.
5. Update or add new properties
6. Review the final list in your request body. ⚠️ If you do not include an existing property in this list, it will be overwritten and permanently lost upon submission.
7. Submit the PUT request to replace the existing property set with your updated list.

If you do not see the endpoints above, you are missing Billingaccount rights, please contact your administrator so they can grant you the necessary rights.

Available Namespace Properties

The following is a table showing the available namespace properties and their purpose:

Name	Component	Description	Example
iam_group_mapping	Authorization	No longer evaluated as of 26.09. Mapped external application user groups to our platform user groups for SAML sign-ins. Use an access rule matching the identity-provider claim your IdP sends instead, or one on the user's email domain (see How to add a new user).	{ "groups": { "some_group@some_company.org": 4587849705848832,"some_other_group@some_company.org": 4587845605812632} }
iam_user_property_mapping	Authorization	Mapping of external user attributes into Energyworx User attibutes	{"city":"last_seen_city", "region":"last_seen_region"}
global_cache_ttl	Processing caching	Cache time to live, in seconds, for the configurations the processing pipeline reads while handling a message, and for the API's channel classifier cache. A value of 0 disables both caches, so every message re-reads its configuration.	600 — default is 60
rule_cache_ttl	API caching	Cache time to live, in seconds, for rule lookups made by the API. Does not affect the processing pipeline, which caches rules under global_cache_ttl. Also editable in the UI under Settings → Other, which is the recommended way to set it.	300 — default is 3600
market_adapters	Processing	Maps the payloadtype of an ingested file to the id of the market adapter that should parse it. Use the key default to match files ingested without a payloadtype.	{"some_label":123456789} where the value is the MA id.
pubsub_topic_name	Processing	The Pub/Sub topic that forwarding rules publish to when the rule does not name a topic itself. The topic must already exist and its name must start with custom-. Some rule families read their own property instead — billing_pubsub_topic_name for billing forwarding and master_data_pubsub_topic_name for master-data forwarding.	custom-events-handling

Process Pool Assignment

Each namespace is assigned to a process pool. Process pools separate data processing into different compute environments, allowing namespaces that share a process pool to share processing resources.

The process pool assignment determines which compute infrastructure is used when processing data for the namespace. To change a namespace's process pool assignment, contact the service desk — a platform deployment is required for changes to take effect.