You control membership
Circlus has no public people search. Members enter through invitations created by someone who is allowed to invite them.
A practical guide for the person who creates a Circle, invites members, controls access, and keeps the trusted space understandable and safe.
The owner controls membership and product-level rules. The server administrator controls infrastructure; these can be different people.
Circlus has no public people search. Members enter through invitations created by someone who is allowed to invite them.
Review active invitations, participant roles, devices, and public or guest entry points.
Another person may run updates and backups. Agree in advance who handles outages, domains, and migration.
A new Circle is normally created after its server is reachable over HTTPS. Joining an existing Circle is a different flow and usually starts from an invite link.
Use web.circlus.org or the installed Android app. The same identity can later be added to other trusted devices.
Enter its HTTPS address and short-lived server claim token. If the Circle already exists, use an invitation instead.
This profile and its keys authorize owner decisions. Protect the device and complete the recovery setup.
Choose a recognizable name and confirm the technical Circle address before inviting other people.
Add another trusted device or trusted participant and save the Recovery Package before expanding the Circle.
An invitation is the normal way to add a full member. Send it only to the intended person and revoke unused links.
Use it for family, colleagues, or friends who should participate in the full trusted space.
Prefer short validity and the minimum necessary number of uses. Create a fresh invite when needed.
If someone lost access, first inspect their old devices and identity state instead of blindly creating duplicate identities.
A guest link is for a person who should contact you or a team without seeing all members or joining the whole Circle.
Use separate links for support, clients, or public contact so each entry point has a clear purpose.
A guest enters the configured contact flow rather than receiving general Circle membership.
Revoke links that are no longer needed and avoid mixing public incoming contacts with a private family Circle.
Access belongs not only to a person but also to their approved devices. Device hygiene is part of Circle security.
Revoke the missing device and use the documented recovery or device-enrollment flow.
Remove or disable future access. Data already stored locally on their devices cannot be remotely erased.
Use the trusted enrollment flow and verify which identity and Circle the new device will receive.
Pause new invitations, inspect active devices and roles, and contact the server administrator if infrastructure may be involved.
The owner need not be a system administrator, but should understand the decisions that affect availability and long-term access.
Periodically inspect invitations, guest links, roles, and trusted devices.
Have another way to reach participants if the Circle, device, server, or domain becomes unavailable.
Agree who handles updates, backups, monitoring, domain renewal, and incident response.
If the Circle needs another server or domain, prepare the destination first and follow the Circle migration guide.