Skip to content

Settings & notifications

Operations → Settings (“Organization Control”) requires org:read; changes require org:manage.

  • Display Name — editable.
  • Organization ID and Slug — read-only; include the ID when contacting support.

Click Save Configuration to apply.

Contact details shown to end users on the SDK’s blocked device screen: Business Email, Phone Number, Business Number, Website and Logo URL (with preview). Click Save Organization Info.

Property names listed here are redacted ([MASKED]) from SDK logs — network headers and bodies, trace logs and crash messages — before they’re stored.

  • Default properties (tagged default) can’t be removed: password, authorization, token, secret, api_key, cookie, ssn, cvv, card_number, private_key, client_secret, access_token, refresh_token, pin.
  • Add your own, e.g. phone_number, iban, email, and click Add. Matching is case-insensitive and applies at any depth of a JSON body.
  • Remove a custom property with ×.

Register apps and download cimka_config.json — see Applications & SDK setup.

  • Security & IAM — PII anonymization.
  • End-to-End Encryption — the SDK encrypts every log on the device with your organization’s public key; only holders of your private key can read them in the dashboard.

The bell in the header opens Notifications. Tabs: All and Unread; Mark all read clears the badge. Click a notification for details and an action button (e.g. open the alert).

Type Examples
Team You were invited, your role changed
Alerts Crash spike, new fatal issue, regression, network anomaly
Security Risky device detected
Billing Top-up requested / approved / rejected, low balance, credit added
Admin Announcements from Cimka or your admins

Priorities are low, medium, high and critical; high and critical notifications are also emailed.