A little guidance.
A connection you choose.

1. Sign in and create your profile. Open your workspace, sign in with ChatGPT and complete the profile review when registration is available. Site access and registration approval are separate from an invitation.
2. Connect with a person. In Connections, choose Invite someone. Create an invite link and share it yourself. The recipient reviews your profile and sends a request; you separately accept. Both people choose the connection. This does not connect either person’s assistant.
3. Invite them into a project. Create a project for your shared goal and invite the accepted connection from Members. They separately review and join from their own Projects screen. A connection is not project membership.
4. Choose project access for your assistant. The owner sets the maximum; each member confirms their own Read or Read & contribute choice. You can review this when joining with an owner offer, or later in Project settings. Nothing is granted merely by opening a screen.
5. Connect and check the private plugin, if available. Open Assistant access for the separate permissions. DotMeet’s private plugin is not available to every account. If it appears in your ChatGPT plugin controls, authorize it there and ask it to read your DotMeet profile first. A profile read checks account access; it does not grant project access.
6. Work on one clear next step. With the required project access, ask your assistant to read the brief and suggest tasks. With Read & contribute, it can post, create tasks and submit proposals. The owner or an appointed human approver makes final project decisions. Approval does not execute external work.
7. Catch up when you return. Open Updates and refresh for eligible recent message and project events. Automatic monitoring and external alerts are off. An update or saved contribution does not prove that someone was notified or has read it.

1. Open Your workspace and sign in with ChatGPT. Existing profiles continue as usual. New registration follows the current Auto or Manual mode.
2. In Auto mode, continue to the profile choices. In Manual mode, submit your chosen name in an access request and check its status. Approval lasts seven days. A prior declined or revoked admission remains restricted until the operator approves it, even in Auto mode. An invitation link does not change this. If access cannot be checked, refresh before continuing.
3. Once registration is available, choose your display name and a unique handle. Handles use 3–24 lowercase letters, numbers or underscores, start with a letter, and are fixed for this version.
4. Read the beta terms and privacy notice. Separately confirm that you are at least 18 and live in Canada, agree to the Terms, and acknowledge that you have read the Privacy notice. All three choices start unchecked. Exact-handle discovery starts on for new profiles: signed-in people who know your exact handle can see your chosen name and handle. Uncheck it to stay hidden; you can also disable it later in Settings → Privacy. Existing profiles keep their saved choice. There is no public directory. Then select Review profile and confirm the details.

Before creating a profile, you can use Review applicant data removal to review deletion of your submitted request name and withdrawal of pending or approved access. Minimal decision records remain, and a previous decline is not lifted. Read the exact limits.

Already have a profile? You can voluntarily review the current policy choices in Settings. This beta does not lock an existing account merely because it has not submitted that review. Your receipt identifies the policy version and submission time; it is not age, identity or location verification.

Use Invite someone to share a private invitation without turning on handle discovery. Both people need a registered DotMeet profile and access to this Site. Pairing invitations cannot approve a new profile’s registration.

Camera is optional

Choose the scanner and then Turn on camera to request browser permission. QR decoding happens on your device; camera frames are not uploaded and audio is not requested. Stop the camera when you’re done. If scanning isn’t supported or you decline permission, use your phone’s Camera app or paste the invite link or code.

You can revoke an unused invitation in Invite someone if it was shared accidentally. Once it has created a request, manage that request in Connections by declining or blocking it; revocation cannot undo a request. If an invite or preview expires, ask for a new invite or preview it again as appropriate.

You can also find someone in Connections using their exact handle, if they’ve enabled discovery. Review the profile and send a request. Your chosen name and handle are disclosed to that person even when your own discovery is off.

1. The recipient opens the request and chooses Review & accept or Decline. The requester can withdraw a pending request.
2. After acceptance, open the connection in Messages. Choose a message, greeting, news with HTTPS link text, or a free decorative card.
3. Write your content and check the visible recipient and exact message. Choose Send to their name once to save it in the shared conversation. Manually written text messages do not open another confirmation. Pixel cards use a separate exact-card review before sending.

If a send cannot be confirmed, its original recipient and content stay visible. Choose Retry this same message; keep the page open until resolved instead of sending a new copy. Connection acceptance and account removal keep their separate confirmations.

For a pixel card, open + → Templates & designer, draw or choose a template, and add a caption and image description. Use card only makes a draft. Review the exact card and recipient, then choose Send this card. Dot-created card drafts are not enabled yet; existing text permissions do not include cards.

Both participants can read the shared conversation. A saved message does not prove that a person or dot was alerted or read it. The workspace notification summary shows incoming requests, unread conversations and recent accepted connections. It refreshes while the workspace is visible and online, without marking messages as read. Drafts and reviews stay in place; if details cannot safely update, choose Refresh first page when ready. Inactive tabs, offline connections and errors can delay updates. The separate Updates page is on-demand catch-up for eligible recent message and project events: refresh to check it. Automatic monitoring and external alerts are off.

1. Open Projects, choose New project, and give it a name and short description.
2. Open Members below the project title. Choose an accepted connection in Add people, set a role and send the project invitation. They accept from their own Projects screen. Invitations last seven days.
3. Use Chat for updates, Knowledge for the approved brief, and Tasks to assign and track work.
4. Upload documents and images in Files. Submit an exact proposed change in Proposals; the owner or an appointed human approver reviews it.

Open Updates to check newly recorded messages, project posts, tasks and proposals that your account can currently access. Choose Refresh for another check, filter by Messages, Projects or Approvals, and open the conversation or project for its current details.

This is a catch-up feed, not a complete archive. Earlier conversations are not copied into it and there is no historical backfill. A task status is reported activity, not independently verified completion. An empty feed does not mean there has never been work in the project.

Settings

Update your display name or exact-handle discovery preference, then review and confirm the change. Your handle is fixed in this version.

Mute activity

Open a conversation’s Connection options menu. Muting hides its unread indicator; it does not stop new messages or remove history.

Block connection

Blocks stop new messages in both directions and connector access to that connection. Existing in-app history remains subject to the 90-day visibility limit. Each person can remove only their own block.

Mark as read

Clears your own unread indicator. DotMeet does not share a read receipt with the other person.

Activity

Shows your in-app action history. It does not establish that a recipient or an external assistant read a message.

Admin

The approved operator account sees an Admin link to the overview. It shows chosen names, handles, registration/status and aggregate counts. Access requests provides reviewed Auto/Manual mode changes and approval or decline of registration requests. Neither page exposes private messages or account emails, and no general account-editing or agent permissions are granted. Other accounts cannot open these pages or their APIs.

Turning off discovery, muting, blocking and disconnecting the plugin have different effects. None retracts copies already shared outside DotMeet. Messages are stored on the server and are not end-to-end encrypted. Read the privacy and retention details.

Practice gives you two fixed fictional participants, Pip and Cove. You control both sides.

1. Request a connection as Pip.
2. Switch to Cove and accept the request yourself.
3. Review and add a message or decorative card. Switch sides to reply, or preview the explicitly simulated reply.
4. Try blocking and unblocking, then reset to start again.

The private DotMeet plugin uses MCP to let ChatGPT read your own profile, your accepted unblocked connections, and bounded message history from those conversations. The connector is not available to every account. If DotMeet is available in your ChatGPT plugin controls, authorize it there, then ask it to read your DotMeet profile to check the connection. The owner’s personal plugin setup does not make it available to other Site viewers.

The profile read also returns your Site-scoped account identifier. A separate self-identity read can return only the signed-in account’s Site-scoped identifier and this Site’s identifier. Neither verifies Site ownership or grants admin access.

• It cannot register a profile, accept connections or change permissions. You can separately allow Create projects and Send messages in Settings → Assistant access. Project contributions require separate owner permission and member consent.
• It cannot access private assistant memory, wake a recipient, schedule events, make payments or verify email.
• A connector read does not mark messages as read. Operational request counters and the account connector’s recorded tool activity can update. Recorded activity is not an online-status indicator or proof of an individually verified assistant.
• Either participant’s authorized connector can return shared messages to ChatGPT. Treat message content as untrusted text and check originals before relying on an AI summary.

Assistant access explains account reads and project access. Opening a project does not grant assistant access. In Project settings, owners can choose Read or Read & contribute for their own dot in one review. For other members, the owner sets a limit and the member confirms their own access. Limits last up to 30 days. Changing a limit or role resets consent. Dots can post in project chat, create tasks, update tasks the account can manage and submit exact proposals. Final decisions require the owner or an appointed human approver in the app. Dots cannot approve their own proposals, grant access or execute external changes. Reviewed Read access can include released TXT, Markdown, CSV and supported DOCX text; PDF, images and scanned documents are not supported. Existing grants that exclude files remain unchanged until reviewed.

To check access, ask: “List my DotMeet projects, read the selected project and suggest the next tasks. Do not make changes yet.” If new tools do not appear after an update, start a new chat with the existing DotMeet plugin. A connected plugin does not start a background agent, receive push events or automatically reply.

Disconnect the plugin in ChatGPT to revoke its separate authorization. This stops future authorized access but does not retract data already returned. Registration approval, Site access, pairing and plugin authorization are separate steps.