Skip to main content
Every Digital Twin decides who can join it and how. This page covers the joining modes, invitation links and their approval, the no-account guest link, keeping people on one Digital Twin, and what happens when someone signs up.

​
Joining policy modes

The primary control is the Allow Joining mode on the Digital Twin. It has three values, each tuned for a different kind of audience.

Disabled

Not listed for self-service joining. People get in when an admin adds them, through an invitation link, through single sign-on or through an LMS launch. Use this for private Digital Twins.

Account only

Users who already belong to another Digital Twin under the same parent Account can join this one. Ideal for a school or organization offering several Digital Twins to its own population.

Everyone (public)

Any signed-in person can find and join this Digital Twin from their Digital Twin list. Use this for community Digital Twins and open courses.
The mode shows under Allow Joining in the Digital Twin editor (Configuration and Integrations → Access & Membership; Studio UI: People › Access & Members › Who can join). It is set by the Praxis AI team — contact humans@praxis-ai.com to change it.
“Account only” is based on membership, not email domain: the Digital Twin is offered to users who already have a membership in another Digital Twin under the same parent Account. A brand-new user with no existing membership gets in via an admin, an invitation link, single sign-on, or an LMS launch.

​
Admin-only joining toggle

Independent of the joining mode, Joining Admin Only hides the Digital Twin from regular users’ join options — only administrators can self-join it. It appears once Allow Joining is “Account only” or “Everyone (public)”. In the Studio UI it is the Admins approve new members switch under Who can join (despite its name, no approval is involved); in the classic editor it is set by the Praxis AI team. An admin with users.add can invite people with an invitation link (Instance Settings → Invite, with a QR code, or Send invitation by email). Joins that come through someone’s link are held for that person’s approval:
1

User follows the invitation link

The candidate signs up or signs in, then accepts the join. Their membership is created as Pending.
2

The inviter gets an email

The person who shared the link receives a Membership Request email with an Approve Membership Request button (it works while they are signed in as themselves).
3

The inviter approves

The membership becomes Active and the new member receives a Joining Request APPROVED email with a link to start. An admin can also set the membership to Active under Admin → Users → Membership.

​
Guest access without an account

For public demos and marketing pages, give the Digital Twin a Convo Web Access Link (Instance Settings → Invite → Guest Access, or Realtime / Convo → Convo Web Access Link in the editor): visitors open /twins/<slug> and talk to the Digital Twin without signing up. See Guest Twin Links. Guest UI (Minimum screen) is something else: it strips the interface down to a chat-only screen for signed-in standard members (no navigation, file management or profile menu; admins are unaffected). Find it under Personalization and AI Models → UI & Appearance (Instance Settings → Personalization; Studio UI: Minimal screen for guests).

​
Preventing switching between Digital Twins

By default, a user who belongs to multiple Digital Twins can switch between them from a menu in the UI. For some deployments — branded apps, focused classroom experiences, embedded assistants — you want the user pinned to a single Digital Twin.

Lock users to one Digital Twin

Enable Prevent Switching to other Instances (Configuration and Integrations → Access & Membership; Studio UI: Keep people on this twin). Standard members of this Digital Twin can no longer switch: their other Digital Twins show as locked, and adding or joining Digital Twins is hidden. Admins can still switch.
This is a per-Digital-Twin setting. If a user belongs to two Digital Twins and only one has the lock enabled, the lock applies only when they are inside that Digital Twin.

​
What happens when someone signs up

1

Email verification

Someone who signs up with an email and password gets a one-time activation link; until they click it the account is unactivated and cannot sign in (every sign-in attempt sends a fresh link). Sign-ups through Google, Microsoft, Apple, single sign-on or an LMS launch are active at once, and so are accounts an admin creates.
2

Joining

They join the Digital Twin as described above — by self-service, through an invitation link (held as Pending until approved), or because the launch or single sign-on placed them there.
3

In the Digital Twin

They land in the conversation with any welcome credits the Digital Twin awards (see Credit Allocation). Someone who created a personal account sees a one-time welcome message first.

​
Email verification and activation

Email-and-password sign-ups need a verified email. The activation email is sent at sign-up and again at every sign-in attempt until the account is activated.
If the activation email is missing, check the person’s spam folder, then verify in Admin → Users that the email address on file is correct. To let them in without the link, set their Status to active.

​
Contact email auto-promotes to Admin

The Digital Twin editor carries a Contact Emails list. When a sign-in with one of those addresses first creates the person’s membership, they join as an Admin with full entitlements — treat that list as the keys to the twin. Through an LMS launch or single sign-on, a new contact address must first confirm with an emailed code.

Why this exists

It lets the platform bootstrap a brand-new Digital Twin: set the contact email to whoever should own it, hand them the link, and the first time they sign in they get the Admin permissions they need.

What it means in practice

Anyone who can sign in with one of those addresses becomes an Admin when they first join.
Update Contact Emails carefully. An unverified or shared address effectively grants Admin to whoever controls that mailbox.

​
LMS launches bypass joining policy

Users who arrive via an LMS launch — Canvas, D2L Brightspace, or any other LMS-supported tool — bypass the joining policy entirely.

Why

The LMS has already authenticated the user and asserted their identity. Re-asking them to sign up would break the launch flow and confuse students.

Implication

Even with Allow Joining: Disabled, an LMS launch from a configured course creates a membership and grants access. A launch is accepted only from a page whose address is in the Digital Twin’s Public Authorized URLs — restrict that list and the LMS configuration to limit which courses can launch.
LMS-launched people land directly in the Digital Twin as ordinary members (only the Contact Emails rule makes an admin), with no email-verification step.