A little nudge.
A clearer
next step.

Ping is Leera’s AI teammate. It watches the projects in scope for late or stuck work, checks in with the responsible person in a private thread, remembers useful work context, and follows up on commitments. It can answer project questions, coordinate team asks and meetings, and act within the administrator’s charter. Availability depends on the matching release, module access and configured services.

The workspace charter sets each action to automatic, approval first, or off, with project overrides. With a decision provider configured, Ping can update dates, owners and statuses, create issues, and take other permitted actions when the case is clear; otherwise it proposes a change. A change requested in your own Ping thread is always proposed for review. Approved changes record the approver, and a proposal is not applied if the issue has changed in the meantime.

Other members and workspace administrators cannot open your private Ping thread through the application. When someone asks you a question through Ping, you choose the facts and audience on a Share card. Shared by me lets you withdraw the copies Ping can recall and shows what cannot be taken back, such as an issue date already changed or a posted comment. Reusable work memories have personal, project or workspace scope and are available to that scope. Configured model providers process the content they receive, and the instance operator can access stored database data. Email and Slack copies follow those services’ own access and retention rules.

Review the message, named recipients, deadline and response tracking before choosing Confirm and send. Track responses only from people in your reporting subtree or a project you administer; recipients are told who can see their status, and private answer text still requires Share. Announcements can request Got it. Repeating questions have a confirmed schedule, refresh their audience on each run, and can be paused, resumed or stopped. Summaries use only shared facts.

Ping automatically saves explicit, useful work facts, named groups and away periods from your conversation within the scopes you may use. What Ping remembers shows the fact, scope and author, with edit and forget controls where you have permission. A turn that reads connected email cannot create memory, and private relay answers keep their sharing restrictions. Forget my memories deletes your personal memories and the shared memories you authored.

Email copies require outgoing email, and Slack copies require the workspace’s Slack connection, administrator settings and your linked account. Delivery respects your working and quiet hours. Approvals and sharing stay in the app; typed email or Slack replies do not approve changes. Replies by email require a self-hosted instance running Leera’s built-in inbound mail server. Google Calendar and Microsoft 365 calendars need instance configuration and your own permission; Ping uses busy times to help suggest meetings and can add or remove meetings you organise.

Only on an instance where an administrator enables the service and you grant access. Gmail is not available on Leera Cloud yet, pending Google’s restricted-scope verification. Ping reads Gmail only when you ask in your own thread; answers that used email stay there and are marked accordingly. Sending needs a separate permission, your request, and approval of the exact recipients, subject and text on a draft card. Ping never sends mail from your account on its own. Outlook mail, attachments, HTML email and a shared Ping mailbox are not supported.

Each person accepts a one-time notice before receiving normal Ping contact and can turn it off. Set working hours, quiet hours and channel preferences, and choose whether to receive daily briefs and weekly digests, which are on by default. Administrators can pause a project or the whole workspace and control scope, action permissions, budgets and retention. Briefs appear in Ping and, when enabled, email; they are not sent to Slack.

Yes. Web and desktop clients offer ten animated appearances plus Classic Ping. Your companion and animation choice are saved for your account in that workspace and shared across signed-in web and desktop clients. Reduced-motion settings take precedence. This changes appearance only; it does not grant access or turn Ping contact on. Mobile companion rendering and its picker are not yet available.

Ping needs a matching database, API and web release, with both AI and Planner access for the person using it. An AI provider powers conversational features. A decision provider enables autonomous decisions within the charter; without it Ping proposes, and without an AI provider it falls back to templated check-ins. Email, Slack and connected accounts each need their own setup; Ping uses a connected account only with that person’s approval. Availability and provider behaviour must be verified on the running deployment.