Sign-in and members

Say what members should get. frascati builds the sign-in, the pages for members and the tables behind them:

frascati also sets which tables are for members only and which entries each member sees again. Asking for it is a normal change and uses credits; signing in and the accounts use none.

1. 1

   They enter their email address, and frascati sends them a six digit code in your website's name.

2. 2

   They enter the code. It is valid for 10 minutes and allows 5 tries; after that they ask for a new one. The account is made when they enter their first code.

3. 3

   They stay signed in on that browser until they sign out, also on all their devices at once, or until they stay away for 30 days.

Asking for a code answers the same for every address, so nobody can find out through your website who has an account. One address gets at most 5 codes an hour and 10 a day, and a website sends at most 300 a day. Codes go out while your plan or trial runs.

There is no password, and no sign-in with Google or Apple.

Members-only content

The entries of a table you show to signed-in members only, like a training plan, minutes or news for members. frascati sends them from its server only to visitors who are signed in.

Their own entries

What they sent through a form while signed in, like their registrations, from a table that lets each member see their own. Never anyone else's. They see every column of their own entries, also one you add later, like a status, which you set on each entry in the Cloud tab.

Their bookings

Bookings of times and of places in classes and events that they made while signed in, and earlier ones with the same email address, which the code proved is theirs. Each has the usual link to view it and to cancel it under your rules.

What the website keeps for them

Small things kept in their account, like favorites or a plan: up to 50 records of 100 KB each.

Where your website offers it, members change their name, sign out and delete their account themselves.

Open Cloud, click a table and choose under Visible to:

Content on your website

Everyone, or Signed-in members only.

Entries from visitors

Only you, or You, and each member their own. Entries sent without signing in stay with you only.

A change works at once on your published website, without publishing again and without credits. The AI sets it as well when you ask for a members area.

People with an account

Everyone who signed in on your website, with email address, name, since when and when last seen.

Sign out

Ends a person's sign-in on every device. They can sign in again with a new code.

Delete

Deletes the account and what your website kept in it. The entries and bookings the person sent stay with you, without the link to the account.

Member

A column in each table of entries that shows which account sent an entry. Entries sent without signing in have none.

The sign-in works in the preview, and frascati sends a real code, so use your own address. You stay signed in until the preview reloads, which happens with every change. On a share link, signing in is only tried: no code is sent and nothing is saved.

Accounts you make while testing show under People with an account; delete them there.

frascati keeps the accounts on your behalf in a database in Frankfurt, Germany, under our Data Processing Agreement. Say on your privacy page which data that is, how long it is kept and how people delete their account, and check what frascati wrote there before you publish: you are responsible for your website's privacy page.

• No roles or member levels: everyone who is signed in sees the same members-only content, and there are no admins or editors among them.
• Anyone with an email address can create an account. There is no invitation list and no approval of new members, so keep confidential documents off the website.
• No sign-in with a password, Google or Apple.
• Visitors cannot upload files or photos on a website. A phone app can send a photo with an entry.
• No server code of your own: what runs on the server are frascati's tables, bookings, payments and AI.
• Members see their own entries but cannot change or delete them. Bookings they cancel through the usual link.
• A Stripe subscription is not tied to the sign-in: being signed in does not show that someone paid.
• Messages from contact forms are not linked to an account.
• Phone apps keep their customer accounts as before; members-only tables and own entries are for websites.