Appearance
Work together in Casa del Pingüino #
Casa del Pingüino is the Dataplicity workspace for conversations with colleagues and support specialists. Keep the engineering discussion, shared evidence and specialist help together as the work develops.
For example, your firmware engineer and support lead can investigate missing readings in one room. Invite Pingüino to help interpret the evidence, discuss the findings together, and retain the conversation for the next person who encounters the problem.
Team messaging is included on Device Access, Standard, Business+ and Enterprise, subject to your organisation's access policy. The specialists available to invite follow your organisation's plan and persona access.
Start a conversation #
Open Casa del Pingüino from Quick access in the web app and choose New conversation. Choose the type that matches the audience:
| Conversation type | When to use it |
|---|---|
| Ask an assistant | Work privately with a specialist. You can invite colleagues later. |
| Direct message | Talk privately with one colleague. |
| Private group | Work with the members you invite, such as the engineers investigating a fault. |
| Organisation room | Create a room other members of your organisation can discover and join. Messages are visible to members after joining. |
Give a team room a clear name and purpose, such as “Level monitor integration” or “Gateway release investigation”. Add the colleagues who own the relevant work. You can share files and links and pin important messages. Put the relevant findings and requirements directly in the conversation so colleagues and invited specialists can follow the evidence.
Invite a specialist into an ongoing discussion #
- Open the conversation and choose Invite assistant.
- Select a specialist from the available choices.
- Choose Whole conversation or Selected reply thread for where it listens.
- Choose From now on only, or From now on, plus earlier content and select where the earlier context begins.
- Review the specialist, scope and access summary, then confirm the invitation.
- Mention the handle shown in the app, such as
@pinguino, or reply to one of the assistant's messages to bring it into the discussion.
In group discussions, assistants respond when addressed and can continue contributing while they are engaged and well placed to help. They step back after a quiet stretch. Mention them again when you need another contribution. Use the conversation's assistant controls to remove a specialist when its part of the work is finished.
A useful request refers to the evidence already in the room:
@pinguino, review the connection timeline and application logs we shared above. What explains the missing readings, what remains uncertain, and what should we check next?
Or bring product planning into the same conversation:
@nutria, use the requirements in our shared notes to outline the customer workflow. Separate the first useful release from later improvements, and identify which Dataplicity capabilities we would use.
Control the context and access #
The person who invites an assistant is its sponsor. The assistant works within that person's current authority and the scope granted when it was invited. Its messages identify the sponsor so the team can see who brought it in.
The assistant receives the messages selected by the invitation's scope and history settings. Giving it earlier messages lets it follow the existing discussion; starting from now keeps earlier room messages out of that context. For a selected reply thread, the original message remains part of the context even when you choose From now on only. Long discussions may be truncated, so include a concise summary of the evidence it needs.
Do not assume an invited assistant automatically reads shared canvases, the channel task tracker, organisation project boards, initiatives, or linked documents. Post the relevant excerpt or findings in the granted conversation. For live device or fleet investigation, open a private conversation with Pingüino and provide the device and time range.
Access to account or organisation information does not automatically make that information appropriate for everyone in a room. When another participant asks for protected information, the app can ask the sponsor to approve its disclosure to that audience. Review the information and audience before approving.
Invited assistants provide read-only help in shared conversations. A person in the room must invite each additional specialist; assistants cannot hand off to one another there. Use a private support conversation or the appropriate operating workflow for a change that needs review and confirmation. Removing an assistant revokes its participation; it does not remove replies already visible to the room.
Make the conversation useful to the next person #
Pin the confirmed finding, post the accepted design in the conversation, and assign remaining checks to the responsible colleagues. For an investigation, record the device or release affected, the evidence and time range, the next test, and the result. For a product design, record decisions and unresolved assumptions.
Keep secrets out of messages and attachments. Share redacted logs and the specific design evidence needed for the task. Choose a private group when the discussion is for a limited team.
Next: plan a Product Application or work through board and container integration.