You control membership
Circlus has no public people search. Members enter through invitations created by someone who is allowed to invite them.
For the person who creates a Circle, invites people, and keeps track of who has access.
The owner decides who is in the Circle and under which rules. The server administrator is responsible for the server itself. These can be different people.
Circlus has no public people search. Members enter through invitations created by someone who is allowed to invite them.
From time to time, review active invitations, participant roles, their connections, and guest links.
Someone else may handle updates and backups. Agree in advance who does what when something fails.
The first Circle is created once the server is installed. If you are joining an existing Circle, you need an invitation instead.
Use web.circlus.org or the Android app. Later the same profile can be connected on other devices too.
Enter the server address and the one-time key from the installation guide.
This profile confirms the owner’s decisions. Protect the device it is stored on.
Choose a clear name and check the Circle address before inviting people.
Connect the profile on a second device and save the recovery package before inviting everyone else.
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 check whether their previous profile can be restored — otherwise the Circle gets a duplicate of them.
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.
Every approved app and browser of a participant has access to the Circle. That is why connections need watching too.
Revoke the lost connection. On a new device, the participant restores the profile from the recovery package or connects it from another of their devices.
Remove or disable future access. Data already stored locally in their apps or browsers cannot be remotely erased.
Add it through the app and check which profile and which Circle the new connection will receive.
Pause new invitations, inspect active connections 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 connections.
Have another way to reach participants if the Circle, device, server, or domain becomes unavailable.
Decide who is responsible for updates, backups, domain renewal, and what to do when something fails.
If the Circle needs another server or domain, prepare the destination first and follow the Circle migration guide.