Managani Docs

Appearance

Support ​

Getting Help ​

When something blocks your team, start with the docs, then reach out if you need a human.

  • Documentation — You're here. Browse the Guide and API Reference
  • Managani Feedback — Use the Feedback link in your signed-in Managani navigation to report bugs or request features
  • Email — Reach us at hi@managani.com

Status ​

Check service status at status.managani.com.

SLA ​

MANAGANI Cloud targets reliable uptime for hosted workspaces.

Describe the Problem Clearly ​

Include the part of Managani where the issue occurs, what you expected to happen, and what happened instead. A short sequence of reproduction steps is more useful than a general description such as “the widget does not work.” Note whether the problem happens consistently or only under particular conditions.

Identify the affected account and site using non-secret details. If your login belongs to multiple accounts, confirm which account was selected when the issue occurred. For a customer-facing problem, include the affected page URL and whether the customer was signed in or anonymous.

Include Relevant Diagnostics ​

For web issues, record the browser and operating system. For Desktop or Mobile, include the application version and device platform. A screenshot can show an error or unexpected layout, but remove private customer information before sharing it.

When an API integration fails, provide the HTTP method, endpoint, status code, and a sanitized error response. Never send a password, personal access token, authorization header, or signed customer token. Describe the authentication method without sharing its secret value.

Choose the Right Route ​

Check service status first when several people are affected at the same time. Use the signed-in Feedback link for reproducible bugs and product requests that need review. Email support when you cannot sign in or need help explaining an account-specific issue.

After sending a report, keep any new observations with the same conversation so the troubleshooting history remains clear. If a workaround restores access, mention exactly what changed; that can help distinguish a local setup issue from a wider service problem.