Managani Docs

Appearance

Desktop Links ​

Managani Desktop registers the com.managani.desktop: protocol during installation.

Open a View ​

text
com.managani.desktop://open?view=chats

Supported view values are:

  • dashboard
  • chats
  • feedback
  • notifications
  • settings

Unknown view values open the Dashboard.

Open an Account ​

Add a 24-character account tenant ID:

text
com.managani.desktop://open?view=feedback&tenant=ACCOUNT_TENANT_ID

Desktop switches only when the signed-in user can access that account. Invalid tenant IDs are ignored.

Authentication Callback ​

text
com.managani.desktop://auth/callback?code=...&state=...

This route is reserved for Desktop OAuth. Applications should not create callback links themselves.

Desktop accepts only the known actions and validated tenant identifiers above. Normal external web links open in the system browser.

A Desktop link can provide a convenient shortcut from an internal checklist or team document to a supported Managani view. Choose the view that matches the task: chats for conversations, feedback for product requests, notifications for recent alerts, or settings for configuration. Use the dashboard when you want a general starting point.

The application must be installed and its protocol handler registered on the receiving computer. A browser or operating system may ask the user to confirm opening an external application. If the link does not launch Desktop, open Managani normally once and review the troubleshooting guide.

Check Account Context ​

Include a tenant identifier only when you know which account the task belongs to. The identifier selects an account; it does not grant access to it or sign a user in. Someone receiving the link still needs an existing membership and a valid Desktop session.

After opening a link, check the selected account before changing product data. This is especially useful for teammates who work across several accounts. An invalid identifier is ignored, so a malformed link should not be treated as evidence that the intended account was selected.

Keep Authentication Separate ​

Use the normal Desktop sign-in process when authorization is needed. The reserved callback carries temporary authorization information and is not a general-purpose shortcut. Do not copy callback URLs into team documents or attempt to reuse a completed sign-in link.