General settings

In this section of Settings, you can reload various sections of the Dawiso platform, and monitor your logs.

Administrative tasks

When you encounter issues in Dawiso, in most cases, reloading the platform will solve the issue.

1. Navigate to Settings > General > Administrative tasks.
2. Here you can:

Task	Description
1. Refresh templates (or Force refresh templates)	Reloads the Dawiso environment UI (e.g., tables) to resolve display issues.
2. Refresh keywords	Refreshes tokenization (for more information, see Business Glossary), ensuring changes made to object links or business glossary objects autolinks (tokens) are reflected accurately.
3. Refresh index	Updates search indexes. Refresh globally, or select a specific space or application to reindex only that area.
4. Synchronize LDAP users	Manually refreshes the user database when third-party login systems are used, with removed users being soft-deleted.
5. Reload configuration	Reloads the Dawiso environment configuration (e.g., enabling features) to address functionality issues.
6. Start sync (Marketplace sync)	Checks the Marketplace for the newest standard packages and automatically syncs the latest updates.
7. Data products	The Data Products panel surfaces the state of Dawiso’s integration with Gate, the external access-management service used to govern data products and their output ports. From here you can verify that the integration is wired up correctly and trigger an on-demand sync. For more information, see Data products

Data products

The Data Products panel shows Dawiso’s Gate integration status. Gate is the external service that governs data products and output ports.

• Test connection: Confirms Dawiso can reach Gate. Use it after initial setup or any credential, URL, or network change.
• Sync with Gate: Pushes the current state of domains, data products, and output ports to Gate immediately, outside the normal event-driven sync. Use it after a bulk import or to recover from a missed event.

Test connection

Probes Gate live and reports:

• URL configured and Gate reachable (with the detected version): green when healthy, red when not.
• Two channel rows follow, one per scope. Dawiso authenticates to each with a short-lived, identity-service-issued token: gate:access_requests (checkout requests) and gate:catalog_sync (pushing domains, data products, and output ports to Gate).

Each channel row shows one of these states:

State	Cause	Reason codes
Green	Verified: token issued, Gate accepted a write-free probe	None
Red: no token obtained	Identity service refused the request or was unreachable; check the connection to it	not_configured, unreachable, grant_rejected, unexpected_error
Red: token rejected	Gate refused an issued token; check Gate’s allow-list, expected subject, or scope grant	client_not_allowed
Hollow: unverified	Token issued, but the probe was inconclusive or didn’t complete. Not a failure and not a reason to rotate the credential: rerun once Gate responds	probe_timeout, probe_failed, or an inconclusive response (429/5xx)

The overall indicator turns green only when both signals are healthy and both channels are verified. An unverified channel blocks green without counting as a failure. A diagnostics list below shows one message per step (token and probe) for each channel.

The panel also verifies metamodel readiness: the package must have the object, relation, and attribute types below for data product features to work.

• Gate sync: data product, domain, and output port object types, and the contains relation type.
• Create data product wizard’s Business Context step: the use case object type, the related and has label relation types, and the use case description attribute type.
• Optional, for the classifications payload only: confidentiality and PII-level object types and their has_* relation types.

The metamodel check describes your own metamodel rather than Gate, so it’s reported whether or not a Gate URL is configured.

Last sync run

Below the buttons, the panel shows the outcome of the most recent finished sync run for data products. It is read-only, and it is read from the stored result rather than from a run in progress, so it stays available between runs — the morning after the overnight sync, for example.

The summary counts are always visible, whether or not the lists below are expanded: delivered, could not be built, not delivered, delivered without a classification, newly marked inactive by Gate, newly marked active again by Gate, and delivered with a port that has no linked data.

Two collapsible lists follow, Could not be built and Not delivered. Each is a table of object, reason, and recommendation, sorted by reason and then by object name, and each opens automatically when it has at least one entry. A list shows at most 50 entries and states how many more there were.

The panel also reports the state of the run itself:

What you see	What it means
No run has completed yet	The channel has never finished a run.
A positive message inside an empty list	The last run succeeded and that list is genuinely empty — not the same as never having run.
The run did not complete cleanly, followed by a reason	The run finished in a degraded state: Gate reported a failure, the delivery fell short of the completeness Dawiso declared, or the run was abandoned before it finished. The line below the notice is the reason Gate or Dawiso recorded for it.
The report could not be read back	The run finished, but the result it stored cannot be read, so what it delivered is unknown. This is reported as its own state rather than as a clean run, because the counts would otherwise all read zero.
Gate was not told the delivery is complete this run	When the run started, the channel had not yet successfully delivered any object, so Dawiso declared no completeness and Gate skipped its own absence check for that run.

If the overview itself fails to load, the panel explains the failure and offers Try again. A permissions error offers no retry, because retrying only reproduces it.

Task log

To see a detailed list of all activities on your Dawiso account, navigate to Settings > General > Task log.

Task states

State	Description
Waiting	The task is in a queue and will be processed soon.
Finished	The task has been successfully completed.
Running	The task is being processed.
Canceled	The task was canceled. Note that for certain tasks, cancelation can be done only by an admin.
Creating	Used for ingestion tasks. The ingestion task is being set up.
To send	Used for event queue tasks. The event queue task is being set up.

Features

Navigate to Settings > General > Features to see which platform features are available for your environment.

Available features:

• MCP: Enables Dawiso MCP for AI assistant integration. Also activates the contributor read-only restriction mode.
• Lineage parser: Enables external SQL script upload for automatic lineage generation.

To enable or disable a feature, contact Dawiso customer support.

Data market checkout

The Checkout target picker on this page decides where Dawiso raises an access request when a user checks out a data cart: dawiso-gate (the default), Jira Service Management, or ServiceNow. Selecting an ITSM target reveals its connection and field-mapping settings, which you can edit yourself. See Data market checkout targets.

Version

To see the current version of Dawiso, navigate to Settings > General > Version.