Visitors who sign in
Your site can let visitors join it: a new site can from its start, and an older one may not be able to yet. A visitor picks a name, and from then on your site knows them: it can show them their own messages, let them answer in a chat, and keep what they wrote apart from what everybody else wrote. Your coding agent builds this into your site’s pages. You see the people on the dashboard and approve what they may do.
Who has joined
Section titled “Who has joined”Everybody who has joined is a row of the table People on the Database screen. Removing a person there bans them: they are signed out everywhere, and the next page they open shows them only what anybody may see. What they wrote stays, shown with its author missing, until you remove that too.
What you approve
Section titled “What you approve”What visitors may read, add, change and remove is written into your site’s tables, as rules. A merge that lets visitors do more than they could before waits for you on the Branches screen, whoever asked for it. The screen says each rule in a sentence, and puts first, marked Wide, a rule that lets more people at more rows. Below them it lists what else holds the merge for your click.
Your agent can change pages and components without you, unless the change lets visitors learn more. That waits for you too.
Your own address, and a domain you connect
Section titled “Your own address, and a domain you connect”A visitor stays signed in on the address they joined at. When you
connect a domain, your site moves to it, and the
people who joined at your vizitka.page address join again there. The
Domains screen says how many before you connect.
What visitors’ words are
Section titled “What visitors’ words are”What a visitor writes on your site, a message or a name, is stored with your site’s rows. You can read it on the Database screen, as you can read anything your site holds.